EAP653 is not able to give an IP if the VLAN is configured on a WLAN
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
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
if you are sure that the vlan is configured correctly, there is only one thing left to check,
check that vlan is enabled on the router interface that is connected to the switch or access point.
- Copy Link
- Report Inappropriate Content
Hi MR.S,
I have renamed the default VLAN (called initially LAN) to System and this is the configuration:
It's in italian, so let me know if I need to check language and do the screenshot again.
I think these are the ports of ER605, where only WAN and WAN/LAN1 are physically connected.
The Internet Gateway is in DMZ and connected to WAN port and the Omada Switch is connected to WAN/LAN1 port.
Thank you,
Fra
- Copy Link
- Report Inappropriate Content
ok, all ports on deafult is enabled by default, do you have a screnshoot of your vlan interface? (VLAN2)
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
This is problably your problem, enable this interface. you have problably somthing connected to this port and to get vlan on this port it have to be enabled
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hi MR.S,
I tried it now, but nothing changed ! :(
There you go was referred to the screenshot availability. Sorry for the confusion! :)
What I don't understand is why I don't get the IP if the VLAN is set on the Casa WLAN...
I should get an IP, no matter the other settings, right?
Thank you,
Fra
- Copy Link
- Report Inappropriate Content
show me a screenshot of your ssid settings.
ssid on vlan 1 do nothing with vlans settings, not enable vlan on this.
ssid with vlan2 enable vlan and type 2
- Copy Link
- Report Inappropriate Content
If VLAN is set to 2, it doesn't grab the IP.
If I don't set any VLAN, like in the picture, it gets the IP from the System default VLAN. I would say it's like it's set to VLAN 1.
Thank you,
Fra
- Copy Link
- Report Inappropriate Content
Strang, where is your access point connected?, somewhere on the way from router to access point the vlan is broken.
do you have anything other than omada switches?
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 3080
Replies: 33
Voters 0
No one has voted for it yet.