EAP653 is not able to give an IP if the VLAN is configured on a WLAN - FOLLOW-UP
Just wondering if there is any update on your thread regarding VLAN issues on your network?
Have TP-Link fixed this bug, and if so, which device was the problem?
Because your original thread is locked I can't post this to it, but I would very much like to know if this issue is resolved. I also have a TL-SG3428 at the heart of my network (along with other TP-LInk switches and various access points).
Incidentally I do find that every now and then I need to reboot the switches as they stop working properly. I wish they had a function to reboot on a schedule to clear whatever bug is causing this - possibly a slow memory leak or stack overflow?
Hi @SuperFocus
There was a solution on that forum.
When you create VLAN Interface on Omada controller, static routes will be generated automatically.
That is to say, you don't need to manually configure any extra static routing to make the VLANs accessible to each other.
Do you have the same configuration?
Hi @SuperFocus
There was a solution on that forum.
When you create VLAN Interface on Omada controller, static routes will be generated automatically.
That is to say, you don't need to manually configure any extra static routing to make the VLANs accessible to each other.
Do you have the same configuration?