802.1x for wired networks

[Sam Leffler]

Guido van Rooij wrote:
> On Wed, Apr 09, 2008 at 09:58:31PM +0200, Guido van Rooij wrote:
>   
>> wpa_supplicant send a EAPOL start (version 1, type start)
>> procurve sends EAP failure (version 1, type: eap packet (code failure, id: 2)
>> procurve send EAP request identify (veersion 1, type: eap packet (code: request
>> type: identify).
>>
>> And that's it. wpa_supplicant does not respond. After a timeout, the
>> start eapol packet is sent again.
>>     
>
>
> After some research, it seems that wpa_supplicant is supposed to indeed
> react to the requests identity with a repsonse identity. It does not
> however. I verified that the multicast address as used by the switch
> is the correct one. On the other hand it seems that the request identity
> is not received..
> I tried debugging and it seems that indeed nothing is received (I asume
> that reception of packets is handled in eloop.c:eloop_run(),
> and I see no calling of eloop_sock_table_dispatch() there.
>
> Right now, I can't find thee place where a socket is created from which
> to read the multicast frames.
>   

I believe it's done w/ bpf and the important change for wired support 
was to accept mcast frames from the PAE mcast address.  Like I said to 
you privately; you might try this on releng7 where it was tested by someone.

    Sam