Accepted WAN/LAN auto-sensing
Background:
There is a typical network topology:

Some users might notice that, once the internet service fails, they are no longer able to access the NAS server from the local network.
The cause of this Phenomenon:
When internet service went down and the cable modem failed to provide an IP address for Main Deco, both Ethernet ports on the main Deco would work as WAN ports to detect internet connection. NAS would no longer obtain an IP address from Deco.
Why do we use WAN/LAN auto-sensing on Deco?
For the Deco Mesh system, normally, it would have more than 2 units, and each unit has at least 2 Ethernet ports; It would be time-consuming and confusing to find out which port should be connected to the ISP modem. And supposing that the WAN port is fixed, once this port is broken, the whole Mesh kit would be useless.
Recommended Solutions:
- Given that the issue arises only when the ISP modem fails to assign an IP address for the main Deco, once the cable modem recovers, the problem should be resolved. It is suggested to contact the ISP to restore the modem connection as a priority.
- The current workaround would be connecting the wired servers to the satellite Deco units instead of the main one.
- And we have also implemented enhancements on certain models, ensuring that the WAN port remains constant as long as the physical Ethernet connection between the modem and main Deco is unchanged, even when there is no internet service from the modem. Moreover, it is also planned to support manually fixing a specific Ethernet port as the WAN post on the Deco APP later.
The following models already support fixing the WAN port:
| Deco X80-5G Deco X50-5G Deco X20-4G Deco X50/X55_V1/V1.2 Deco X20/X60_V4 Deco X60_V3/3.2/V4.2 |
1.11.0 Firmware Platform Understand the Differences Among Deco Firmware Platforms
|
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
I have the same issue with TP-Link Deco AXE5300 Wi-Fi 6E Tri-Band Whole-Home Mesh Wi-Fi System. I kept on getting these odd occurances where we would loose internet for a brief period, the wifi would come back but the ethernet was down. I would play around with the Deco and restart it a few times and it eventually came back. Here lately it just stopped working. After reading this article, I connected my ethernet to a satelite and converted my satelites to only wifi backhaul. It worked as described. I will see how well it goes but it is a huge bug. I am going to look at other systems but not for sure what issues they will bring with them.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@TP-Link It's been over a year since reporting, and this problem hit me again yesterday. My ISP had some downtime, and all my home network with many IoT devices and NAS went south - unable to use part of the lights (those behind WiFi relays), unable to access NAS - the whole network f*cked...
Can you declare if anything is happening with this topic (with some ETA), or do You just have Your clients in the back and won't fix it...
- Copy Link
- Report Inappropriate Content
@TP-Link Because my Deco units will serve only as AP and I have my DHCP server separate, I assume this is not going to affect me Regardless I am browsing the forums to see all the non-sense you guys are spitting out, this one is pretty epic:
Why do we use WAN/LAN auto-sensing on Deco?
For the Deco Mesh system, normally it would have more than 2 units and each unit has at least 2 Ethernet ports; It would be time-consuming and confusing to find out which port should be connected to the ISP modem. And supposing that the WAN port is fixed, once this port is broken, the whole Mesh kit would be useless.
Seriously???
First, every other router on the market has fixed ports. This has and will always be the norm. Trying to re-invent the wheel helps no one. Second, if a port is broken, the unit is broken. You get it repaired or you replace it. Better yet, put the classic 1 WAN + 4 LAN. Seriously what is wrong with the product owner who made all these decisions???
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Grud wrote
David-TP wrote
Hi, For Deco X50/X55 V1, it might be good news that the latest firmware 1.2.0 has optimized this working mode. Deco will not reselect the wan/lan port until the Ethernet WAN cable is re-plugged.
Best regards.
@David-TP This is a pointless mitigation. The first troubleshooting step for loss of internet, is re-plugging the WAN cable, or power cycling the router. This kicks it straight back into WAN sensing mode and we have the problem all over again. Just allow the user to manually set a fixed WAN port in the settings! It's that simple.
@Grud
That is very true. Troubleshooting 101 :(
As pointed out by @GaryParr almost ONE YEAR ago... port selection code is already implemented for IPTV functionality.
Just copy/paste this code and use it to WAN port selection... cmon TP-LINK!
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
David-TP wrote
Hi, For Deco X50/X55 V1, it might be good news that the latest firmware 1.2.0 has optimized this working mode. Deco will not reselect the wan/lan port until the Ethernet WAN cable is re-plugged.
Best regards.
@David-TP This is a pointless mitigation. The first troubleshooting step for loss of internet, is re-plugging the WAN cable, or power cycling the router. This kicks it straight back into WAN sensing mode and we have the problem all over again. Just allow the user to manually set a fixed WAN port in the settings! It's that simple.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 160
Views: 115428
Replies: 326
