On 30 Jul 2013, at 05:43, Jean-Sébastien Pédron
wrote:
> On 29.07.2013 21:56, Rui Paulo wrote:
>> Disable all the configuration settings and run wpa_supplicant -ddd
>>
>
> I'm not sure I understand what you mean by "disable all the
> configuration settings" but I did some more tests by running
On 29.07.2013 21:56, Rui Paulo wrote:
> Disable all the configuration settings and run wpa_supplicant -ddd
>
I'm not sure I understand what you mean by "disable all the
configuration settings" but I did some more tests by running
wpa_supplicant manually (ie. not using netif script) with the same
On 29 Jul 2013, at 07:00, Jean-Sébastien Pédron
wrote:
> On 29.07.2013 15:34, Adrian Chadd wrote:
>> I think you were lucky.
>
> I think you're right.
>
> It works perfectly on FreeBSD 9.1, because wpa_supplicant finishes the
> auth process really quickly, ie. before dhclient receives an answe
... wait, so the new version of wpa_supplicant takes 10 seconds to
even start doing anything?
Or are the rc scripts to blame?
-adrian
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe,
On Mon, Jul 29, 2013 at 04:00:44PM +0200, Jean-Sébastien Pédron wrote:
> On 29.07.2013 15:34, Adrian Chadd wrote:
> > I think you were lucky.
>
> I think you're right.
>
> It works perfectly on FreeBSD 9.1, because wpa_supplicant finishes the
> auth process really quickly, ie. before dhclient rec
On Mon, Jul 29, 2013 at 04:00:44PM +0200, Jean-Sébastien Pédron wrote:
> On 29.07.2013 15:34, Adrian Chadd wrote:
> > I think you were lucky.
>
> I think you're right.
>
> It works perfectly on FreeBSD 9.1, because wpa_supplicant finishes the
> auth process really quickly, ie. before dhclient rec
On 29.07.2013 15:34, Adrian Chadd wrote:
> I think you were lucky.
I think you're right.
It works perfectly on FreeBSD 9.1, because wpa_supplicant finishes the
auth process really quickly, ie. before dhclient receives an answer from
dhcpd from the unauthenticated network:
Jul 29 15:39:46 - kerne
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 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 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.
>
> Toda
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 in
10 matches
Mail list logo