EAP653 is not able to give an IP if the VLAN is configured on a WLAN
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hi all,
I have this configuration:
- OC300 v1
- 2x EAP653 v1
- ER605 v2
- SG3428X v1.30
I'm trying to create 3 WLANs, each one with its own VLAN, created upfront.
I'm using the OC300 to configure all the network.
I have also wired PCs connected to the switch.
The problem is that when the WLAN has no VLAN set, it works correctly, but as soon as I assign a VLAN ID, the laptop gets dissociated from the AP and it gets no IP, while the IP shown in the Controller is still the old one on the default 'LAN' VLAN. I expected an IP of 192.168.10.x (the one of VLAN 2), while I'm seeing in Controller 192.68.0.x (the one of VLAN 1).
Everything is updated with the latest firmwares and I have also tried to beta firmware of EAP653, which solves a MLK bug.
I doubt it's a configuration error, since the PC on the same VLAN 2 connected by Ethernet works correctly, but I'm new to this Networking topic! :)
Any input is appreciated !
Thank you,
Fra
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hi all,
let me add one relevant point to the discussion, meanwhile I'm directly working with the TP-Link support.
The DHCP Server is the Router (ER605 V2) one, not the Switch one, when everything is connected through the Omada Controller.
Moving the EAP directly connected to the router doesn't solve the issue.
A partial solution is reserving the IP into the DHCP Server and also binding the IP to MAC and then reboot, but this doesn't work always.
Thank you,
Fra
- Copy Link
- Report Inappropriate Content
Hi all,
I discovered the issue by chance!
The problem is the Static Routing!!!
When I created the VLANs, the Controller created me a Static Routing, one for each VLAN, like:
192.168.10.0/24 --> 192.168.0.1
192.168.20.0/24 --> 192.168.0.1
192.168.30.0/24 --> 192.168.0.1
192.168.40.0/24 --> 192.168.0.1
This prevented the DHCP Server working properly when VLAN ID is assigned to a WLAN.
However, as far as I know, Static Routing are needed to make the routing part of the system working correctly, otherwise it doesn't know how to answer to packets.
So, it looks a bug to me, but I'm still in touch with TP-Link support for this.
I'll keep this thread updated.
Thank you,
Fra
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 3070
Replies: 33
Voters 0
No one has voted for it yet.