Date: Tue, 05 Jul 2005 14:14:49 -0700 From: Sam Leffler <sam@errno.com> To: Brooks Davis <brooks@one-eyed-alien.net> Cc: Bakul Shah <bakul@BitBlocks.com>, freebsd-current@freebsd.org Subject: Re: minor WPA problem on a Thinkpad R40 Message-ID: <42CAF849.3020508@errno.com> In-Reply-To: <20050705195945.GA28034@odin.ac.hmc.edu> References: <200507012348.j61NmQEs070640@gate.bitblocks.com> <20050705195945.GA28034@odin.ac.hmc.edu>
index | next in thread | previous in thread | raw e-mail
Brooks Davis wrote: > On Fri, Jul 01, 2005 at 04:48:26PM -0700, Bakul Shah wrote: > >>After suspend/resume the old wpa_supplicant does not die >>and ath0 does not come up. Manually running >> /etc/rc.d/netif stop ath0 >>or >> /etc/rc.d/netif start ath0 >>does the right thing. I am running yesterday's kernel. >>rc.conf contains >> >> ifconfig_ath0="WPA DHCP" >> >>Not sure if I am doing something wrong or if this area still >>needs work. As I understand it, wpa_supplicant should die >>when an interface goes down just like dhclient should. > > > Hmm, this isn't something I've been able to test. One shot in the dark > would be adding -w to the wpa_supplicant command line in > /etc/rc.d/wpa_supplicant. I know wpa_supplicant deals badly with > yanking and reinserting a nic under normal circumstances so I'm not too > suprised it's having trouble with suspend/resume. > > >>Another curious behavior is that after a manual >> ifconfig ath0 down >>the interface does not stay down. > > > I suspect wpa_supplicant is bringing it back up. I'm not sure what the > answer is there. IMO wpa_supplicant should exit when the interface goes down/away but it does not. I sent mail to Jouni about this but he hasn't responded yet. I was going to check if there was a way to make it work this way. Not sure why it works this way except to avoid recalculating various crypto state or perhaps to avoid linux hotplug issues. Samhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42CAF849.3020508>