I think you were lucky.

dhclient shouldn't start running until wpa_supplicant has completed


On 29 July 2013 02:59, Lars Engels <lars.eng...@0x20.net> wrote:
> On Fri, Jul 26, 2013 at 02:34:51PM +0200, Jean-Sébastien Pédron wrote:
>> Hi!
>> At $WORK, we use 802.1X to authenticate computers on the network.
>> Authenticated computers receive a lease in the 192.168.X.X/24 network.
>> Unauthenticated ones receive a lease in the 172.16.X.X/24 network.
>> Today, I upgraded one computer running 10-CURRENT to latest HEAD and it
>> seems that the interface is brought up to early now: dhclient is started
>> before wpa_supplicant finishes. This was working perfectly before the
>> upgrade.
>> I don't have logs of the working case, but here are the logs of the
>> non-working one:
>> http://pastebin.com/ZHcbHLQZ
>> Was I lucky with wpa_supplicant/dhclient timing? Or is there a real
>> issue here?
> CC'ed wireless@, that's probably the proper list for the issue.
freebsd-wireless@freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Reply via email to