Dieses Problem besteht seit Jahren, daher würde ich mich nicht darauf verlassen, dass es vor diesem Datum behoben wird. Schicke sie jetzt einfach zurück.

  @TP-Link 

Liebes TP-Link Team, ich bitte um Info bis wann das Problem gelöst ist? Wenn es vor dem 28.09.2022 gelöst ist kann ich die Geräte behalten wenn nicht werde ich sie zurückschicken müssen, denn nurt weil gerade das Internet aufällt kann ja nicht das interne Netzwerk mit ausfallen....
LG Thomas
 

  @gn0s1s 

 

I actually "side-graded" my whole network from a unifi-based one, because I decided that all the granularity and power user stuff was not really needed for home use and the Deco hardware had been top-notch until this point. 

 

The fact that the lack of internet crippled my entire network for something that could be very easily fixed is just mind boggling to me. "Oh we dont have a dedicated WAN port so users have an easier time connecting their modem into whatever port they please"... ok, that's valid, how about we just toggle that feature off and have the WAN port always be port 1?

 

On top of that, my internet connection got reestablished after 4 days and when it came back, all the deco stations were freaking out and coming in and out of service. The main deco would come online but the secondary ones (all with ethernet backhaul) would stay offline and viceversa. Eventually I had to remove all of them except the main one, and then re-add one by one manually... Again, i'm pretty sure this was due to the auto-sense trying to figure out which cable had internet access and whatnot. 

 

Considering switching to eero, they have clear WAN/LAN ports so i'm pretty sure this is not gonna be an issue there, but I still need to properly investigate to avoid similar issues. 

  @Andrewe1 

 

"Never buying tp-link devices ever again."

 

This is where I am at as well. I have completely lost all incentive to purchase from TP-Link ever again because of this crazy implementation. Our next home network (which I am currently planning) will NOT contain any TP-Link based hardware.

 

The fact that developers think this is a feature rather than a major bug just shows how out-of-touch they are with their user base. The truth is most users that run into this issue will (1) not know enough to figure out what's going on and (2) not bother to sign up for this forum to complain about it. It doesn't mean this problem isn't affecting a massive amount of users, it just means that few users will actually have their frustrations heard. And what happens when a product doesn't work and a user can't figure it out? Either they return the product or they throw it away and buy a different brand. TP-Link's boneheaded development decision is marketing against its own interests.

  @Ludacrus 

 

Hi, pretty sure it's in all Decos, I have a mix of x20s x50s, and E4, and I have the same problem. 

  @David-TP 

 

I'm on my third day without internet (fiber snapped and i'm waiting for the ISP to fix it).

 

The first couple of days I didn't have any problems since I was just working with a wireless hotspot and could still access all of my network devices...

 

Today I see that for some reason, all my wired devices aren't getting an IP... My NAS is down, my NVR with 16 IP cameras are down... everything is useless and I just learned the reason is some dumb auto-sensing feature cannot be disabled on the main deco?!? I have the main switch connected to that deco, I never thought doing that would cause so much grief.

 

I cannot believe I have recommended these devices so much... not anymore, and i'm getting rid and replacing my devices as soon as possible.

 

https://imgur.com/a/NvCImcU

 

 

Never buying tp-link devices ever again.

 

 

  @Ludacrus 

IKR

All tplink products are a waste of money now.  Never again-  this company is dead to me

Imagine making a router that doesnt work properly and calling it a "feature".  Epic fail

  @TP-Link Have just come across this thread after running into this issue during an internet disruption with my Deco M5. I honestly can't believe this isn't a supported feature and is highly annoying, especially whilst I was trying to figure out what was going on!

 

Please add this as a standard feature! Does this apply to all Deco models, or just the M5?

  @TP-Link I purchased the Deco M5's to expand my Christmas display in my yard. The devices down stream of the Deco's are relatively low speed (in ethernet terms at least) and spread over about 1000 sq meters of my yard. Most are in a master/puppet relationship with pre-programed sequences triggered by the master. The RF devices are on a frequency that does not conflict with WiFi. I am a Comcast customer. It is not unuasual for the Internet to drop out during the night as my display runs. If you tell me I can not simply use the eithernet ports on both Decos to drive switches (my only use case) then I still have the boxes and can replace them with another brand of mesh router that will work. If it did work then I could span a single IP address range between the two Decos simplifying my programing of devices down stream.