Hello Fabrice, By adding the fix_avaya function, the MAC authentication work ! I will continue testing to see if there is no side effect.
Otherwise, have you some advice with MAC authentication ? Thanks for your help, Adrian. De: "packetfence-users" <[email protected]> À: "packetfence-users" <[email protected]> Cc: "Fabrice Durand" <[email protected]> Envoyé: Mercredi 24 Avril 2019 14:56:01 Objet: Re: [PacketFence-users] No-EAP Authentication issue with Avaya switches Hello Adrian, you need to create the Calling-Station-Id attribute because it miss in the request. To do that add the following in the raddb/policy.d/packetfence file: fix_avaya { if (!&Calling-Station-Id) { if (&User-Name && (&User-Name =~ /^${policy.mac-addr-regexp}$/i)) { update { &request:Calling-Station-Id := "%{tolower:%{1}%{2}%{3}%{4}%{5}%{6}}" } } } } and in conf/radiusd/packetfence (Here [ https://github.com/inverse-inc/packetfence/blob/devel/conf/radiusd/packetfence.example#L15 | https://github.com/inverse-inc/packetfence/blob/devel/conf/radiusd/packetfence.example#L15 ] ), add fix_avaya Like that: .... # need to setup hints for the remote radius server authorize { fix_avaya # Add in PacketFence specific configuration update { .... Let me know if it works. Regards Fabrice
_______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
