You are not logged in.
- Topics: Active | Unanswered
#1 2009-03-24 05:02:50
- cdom
- Member
- Registered: 2009-03-24
- Posts: 11
[Solved] Network problem (DHCP: error fetching interface information)
Hi I just finished installing (almost) successfully my new Arch linux OS.
I am having some problems setting up my network. I can access the internet by using manual commands. Both eth0 and wlan0 are usable.
When I boot I get the an error when the network daemon is loaded
Network:
dhcp: error fetching interface information: device not found
dhcp: error fetching interface information: device not found
here is my rc.conf:
#
# /etc/rc.conf - Main Configuration for Arch Linux
#
# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
LOCALE="en_US.utf8"
HARDWARECLOCK="UTC"
USEDIRECTISA="no"
TIMEZONE="America/Los_Angeles"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
#
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
#
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(iwl3945)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
#
HOSTNAME="betty"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
#
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#
eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
eth0="dchp"
wlan0="dchp"
INTERFACES=(wlan0 eth0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network.d
#
# This now requires the netcfg package
#
NETWORKS=(hawknet linksys ethernet)
# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(syslog-ng network net-profiles netfs crond hal alsa kdm)I am in the process of trying to get netcfg to work, when I try to start my profile I get:
[root@betty ~]# netcfg linksys
:: linksys up [done]but the internet does not work unless I use dhcpcd wlan0.
Here is a copy of my network profile in linksys
[root@betty ~]# cat /etc/network.d/linksys
CONNECTION="wireless"
DESCRIPTION="wireless access at Vivians house"
INTERFACE=wlan0
HOSTNAME=betty
# Interface Settings (use IP="dhcp" for DHCP)
#IP="static"
#IFOPTS="192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
#GATEWAY=192.168.0.1
# DHCP Example
IP="dhcp"
DHCP_TIMEOUT=10 # Default is 10.
#DHCP_OPTIONS="" # Extra arguments for dhcpcd
# DNS Settings (optional)
DOMAIN=localdomain
DNS1=192.168.0.1
# Standard Wireless Settings
ESSID=linksys
SECURITY=none # One of wep, wpa, wpa-config, none
KEY=""
# Scans to see if network is available before connecting (reccomended)
SCAN="YES"
# Time to wait to connect to a network. Default 15.
#TIMEOUT=10
# Pass *custom* options to iwconfig. Usually not needed (optional)
#IWOPTS="mode managed essid $ESSID channel 6 key restricted $KEY"
# Any extra arguments for wpa_supplicant
#WPA_OPTS=
# For SECURITY='wpa-config' only - filename of a wpa-supplicant config
#WPA_CONF=
# Commands to run at various stages of configuration
#PRE_UP=
#POST_UP=
#PRE_DOWN=
#POST_DOWN="some command"What is the deal here?
Last edited by cdom (2009-03-25 00:06:04)
Offline
#2 2009-03-24 05:33:38
- sand_man
- Member
- From: Australia
- Registered: 2008-06-10
- Posts: 2,164
Re: [Solved] Network problem (DHCP: error fetching interface information)
remove
eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"and keep
eth0="dhcp"
wlan0="dhcp"By the way. You have dchp. It's dhcp.
Last edited by sand_man (2009-03-24 05:34:05)
Offline
#3 2009-03-24 15:52:36
- cdom
- Member
- Registered: 2009-03-24
- Posts: 11
Re: [Solved] Network problem (DHCP: error fetching interface information)
Okay! Thanks that seemed to fix some of it. However, now when I boot up, the Network daemon waits and then says
wlan0 timedout
eth0 timedout
Then net-profiles starts and says
starting Linksys [done]
So netcfg thinks that it is working, but after I boot up I cannot access the internet via wireless, I can only run an ethernet cable and only by typing dhcpcd eth0, can I access the internet.
Last edited by cdom (2009-03-24 15:53:06)
Offline
#4 2009-03-24 16:26:18
- kgas
- Member
- From: Qatar
- Registered: 2008-11-08
- Posts: 718
Re: [Solved] Network problem (DHCP: error fetching interface information)
I thing you are trying to use two interfaces same time.try after commenting out
# eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
#eth0="dchp"
#wlan0="dchp"
#INTERFACES=(wlan0 eth0)
and !network in the DAEMONS array.
NETWORKS=(hawknet linksys ethernet)<----- Have you got profiles for hawknet and ethernet.If not bang them too.
Offline
#5 2009-03-24 18:46:39
- cdom
- Member
- Registered: 2009-03-24
- Posts: 11
Re: [Solved] Network problem (DHCP: error fetching interface information)
okay everything seems appears to load correctly but after I boot up and open firefox I cannot access the internet through wifi, but i can use an ethernet connection and type: dhcpcd eth0
Here is my rc.conf files, any ideas?
[root@betty ~]# cat /etc/rc.conf
#
# /etc/rc.conf - Main Configuration for Arch Linux
#
# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="en_US.utf8"
HARDWARECLOCK="UTC"
USEDIRECTISA="no"
TIMEZONE="America/Los_Angeles"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
#
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
#
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(iwl3945)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
#
HOSTNAME="betty"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
#
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
#eth0="dhcp"
#wlan0="dhcp"
#INTERFACES=(wlan0 eth0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network.d
#
# This now requires the netcfg package
#
NETWORKS=(hawknet linksys ethernet)
# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(syslog-ng hal !network net-profiles netfs crond alsa kdm laptop-mode)and my profile for linksys, hawknet is exactly the same except for the essid
[root@betty ~]# cat /etc/network.d/linksys
CONNECTION="wireless"
DESCRIPTION="wireless access at Vivians house"
INTERFACE=wlan0
HOSTNAME=betty
# Interface Settings (use IP="dhcp" for DHCP)
#IP="static"
#IFOPTS="192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
#GATEWAY=192.168.0.1
# DHCP Example
IP="dhcp"
DHCP_TIMEOUT=10 # Default is 10.
#DHCP_OPTIONS="" # Extra arguments for dhcpcd
# DNS Settings (optional)
DOMAIN=localdomain
DNS1=192.168.0.1
# Standard Wireless Settings
ESSID=linksys
SECURITY=none # One of wep, wpa, wpa-config, none
KEY=""
# Scans to see if network is available before connecting (reccomended)
SCAN="YES"
# Time to wait to connect to a network. Default 15.
#TIMEOUT=10
# Pass *custom* options to iwconfig. Usually not needed (optional)
#IWOPTS="mode managed essid $ESSID channel 6 key restricted $KEY"
# Any extra arguments for wpa_supplicant
#WPA_OPTS=
# For SECURITY='wpa-config' only - filename of a wpa-supplicant config
#WPA_CONF=
# Commands to run at various stages of configuration
#PRE_UP=
#POST_UP=
#PRE_DOWN=
#POST_DOWN="some command"When I type netcfg linksys I get:
[root@betty ~]# netcfg linksys
> linksys already connectedtyping iwconfig shows:
[root@betty ~]# iwconfig
lo no wireless extensions.
wmaster0 no wireless extensions.
wlan0 IEEE 802.11abg ESSID:"linksys"
Mode:Managed Frequency:2.437 GHz Access Point: 00:1A:70:E2:97:55
Bit Rate=1 Mb/s Tx-Power=15 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Encryption key:off
Power Management:off
Link Quality=99/100 Signal level:-22 dBm Noise level=-127 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
eth0 no wireless extensions.Any help would be welcome.
Offline
#6 2009-03-25 00:05:39
- cdom
- Member
- Registered: 2009-03-24
- Posts: 11
Re: [Solved] Network problem (DHCP: error fetching interface information)
Thanks for all the help I'm gonna move onto trying wcid instead of netcfg.
Offline