[RADIATOR] EAP method registry - Support?

Heikki Vatiainen hvn at open.com.au
Mon Mar 18 06:02:18 UTC 2024


On 18.3.2024 4.46, Stefan Paetow via radiator wrote:

> Just FYI – I noticed that as part of some code to identify broken EAP 
> packets, the RADIATOR $Radius::EAP::eap_type_to_everyname{} lookup 
> returns nothing when it comes to EAP method 55 (TEAP). I call it like 
> this:
>
> my $eap_type = ($Radius::EAP::eap_type_to_everyname{$type} || 'Unknown');
>
> So with TEAP, I see 'Unknown'. Should that be 'Unsupported' instead, 
> or should the function return 'TEAP'?
>

You're right, 'Unsupported' would be better. Or maybe even 'Unsupported 
(55)', in case of TEAP, to give a hint what the EAP type was.

> See the IANA registry for the EAP methods here:
>
> https://www.iana.org/assignments/eap-numbers/eap-numbers.xhtml#eap-numbers-4
>
> The reason I ask is because I picked this up from the Hotspot 2.0 NAI 
> information in the Aruba UI in ArubaCentral…
>
> Thoughts? :-)
>
We'll need to add TEAP and EAP-NOOB to the list of known types. There's 
no reason they are not included.

Thanks for letting us know about this.

-- 

Heikki

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.open.com.au/pipermail/radiator/attachments/20240318/2bc9f08d/attachment.html>


More information about the radiator mailing list