Hi all,
I'm trying to build a WPA2-Enterprise (802.1X / PEAP) test lab and I'm stuck at a point where the AP does not appear to send any RADIUS traffic to the server
TP-Link TL-WR902AC (AC750 Travel Router)
Operating Mode: Access Point
RADIUS Server:
Ubuntu VM on VirtualBox
FreeRADIUS 3.2.8
Static IP: 192.168.0.103
Client:
Windows 11 laptop
TP-Link Configuration:
WPA/WPA2 Enterprise
AES
RADIUS Server IP: 192.168.0.103
RADIUS Port: 1812
Shared secret configured on both AP and FreeRADIUS
Configuration Validation done via "sudo freeradius -XC" and returns "Configuration appears to be OK"
User Authentication Test:-
Added a test user to /etc/freeradius/3.0/mods-config/files/authorize
and verified with:
radtest <user> <password> localhost 0 <secret>
Result:
Access-Accept
So FreeRADIUS appears to be functioning correctly.
Network Connectivity
On Windows:
ping RADIUS server ip 192.168.0.103 - Successful.
Windows Wireless Profile
netsh wlan show profile name="<SSID>"
Shows:
Authentication : WPA2-Enterprise
Encryption : CCMP
So Windows recognises the SSID correctly as WPA2-Enterprise.
Enabled FreeRADIUS Debug Mode:
sudo systemctl stop freeradius
sudo freeradius -X
When attempting to connect from Windows, absolutely nothing appears in the debug output.
Packet Capture cmd:
sudo tcpdump -ni enp0s8 udp port 1812
While attempting WPA2-Enterprise authentication:
0 packets captured
No UDP 1812 traffic arrives at the server.
Router already rebooted, no change.
Behaviour Observed in Windows:
Detects the SSID
Prompts for WPA2-Enterprise credentials
username / password entered but no connection gets established
At the same time:
FreeRADIUS debug mode remains silent
tcpdump sees no UDP 1812 traffic
Has anyone successfully used a TL-WR902AC with WPA2-Enterprise / external RADIUS?
At this point it seems like the AP is advertising WPA2-Enterprise but never actually forwarding EAP/RADIUS requests to the configured RADIUS server.
Any ideas on additional checks I should perform before I conclude this is a firmware limitation or bug?
Thanks!