(Yet another) Problem with LAN breaking down between Router and Satellites

Question

Hello,&nbsp;I have found quite a few (older) threads here from users that used to have problem with their LAN connection breaking down between devices connected in various scenarios on the main unit and any number of satellites. Most of the users claim their issues to have been resolved with newer firmwares but on the&nbsp;newest&nbsp;one I am still suffering from it.&nbsp;My setup:- ISP's modem/router turned to bridge mode and connected with RBR20 via its WAN port (essentially being just a simple modem).- RBR20 turned to router mode handling pretty much everything (DHCP, DNS, ROUTING).- 2 x RBS20 spread accross various rooms with a few meters distance between them and the RBR20 (with brick walls in between).- Firmware:&nbsp;V2.7.3.22 (forced on me recently by Netgear - thanks for that!)&nbsp;What I observed that led me to open this discussion:I am using Home Assistant (an open-source smart home management platform) to control all my IOT devices in my house. Recently I started noticing in the logs communication between my Roborock S5 Vacuum and Home Assistant breaking down intermintently.&nbsp;&nbsp;2021-11-22 03:22:06 DEBUG (SyncWorker_3) [homeassistant.components.xiaomi_miio] Unable to fetch timers, this may happen on some devices: Unable to discover the device 192.168.1.49
2021-11-22 03:22:11 DEBUG (MainThread) [homeassistant.components.xiaomi_miio] Finished fetching roborock.vacuum.s5 data in 10.003 seconds (success: False)&nbsp;Of course there are also success communications still:&nbsp;2021-11-22 03:47:06 DEBUG (MainThread) [homeassistant.components.xiaomi_miio] Got new vacuum state: (Vacuum state omitted on purpose)
2021-11-22 03:47:06 DEBUG (MainThread) [homeassistant.components.xiaomi_miio] Finished fetching roborock.vacuum.s5 data in 0.103 seconds (success: True)&nbsp;The success to fail ratio in communication was alarming to say the least: 4256 successes vs. 1403 fails in 24 hours of logs for the vacuum alone. The whole issue started when I swapped two&nbsp;other&nbsp;IoT devices IPs on the Orbi DHCP for one another. Deleted one record and then re-assigned the IP to another record - always of course while restarting the system after each change through the dedicated "Reboot" menu on the web interface.&nbsp;Restarts didn't really solve anything. At first the vacuum would get some successes and then it would start to intermitently fail again with the above ratio. Sometimes things were so bad that the fail ratio would be 100% forcing me to issue another restart on the Orbi and another and another until I got a state that would be acceptable.&nbsp;&nbsp;Up to that point I was mostly blaming the vacuum itself dropping out of network (although it had never given me reasons to do that ever - but let's face it it's Xiaomi :smileytongue:) but during those restarts I was also noticing other devices being unable to communicate with my Home Assistant server intermitently (same as the vacuum) although not as often as the vacuum - like for example some TP-Link smart plugs that I have around the house, and those devices I cannot question! Those have been the solidest devices I ever had, never dropped once in their life. This is when I started looking into things on the Orbi side.&nbsp;Another issue I have to complement all the above is me accessing my personal file server via my phone through local IP (so my phone on some Satellite WiFi would request content from my file server on the main Orbi Router via local IP 192.168.1.4 to be precise) fails systematically. What I haven't tested is whether this happens if I am under&nbsp;a specific&nbsp;satellite or&nbsp;any&nbsp;satellite. I know it doesn't happen when I am connected to the router itself (via WiFi).&nbsp;Final thoughts:All the above, along with some other things I've noticed on the Orbi(s); like the fact that whenever I restart the Orbi system the satellites do take&nbsp;A LOT&nbsp;of time to sync the backhaul - more than they used to when I first bought them - but when it's synced it reports 'GOOD'. Or the fact that the devices failing to communicate properly are mostly connected to some satellite. I am thinking that there is some serious glitch going on in this firmware between main Orbi units and satellites. More specifically I am thinking DHCP and ARP being the main culprits and a bad sync between the main unit and the satellites&nbsp;all on LAN.&nbsp;What I failed to mention in this long text is that all devices have&nbsp;impecable&nbsp;access to the internet and all those communications failing are strictly LAN communications.&nbsp;Other technical stuff:I have the recommended settings to by Orbi(s) from here in the forum (i.e. Beamforming (on), Coexistence, Daisy chain (off) etc.) I do not have a firewall (both armor and circle are off). My devices all have static addresses assigned via Orbi's DHCP.&nbsp;I would appreciate any suggestions and help however I would like to refrain from having to reset my sytem.Spoiler (Highlight to read)I see this is an advice that "plays alot" here in these discussion boards. My home is actually a home-office. A lot of devices and configurations in place and we actually rely on the Orbi(s) to get work done plus the smart home relies on them as well. There&nbsp;shouldn't&nbsp;be the need to reset after firmware upgrades and the devices should be able to operate consistently 24/7 unless power disrupted - this is how I envision a reliable router.&nbsp;I see this is an advice that "plays alot" here in these discussion boards. My home is actually a home-office. A lot of devices and configurations in place and we actually rely on the Orbi(s) to get work done plus the smart home relies on them as well. There&nbsp;shouldn't&nbsp;be the need to reset after firmware upgrades and the devices should be able to operate consistently 24/7 unless power disrupted - this is how I envision a reliable router.&nbsp;Thank you,George&nbsp;

DarkNet · Answer

