[Bug 53387] Re: Boot order problem
I have the same problem on Gutsy, also with an Atheros card (kernel module: ath_pci). I don't want to use NetWorkManager as it is a desktop computer shared by multiple users and I do not want to give them the wifi password. ifdown/ifup ath0 works so I will try to use blabj's workaround. -- Boot order problem https://bugs.launchpad.net/bugs/53387 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53387] Re: Boot order problem
This seems to be a duplicate of bug #53387. -- Boot order problem https://bugs.launchpad.net/bugs/53387 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53387] Re: Boot order problem
Sorry, this is bug 53387. This seems to be a duplicate of bug #50099. -- Boot order problem https://bugs.launchpad.net/bugs/53387 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53387] Re: Boot order problem
My solution (reached independently) has been to disable the udev rule entirely: sudo mv /etc/udev/rules.d/85-ifupdown.rules /etc/udev/rules.d/85-ifupdown.rules.bak I can confirm this solved the issue. -- Boot order problem https://bugs.launchpad.net/bugs/53387 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53387] Re: Boot order problem
This workaround solved the issue for me too, great clue! -- Boot order problem https://bugs.launchpad.net/bugs/53387 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53387] Re: Boot order problem
I can confirm this bug on a fresh install of Gutsy -- Boot order problem https://bugs.launchpad.net/bugs/53387 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53387] Re: Boot order problem
I have the same problem with gutsy. auto ath0 iface ath0 inet dhcp wpa-psk *** wpa-driver wext wpa-key-mgmt WPA-PSK wpa-proto WPA2 wpa-ssid *** /etc/init.d/networking restart works... but reboot.. wpa_supplicant and dhclient get launched but interface gets no IP. -- Boot order problem https://bugs.launchpad.net/bugs/53387 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53387] Re: Boot order problem
static IP also doesnt work. -- Boot order problem https://bugs.launchpad.net/bugs/53387 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53387] Re: Boot order problem
** Also affects: netbase (Ubuntu) Importance: Undecided Status: New -- Boot order problem https://bugs.launchpad.net/bugs/53387 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53387] Re: Boot order problem
I experience the same behaviour with gutsy (I had this problem in Feisty as well): 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 ? ** Attachment added: services.txt http://launchpadlibrarian.net/9475820/services.txt -- Boot order problem https://bugs.launchpad.net/bugs/53387 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53387] Re: Boot order problem
FYI, a workaround that I am using.. in /etc/rc.local I put the following: sudo ifdown eth1 sudo ifup eth1 (where eth1 is my wireless interface) -- Boot order problem https://bugs.launchpad.net/bugs/53387 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53387] Re: Boot order problem
Having same issue - ubuntu feisty - with the following
/etc/wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
network={
ssid=daintylink
scan_ssid=1
key_mgmt=NONE
wep_key0={wep key}
wep_tx_keyidx=0
priority=999
auth_alg=SHARED
}
network={
ssid=airplus
scan_ssid=1
key_mgmt=NONE
wep_key0={wep key}
wep_tx_keyidx=0
priority=998
auth_alg=SHARED
}
And the followng entry in /etc/network/interfaces:
auto eth1
iface eth1 inet dhcp
pre-up /sbin/wpa_supplicant -Bw -Dwext -ieth1 -c/etc/wpa_supplicant.conf
post-down /usr/bin/killall -q wpa_supplicant
Again - /etc/init.d/networking restart works... but reboot..
wpa_supplicant and dhclient get launched but interface does not come up!
-Bob
--
Boot order problem
https://bugs.launchpad.net/bugs/53387
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53387] Re: Boot order problem
I use wpasupplicant ver. 0.6.0-1 on Ubuntu Gutsy tribe 5, which is installed by default and configured through the gnome-network-admin interface. I changed the boot priority of /etc/init.d/networking to be one of the first or last init to be launched (because WPAsupplicant is launched through it). It gave no result at all. I inspected my dmesg output and found interesting outputs : // On normal boot Aug 23 22:54:46 zxz-laptop kernel: [ 18.092000] ieee80211_crypt: registered algorithm 'NULL' Aug 23 22:54:46 zxz-laptop kernel: [ 18.772000] ieee80211: 802.11 data/management/control stack, git-1.1.13 Aug 23 22:54:46 zxz-laptop kernel: [ 18.772000] ieee80211: Copyright (C) 2004-2005 Intel Corporation [EMAIL PROTECTED] Aug 23 22:54:46 zxz-laptop kernel: [ 18.84] usbcore: registered new interface driver hci_usb Aug 23 22:54:46 zxz-laptop kernel: [ 18.852000] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.0kmprq Aug 23 22:54:46 zxz-laptop kernel: [ 18.852000] ipw2200: Copyright(c) 2003-2006 Intel Corporation Aug 23 22:54:46 zxz-laptop kernel: [ 18.852000] ACPI: PCI Interrupt :03:03.0[A] - GSI 17 (level, low) - IRQ 18 Aug 23 22:54:46 zxz-laptop kernel: [ 18.852000] ipw2200: Detected Intel PRO/Wireless 2915ABG Network Connection Aug 23 22:54:46 zxz-laptop kernel: [ 19.196000] ipw2200: Detected geography ZZA (11 802.11bg channels, 13 802.11a channels) Aug 23 22:54:46 zxz-laptop kernel: [ 20.824000] ADDRCONF(NETDEV_UP): eth1: link is not ready //After I typed sudo /etc/init.d/networking restart Aug 23 23:01:50 zxz-laptop kernel: [ 469.14] ADDRCONF(NETDEV_UP): eth1: link is not ready Aug 23 23:01:50 zxz-laptop kernel: [ 469.776000] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready Aug 23 23:01:50 zxz-laptop kernel: [ 469.856000] ieee80211_crypt: registered algorithm 'CCMP' Aug 23 23:02:01 zxz-laptop kernel: [ 480.164000] eth1: no IPv6 routers present ieee80211 uses the registered algorithm 'NULL' while it boots, but uses CCMP after a sudo /etc/init.d/networking restart. It looks like the CCMP algorithm doesn't exist during boot but is ready to use after gdm is started. -- Boot order problem https://bugs.launchpad.net/bugs/53387 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53387] Re: Boot order problem
I'm moving this as confirmed. ** Changed in: wpasupplicant (Ubuntu) Status: Incomplete = Confirmed -- Boot order problem https://bugs.launchpad.net/bugs/53387 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53387] Re: Boot order problem
I have the following /etc/network/interfaces on my feisty system (installed from the Ubuntu Server CD, if this makes a difference): auto lo eth0 iface lo inet loopback iface eth0 inet dhcp wpa-ssid peanuts wpa-psk thepassword At boot-up, I do see Configuring network interfaces fly by, and it says OK, but while lo is set up correctly and eth0 is up, it doesn't get an IP address (I assume it didn't do the WPA2 stuff either). Running sudo /etc/init.d/networking restart get it working without a hitch. -- Boot order problem https://bugs.launchpad.net/bugs/53387 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53387] Re: Boot order problem
I have this problem too, still not resolved. I'm on Gutsy with all updates, using WPA through the network-manager with a static IP. I have no error message in dmesg about WPA but the network isn't active at reboot, I have to do a /etc/init.d/networking restart to make it works. My /etc/network/interfaces look like this : auto eth3 iface eth3 inet static address 192.168.1.100 netmask 255.255.255.0 gateway 192.168.1.1 wpa-psk ac22b218cf97263ef58887a86f9e32605bd638017a9c4dacd8d80e8f6bd07696 wpa-driver wext wpa-key-mgmt WPA-PSK wpa-proto WPA wpa-ssid strangebanality When doing a /etc/init.d/networking restart, I get this in dmesg but nothing more : [ 231.332000] ADDRCONF(NETDEV_UP): eth3: link is not ready [ 231.392000] ADDRCONF(NETDEV_CHANGE): eth3: link becomes ready [ 232.48] ieee80211_crypt: registered algorithm 'TKIP' Is it really a boot order problem? -- Boot order problem https://bugs.launchpad.net/bugs/53387 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53387] Re: Boot order problem
Thank you for your bug report. Do you still have this issue with the latest release of Ubuntu ? ** Changed in: wpasupplicant (Ubuntu) Importance: Undecided = High Status: Unconfirmed = Needs Info -- Boot order problem https://bugs.launchpad.net/bugs/53387 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53387] Re: Boot order problem
What worked for me (I have an atheros chipset, using madwifi) is a
/etc/wpa_supplicant.conf like this:
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=2
fast_reauth=1
network={
ssid=YOUR-SSID
proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP
group=TKIP
psk=(fill in this using wpa_passphrase)
}
And a wpa_supplicant start up script in /etc/init.d like this:
#!/bin/sh
# wifi wpa_supplicant init
echo * [Wifi] enabling wpa_supplicant...
if [ -x /sbin/wpa_supplicant ]; then
/sbin/wpa_supplicant -B -c/etc/wpa_supplicant.conf -iath0 -Dmadwifi -w
fi
You then have to:
sudo chmod +x /etc/init.d/wifi_wpa.sh (or whatever you called it)
sudo ln -s /etc/init.d/wifi_wpa.sh /etc/rcS.d/S40netwifiwpa
Yes, this should probably be automated.
--
Boot order problem
https://launchpad.net/bugs/53387
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
