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 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.
Recommended Solutions:
- Given that the issue arises only when the ISP modem failed to assign IP address for the main Deco, once the cable modem recovered, 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 WAN post on the Deco APP later. (Some models already support this feature, such as Deco X80-5G/Deco X20-4G)
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
I wonder how many people in this thread have actually encountered the problem vs. just seeing the thread. I ask because I actually had an internet outage recently and had no problems connecting internally between any two devices, whether wired or on wifi, including a NAS, and connecting to a PC with remote desktop. I have two X20s. My topology is modem -> 1st deco -> ethernet hub with a bunch of wired devices + second deco -> 2nd deco. So in other words, all of my wired devices are on a couple of hubs between the first and second deco. Per the OP: "the workaround would be connecting the wired servers to the satellite Deco units, instead of the main one." It's a little unclear how I satisfied that condition, nonetheless things worked fine. <shrug>
- Copy Link
- Report Inappropriate Content
@jrd101 what are you implying here? We did not read? Sure everyone knows wired devices to satellites work. That is not the issue. The issue that got everyone riled up is the fact that the main deco goes apesh*t everytime the wan went down.
Not everyone could wire things up to satellites. Or wire the satellites to main. In the first place, the fact that this auto sensing "feature" is there and not advertised is a problem. To add fuel to the fire, they made it mandatory. QoL (for dumbs) should be optional.
- Copy Link
- Report Inappropriate Content
@jrd101 you are implying that we are all making this up and haven't a clue. I would suggest that this is not the case as TP Link support have work around and know how to resolve the problem. That implies it's real!
how may have experienced the scenario? most who have bothered to find this discussion will have had a reason to go searching for help - therefore they have had at least some problems/symptoms. There is however a world of difference between symptoms and identifying a root cause. This discussion has gone to a root cause that we have asleed TP-Link to rectify
and BTW - the reason your system worked is that the 2nd deco provided wireless access into your wired network, and the devices you were using already had IP addresses from the DHCP server that was in the deco that then ceased being a router. You most likely would have started to experience problems either introducing new devices, or as DHCP leases expire.
I can only comment on the system I have - but this fault disabled my central heating control (albeit the actual heating worked as it's on a zwave network), I lost most home automation (as the HA controller is hard wired to the main deco) and most of the HA devices are wifi ones. It's not made up
- Copy Link
- Report Inappropriate Content
@MarkRound Same here. Just installed the Deco P9's. WiFi works fine, but no connection to all home automation bridges which are connected to the Switch behind the main Deco (TADO central heating, HUE lights, etc.). What a joke! Just connected my provider's cheap Router (Zyxek T-50) again between the media converter and Deco again... Waste of money, TP-Link should have made this issue more clear before buying the Deco's!
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@David-TP Hello David,
Please there is any news about some new firmware for models Deco E4 in order to improve this feature?
Thanks
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 136
Views: 68643
Replies: 275