Home Network Community > Deco > LAN devices are not reachable from an Ethernet Backhaul connected Deco
< Deco

LAN devices are not reachable from an Ethernet Backhaul connected Deco

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

LAN devices are not reachable from an Ethernet Backhaul connected Deco

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
LAN devices are not reachable from an Ethernet Backhaul connected Deco
LAN devices are not reachable from an Ethernet Backhaul connected Deco
2021-03-22 13:47:38
Model: Deco M5  
Hardware Version: V1
Firmware Version: 1.5.2 build 20210121 Rel. 55884

Dear Support!

I have a TP-Link mesh system consist of 5 Deco units: 3 M5 and 2 M4R.
Topology: [ISP ONT device]---[Main Deco M5]---[TP-Link Gbit switch]---[Deco M5 upstairs]. These connections are with Ethernet Cable. The rest one M5 (Living room) and two M4R (Garage, Attic) units are connected to the Main Deco M5 with Wireless Mesh only.

Problem is the following: any clients connected to the "Garage" Deco unit are not reachable from any device which are nearby and connected to the "upstairs" Deco unit. Ping request of devices says connection timeout. When I move closer to other Deco units then suddenly those devices are reachable again, ping works fine from the testing device. If I go back to the nearby of the "upstairs" Deco, then ping does not work again: connection timed out.
The problem is only with those clients which are connected to the "Garage" Deco. Other devices connected to another Deco routers are reachable nearby of the "Upstairs" Deco unit. Internet access is also working fine nearby of this "upstairs" Deco, I encounter only local LAN issues as described. Internet access is also working fine for those clients, which are connected to the "garage" unit.

Pinging of the affected "Garage" Deco itself works fine, but any connected devices to this unit doesn't reachable.

I have already rebooted the Decos, also switched temporarily two Decos: moved the M4R from the "Garage" to the "Upstairs" and moved the M5 from "Upstairs" to the "Garage". With this setup the results are the same.

For other testing I removed the Ethernet cable from the "upstairs" Deco, with this setup the issue is solved, but for me it is not a solution I need the Ethernet backhaul to be working here.

 

  1      
 
  1      
 
#1
Options
6 Reply
Re:LAN devices are not reachable from an Ethernet Backhaul connected Deco
2021-03-23 03:53:09

@zsd111 

Hi, 

Were the clients connected to upstairs Deco able to access other Decos, such as living room Deco, attic Deco, or just garage Deco?

How about the devices connected to the Ethernet switch and are they able to access the garage Deco?

Have you enabled the guest network on the Deco?

And may I know the model number of the TP-Link switch?

Have you done the VLAN settings on the switch?

 

Thank you very much and wait for your reply.

Deco Monthly Recap- Check What's Currently Going on With Deco KidShield Test Recruitment, Share Your Ideas With us! Wi-Fi Schedule Ideas Wanted!
  0  
  0  
#2
Options
Re:LAN devices are not reachable from an Ethernet Backhaul connected Deco
2021-03-23 08:32:16

@TP-Link 

 

Devices which are connected to other Deco "main, attic, living room" are reachable from devices connected to the "upstairs" Deco. Only the devices which are connected to the "garage" are not reachable from the clients connected to "upstairs" Deco using Ethernet backhaul.

Switch type: TL-SG1008D. It's an unmanaged switch, there is no way to configure VLANs on it.

 

There is an Intel NUC connected to this switch, from this device I am able to ping any devices connected to the "garage" Deco, or any device connected to the "upstairs" Deco, also the Decos itself are pingable from this source.

Internet access is also available on all devices connected to whichever Deco, only local LAN issue is visible as I described.

  0  
  0  
#3
Options
Re:LAN devices are not reachable from an Ethernet Backhaul connected Deco
2021-04-15 11:07:11

@TP-Link,

 

is there any news here? Since then I have installed the latest 1.5.3 version on the M5 Decos, but the problem is still not being resolved. 

 

 

  0  
  0  
#4
Options
Re:LAN devices are not reachable from an Ethernet Backhaul connected Deco
2021-11-03 13:54:49

@TP-Link,

 

any news?

 

I could manage to have a new setup: ISP router --- Main Deco M5 --- TP-Link switch. From the switch, the following Decos are connected with Ethernet backhaul: Garage M5, Upstairs M4R. Two Decos are still connected with Wireless backhaul: Living Room M5 and Attic M4R.

 

Some clients connected to the Garage M5 are still not available when I am in the near of Living Room or Attic. Running a ping test, when I'm continuously pinging the IP of a device which is wirelessly connected to Garage M5, if I go to the near of living room or attic, the clients are not responding to ping. If I go back to other decos which are Ethernet backhaul connected, ping works again. Going to Wireless backhaul connected deco again, ping has got timeot.

 

Problematic devices can go to the WAN/Internet: for example one problematic device is an IP camera connected to Apple Homekit Secure video, recordings are available all the time, but live view is not available if I want to check it in the near from wireless backhaul connected decos. It's weird.

  0  
  0  
#5
Options
Re:LAN devices are not reachable from an Ethernet Backhaul connected Deco
2021-11-03 15:18:05

@TP-Link,

 

Today I did further tests, with a Powerline adapter I was able to connect the living room M5 also with Ethernet backhaul to the main deco via the switch. Once the connection is established the previously not responding devices are suddenly responding to ping near to the living room deco too. When I remove then the ethernet cable the ping test is still successfull. 

Unfortunately the powerline adapter is not the best solution due to poor bandwidth (only 40-50 Mbit/s) so I removed it and went back to wireless backhaul. After removal of the cable the ping tests and connections are fine.

As further test I rebooted the living room deco, then the original problem came back. Then again with powerline and ethernet backhaul the problem is solved, removed the cable all good again, until the next reboot. 

 

 

Please help to solve this weird problem!!!

  0  
  0  
#6
Options
Re:LAN devices are not reachable from an Ethernet Backhaul connected Deco
2021-11-03 16:23:00 - last edited 2021-11-03 17:25:48

@TP-Link 

 

checking the logs after today's test it's clearly obvious, ARP table of the "living room" does not have the client entries connected to another deco. The log entries are from the same time when I did the test walking around the house during the ping test. The ARP error issues pop up, then disappear and pop-up again, when I was near the living room deco:

 

