Arch Linux

manmower

Member

From: Belgium

Registered: 2006-11-17

Posts: 100

Network fails to start on boot but connects anyway

I'm having this weird issue after changing the channel and SSID on my wireless router yesterday: "Starting Network" at boot time fails every time yet after logging in I am connected anyway. All I did was change the ssid in the relevant configuration files. I'm reluctant to change anything since I had it working in this exact way...

rc.conf

# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
HOSTNAME="xxxxxxxx"
#
# 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
#
# Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
#
lo="lo 127.0.0.1"
eth0="dhcp"
ath0="dhcp"
wlan_ath0="ath0 essid xxxxxxxx"
WLAN_INTERFACES=(ath0)
INTERFACES=(lo eth0 ath0)
#
# 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.1.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-profiles
#
NET_PROFILES=(Atheros)

Network profile:

DESCRIPTION="Atheros"

# Network Settings
INTERFACE=ath0
HOSTNAME=xxxxxxxxxxxx

# Interface Settings (use IFOPTS="dhcp" for DHCP)
IFOPTS="192.168.1.250 netmask 255.255.255.0 broadcast 192.168.0.255"
GATEWAY=192.168.1.1

# DNS Settings (optional)
#DOMAIN=localdomain
#DNS1=192.168.0.1
#DNS2=

# Wireless Settings (optional)
ESSID=xxxxxxx
#KEY=
IWOPTS="mode managed essid xxxxxxx"

#WIFI_INTERFACE=wifi0   # use this if you have a special wireless interface
                        # that is linked to the real $INTERFACE

#WIFI_WAIT=5            # seconds to wait for the wireless card to
                        # associate before bringing the interface up
USEWPA="yes"           # start wpa_supplicant with the profile
WPAOPTS="-D wext"             # use "" for normal operation or specify additional
                        # options (eg, "-D ipw")
                        # see /etc/wpa_supplicant.conf for configuration
#AUTOWPA="yes"          # automatically configure WPA
#PASSKEY=""             # wpa passkey/phrase. for use with AUTOWPA

wpa_supplicant.conf

# Only WPA-PSK is used. Any valid cipher combination is accepted.
network={
    ssid="xxxxxxx"
    proto=WPA
    key_mgmt=WPA-PSK
    pairwise=TKIP
    group=TKIP
    psk="xxxxxxxxxxxxx"
    priority=9
}

stonecrest

Member

From: Boulder

Registered: 2005-01-22

Posts: 1,190

Re: Network fails to start on boot but connects anyway

It's because you have both an eth0 and ath0 interface. If one of them fails, the network process as a whole is considered to fail.

(I filed a bug report about this many, many months ago, and it was decided that each interface should be displayed in the output, but it still hasn't been done.)

---

I am a gated community.

manmower

Member

From: Belgium

Registered: 2006-11-17

Posts: 100

Re: Network fails to start on boot but connects anyway

Thanks, I added a ! in front of eth0 and now everything works as it should again. I think it must have been doing this all along but I just never noticed.

Additionally, I figured out all the lines referring to the wireless interface can be removed from rc.conf when using profiles, so at least I learned something from the problem. 

Thanks again!