Date: Sat, 21 Jun 2014 17:46:59 -0700 From: John-Mark Gurney <jmg@funkthat.com> To: Adrian Chadd <adrian@freebsd.org> Cc: Rui Paulo <rpaulo@freebsd.org>, "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org> Subject: Re: conflict between netif and pccard_ether... Message-ID: <20140622004659.GS31367@funkthat.com> In-Reply-To: <CAJ-Vmo=8QseV2bgQYJcWAt0oXYEDoD=fncb7p--_%2B=W7gGnZuQ@mail.gmail.com> References: <20140618231318.GH31367@funkthat.com> <201406190917.16458.jhb@freebsd.org> <20140621104031.GM31367@funkthat.com> <CAJ-Vmo=8QseV2bgQYJcWAt0oXYEDoD=fncb7p--_%2B=W7gGnZuQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Adrian Chadd wrote this message on Sat, Jun 21, 2014 at 07:36 -0700: > Why'd you remove these: > > -DCONFIG_GAS \ > -DPKCS12_FUNCS Hun? I didn't... I think your mail client is broken and ate the white space at the begining of the line... > On 21 June 2014 03:40, John-Mark Gurney <jmg@funkthat.com> wrote: > > John Baldwin wrote this message on Thu, Jun 19, 2014 at 09:17 -0400: > >> On Wednesday, June 18, 2014 7:13:18 pm John-Mark Gurney wrote: > >> > So, I recently was trying to figure out why wireless on my notebook > >> > wouldn't work.. I would boot up the machine w/o the wireless > >> > configured, uncomment the lines in rc.conf, and then run > >> > "service netif start"... > >> > > >> > Wireless would associate, but when disconnect... After some > >> > investigation, it turns out that two copies of wpa_supplicant are > >> > being launched... I believe one from netif, and another from > >> > pccard_ether launched by devd... > >> > > >> > The issue is that both netif and pccard_ether "claim" ownership of > >> > them. pccard_ether will ignore the ifconfig_ line if NOAUTO is > >> > specified. IMO, we need to make one or the other "own" configuring > >> > and launching the interface... > >> > > >> > There is also the issue that wpa_sup doesn't use proper locking on > >> > the pidfile and allows two copies to be launched... My thoughts > >> > is to convert it to pidfile to fix this issue the easiest... > >> > >> I think this is actually the best fix. dhclient handles this correctly for > >> this reason. > >> > >> > Comments? Suggestions? > >> > >> We had a thread a few months ago about this very topic and I committed changes > >> to the rc.d scripts that I then had to revert because it broke other use > >> cases. Having the redundant start be harmless is the simplest way to handle > >> this. > > > > Ok, I converted wpa_supplicant to use pidfile(3), and it successfully > > fixes the issue I had... I get the error that wpa_supplicant is already > > running... It looks like in my case, devd was beating out netif in > > launching wpa_sup... > > > > I've attached the patch... > > > > -- > > John-Mark Gurney Voice: +1 415 225 5579 > > > > "All that I will do, has been done, All that I have, has not." > > > > _______________________________________________ > > freebsd-arch@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-arch > > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-arch@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140622004659.GS31367>