I also have a RBR20 and 2 RBS20 satellites.&nbsp; However my RBR20 is in AP mode.&nbsp; I have the latest firmware and do not have the issues you’re experiencing.&nbsp; Have you changed the location of any of the ORBIs?&nbsp; I’m into home automation as well but use an ISY994i as my controller.&nbsp; I realize that doesn’t relate to your connectivity problems.&nbsp; Assuming you had solid connectivity at one time, it sounds like you’re getting interference now or an Orbi has been relocated.&nbsp; However, since I’m not in router mode with my RBR20, it could be a firmware issue as you suspect.&nbsp; Do you have fast roaming turned ON?&nbsp; I had problems with that in the past and turned it OFF.&nbsp; Is your transmit power at 100% ?&nbsp; MIMO turned ON?

elementoulis · Answer

I have not relocated any Orbi , at least not vastly. I mean when I de-dust the place where each Orbi device is, yes they may be moved a few centimeters (2-3-5max cm) but that's it.&nbsp;&nbsp;Fast roaming is OFFTransmit power is 100% for both 2.4 and 5Ghz&nbsp;And MIMO is ON&nbsp;I am leaning towards firmware issue(s) as interference would be affecting my devices under all circumstances. However this is not the case. To make an example using my aforementioned robot-vacuum , it is possible to control the vacuum from 2 clients.&nbsp;1. From Xiaomi Mi Home which is the official client (app) of the maker company and utilizes a client-&gt;server-&gt;device topology. That means that when I log onto the app I am actually loging into the cloud&nbsp; server of Xiaomi which in turns has info on which external IP my vacuum is at (my IP) and whatever command I issue goes through the server, to the robot. In that scheme the vacuum is still able to respond no matter what. Very fast very accurately. Which means it's signal is not being interfered with. If it was ... the command arriving from Xiaomi Cloud , to my Router , to the Satellite and wirelessly looking for the vacuum would not be delivered, but it is.&nbsp;2. From Home Assistant platform which resides in my local network. Home Assistant is a server-like program which issues commands directly to my vacuum through the local network. So Home Assistant is on 192.168.1.4 on Orbi Router (RBR20) and the vacuum is on 192.168.1.49 on Satellite-1 (RBS20) and of course as it vacuums it jumps locations to Satellite-2 or Router as well. When the logs of Home Assistant show it cant reach the vacuum on 192.168.1.49 two things are also true:&nbsp;I am able to ping my&nbsp; vacuum through a cmd ping 192.168.1.49 and it replies perfectlyThe Xiaomi App (mentioned in #1) is also able to reach my vacuum through the internet perfectly&nbsp;This is what leads me to believe that there is something weird going on between the routing tables inside of Orbi. I don't know if it's the DHCP or the ARP or if it is even the sync that should be happening between the Router and the Satellites after every reboot - that could also be a possible culprit in a sense that it could have a bug in the process of passing the ARP tables from the Router to the Satellites.&nbsp;&nbsp;After my original post I tried hard-rebooting Router and Satellites (turned off and on through their respective hardware buttons) something that I do not usually do since I prefer rebooting them through the management panel. Thought maybe there was a glitch that persisted through software reboots in some weird cache... How wrong I was.&nbsp;Next test would be turning off the Satellite that seems to present the most problems. And monitor the logs for a few hours. I'll be back with more info.&nbsp;Thank you,George

FURRYe38 · Answer

So you say RBS are on LAN...does this mean the RBS are ethernet connected to the RBR? if so,&nbsp;
What CAT# cables are you using between the RBR and RBS?&nbsp;
There a LAN switch being used in between the RBR and RBS? If so, brand and model# please.&nbsp;
Has a factory reset and setup from scratch been performed since last update?

elementoulis · Answer

Hello!&nbsp;So, yes the RBS are on LAN , not wired though but through the wireless backhaul. RBR is in router mode and the RBS are connected on it as satellite devices (see Untitled.png).(One is Disconnected right now due to me testing things out but when I wrote the original post it was connected as well)&nbsp;Due to the wireless nature of connectivity of RBS(s) to RBR there is no switch, or Ethernet cables of any kind. Additionally I have never factory reset my Orbi system, which is my last option to be quite honest. I know that at some point it might end up there, however, I consider it kind of unacceptable to have to reset a system after its update to ensure proper function.&nbsp;As an update to my previous post I will mention that turning off the one Satellite that the robot vacuum was connected to, forced the vacuum to connect to the main router. Doing so, and collecting approximately 24h of logs resulted in the following:&nbsp;4854 success calls from my server to my vacuum on LAN3 failed calls from my server to my cacuum on LAN&nbsp;The difference is staggering. Next step in my investigation is to swap positions of the Kitchen-Satellite with the Bedroom-Satellite and enable both&nbsp;for another 24hours. This positioning will force the vacuum to connect to the Kitchen-Satellite (as it will have taken the place of the Bedroom-Satellite) and monitor the success/fail ratio from my server. This will allow me to establish if the failed LAN communications are a result of bad firmware implementation between RBR and RBS in general&nbsp;OR&nbsp;if I have a faulty RBS (the Bedroom one).&nbsp;Any more opinions or suggestions are highly welcome.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;

FURRYe38 · Answer

Has a factory reset and setup from scratch been performed since last update?
&nbsp;
I see you have a RBS20, does this get connected or no?&nbsp;
What version of FW is loaded on this RBS20?&nbsp;
Does the system work ok with out the RBS20 being connected? 
&nbsp;
What is the size of your home? Sq Ft? What is the distance between the router and 📡 satellite(s)? 30 feet or more is recommended in between RBR and RBS📡 to begin with depending upon building materials when wirelessly connected.

Forum Discussion

(Yet another) Problem with LAN breaking down between Router and Satellites