[Bug 53387] Re: Manual WPA networks doesn't connect at boot
Nothing in this bug report suggests a udev bug? ** Changed in: udev (Ubuntu) Status: New = Invalid -- Manual WPA networks doesn't connect at boot https://bugs.launchpad.net/bugs/53387 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53387] Re: Manual WPA networks doesn't connect at boot
--Scott James Remnant wrote: Nothing in this bug report suggests a udev bug? I agree, I'd say it's an ifupdown bug. ** Also affects: ifupdown (Ubuntu) Importance: Undecided Status: New -- Manual WPA networks doesn't connect at boot https://bugs.launchpad.net/bugs/53387 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53387] Re: Manual WPA networks doesn't connect at boot
*** This bug is a duplicate of bug 44194 *** https://bugs.launchpad.net/bugs/44194 This seems to be a duplicate of bug #44194. There Roman Yepishev posted a similar (but somewhat more elegant) workaround to what I posted here. ** This bug has been marked a duplicate of bug 44194 wpasupplicant doesn't start when the network start -- Manual WPA networks doesn't connect at boot https://bugs.launchpad.net/bugs/53387 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53387] Re: Manual WPA networks doesn't connect at boot
I can confirm this bug on a fresh install of Ubuntu 8.04 beta Please fix this bug for the peoples who don't use NetworkManager -- Manual WPA networks doesn't connect at boot https://bugs.launchpad.net/bugs/53387 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53387] Re: Manual WPA networks doesn't connect at boot
OK, I should have looked more closely at the init scripts before. It turns out that lo is brought up by S08loopback in /etc/rcS.d before udev is started. So testing whether lo is up doesn't do much good. I have come up with a temporary workaround though. I modified /etc/init.d/networking to touch a file (/var/run/network/started) when networking is started (or restarted), and remove it when networking is stopped. I also changed my udev ifup script to test for this file to determine whether to bring up the interface. It's a horrible hack, and I hope someone can come up with a better solution soon, but for now it works at least. ** Attachment added: patch for /etc/udev/ifup.sh http://launchpadlibrarian.net/12737809/ifup.sh.patch -- Manual WPA networks doesn't connect at boot https://bugs.launchpad.net/bugs/53387 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53387] Re: Manual WPA networks doesn't connect at boot
** Attachment added: patch /etc/init.d/networking to create /var/run/network/started when networking is started http://launchpadlibrarian.net/12737818/networking.patch -- Manual WPA networks doesn't connect at boot https://bugs.launchpad.net/bugs/53387 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53387] Re: Manual WPA networks doesn't connect at boot
My apologies, I am officially an idiot. The ifup script I uploaded was severely broken, which means using it is more or less equivalent to having the udev rule disabled (that's what happens when I try to code before sunset). I've fixed the error in the script, but it seems it doesn't work -- the original problem has returned. I don't really understand it. The only explanations I can come up with is that either there's some other stupid mistake in my script, that I'm just not seeing; or lo is actually brought up somewhere before /etc/init.d/networking starts; or it is possible to ping localhost over lo even when lo hasn't been brought up yet. For what it's worth, I'm attaching the patch to fix my ifup script anyway. ** Attachment added: ifup.sh.patch http://launchpadlibrarian.net/12723596/ifup.sh.patch -- Manual WPA networks doesn't connect at boot https://bugs.launchpad.net/bugs/53387 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53387] Re: Manual WPA networks doesn't connect at boot
I confirm that the heindsight solution works for my laptop. -- Manual WPA networks doesn't connect at boot https://bugs.launchpad.net/bugs/53387 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53387] Re: Manual WPA networks doesn't connect at boot
** Changed in: udev (Ubuntu) Importance: Undecided = High -- Manual WPA networks doesn't connect at boot https://bugs.launchpad.net/bugs/53387 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53387] Re: Manual WPA networks doesn't connect at boot
here's my patch for /etc/udev/rules.d/85-ifupdown.sh ** Attachment added: 85-ifupdown.rules.patch http://launchpadlibrarian.net/12689312/85-ifupdown.rules.patch -- Manual WPA networks doesn't connect at boot https://bugs.launchpad.net/bugs/53387 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53387] Re: Manual WPA networks doesn't connect at boot
I have implemented something like what I suggested in my previous comment and it seems to work. I haven't been able to test it as completely as I'd like, but my wireless network is starting correctly at boot now with the 85-ifupdown udev rule enabled. I wrote a script that tests whether the loopback interface is up before bringing an interface up. The idea being that if lo is not up yet when a network device is added, then presumably the system is booting and /etc/init.d/networking has not been started yet (and when it is started, it will bring up the interface). If lo is up, on the other hand, then /etc/init.d/networking has been started already and so the new interface should be brought up by the udev rule. I'm attaching the script with this comment, save it as /etc/udev/ifup.sh (and make it executable, obviously) and then apply the patch to 85-ifupdown.rules (which I'll also upload here). ** Attachment added: ifup.sh http://launchpadlibrarian.net/12689304/ifup.sh -- Manual WPA networks doesn't connect at boot https://bugs.launchpad.net/bugs/53387 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53387] Re: Manual WPA networks doesn't connect at boot
I have been having the same problem. When I boot up, my eth1 is brought
up, but wpa_supplicant is not started, so I have to manually bring eth1
down and up again to get my wireless networking working. Disabling the
ifupdown udev rule has fixed the problem, so I'm fairly certain that
this bug is caused by udev bringing up the interface too early, so that
wpa_supplicant fails to start. I thought perhaps the problem might be
that / is still mounted read-only when udev brings up the interface?
Perhaps a fix would be to somehow modify the udev rule so that it does
not trigger at boot time? I don't know if there's a way to do this, but
surely the intention of this rule is to do hotplugging of network
devices after bootup, rather than bringing up interfaces at boot (that's
what /etc/init.d/networking is for). So perhaps instead of bringing up
the interface, the udev rule should call a script that tests whether the
system is booted up already and then brings up the interface.
Here's my interfaces file:
auto lo eth1
iface lo inet loopback
iface eth0 inet dhcp
iface eth1 inet manual
wpa_roam /etc/wpa_supplicant.conf
iface solis-air inet dhcp
iface huisnet inet static
address 192.168.0.2
netmask 255.255.255.0
broadcast 192.168.0.255
iface default inet dhcp
And my wpa_supplicant.conf:
# allow config file overwrite
update_config=1
# path to UNIX socket control interface
ctrl_interface=/var/run/wpa_supplicant
# scanning mode
ap_scan=2
# auth timeout
dot11RSNAConfigSATimeout=90
# Ad-Hoc home network
network={
priority=2
id_str=huisnet
scan_ssid=1
ssid=Hein
mode=1
key_mgmt=NONE
auth_alg=SHARED
group=WEP104
wep_key0=key
wep_tx_keyidx=0
}
# SOLIS_AIR
network={
priority=2
id_str=solis-air
ssid=SOLIS-AIR
scan_ssid=1
key_mgmt=IEEE8021X
eap=TTLS
phase2=auth=PAP
identity=username
password=password
}
# other (open)
network={
key_mgmt=NONE
}
--
Manual WPA networks doesn't connect at boot
https://bugs.launchpad.net/bugs/53387
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53387] Re: Manual WPA networks doesn't connect at boot
DISTRIB_ID=Ubuntu DISTRIB_RELEASE=8.04 DISTRIB_CODENAME=hardy DISTRIB_DESCRIPTION=Ubuntu hardy (development branch) I replaced the following line in /etc/modprobe.d/ndiswrapper: alias usb:v0846p6A00d*dc*dsc*dp*ic*isc*ip* ndiswrapper with alias wlan0 ndiswrapper When I changed that line, my wireless adapter (Netgear wg111v2) received an ip address from the router. Before that, it would sometimes receive one but most of the time dhclient would time out. Seems like wpa_supplicant has trouble connecting properly when the interface was not created by it ? Would that be a correct conclusion ? -- Manual WPA networks doesn't connect at boot https://bugs.launchpad.net/bugs/53387 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53387] Re: Manual WPA networks doesn't connect at boot
did someone check what what consequences removing /etc/udev/rules.d/85-ifupdown.rules has? The bug commenters have made it pretty clear that the cause is that udev brings up the network interfaces too early. I still suspect that wpasupplicant fails because some kernel crypto modules have not been loaded yet. ** Also affects: udev (Ubuntu) Importance: Undecided Status: New -- Manual WPA networks doesn't connect at boot 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: Manual WPA networks doesn't connect at boot
I also have this problem on a fresh install of Gutsy. I am using ndiswrapper with a RaLink RT61 based card. I have used a module alias to ensure that ndiswrapper gets loaded for the card. The interface does attempt to come up at boot. ip a shows that an IP address has been assigned, but it shows no-carrier and wpa_cli shows disconnected. wpa_supplicant does appear to be running at this point. An ifdown and ifup of the interface fixes the problem. In fact, I have placed an ifdown and ifup into /etc/rc.local to work around the problem. I don't believe that the udev rule is the cause of the problem, but rather, the point during boot at which it is called. If I ifdown the interface, rmmod ndiswrapper and modprobe ndiswrapper, it comes up just fine automatically. This demonstrates that the udev rule is working correctly. This leads me to believe that wpa_supplicant has some problem running early in the boot sequence. Is it perhaps trying to write to somewhere on the root partition, which is still mounted read-only at this point? I have had a brief look through the scripts and can't see why it might be doing this, but thought I'd throw it out there nevertheless. -- Manual WPA networks doesn't connect at boot 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: Manual WPA networks doesn't connect at boot
Confirming that the same the disabling of the udev rule worked on my fresh install of Gutsy (7.10) -- Manual WPA networks doesn't connect at boot 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: Manual WPA networks doesn't connect at boot
This bug was nominated for Gutsy but does currently not qualify for a 7.10 stable release update (SRU) and the nomination is therefore declined. According the the SRU policy, the fix should already be deployed and tested in the current development version before an update to the stable releases will be considered. With 7.10 now released, that policy applies to this bug. See: https://wiki.ubuntu.com/StableReleaseUpdates . The bug is not being closed as work will continue on fixing it for the next release, Hardy Heron (8.04). If the state of this bug should change such that it qualifies for the SRU process, please contact the person who originally declined it and ask them to re-evaluate it. To help improve the state of this bug see: https://wiki.ubuntu.com/Bugs/HowToTriage . -- Manual WPA networks doesn't connect at boot 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: Manual WPA networks doesn't connect at boot
** Changed in: wpasupplicant (Ubuntu) Status: Confirmed = Triaged ** Description changed: When configuring a wireless network to use WPA outside Gnome Network- manager applet, the network will not reconnect after a reboot without a /etc/init.d/networking restart I moved over to nw-manager for the time being. I set up /etc/network/interfaces with this type of configuration for ath0 iface ath0 auto iface ath0 inet dhcp wpa-driver madwifi wpa-ssid homezone wpa-key-mgmt WPA-PSK wpa-psk quoted passphrase # wpa-psk 0001231203 - I didn't have time to try out the wpa-conf method but I did try wpa-psk - in passphrase and hexidecimal mode with identical results. - - The only thing I can think of is trying to use pre-up commands to start - wpasupplicant before it does dhcp. - - **Workaround : It has been found that renaming the file - /etc/udev/rules.d/85-ifupdown.rules so that udev won't read the rules - from that file actually solves the problem. + Renaming the file /etc/udev/rules.d/85-ifupdown.rules so that udev won't + read the rules from that file actually solves the problem. It looks like + udev starts the network in a way that prevent WPA drivers to load + correctly. -- Manual WPA networks doesn't connect at boot 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: Manual WPA networks doesn't connect at boot
** Summary changed: - Boot order problem + Manual WPA networks doesn't connect at boot ** Description changed: - Everything seems to work correctly when I set up the network but when I - reboot and log into gdm, my networking will not work until I run - '/etc/init.d/networking restart'. + When configuring a wireless network to use WPA outside Gnome Network- + manager applet, the network will not reconnect after a reboot without a + /etc/init.d/networking restart I moved over to nw-manager for the time being. I set up /etc/network/interfaces with this type of configuration for ath0 iface ath0 auto iface ath0 inet dhcp wpa-driver madwifi wpa-ssid homezone wpa-key-mgmt WPA-PSK wpa-psk quoted passphrase # wpa-psk 0001231203 I didn't have time to try out the wpa-conf method but I did try wpa-psk in passphrase and hexidecimal mode with identical results. The only thing I can think of is trying to use pre-up commands to start wpasupplicant before it does dhcp. + + **Workaround : It has been found that renaming the file + /etc/udev/rules.d/85-ifupdown.rules so that udev won't read the rules + from that file actually solves the problem. -- Manual WPA networks doesn't connect at boot 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
