@TP-Link 

@David-TP 

X50-4G needs an option to chose fixed Wan port.

  @C0deape 

Sadly, I haven't found that setting. It's not under Advanced, not under Offline Detection  or anywhere else that I can find.

It's strange, as X20 or X80 with cell backup got that setting, but not X50 does not, witch just doesn't make sense. And since other models already have it, it should be relatively easy to fix.

  @Vang1 I thought that was already an option on x50-4g?

I've not got mine set as primary at the moment so can't check, but could swear there was a setting to specify the wan port it listens to in order to flip to 4g? Does that not force the other 2 to lan? Seems a huge oversight if not!

  @TP-Link 

Are there any progress on this issue. I got X50-4G, and using it as wifi-router, with my fibre connection as primary WAN and 4G as backup. When my fibre drops out, it uses 4G to provide, but it drops both my wired satellite and my 16 port switch, and only provides wifi enabled devices. Seing as Fixed WAN port already exists on other similar deco devices, this should be implemented on the rest of them.

I'm loving both my X50-4G as main router, and both my satellites (X50 and X50-Outdoor), but this simple issue makes me considering switching the setup, even if I'm really happy with the rest of it.

  @Mark-R Thanks for the info/suggestions/discussion/etc!  My setup is only ethernet back haul.  With my old Orbi setup restored, I no longer have any issues. I had an older ASUS mesh setup prior (it had a terrible mesh solution - but in their defense it wasn't their latest MESH solution - unfortunately the experience was so terrible that I don't want to risk their newer solutions).  But seemless handoff issues aside, the ASUS system was rock solid as far as overall network staying up.   So its hard to believe there is something "wrong" with my setup for the Deco solution to hiccup (only a second to a few seconds) so frequently during the day.  Could it really be my AT&T fiber ISP losing connections for split seconds (perhaps the ASUS or Negear simply "ignore" these hiccups and that's why everything appears to be stable) and throwing the Deco into port sensing mode?!

Anyway, I left all my Deco setting as is - so if there is a firmeware update/fix in the future, I can easily swap it back in for a weekend or so to test.  But until there is a fix (this thread is 3+ years old?!), I'm going to stick with my "slowish" Netgear Orbi! 

  @ClemDaddy I think the behaviour varies if you have wired back haul or not. With wired, my m5

master goes hunting a wan if it's disconnected. As

the wireless range isn't enough in my case to

use wireless back haul ALL my decos go offline as the master tries to auto sense using both its wired

ports - which is where I've connected My streaming and home automation systems and als where the backhaul to the other m5s is. At which point it's all in a snotty heap. 
 

if your decos can see each other on WiFi - You may get a different behaviour, but using only wired connections for backhaul I lose everything!

this renders the decos useless to me apart from for guest access to WiFi 

  @Mark-R thanks for the info.  I guess it makes sense that it is still cloud reliant to be able to configure via the mobile app.   BUT I can confirm that in AP mode (with another DHCP server in play - in my case my ATT fiber modem/router) you do NOT loose you home LAN when the WAN wire is disconnected.  Things seemed to go offline for a few seconds (I almost concluded that the LAN was offline), but eventually I was able access my network shares (despite the WAN wire disconnected).

SINCE I was fed up trouble shooting this nonsense (my wife works from home and can't deal with this unreliability - and I don't want to waste my evenings trouble shooting something that should just work out of the box), I restored everything back to router mode.  I disconnected the WAN wire and as reported in this thread, my LAN (wired and wireless nodes) all went offline. 

I put back my older Netgear Orbi RBR50.  It tops out around 300 up/down - but it is stable - and that's what counts! 

  @ClemDaddy AP mode doesn't prevent the deco's from trying to auto sense the wan connection. They are still cloud reliant!
 

I have now replaced 3 of my 5 decos with open wrt based devices with the decos only in secondary areas (guest spaces) and I don't lose my wired devices or home WiFi when the broadband drops out

ClemDaddy wrote

  @C0deape thanks for the suggestions.  In my original setup, I had not disabled DHCP on the fiber modem, but I don't think that was a factor.   My new setup where I have the DECOs in AP mode, I ended up making the fiber modem/router the DHCP server.  So for sure in this configuration there isn't any other DHCP server on the network competing.  I also don't have any devices with fixed IPs.  I do have reserved IPs for machines, but it is still the DHCP server handing those resevered IPs out.

 

Well, I don't want to hijack this thread with my unique issue.  I'll keep searching other threads to see if others have a similar issue, or perhaps I start a new thread.  If for some reason the issue ends up being related to this thread, I'll be sure to give an update!

  @C0deape thanks for the suggestions.  In my original setup, I had not disabled DHCP on the fiber modem, but I don't think that was a factor.   My new setup where I have the DECOs in AP mode, I ended up making the fiber modem/router the DHCP server.  So for sure in this configuration there isn't any other DHCP server on the network competing.  I also don't have any devices with fixed IPs.  I do have reserved IPs for machines, but it is still the DHCP server handing those resevered IPs out.

Well, I don't want to hijack this thread with my unique issue.  I'll keep searching other threads to see if others have a similar issue, or perhaps I start a new thread.  If for some reason the issue ends up being related to this thread, I'll be sure to give an update!

  @ClemDaddy have you got anything with a fixed IP on your network, or a device that may also be a DHCP server?

Reason being I had OMADA outdoor access points linked to the LAN with an OMADA controller, and they didn't always play nice. I also had set some devices to fixed IP which I think caused thr 2 systems to fight.