[pkg-wpa-devel] No WPA Association on boot with "working" configuration

Reinhard Tartler siretart at tauware.de
Sat Jun 3 09:41:00 UTC 2006


On Fri, Jun 02, 2006 at 02:35:53AM -0700, Krontab Krontab wrote:
 
> I'm going up against a lame issue with the new way of invoking
> wpa_supplicant via the ifupdown suite.  A couple of my laptops are
> experiencing the same issue.  wpa_supplicant will successfully
> auth/associate, and dhclient3 will obtain an IP when I manually issue
> an "ifup eth1" command.  "sudo /etc/init.d/networking restart" even
> brings it up nicely.  But for some reason... on system startup, it
> will not associate or pull an IP.  The if-pre-up.d script
> "wpasupplicant", which is really just a sym link to
> /etc/wpa_supplicant/ifupdown.sh, obviously works, because again...
> manual restart of the networking scripts and ifup commands bring up
> wpa and dhcp.
> 
> Upon boot, and first logon, iwconfig and ifconfig both show no
> association or dhcp lease.  The following shows that wpa_supplicant
> was invoked and is running.  (although I don't have debug output from
> the first connection attempt.  A subsequent "ifdown -a" and "ifup -a"
> kills and initiates the same process, but brings up the interface
> fine.

You are right, I'm seeing this problem on my ubuntu laptop as well.
Unfortunately, I think this doesn't happen for me all the time, but
quite often. I'm still investigating whats different at boot-time to
configuring them manually..

btw, Scott told me that ubuntu was going away from ifupdown for edgy,
the next release. Perhaps this issue is solved then that way. We'll see.

Gruesse,
	Reinhard
 



More information about the Pkg-wpa-devel mailing list