hi
> The log follows. > Also the ethreal text file, from the windows authentication. > (i included only the radius protocol to shorten the text) oh, could you please record both the windows AND the freeradius cases with ethereal (there is an ethereal version for linux too) including only radius conversation between the NAS and the server, attach it and send it to me personally? the problem is that the log which you send clearly represents the case which has already been explained (there is an access challenge coming from the AP) but the ethereal log doesn't correspond to that case, it rather represents a successful exchange, IMHO. please provide both ethereal logs as ethereal-files (you can save the recorded packets into a file), i can load them into ethereal and see the packets in right sequence, detail degree etc. > rad_recv: Access-Challenge packet from host 192.168.1.100:1024, id=125, > length=90 > Reply packet code 11 sent to a non-proxy reply port from client > intel-AP:1024 - ID 125 : IGNORED the whole is repeated some times since the AP resends his request without response... > Frame 3 (193 on wire, 193 captured) > Radius Protocol > Code: Access Request (1) > Frame 6 (118 on wire, 118 captured) > Radius Protocol > Code: Access challenge (11) > Frame 7 (271 on wire, 271 captured) > Radius Protocol > Code: Access Request (1) > Frame 8 (1514 on wire, 1514 captured) > Radius Protocol > Code: Access challenge (11) in contrary, this basically looks like a right sequence for me, i just wonder what happened to frames 4 and 5 :) so, just record the both auths (win and freeradius) and send them to me without corrections (except if you have sensitive data etc. to protect) ciao artur -- Artur Hecker Groupe Accès et Mobilité hecker[at]enst[dot]fr Département Informatique et Réseaux +33 1 45 81 7507 46, rue Barrault 75634 Paris cedex 13 http://www.infres.enst.fr ENST Paris - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
