Preethi Mohan [EMAIL PROTECTED] wrote:
I'm using a FreeRADIUS1.0.1 with hostap source
code+xsupplicant.When I use EAP/TLS authentication,after running for
24-26 hours , authentication fails.In hostap, I'm getting a RADIUS
packet with Access-Reject/no EAP-Message attribute.
Run
Hello,
I think Freeradius does not comply with RFC3579 with respect of the EAP
Start packet.
RFC 3579 says that an empty EAP-Message attribute signifies the
EAP-Start. To me this means the following attribute hex 0x4f 0x02
An evaluation copy of Steel Belted RADIUS takes 0x4f 0x02 as a valid
[EMAIL PROTECTED] wrote:
An evaluation copy of Steel Belted RADIUS takes 0x4f 0x02 as a valid EAP
start, on receipt it sends back a Access-Challenge with a EAP-Request
for Identity.
I updated the server yesterday to handle this situation. Please
grab the current CVS snapshot, and re-try it.
: EAP-Message attribute.
[EMAIL PROTECTED] wrote:
Question 1. RFC 3579 states that EAP-Start is indicated
by sending
an EAP-Message attribute with a length of 2 (no data). I interpret
this to be the following two bytes '0x49 0x02'.
Hmm... I think that's a typo, or, at least, it's
Hello all,
I have two EAP related questions when running radiusd: FreeRADIUS
Version 0.9.0 running in debug mode -X.
Question 1. RFC 3579 states that EAP-Start is indicated by sending an
EAP-Message attribute with a length of 2 (no data). I interpret this to
be the following two bytes '0x49
5 matches
Mail list logo