Thanks for the details so far. To diagnose the MAC‑based RADIUS authentication behaviour you’re seeing on the TSW202, please provide the following information that isn’t yet included:
RADIUS/The Server Side
RADIUS server software/version (e.g., FreeRADIUS build).
Expected format for MAC credentials (e.g., User‑Name only, MAC as password).
Server debug logs showing the Access‑Request received and server interpretation.
Switch 802.1X/RADIUS Config
Full 802.1X/MAC authentication settings per port (screenshots/text export).
Authentication order/mode, VLAN assignments, and any fallback.
This information will allow me to investigate further,
No fallback or secondary authentication configured
──────────────────────────────
The key difference observed is that the “Test user credentials” function sends both User-Name and User-Password, whereas live 802.1X authentication appears to send only User-Name.
I have analyzed the MAC-based 802.1X authentication issue on the TSW202 switch, where FreeRADIUS rejects requests with the log:
No Auth-Type found: rejecting the user via Post-Auth-Type = Reject
Root Cause:
The TSW202 switch sends only the MAC address as the User-Name in Access-Requests, without providing a password or EAP credential. FreeRADIUS requires an Auth-Type to be set to determine the authentication method. Without a credential, it defaults to rejecting the request.
Solution:
To resolve this, configure FreeRADIUS to treat the MAC address as a PAP password for authentication. This can be done by updating the users file:
Add the lines above to allow MAC addresses to authenticate.
Save the file and restart FreeRADIUS:
sudo systemctl restart freeradius
Test authentication using the MAC address as both username and password.
This configuration enables FreeRADIUS to accept MAC-only Access-Requests, resolving the “No Auth-Type” rejection while maintaining secure MAC-based authentication.
Please let me know if you need assistance applying this change or testing the setup.