freeradius confuses switch
Christoph Egger
christoph_egger at gmx.de
Fri May 9 07:56:04 UTC 2025
Hello,
In tcpdump I see the radius packets in the following order:
switch -> freeradius: access-request (1), id: 0x2d
freeradius -> switch: access-reject (3), id: 0x2d
freeradius -> switch: access-accept (2), id: 0x2c
In the last packet the switch receives all proper vlan attributes.
In the tplink switch CLI I see it does *not* change the port state from unauthorized to authorized.
Upgrading the switch to latest firmware did not change anything.
I am not sure is the switch working correctly because of the access-reject package?
Regards,
Christoph
More information about the Freeradius-Users
mailing list