hi
> I didn´t realize about the problem because I am using authentication with an
>ethernet card and a Switch as Authenticator.
>
> Indeed, MD5 disappers with XP SP1 in Wireless cards, but not in Ethernet ones.
it's bizar, even if i perfectly understand why md5 is not good enough.
md5 is de
34 Paris cedex 13http://www.infres.enst.fr ENST Paris - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Partial
thread listing:
Re: EAP-MD5.
Problems with XP Client, (continued)
Art
Hi Jorge
I'm sorry, i wanted to test out what you wrote about two weeks ago
because i finally found some time.
> First of all, c1 and c2 are two consecutive Hex numbers. I got them
> for the ID field in the EAP message.
> I have captured the traffic between the AP and the XP client and I
Hi Arthur, First of all, c1 and c2 are two consecutive Hex numbers. I got them for the ID field in the EAP message.I have captured the traffic between the AP and the XP client and I think (never 100% sure) that the NAS is working right because it has copied exactly the EAP packet from Radius
hi
> I am not sure, but I thing that is a problem with the EAP Id field in
> the EAP-Success frame. Here you have a resume of the conversation
> writing into parenthesis the eap id.
>
> NAS RADIUS
> --> RAD-Req/EAP-Resp(id=1) >
> <-- RAD-Chall/EAP-Req
Title: EAP-MD5. Problems with XP Client
Hi,
I am trying authenticate XP supplicants with freeradius, but I have found a problem I am not sure if is a bug (I don´t think so) or I am configuring something wrong.
When I authenticate a nuser using XP client , The Radius authentication is
