OMADA - Client doesn't get IP Adress
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.OMADA - Client doesn't get IP Adress
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
hi guys,
i recently enlarged my omada network. Originally I had some EAPs, a TL-SG2008P switch and an ER605 router. Due to lack of ports on the switch, I also used the LAN ports at the router. Yesterday I installed a TL-SG2218 to increase the number of LAN ports. Now i was able to move the clients, connected to the router, to the new switch. Two of these devices had a static IP addresses (IoT devices, no separate VLAN). Since I plugged them into the new switch, they don't get a valid IP address. Neither the static IP works nor a dynamic one. When i reconnect them directly to the router they come back online (with dynamic IP only). I tried a lot of different things, like rebooting (both switch an router), resetting the router, blocking and unblocking of the two devices, connecting to different ports at the switch and the router. But actually I reached my limits and have no idea how to solve this issue.
I have also noticed, that it takes a lot of time to get the controller updated (i use the OC200 hardware controller). The map view takes minutes to get actualized and also the client list shows the wrong port for several minutes.
I really would appreciate to get some hints or tips, how to solve this issue. Thanks.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hello @Pras71
Please try disabling the DST settings on your Controller and then reconfigure it for checking, or switching to another DST setting and switch it back. Let me know what you have tried and if that helps for your case. Thank you!
If it doesn't help, please provide the following information for checking,
1. Does the issue start to happen after you add the TL-SG2218 switch into the network?
2. Do you have any VLAN or Interface configured on your controller, and how did you configure it?
3. Could you please describe the network topology to show how your devices are connected?
- Copy Link
- Report Inappropriate Content
@Fae Thanks for your feedback.
DST means daylight saving time?
Actually this option is not enabled. I will enable it, try it once more and disabling it again.
- Copy Link
- Report Inappropriate Content
@Fae Enabling and disabling the DST setting didn't change anything.
To your questions:
1. Yes, the problems did occur, when I added the new switch (TL-SG2218)
2. I have configured the standard LAN as an interface:
Purpose : Interface
LAN Interfaces:
WAN/LAN1 ON
WAN/LAN2 ON
LAN1 ON
LAN2 ON
VLAN: 1
Gateway/Subnet: 192.168.0.1/24
DHCP Range: 192.168.0.1 - 192.168.0.254
DNS Server: Manual
1.1.1.1 8.8.8.8
Lease Time: 120 minutes
Default Gateway: Auto
Legal DHCP Servers: disabled
DHCP L2 Relay: disbaled
No Advanced DHCP Options or IPv6 configuration
3. Old Configuration
Router ER605 - WAN/LAN 1 IoT Device 1
- WAN/LAN 2 IoT Device 2
- LAN1 Down link to old Switch (TL-SG2008P)
- LAN2 IoT Device 3
Switch TL-SG2008P - OC200
- 3x EAPs
- Other devices
New Configuration
Router ER605 - WAN/LAN 1 not used
- WAN/LAN 2 not used
- LAN1 Down link to new Switch (TL-SG2218)
- LAN2 not used
Switch TL-SG2218 - Port 5 IoT Device 1 (not working)
- Port 7 Iot Device 2 (not working)
- Port 4 PC (working)
- Port 10 IoT Device 3 (working)
- Port 9 Down link to old switch (TL-SG2008P)
- Port 16 Up link to router (ER605 )
Switch TL-SG2008P - OC200
- 3x EAPs
- Other devices
And yes, all three Port 5, 7 and 10 have the LAN interface as profile.
- Copy Link
- Report Inappropriate Content
Hello @Pras71
So only one VLAN Interface (the default VLAN1) is configured in your network, right?
How is the Port Profile of Port 9 and 16 configured on the new SG2218 switch? Are they using default ''All" profile?
If you connect different devices to the same Port 5 separately, would any device obtain the IP address properly? How about if you connect the same device (like the working PC) to different ports for checking, would there be any difference?
Also, you mentioned that the two IoT devices had a static IP addresses, did you set the static IP on the controller? Could you please remove the static IP for a try? What's the current firmware version (the Build number) of your TL-SG2218?
- Copy Link
- Report Inappropriate Content
Hi @Fae ,
there are a lot of questions. I try to answer all of them.
I have also two VLANs (one for guests and one for children), which are also configured as an interface. The uplink and downlink ports of the new switch are of course configured with ALL. The two ports in question are only configured as LAN, so the two VLANs are not available there. Of course the former static IPs were within the range of LAN and not within one of the VLANs.
I also removed the static IP from both IoT devices. The standard configuration within the controller has always been DHCP active. I just wanted a few clients to get a static IP, such as my NAS, a smart home controller (one if the IoT devices in question) and an IP camera. Standard clients can just have a floating address.
Even if I put the ports from LAN to ALL it makes no difference. So I guess the problem is not related to any VLAN or port configuration
If I put the PC to port 5 or 7 it is working. The failure moves with the IoT devices (MAC address?). I assume it has something to do with the former static IPs. Is there any chance to delete them permanently? I guess there has to be some table, where there’s still some unwanted entry. Some decades ago I once had a problem with an ARP table, which had to be reset or modified manually (can't remember exactly). Is there a chance to get access to this and check it for false/unwanted data?
The TL-SG2218 should be up to date with FW version 1.1.7 Build 20221130 Rel.42340.
I hope I did cover all questions. Thanks for your effort.
- Copy Link
- Report Inappropriate Content
Hello @Pras71
The issue is odd as only the IoT devices are not getting the IP address from the port 5 or 7. If there is no special settings configured on port 5 or 7 on the SG2218, you may try to restart the SG2218 and the IoT devices to clear the data cache for checking.
For the static IPs, if you configured them on the OC200 before, you can delete them at Settings > Services > DHCP Reservation. Please also go to Settings > Network Security > IP-MAC Binding, check if you created IP-MAC binding for the IoT devices, if yes, pls delete them.
If you are familiar with CLI command, you can also try enable SSH to check the switch configuration via CLI.
- Copy Link
- Report Inappropriate Content
@Fae I checked the settings for DHCP Reservation as well as for IP-MAC Binding.
There weren't any IP-MAC Bindings, but of course some DHCP Reservations. I delted them all and made new ones. Didn't help
I also did a reset of both switches and the router (hard reset on device). Before that I connected the two IoT devices to the new switch.
Then I adopted the new siwtch first. (old switch and router still in state pending). Both IoT devices were found, one got an IP address from DHCP (no reservation) the other one didn't get an IP address (with reservation). I was also able to reach the device with my browser. So the connection really worked. When I adopted the old switch, nothing changed. When I adopted the router both IoT devices had no IP address.
That's really strange. I'm really close to completely erase the router and set it back to factory settings. Any other ideas?
- Copy Link
- Report Inappropriate Content
@Fae I just found this in the logs:
|
Router detected ARP conflict and dropped 1 packets. (Packet=192.168.0.1:54-AF-97-FE-E2-A1, Bind-Rule=192.168.0.1:14-EB-B6-E6-48-60)
|
Mar 06, 2023 17:17:14
|
|
|
Router detected ARP conflict and dropped 1 packets. (Packet=192.168.0.1:9C-A2-F4-BA-F7-03, Bind-Rule=192.168.0.1:14-EB-B6-E6-48-60)
|
Mar 06, 2023 17:17:08
|
When I archive these warnings, they reappear again with new timestamps.
Was my wild guess regarding ARP table somehow close?
It gets even more weird. Even if the client list on the controller doesn't show a valid IP address for the IoT device without DHCP reservation, I can still reach it with the original given IP address.
- Copy Link
- Report Inappropriate Content
I was able to get a SSH connection and open the ARP table of the router:
#show arp
---------------------------------------------------------------------------------------------------
Interface IP Address MACAdress Type AGE
---------------------------------------------------------------------------------------------------
vlan1 192.168.0.101 54-AF-97-0B-FA-0D Dynamic N/A
---------------------------------------------------------------------------------------------------
vlan1 192.168.0.22 4C-87-5D-B0-88-E1 Dynamic N/A
---------------------------------------------------------------------------------------------------
vlan1 192.168.0.20 28-87-BA-A2-87-36 Dynamic N/A
---------------------------------------------------------------------------------------------------
vlan1 192.168.0.107 54-AF-97-43-82-C2 Dynamic N/A
---------------------------------------------------------------------------------------------------
vlan1 192.168.0.114 A4-08-01-AF-53-D5 Dynamic N/A
---------------------------------------------------------------------------------------------------
vlan1 192.168.0.105 28-87-BA-7D-2E-5C Dynamic N/A
---------------------------------------------------------------------------------------------------
vlan1 192.168.0.112 B0-A7-B9-B5-76-02 Dynamic N/A
---------------------------------------------------------------------------------------------------
vlan1 192.168.0.111 B6-35-DA-AD-DC-04 Dynamic N/A
---------------------------------------------------------------------------------------------------
vlan1 192.168.0.118 00-5F-67-A9-BE-7D Dynamic N/A
---------------------------------------------------------------------------------------------------
vlan1 192.168.0.109 90-A8-22-38-12-E4 Dynamic N/A
---------------------------------------------------------------------------------------------------
vlan1 192.168.0.122 00-11-32-84-AB-B5 Dynamic N/A
---------------------------------------------------------------------------------------------------
vlan50 192.168.50.3 80-58-F8-61-27-0A Dynamic N/A
---------------------------------------------------------------------------------------------------
vlan1 192.168.0.124 00-1D-63-17-55-25 Dynamic N/A
---------------------------------------------------------------------------------------------------
vlan1 192.168.0.10 28-87-BA-EA-22-7F Dynamic N/A
---------------------------------------------------------------------------------------------------
vlan1 192.168.0.102 B8-74-24-05-D1-4A Dynamic N/A
---------------------------------------------------------------------------------------------------
vlan1 192.168.0.106 9C-A2-F4-BA-F7-03 Dynamic N/A
---------------------------------------------------------------------------------------------------
vlan1 192.168.0.104 7C-D5-66-C8-A9-10 Dynamic N/A
---------------------------------------------------------------------------------------------------
vlan1 192.168.0.115 BE-95-6D-BA-95-70 Dynamic N/A
---------------------------------------------------------------------------------------------------
vlan1 192.168.0.113 54-AF-97-FE-E2-A1 Dynamic N/A
---------------------------------------------------------------------------------------------------
vlan1 192.168.0.25 00-11-32-84-AB-B5 Dynamic N/A
---------------------------------------------------------------------------------------------------
vlan1 192.168.0.108 28-87-BA-37-DD-6E Dynamic N/A
---------------------------------------------------------------------------------------------------
vlan1 192.168.0.119 CC-98-8B-D5-0B-3D Dynamic N/A
---------------------------------------------------------------------------------------------------
vlan1 192.168.0.38 28-87-BA-EA-22-7F Dynamic N/A
---------------------------------------------------------------------------------------------------
vlan1 192.168.0.123 3C-7C-3F-C3-90-02 Dynamic N/A
---------------------------------------------------------------------------------------------------
vlan1 192.168.0.130 F8-0D-AC-BB-A8-C1 Dynamic N/A
---------------------------------------------------------------------------------------------------
vlan1 192.168.0.121 24-0B-B1-1B-1E-3A Dynamic N/A
---------------------------------------------------------------------------------------------------
vlan1 192.168.0.125 7C-2F-80-D7-C4-C2 Dynamic N/A
---------------------------------------------------------------------------------------------------
The message is still the same: Router detected ARP conflict and dropped 1 packets. (Packet=192.168.0.1:54-AF-97-FE-E2-A1, Bind-Rule=192.168.0.1:14-EB-B6-E6-48-60)
I can find 54-AF-97-FE-E2-A1 which is connected to IP 192.168.0.113. I can't find any client, which is using this IP address x.y.z.112 and x.y.z.114 are used, but not x.y.z.113.
14-EB-B6-E6-48-60 is not shown in the ARP table of the router. Something seems to be very wrong here. x.y.z.113 seems to be the switch TL-SG2008P. That's new.
Anyhow, since I did the reboot of all major devices, at least one of the two IoT devices is no working properly, which is IP address x.y.z.121.
The second one had the fixed IP address x.y.z.38, but is actually configured as DHCP without static IP, but still gets no valid IP.
- Copy Link
- Report Inappropriate Content
Hello @Pras71
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 TKID230312660, please check your email box and ensure the support email is well received. Thanks!
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 4535
Replies: 11
Voters 0
No one has voted for it yet.