Ubuntu

Have to manually restart networking on every reboot

Reported by Eric Donkersloot on 2007-05-12
8
Affects Status Importance Assigned to Milestone
wpasupplicant (Ubuntu)
Undecided
Unassigned
Nominated for Gutsy by Joachim Noreiko

Bug Description

On boot, my wireless interface is not working. I have to manually restart networking to obtain an ip address.

Ubuntu Version: 7.04
Kernel: 2.6.20-15
Hardware: netgear wg111v2 (rtl8187 chipset, using ndiswrapper 1.38)

/etc/network/interfaces:

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid xxxxxx
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP TKIP
wpa-group CCMP TKIP
wpa-key-mgmt WPA-PSK
wpa-psk xxxxxxxxxxxxxxxxxxx
post-down killall -q wpa_supplicant

Workaround:

/etc/rc.local:

sh /etc/init.d/networking restart

Eric Donkersloot (ericd) on 2007-05-12
description: updated
description: updated

Confirmed. I have to restart my network too in Feisty (2.6.20-15-generic).
Hardware: Buffalo WLI-U2-KG54 (Ralink rt2570 chipset, using the windows driver with ndiswrapper 1.43)

/etc/network/interfaces
auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid xxxxxxxxxxxxxxxxxxxxxxxxx
wpa-ap-scan 1
wpa-proto RSN WPA
wpa-pairwise CCMP TKIP
wpa-group CCMP TKIP
wpa-key-mgmt WPA-PSK
wpa-psk xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Eric Donkersloot (ericd) on 2007-05-14
description: updated
Rubeosis (faspie) wrote :

Confirmed on Feisty (latest version, not upgraded)

- I am using ndiswrapper (Broadcom Chipset, bcm43xx native driver disabled)
- NetworkManager cannot establish a connection at all (that is maybe a different problem. I uninstalled it completely)
- a network configuration was established via /etc/network/interfaces and wpa_supplicant; ifdown/ifup commands were registered in rc.local (without any effect!)
- After Ubuntu has started up in many cases a connection to the access point has not been established; I need to set it up manually (first "ifdown eth1" in order to close an existing connection, then ifup eth1)
- After connection has been corrupted (i. e. standby mode) I have to retry disconnecting/connection several times (my wlan device eth1 is not displayed in the ifconfig printout anymore after a wakeup from standby). The DHCP client first seemed to be the problem (did not get an IP address), but even after static IP configuration the problem has NOT been solved. However, connection on bootup is started correctly with a static IP.
- the dmesg printout often contains the error message "eth1: no IPv6 routers present". I tried to disable the ipv6 module - no effect
- I think I could reduce the number of disconnecting/connection retrials needed to connect by setting the ap_scan variable in wpa_supplicant.conf to 2 (formerly 1) but I don't know

I don't know if my problem is really the same problem as described above, but perhaps I can help to solve that bug on Ubuntu. Please contact me if you need further information!

Regards,

Rubeosis

/etc/network/interfaces

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

# iface eth1 inet static
# address 192.168.2.99
# netmask 255.255.255.0
# gateway 192.168.2.1
# wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
# auto eth1

# auto eth2
# iface eth2 inet dhcp

# auto ath0
# iface ath0 inet dhcp

# auto wlan0
# iface wlan0 inet dhcp

/etc/wpa_supplicant/wpa_supplicant.conf

ap_scan=2

network={
        ssid="XXX"
        scan_ssid=1
        proto=WPA
        key_mgmt=WPA-PSK
        pairwise=TKIP
        psk="XXX"
}

Antonyp (antony-pleace) wrote :

I am also experiencing this behavior

Ubuntu Version: 7.04
Kernel: 2.6.20-16
Hardware: netgear wg111v2 (rtl8187 chipset, using rtl8187 driver)

Any clues on this one would be great, my first guest would be a timing issue but that is just huge speculation

* /etc/network/interfaces

auto lo
iface lo inet loopback

#auto eth0
allow-hotplug eth0

auto wlan0
iface wlan0 inet dhcp
    wpa-driver wext
    wpa-conf /etc/wpa_supplicant.conf

* /etc/wpa_supplicant.conf

ctrl_interface=/var/run/wpa_supplicant
#ctrl_interface_group=0
#eapol_version=1
# ap_scan=2 was the one for me you may try 0 or 1 instead of 2
#ap_scan=1
#fast_reauth=1

network={
    ssid="xxxxxxxxxxxxx"
#scan_ssid=1
    proto=WPA RSN
    key_mgmt=WPA-PSK
    pairwise=TKIP
#CCMP
    group=TKIP
    psk=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
}

I am sorry, meanwhile I have got a new notebook working with an Centrino
chipset. I cannot reproduce the problem anymore.

Am Mittwoch, den 05.09.2007, 10:29 +0000 schrieb Antonyp:
> I am also experiencing this behavior
>
> Ubuntu Version: 7.04
> Kernel: 2.6.20-16
> Hardware: netgear wg111v2 (rtl8187 chipset, using rtl8187 driver)
>
> Any clues on this one would be great, my first guest would be a timing
> issue but that is just huge speculation
>
> * /etc/network/interfaces
>
> auto lo
> iface lo inet loopback
>
> #auto eth0
> allow-hotplug eth0
>
> auto wlan0
> iface wlan0 inet dhcp
> wpa-driver wext
> wpa-conf /etc/wpa_supplicant.conf
>
>
> * /etc/wpa_supplicant.conf
>
> ctrl_interface=/var/run/wpa_supplicant
> #ctrl_interface_group=0
> #eapol_version=1
> # ap_scan=2 was the one for me you may try 0 or 1 instead of 2
> #ap_scan=1
> #fast_reauth=1
>
> network={
> ssid="xxxxxxxxxxxxx"
> #scan_ssid=1
> proto=WPA RSN
> key_mgmt=WPA-PSK
> pairwise=TKIP
> #CCMP
> group=TKIP
> psk=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> }
>

Alexander Sack (asac) wrote :

this isn't a network-manager problem because interfaces configured with options in /etc/network/interfaces are not managed by network-manager. For now assigning to wpasupplicant.

Reinhard Tartler (siretart) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #53387, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can add, or to see if there is a workaround for the bug. Feel free to continue to report any other bugs you may find.

Eric Donkersloot (ericd) wrote :

I have experience the same behaviour with gutsy:

Ubuntu Version: Ubuntu gutsy (development branch)
Kernel: 2.6.22-12-generic
Hardware: netgear wg111v2 (rtl8187 chipset, using ndiswrapper 1.45)

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid blahblahblah
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP TKIP
wpa-group CCMP TKIP
wpa-key-mgmt WPA-PSK
wpa-psk blahblahblah
post-down killall -q wpa_supplicant

See the attached services.txt as well; could this be caused by services starting in the wrong order ?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments