I have a broken WiMax EAP thread (who would have thought eh?). The CPE is sending an EAP Code with a seemingly random value. Sometimes 80, 240 etc. Would the OpenSSL portion drop the packet or does it even care? David
David Peterson wrote:
I have a broken WiMax EAP thread (who would have thought eh?). The CPE is sending an EAP Code with a seemingly random value. Sometimes 80, 240 etc. Would the OpenSSL portion drop the packet or does it even care?
I have no idea what you mean by that. OpenSSL doesn't do EAP. And which "EAP code" are you talking about? Please be specific. Even without that... if it works with FreeRADIUS, then there's no issue. If it doesn't work, FreeRADIUS will produce an error message saying what went wrong. It's more useful to post the error message than to ask confusing questions about OpenSSL doing EAP. That way there's no chance for confusion. Alan DeKok.
Sorry for the confusion. We have identified a problem in the EAP-TTLS packet which had a non-standard code. This isn't a FR problem, more of a question as to how FR would handle a packet that had a bad EAP code in it. David -----Original Message----- From: freeradius-users-bounces+davidp=wirelessconnections.net@lists.freeradius.org [mailto:freeradius-users-bounces+davidp=wirelessconnections.net@lists.freera dius.org] On Behalf Of Alan DeKok Sent: Friday, November 15, 2013 2:38 PM To: FreeRadius users mailing list Subject: Re: EAP question David Peterson wrote:
I have a broken WiMax EAP thread (who would have thought eh?). The CPE is sending an EAP Code with a seemingly random value. Sometimes 80, 240 etc. Would the OpenSSL portion drop the packet or does it even care?
I have no idea what you mean by that. OpenSSL doesn't do EAP. And which "EAP code" are you talking about? Please be specific. Even without that... if it works with FreeRADIUS, then there's no issue. If it doesn't work, FreeRADIUS will produce an error message saying what went wrong. It's more useful to post the error message than to ask confusing questions about OpenSSL doing EAP. That way there's no chance for confusion. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
David Peterson wrote:
Sorry for the confusion. We have identified a problem in the EAP-TTLS packet which had a non-standard code. This isn't a FR problem, more of a question as to how FR would handle a packet that had a bad EAP code in it.
That question is about as content free as your previous question. My previous message said this: ... I have no idea what you mean by that. OpenSSL doesn't do EAP. And which "EAP code" are you talking about? Please be specific. ... If you're not going to answer my question, I can't answer yours. Alan DeKok.
participants (2)
-
Alan DeKok -
David Peterson