update to the closed thread: Central Wireless RADIUS: Roaming Clients between APX320 and APX530 lose connection when on APX530 News from our support case 06845353 as reference in case other users may face such issues. Sophos WiFi Dev Team has successfully recreated the issue. When a client roams from AP1->AP2->AP1, we observe that the client traffic is not getting tagged properly with VLAN, which results in the client not getting the IP address. When Fast roaming is enabled, radius authentication will be skipped when the client roams. The client will receive the correct IP address after turning wifi on and off. This is because the client will go through the complete radius authentication where VLAN information will be captured through radius exchanges. Disabling the fast roaming is a possible workaround for this issue for now but it comes with the cost of roaming delay.

This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

update: Central Wireless RADIUS: Roaming Clients between APX320 and APX530 lose connection when on APX530

News from our support case 06845353 as reference in case other users may face such issues.

Sophos WiFi Dev Team has successfully recreated the issue.

When a client roams from AP1->AP2->AP1, we observe that the client traffic is not getting tagged properly with VLAN, which results in the client not getting the IP address.
When Fast roaming is enabled, radius authentication will be skipped when the client roams.
The client will receive the correct IP address after turning wifi on and off. This is because the client will go through the complete radius authentication where VLAN information will be captured through radius exchanges.
Disabling the fast roaming is a possible workaround for this issue for now but it comes with the cost of roaming delay.

This thread was automatically locked due to age.