ER605 DHCP Client List Missing Clients

Hi,
I have a problem with DHCP server on this router. On DHCP client list some clients always missing. I've tried to connect only one laptop directly to ER605 LAN port (4), refresh list and there are no clients on the list. The list is empty, and there are no clients after 3, 10, 60 minutes, tomorrow or ever. So, I've tried to connect another client to LAN port (5) and refreshed every couple of hours, the list is still empty. Both clients have local IP addresses (192.168.0.10 and .11), have internet access and all Ethernet functionality. But still, they don't show up on the list.
Then, I tried to connect more clients through switch (TL-SG1016D), about 10 clients and some of them appeared on the list. After rebooting many times when specific clients appeared, I made IP reservation for them and noticed something. When a specific client appears on the list it have an address from the reservation list, but when the client does not appear on the list, it has next available address, not the one from the reservation list.
The first thing I did was firmware upgrade to the latest available. Tried factory reset and reconfiguring too but problem still persists. Without this basic functionality, DHCP clients list and address reservation, this mighty tool (ER605) is useless brick, so I wonder what I can do to make it work properly.
Best regards
Vladimir
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
If you are using the Omada Controller you need to go into your LAN interface settings (Site view > Settings > Wired & Wireless Networks > LAN > Your LAN network) check the 'Enable' box and save the settings.
If you are using it in standalone mode I can't help you sorry since I never used mine in standalone.
- Copy Link
- Report Inappropriate Content
@Clive_A
I contacted TP-Link support and quickly got a solution. On the SG1016D switch, "port isolation" was turned on. After turning it off and rebooting, everything started to work fine. Thank you very much for your time and patience!
- Copy Link
- Report Inappropriate Content
try upgrading to the latest firmware.
then enable ARP Detection on LAN interface
- Copy Link
- Report Inappropriate Content
MR.S wrote
try upgrading to the latest firmware.
Done
then enable ARP Detection on LAN interface
Please, can you help me how to do this?
- Copy Link
- Report Inappropriate Content
If you are using the Omada Controller you need to go into your LAN interface settings (Site view > Settings > Wired & Wireless Networks > LAN > Your LAN network) check the 'Enable' box and save the settings.
If you are using it in standalone mode I can't help you sorry since I never used mine in standalone.
- Copy Link
- Report Inappropriate Content
Yes, I'm using it as a standalone. I found the option "Enable ARP Spoofing Defense" under the "Firewall" section. Option was enabled and disabling it did not make any changes. I read instructions from this link configuring_firewall. I set up the firewall according to the instructions, and did bind IPs with MACs but did not make any changes. Still can't see all clients on DHCP client list.
After that, I turned on the other switch. Clients connected to the first switch cannot see or ping clients on second and vice versa. All clients have internet access. Googling that problem I find out that there are two possible reasons for this phenomenon. Using Virtual LAN or bad routing. Since I'm not using VLAN and all the options related to it are turned off it looks like my router is having a lot of trouble doing the routing.
- Copy Link
- Report Inappropriate Content

pkks297 wrote
Yes, I'm using it as a standalone. I found the option "Enable ARP Spoofing Defense" under the "Firewall" section. Option was enabled and disabling it did not make any changes. I read instructions from this link configuring_firewall. I set up the firewall according to the instructions, and did bind IPs with MACs but did not make any changes. Still can't see all clients on DHCP client list.
After that, I turned on the other switch. Clients connected to the first switch cannot see or ping clients on second and vice versa. All clients have internet access. Googling that problem I find out that there are two possible reasons for this phenomenon. Using Virtual LAN or bad routing. Since I'm not using VLAN and all the options related to it are turned off it looks like my router is having a lot of trouble doing the routing.
That statement does not stand. If you have not touched the VLAN or routing table, they should be listed. If you use a different brand switch, we do not guarantee that the ARP discovery will work across the brands. At least with an Omada setup, all Omada gears, the DHCP, or the topology in the controller would properly display.
And ARP sproof does not have anything to do with the function we discussed. You should take a peek at the VLAN1 interface.
And there are many other misconceptions or misunderstandings of the product.
You should also read the ARP table to learn if all devices are listed. Not reading the list from the DHCP list.
Literally, DHCP list only lists whatsoever devices that send a DHCP request to the rotuer and it assigns a DHCP IP. If a device uses a static IP, it does not list.
You should use the IP Statistics feature to scan your subnet to learn the list. That would be the proper way to learn the current devices in your network. That would be more informational than the DHCP list, which lists the subnet.
Routing is a matter of layer 3. ARP is layer 2. They do not see or ping other clients on the switch, which does not mean anything for the router. The switch is layer 2 and if that does not work, it could be a problem with your switch. Meaning that ARP may not work.
Unless you test the devices on the router directly, and they don't show up, they don't ping successfully, and they cannot access the Internet.
The ping and other stuff may not even go to the gateway. I don't know if you have any config to the switches but this does not appear to be a problem with the router either way.
- Copy Link
- Report Inappropriate Content
@Clive_A
I contacted TP-Link support and quickly got a solution. On the SG1016D switch, "port isolation" was turned on. After turning it off and rebooting, everything started to work fine. Thank you very much for your time and patience!
- Copy Link
- Report Inappropriate Content
pkks297 wrote
@Clive_A
I contacted TP-Link support and quickly got a solution. On the SG1016D switch, "port isolation" was turned on. After turning it off and rebooting, everything started to work fine. Thank you very much for your time and patience!
If you have any questions about the features of the switch/router, it is best to read the User Guide and learn what it does and how it works. That feature blocks the inter-port and layer 2 connections; therefore, it does not work for the list.
Community members did not know this was enabled, so we cannot provide feasible suggestions.
Anyway good to know it's resolved.
- Copy Link
- Report Inappropriate Content

Information
Helpful: 0
Views: 430
Replies: 7
Voters 0
No one has voted for it yet.