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
 
@gilg57 took them a few years to accept this issue so fingers crossed we'll see any fix coming this year. Even then, we'll have to see what they actually implement. It might be something else altogether lol
- Copy Link
 - Report Inappropriate Content
 
@David-TP This is very good news.
Is there a forecast date and a target version number, please?
- Copy Link
 - Report Inappropriate Content
 
Hi, welcome to the community.
So far this feature request has been accepted and It is planned to add an option to fix the WAN port on Deco APP.
Best regards.
- Copy Link
 - Report Inappropriate Content
 
- Copy Link
 - Report Inappropriate Content
 
@TP-Link I had to re-install my opnsense router and configure the deco's as AP mode to prevent this situation. There are still issues with the deco's that unlike any other router or mesh system that have built in optimisation to fix network issues, the deco's do not - they also don't constantly check radar frequencies to ensure they are not interfering. I've had to change the bandwidth used on mine because of this issue.
I don't think I would buy another TP-Link system after all these issues, and have even thought about going back to my ISP's FritzBox and getting their extender to go with it. Does mean I lose Wifi 6 and AX speeds but would be more reliable
I've also requested a full refund from Amazon as we've been waiting for the fix for a while and as it is not forthcoming then it's not actually fit for the purpose it was purchased for.
- Copy Link
 - Report Inappropriate Content
 
Once again I find myself without an internet connection, and unable to perform ANY work, because all my work today depends on accessing a headless remote machine within my internal network.
I just decided to consider suing TP-Link for lost wages. Since this "feature" is not mentioned anywhere in marketing materials or the manual, and EVERY OTHER ROUTER IN THE WORLD that's not a TP-Link works correctly (i.e. does not have this egregious bug masqueraded as a "feature"), it should be an easy win. I guess that, since I can't work while the internet is down, I'll use my idle time to call a lawyer and ask about the feasibility of suing TP-Link.
- Copy Link
 - Report Inappropriate Content
 
- Copy Link
 - Report Inappropriate Content
 
- Copy Link
 - Report Inappropriate Content
 
- Copy Link
 - Report Inappropriate Content
 
I discovered this clear, undisputable, absurd, completely unacceptable bug today and was absolutely disgusted to learn that it has existed for years and hasn't been fixed on the very same day that it was reported. As a matter of fact, it should never have existed at all. There are no circumstances under which this abortion of a "design" should have ever been considered by anyone with over 1 hour of experience in programming (speaking as someone with 3+ decades of experience in computer programming). The code cowboys who wrote and signed off on this "design" should be forever banned from ever coming close to a computer again, just as a drunk driver should not be let near a car, and for the same reasons. They deserve to be made an example of. This is the computer equivalent of medical malpractice with gross negligence.
And to think they had the gall to add a "Pro" suffix to this abortion of a negligently designed product that I own. I guess it's for professional Facebook/TikTok content consumers, or professional Netflix viewers, or professional WhatsApp message-typers. It's certainly not for an actual tech professional like myself, who has a network with dozens of devices I remotely access all day long (I literally always have one or more connections to one of the other devices in my network open). If my internet happens to go down, the "Pro" TP-Link router forbids me to do my professional duties. What a load of [redacted]. This is a joke, a disgusting joke. Any product afflicted with this awful joke for a "design" is just a toy for lay users. Anyone who works in tech should stay very very far away from this line of toy products.
I don't care if this is fixed tomorrow, I am never, never, never, NEVER again touching another TP-Link product. I don't care if the competition supposedly loses out on features/performance and costs 10x more. It's just not worth the risk. I will also make sure to tell everyone that will listen about how TP-Link is the most incompetent company I've ever had the displeasure of coming across, and that you should under no circumstances buy any products from them. And of course, when someone comes to me asking for recommendations for network gear (and trust me, I get asked very often), I will make sure to emphasize, in no uncertain terms, that they should not under any circumstances buy a TP-Link product. From now on, my volunteer work will be ensuring that everybody I know avoids TP-Link like the plague, and I will not rest until TP-Link goes bankrupt. And to stress: I don't care if this bug is fixed tomorrow, the mere fact that it ever existed, let alone stayed unfixed for years, means TP-Link became radioactive for me.
- Copy Link
 - Report Inappropriate Content
 
Information
Helpful: 160
Views: 115394
Replies: 326