ed Nov  3 15:02:12 2021 daemon.err client_mgmt: client(40-A3-CC-1F-54-28) not found in arp table disconnect_counter=0
Wed Nov  3 15:02:12 2021 daemon.err client_mgmt: client(94-B9-7E-E0-3E-24) not found in arp table disconnect_counter=0
Wed Nov  3 15:02:16 2021 daemon.err udhcpd[6280]: Sending ACK to 192.168.68.139
Wed Nov  3 15:02:16 2021 daemon.err udhcpd[6280]: clear ip 8b44a8c0
Wed Nov  3 15:02:32 2021 daemon.err client_mgmt: client(40-A3-CC-1F-54-28) not found in arp table disconnect_counter=1
Wed Nov  3 15:02:41 2021 user.warn IMPROXY: WARNING[mcast_recv_igmp@753]: Don't exist this Downstream VIF
Wed Nov  3 15:02:53 2021 daemon.err client_mgmt: client(40-A3-CC-1F-54-28) not found in arp table disconnect_counter=2
Wed Nov  3 15:02:53 2021 daemon.err udhcpd[6280]: Found static lease: 6b44a8c0
Wed Nov  3 15:02:53 2021 daemon.err udhcpd[6280]: Sending ACK to 192.168.68.107
Wed Nov  3 15:02:53 2021 daemon.err udhcpd[6280]: clear ip 6b44a8c0
Wed Nov  3 15:03:09 2021 daemon.err udhcpd[6280]: Sending ACK to 192.168.68.106
Wed Nov  3 15:03:09 2021 daemon.err udhcpd[6280]: clear ip 6a44a8c0
Wed Nov  3 15:03:35 2021 daemon.err client_mgmt: client(44-73-D6-0D-E2-6C) not found in arp table disconnect_counter=0
Wed Nov  3 15:03:56 2021 daemon.err client_mgmt: client(44-73-D6-0D-E2-6C) not found in arp table disconnect_counter=1
Wed Nov  3 15:04:15 2021 daemon.err client_mgmt: client(3C-71-BF-20-83-D2) not found in arp table disconnect_counter=0
Wed Nov  3 15:04:15 2021 daemon.err client_mgmt: client(44-73-D6-0D-E2-6C) not found in arp table disconnect_counter=2
Wed Nov  3 15:04:15 2021 daemon.err client_mgmt: client(D0-3F-AA-5C-E9-AC) not found in arp table disconnect_counter=0
Wed Nov  3 15:04:36 2021 daemon.err client_mgmt: client(40-A3-CC-1F-54-28) not found in arp table disconnect_counter=0
Wed Nov  3 15:04:37 2021 daemon.err udhcpd[6280]: Found static lease: 7444a8c0
Wed Nov  3 15:04:37 2021 daemon.err udhcpd[6280]: Sending ACK to 192.168.68.116
Wed Nov  3 15:04:38 2021 daemon.err udhcpd[6280]: clear ip 7444a8c0
Wed Nov  3 15:04:40 2021 daemon.err udhcpd[6280]: Sending ACK to 192.168.68.125
Wed Nov  3 15:04:40 2021 daemon.err udhcpd[6280]: clear ip 7d44a8c0
Wed Nov  3 15:04:46 2021 user.warn IMPROXY: WARNING[mcast_recv_igmp@753]: Don't exist this Downstream VIF
Wed Nov  3 15:04:56 2021 daemon.err client_mgmt: client(40-A3-CC-1F-54-28) not found in arp table disconnect_counter=1
Wed Nov  3 15:04:56 2021 daemon.err client_mgmt: client(34-7E-5C-37-99-6C) not found in arp table disconnect_counter=0
Wed Nov  3 15:05:16 2021 daemon.err client_mgmt: client(40-A3-CC-1F-54-28) not found in arp table disconnect_counter=2
Wed Nov  3 15:05:17 2021 daemon.err client_mgmt: client(70-A2-B3-E2-E6-1F) not found in arp table disconnect_counter=0
Wed Nov  3 15:05:17 2021 daemon.err client_mgmt: client(34-7E-5C-37-99-6C) not found in arp table disconnect_counter=1
Wed Nov  3 15:05:59 2021 daemon.err udhcpd[6280]: Sending ACK to 192.168.68.151
Wed Nov  3 15:05:59 2021 daemon.err udhcpd[6280]: clear ip 9744a8c0
Wed Nov  3 15:06:43 2021 daemon.err client_mgmt: wireless client associate or disassociate.
Wed Nov  3 15:06:43 2021 daemon.err client_mgmt: client_mac:D0-3F-AA-5C-E9-AC, client_ifname:ath1, client_action:associate
Wed Nov  3 15:06:43 2021 daemon.err client_mgmt: client(D0-3F-AA-5C-E9-AC) assocaite by if(ath1).
Wed Nov  3 15:06:51 2021 user.warn IMPROXY: WARNING[mcast_recv_igmp@753]: Don't exist this Downstream VIF
Wed Nov  3 15:06:57 2021 daemon.err client_mgmt: client(58-D3-49-2D-D2-57) not found in arp table disconnect_counter=0
Wed Nov  3 15:07:06 2021 daemon.err client_mgmt: wireless client associate or disassociate.
Wed Nov  3 15:07:06 2021 daemon.err client_mgmt: client_mac:D0-3F-AA-5C-E9-AC, client_ifname:ath1, client_action:disassociate
Wed Nov  3 15:07:06 2021 daemon.err client_mgmt: client(D0-3F-AA-5C-E9-AC) disassocaite by if(ath1).
Wed Nov  3 15:07:17 2021 daemon.err client_mgmt: client(58-D3-49-2D-D2-57) not found in arp table disconnect_counter=1
Wed Nov  3 15:07:17 2021 daemon.err client_mgmt: client(78-28-CA-84-E0-0E) not found in arp table disconnect_counter=0
Wed Nov  3 15:07:36 2021 daemon.err client_mgmt: client(58-D3-49-2D-D2-57) not found in arp table disconnect_counter=2
Wed Nov  3 15:08:21 2021 authpriv.warn dropbear[20205]: Login attempt for nonexistent user from 192.168.68.139:59215
Wed Nov  3 15:08:37 2021 daemon.err client_mgmt: client(58-D3-49-10-7E-3C) not found in arp table disconnect_counter=0
Wed Nov  3 15:08:56 2021 user.warn IMPROXY: WARNING[mcast_recv_igmp@753]: Don't exist this Downstream VIF
Wed Nov  3 15:08:57 2021 daemon.err client_mgmt: client(3C-71-BF-20-93-5C) not found in arp table disconnect_counter=0
Wed Nov  3 15:08:57 2021 daemon.err client_mgmt: client(58-D3-49-10-7E-3C) not found in arp table disconnect_counter=1

 

 

The MAC addresses 40-A3-CC-1F-54-28, 44-73-D6-0D-E2-6C, 3C-71-BF-20-83-D2 belong to the devices which are connected to the "garage deco". So: ethernet backhaul decos and wireless connected decos does not share/keep sync their ARP tables! 

If all decos are Wireless backhaul connected or ALL decos are Ethernet backhaul connected, the issue is not visible. If the backhauls are mixed, seems to be the ARP table is not synced correctly. Please check!

  0  
  0  
#7
Options

Information

Helpful: 1

Views: 1365

Replies: 6

About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.