Roaming breaks VLAN assignment
I have two EAP653s configured to serve a WPA2 Enterprise / AES SSID with dynamic VLAN assignment via RADIUS. I have also enabled 802.11r for the network (see below)
I have no other Omada hardware in my network (switches are TL-SG108E and TL-SG108PE, gateway is OPNSense), but I configured the VLANs in the Omada controller as below. Setting the other networks as interfaces instead of VLANs changes nothing.
Things work until a client roams between access points, at which point it loses the VLAN assignment: connectivity breaks and the client gets an IP from the native (untagged) VLAN.
I am running the beta firmware v1_1.0.90 as recommended here because otherwise the APs keep freezing after minutes of being adopted and provisioned. Why is this happening?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @Ozymandias,
Thanks for reporting this issue to TP-Link community!
The support engineer has located the issue, and it will also be optimized in subsequent official versions of the Controller. Currently, you may disable the 802.11r and the dynamic VLAN will work properly.
- Copy Link
- Report Inappropriate Content
Hi @Ozymandias,
Thanks for reporting this issue to TP-Link community!
The support engineer has located the issue, and it will also be optimized in subsequent official versions of the Controller. Currently, you may disable the 802.11r and the dynamic VLAN will work properly.
- Copy Link
- Report Inappropriate Content
@Hank21 I actually returned the access points today - not touching Omada anything again.
No disrespect, but between the memory leak in the latest "stable" firmware and this VLAN issue, I don't know how TP-Link can consider these things production ready.
I'm going back to my OpenWRT flashed routers for my access points, which - while not perfect - have been far more reliable and cost less than 1/3 of the EAPs.
And they don't require a controller, to boot.
- Copy Link
- Report Inappropriate Content
I have the same issue - full stack Omada (APs, router, switch, HW controller).
I'm experiencing this with the built-in Radius server as well.
- Copy Link
- Report Inappropriate Content
Hi,
I also have the same issue. I only have one AP, but upon switch from one frequency band to another frequency band, some clients lose connectivity and get a native lan ip upon reconnecting. Not ideal on a security standpoint.
Controller : Software ver 5.13.30.8
Wifi AP : EAP653(EU) V1.0 Firmware 1.0.12 Build20240131 Rel. 45061
Wlan : 2.4GHz/5GHz, WPA3 enterprise with built-in radius, vlan determined on a client basis.
No 802.11r option activated
Am available to provide more data/screenshot as required.
- Copy Link
- Report Inappropriate Content
Thank you so much for taking the time to post the issue on TP-Link community!
To better assist you, I've created a support ticket via your registered email address, and escalated it to our support engineer to look into the issue. The ticket ID is TKID240338920, please check your email box and ensure the support email is well received. Thanks!
Once the issue is addressed or resolved, welcome to update this topic thread with your solution to help others who may encounter the same issue as you did.
Many thanks for your great cooperation and patience!
- Copy Link
- Report Inappropriate Content
@Hank21 Hi, has this issue already been fixed in a recent release?
- Copy Link
- Report Inappropriate Content
Hello, @Hank21!
I'm experiencing the same issue here: losing VLAN when performing fast roaming. Is there a definitive solution for this? Or is disabling 802.11r the only option?
If there isn't a solution yet, is there any forecast for it to be fixed in future releases?
3 cases in this moment here:
Losing VLAN when roaming happens:
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 1461
Replies: 7