Date: Mon, 29 Jul 2013 06:34:07 -0700 From: Adrian Chadd <adrian@freebsd.org> To: Lars Engels <lars.engels@0x20.net> Cc: =?ISO-8859-1?Q?Jean=2DS=E9bastien_P=E9dron?= <jean-sebastien.pedron@dumbbell.fr>, freebsd-current@freebsd.org, wireless@freebsd.org Subject: Re: 802.1X: dhclient started before the auth. process ends Message-ID: <CAJ-Vmo=yw-jL%2BT2QUfiOfx8oGZweNt%2BgWFBaVriVPtWsrVCEiA@mail.gmail.com> In-Reply-To: <20130729095946.GK59101@e-new.0x20.net> References: <51F26CEB.9010200@dumbbell.fr> <20130729095946.GK59101@e-new.0x20.net>
next in thread | previous in thread | raw e-mail | index | archive | help
I think you were lucky. dhclient shouldn't start running until wpa_supplicant has completed authentication. -adrian On 29 July 2013 02:59, Lars Engels <lars.engels@0x20.net> wrote: > On Fri, Jul 26, 2013 at 02:34:51PM +0200, Jean-S=E9bastien P=E9dron 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmo=yw-jL%2BT2QUfiOfx8oGZweNt%2BgWFBaVriVPtWsrVCEiA>