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 the issue:
When internet service went down and cable modem failed to provide 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.
Since the problem only appeared when the internet service went down, once the internet service recovered, there would be no such troubles. And currently, the workaround would be connecting the wired servers to the satellite Deco units, instead of the main one.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@TP-Link I've now removed the Deco X50 as a router and reconfigured it as an AP so hopefully won't get these issues anymore, but definitely a failing on TP-Link side
- Copy Link
- Report Inappropriate Content
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.
- Copy Link
- Report Inappropriate Content
@David-TP I've replaced the Deco X50 as my router and gone back to OpnSense and reconfigured the deco to run in access point mode
this gives me the ability to change lease times, manage devices correctly, assign devices to groups, monitor the usage and protection for free, access to lan devices in the event of an internet outage
- Copy Link
- Report Inappropriate Content
@David-TP well that's good news - and shows that the problem is in the code (and is fixable there!)
lets hope they have plans for the M5 firmware as well (hopefully they are built from a common code base!)
I will ask as I now have a case open with TP-Link support (and an official reference number!)
- Copy Link
- Report Inappropriate Content
yeah - sad - the product has poor design. I bought 4 of these to provide coverage on a biggish area - but also have a bunch of wired devices and want a 'guest' wireless network that cannot access the wired devices. THe Deco when it works does this ok (although I am beginning to think the router functions are pretty pants! - the device naming doesn't stay consistent and the device list doesn't often match an IP address scan of what is active)
They become expensive Access Points - very disappointing
- Copy Link
- Report Inappropriate Content
@MarkRound yeh they do become expensive AP's and it is true the router side is poor for technically minded users. for plug and play they are ok, but still lots of limitations due to the current bugs
- Copy Link
- Report Inappropriate Content
Please also fix this autosensing problem for the Deco M4. Thanks.
- Copy Link
- Report Inappropriate Content
Please vote this bug up (button on the left upper corner of the page).
Seems we need to pass 50 to get the support team's attention.
- Copy Link
- Report Inappropriate Content

Information
Helpful: 66
Views: 15120
Replies: 122
Voters 62





























































