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
Oh, I'm sorry to hear that. If you need rest, pls take it! ;)
MBP is ok via Ethernet and it's on System network, since I use it to connect to the OC300 for management, but I was trying the WiFi on the macbook to connect to VLAN 2 Casa to check the connection :) .
I took my picture, but pls explain me what the numbers are! :)
Thank you,
Fra
- Copy Link
- Report Inappropriate Content
Ok, it seems there is a bug.
Here there is a long discussion on the topic:
https://www.reddit.com/r/HomeNetworking/comments/q25spb/tplink_omada_devices_connecting_to_vlans_not/
I hope TP Links identify this and fixes the problem.
I have moved my ER605 port connection to port4, so that this port is not a mixed WAN/LAN, but only LAN.
Also, I have enabled all the interfaces in all VLANs.
At least, I did the basics, now I don't know if the thing gets automatically solved once the lease ends up.
Thanks a lot for your time! :)
Fra
- Copy Link
- Report Inappropriate Content
The numbers are the switch port that device is connected to. I dont know anything about the switch you have mybee there is a bug in switch,
you have the lates beta on access point same as i use and this is working. so then is the switch, i dont know anything about your model.
so, if everything is updateted and stil not work mybe @Hank21 from tp-link have to look at it. from what i know is everything as it should and whay its not work is a mystery.
- Copy Link
- Report Inappropriate Content
nicolati wrote
Ok, it seems there is a bug.
Here there is a long discussion on the topic:
https://www.reddit.com/r/HomeNetworking/comments/q25spb/tplink_omada_devices_connecting_to_vlans_not/
I hope TP Links identify this and fixes the problem.
I have moved my ER605 port connection to port4, so that this port is not a mixed WAN/LAN, but only LAN.
Also, I have enabled all the interfaces in all VLANs.
At least, I did the basics, now I don't know if the thing gets automatically solved once the lease ends up.
Thanks a lot for your time! :)
Fra
lets hear what @Hank21 have to say about this tomorow...
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hi @nicolati,
I noticed there are different clients who obtained different IP subnets from the same SSID, but it can't rule out whether the different clients connected to the different EAPs.
Please check the BSSID on the client devices to confirm which specific SSIDs the clients are connecting.
- Copy Link
- Report Inappropriate Content
Hi Hank,
sorry, what is BSSID ?
This is the situation right now.
I have even restarted the Switch and Router. Few things changed by doing this, but nothing that solved completely the thing.
Online on Reddit other people mentions the same issue and is seems related to rules at DHCP server of the switch.
In my case the Switch is SG3428X v1.2 from the box, updated to v1.30 by the latest firmware.
One EAP653 is with the beta 1.0.90 and another with the official 1.0.9 firmware, but I don't think this is an issue. I wanted to try the beta firmware, since the problem seemed to be similar.
Thank you,
Fra
- Copy Link
- Report Inappropriate Content
I confirm the DHCP server has a bug, but from the controller I cannot say if the router DHCP or Switch DHCP or both are used...
I simply took an iPhone and my MacBook WiFi network and assigned them a static IP from the 192.168.10.x subnet and they work!
So, how can we proceed to further debug this?
P.S.: I'm used to debug with R&D at work every day, so no problem for this! :)
Thank you,
Fra
- Copy Link
- Report Inappropriate Content
Hi @nicolati,
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 TKID240145326, 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
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 3325
Replies: 33
Voters 0
No one has voted for it yet.