RBK853 With Ethernet Backhaul Satellites Drop Out

Hi

Time to report back with some findings.  I have to say i am extremely frustrated and borderline ready to bail and try another router type.

So, my initial test was to run with just a router which appeared to be relatively stable, albeit parts of the house had dodgy signal and did appear to drop connection, as you would expect at the edge of a signal.  I cant be 100% sure that this was not the same problem as below, but given all devices close operated OK, I dont this this was a reoccurence of the problem.

I then added a satellite with a wireless backhaul connection to the router.  This raises my first key question here.  To add a satellite, I dont seem to need to go through the online webpage of "adding a satellite".  Once i powered the satellite up, the router just see's it and syncs it up.  (is this working as expected, or should I be following the add satellite process?)  This set up appeared to run quite stable and we did not notice any drops in connection.  I only ran the test for 12 hours or so, but usually we would see the issue in this timeframe.

This morning i then connected the same sateliite with an ethernet cable to make ethernet backhaul.  Immediately we saw the satellite have syncing issues.  If i kept on refreshing the ORBI web portal on my laptop, i would randomly see the "out of sync" on the backhaul status section, and it fluctuated from Good to out of sync.  Devices would connect and then drop.  Yet if i moved within range of the main router, the connection would be stable and have no issues.  I tried this with two different ethernet cables connecting the two ORBIs and found the same experience.  (I should note during this phase of testing I had removed ALL connected switches on my network, meaning no phyiscal devices were connected.  In addition I had turned off the vast majority of wireless devices in the house)

Next I tried a fresh reboot of both the router and satellite, keeping the Ethernet connected.  In this instance I brought the Router fully up and running before powering up the satellite.  Once it all connected it appeared to be far more stable, running for a few hours without issues rather than the few minutes we had previously.  However, albeit far less regularly, eventually the issue resurrected and devices dropped from the satellite and struggled to re-connect.

I decided to go for one more brand new build.  Factoring resetting everything, i built the router from scratch with no satellites, and then connected the satellite using the Ethernet cable from the start (incidentally I changed the satellite to the second one I have that has been powered off to date, just to rule out a hardware issue on the first satellite).  Again, i appeared to be stable for several hours and then this evening, 3 or 4 devices started to drop connection in the same way as previously and struggled to re-connect for a few minutes.  When looking at the browser i was unable to see the "out of sync" message on the backhaul, but i did see the devices connecting predominantly to the router rather than the satellite during the troublesome phase.

However, ten minutes later or so, things settled down and were stable again.  (as they are now as i write this message).

So, i really am at a loss here as to what the problem is and what to try next.  

(there is one other point I want to note in case it rings a bell with someone, but my wireless connections on my iphones "sometimes" show a Privacy Warning and a message about encrypted DNS.  Then, the same device will not show that message without me having made any changes.  Probably irrelevant, but it is something else I have noticed).

Anyway, sorry for the long message, any thoughts appreciated.

Thanks

Andy

---

ElCapo wrote:

Hi

 

Time to report back with some findings.  I have to say i am extremely frustrated and borderline ready to bail and try another router type.

 

So, my initial test was to run with just a router which appeared to be relatively stable, albeit parts of the house had dodgy signal and did appear to drop connection, as you would expect at the edge of a signal.  I cant be 100% sure that this was not the same problem as below, but given all devices close operated OK, I dont this this was a reoccurence of the problem.

So the RBR alone is good up to this point. 

 

I then added a satellite with a wireless backhaul connection to the router.  This raises my first key question here.  To add a satellite, I dont seem to need to go through the online webpage of "adding a satellite".  Once i powered the satellite up, the router just see's it and syncs it up.  (is this working as expected, or should I be following the add satellite process?)  This set up appeared to run quite stable and we did not notice any drops in connection.  I only ran the test for 12 hours or so, but usually we would see the issue in this timeframe.

So the RBR and 1 RBS is good up to this point.

 

This morning i then connected the same sateliite with an ethernet cable to make ethernet backhaul.  Immediately we saw the satellite have syncing issues.  If i kept on refreshing the ORBI web portal on my laptop, i would randomly see the "out of sync" on the backhaul status section, and it fluctuated from Good to out of sync.  Devices would connect and then drop.  Yet if i moved within range of the main router, the connection would be stable and have no issues.  I tried this with two different ethernet cables connecting the two ORBIs and found the same experience.  (I should note during this phase of testing I had removed ALL connected switches on my network, meaning no phyiscal devices were connected.  In addition I had turned off the vast majority of wireless devices in the house)

The ethernet connection problems would indicate the following: Bad cable, RBS not directly connected to the back of the RBR. A LAN switch in between the RBR and RBS causing problems. Possible faulty RBS LAN ports, Swap LAN ports on the RBS. Possible bad RBS... 

 

Next I tried a fresh reboot of both the router and satellite, keeping the Ethernet connected.  In this instance I brought the Router fully up and running before powering up the satellite.  Once it all connected it appeared to be far more stable, running for a few hours without issues rather than the few minutes we had previously.  However, albeit far less regularly, eventually the issue resurrected and devices dropped from the satellite and struggled to re-connect.

 

I decided to go for one more brand new build.  Factoring resetting everything, i built the router from scratch with no satellites, and then connected the satellite using the Ethernet cable from the start (incidentally I changed the satellite to the second one I have that has been powered off to date, just to rule out a hardware issue on the first satellite).  Again, i appeared to be stable for several hours and then this evening, 3 or 4 devices started to drop connection in the same way as previously and struggled to re-connect for a few minutes.  When looking at the browser i was unable to see the "out of sync" message on the backhaul, but i did see the devices connecting predominantly to the router rather than the satellite during the troublesome phase.

 

I'd troubleshoot the ethernet connected RBS, Try swapping LAN cables (CAT6 recommended), LAN ports and remove any LAN switches if possible. Seen odd things with LAN switches. 

What brand and model Switches are you using if you have one? 

There any LAN patch panels or wall jacks in use? 

 

I just ran my two RBS ethernet connected to the RBR thru a few lan switches for 12 days, and no issues. I don't think this is a FW issue.

 

However, ten minutes later or so, things settled down and were stable again.  (as they are now as i write this message).

 

So, i really am at a loss here as to what the problem is and what to try next.  

 

(there is one other point I want to note in case it rings a bell with someone, but my wireless connections on my iphones "sometimes" show a Privacy Warning and a message about encrypted DNS.  Then, the same device will not show that message without me having made any changes.  Probably irrelevant, but it is something else I have noticed).

Apple has introduced a Private Address feature in new iOS. Something that mostly enabled by default on there devices. When this feature is disabled, this will how a Privacy Warning on the device. Something to be not too worried about as this only changes the MAC address to something different when it's enabled. Something thats not needed while at home however you might enable it while traveling. 

 

 

 

---

Hi Furry, thanks for response.

I did try it with two different cables and two different satellite boxes.  So i dont think it can be considered a phyisical problem.

Also, i have no LAN switces "in between", they are direct cables, however, once everyting is connected I have switches connected to other ports on my Router / Satellite(s) that extend around the house.  

As mentioned above, i have seen this issue with pretty much everything turned off in my house, no switches, no sky, no sonos etc...

I am going to try a pure wireless connection for a while and see what happens.

Do you think it is worth me trying this new firmware?  When reading the links to the other forums, many of their issues appear similar to mine.

Just thought I would put in a quick update following todays test and also the recent finding.. which may or may not be relevant.

I decided to upgrade to V4.6.6.11_2.1.4T1 and also performed a complete rebuild of the set-up with factory resets etc..

i decided to go with Ethernet connections with the new firmware first.

I have built with both satellites live at the same time.

I noticed that as the satelittes first started to sync up they portrayed the following message when logging directly onto the Satellite portal screen:

"Move your Orbi Satellite closer to your Orbi network to improve connection."  Given this is an Ethernet connection, this is a really strange message to get.

After a few moments, this changed to the better message which is:

"Your WIFI Orbi Satellite connection is up and running "

This remained up and good for approx 6 hours and I had no issues and I checked the satellites regularly to see if the message was the same (it was).  Then, randomly I noticed my laptop had dropped connection to the satellite and was connected back onto the router instead with a slightly weaker connection.  I immediately logged into satellite portal, and sure enough the message had changed back to:

"Move your Orbi Satellite closer to your Orbi network to improve connection." 

Then, literally as I sit here now and type this message, I noticed my signal on the laptop drop completely.  My phone drops and swtiches to 4G and the satellite wifi is effectively gone.  Wait a few moments and it is back and running again, however the satellites now both record that need to move closer to my network!  which as I say, makes no sense.

Firmware does not fix the issue is the bottom line here.

---

ElCapo wrote:

Just thought I would put in a quick update following todays test and also the recent finding.. which may or may not be relevant.

 

I decided to upgrade to V4.6.6.11_2.1.4T1 and also performed a complete rebuild of the set-up with factory resets etc..

 

i decided to go with Ethernet connections with the new firmware first.

It's recommended when setting up the RBS to the RBR, wirelessly synce them to the RBR first to ensure they sync fully. 

 

I have built with both satellites live at the same time.

Never do this. Sync RBS one at a time. 

 

I noticed that as the satelittes first started to sync up they portrayed the following message when logging directly onto the Satellite portal screen:

 

"Move your Orbi Satellite closer to your Orbi network to improve connection."  Given this is an Ethernet connection, this is a really strange message to get.

 

After a few moments, this changed to the better message which is:

 

"Your WIFI Orbi Satellite connection is up and running "

 

This remained up and good for approx 6 hours and I had no issues and I checked the satellites regularly to see if the message was the same (it was).  Then, randomly I noticed my laptop had dropped connection to the satellite and was connected back onto the router instead with a slightly weaker connection.  I immediately logged into satellite portal, and sure enough the message had changed back to:

 

"Move your Orbi Satellite closer to your Orbi network to improve connection." 

 

Then, literally as I sit here now and type this message, I noticed my signal on the laptop drop completely.  My phone drops and swtiches to 4G and the satellite wifi is effectively gone.  Wait a few moments and it is back and running again, however the satellites now both record that need to move closer to my network!  which as I say, makes no sense. This is telling you that the RBS are can't connect via ethernet and are auto changing to wireless and are too far apart to get a wireless connection to the RBR. 

 

Firmware does not fix the issue is the bottom line here. This would indicate a physical problem. LAN cable or switch or possible bad RBS. Since using last v4 FW version I had my RBS ethernet connected for 12 days with no issues. So I don't feel this issue your seeing is FW related.

When you have the LAN switches online, are the RBS connected to them at all? 

What brand and model are these LAN switches? 

---

Hi Furry

I just dont see how that is the issue.  I know it would indicate that the devices have dropped ethernet backhaul, but there is nothing to suggest on any portal that this is the case.  For example:

- the main portal continues to display "Wired" as connection type

- secondly, on each of the two satellite portals the two connection "signals" in the diagram between the Router and the Satellite are greyed out.  When you connnect wirelessly the 5Ghz is showing as blue coloured.

Over the past couple of weeks I have tried setting up direct to ethernet, and in wireless mode first then convert to ethernet.  The outcome is the same.

When i said that i did both satellites at the same time, i just meant i tested with them both (as opposed to just one).  When i went through the actual process of onboarding them, I did them individually.

So, coming to the final point in your mail.  You may well be right and perhaps this has nothing to do with the firmware (although I have seen other comments from people with ethernet connected issues).  However, if we look at my LAN Switch situation it is as follows.  Whenever I test Ethernet Backhaul I have direct ethernet cables from from the RBR to the RBS's.  From the main RBR router there is a connection to a switch, this switch then feeds several other switches (none of these touch the RBS though).  Then I have one switch that connects from one of my RBS LAN ports to feed sky box and tv in one room.

The switches are ALL netgear, and they are all 100/1000mbs however the models vary including:

GS308

GS308P

GS205

GS205-100UKS

GS208-100UKS

GS608

GS605

Those last two are particularly old, but that are all unmanaged switches.  Perhaps I should consider replacing some of the older ones.

I have now configured my set up without the Ethernet Backhaul (wireless only) and with NO LAN connections into either of the two RBS routers.

It has been OK so far.  But then my previous set up worked fine for about 6 hours.

Will report back findings.

Cheers

Andy

Ok Thanks for confirming the setup process and configuration. 

IM curious if you turned OFF 1 RBS and left one ON wireless then connected it wired to the RBR if the RBS would still exhibit this issue..

What CAT# cables are you using between the RBR and RBS? CAT6 is recommended. Good Quality. 

You have swapped out LAN cables to test as well?

So with no Switches in the mix at all, RBS still fail when ethernet directly connected to the RBR is the correct? 

I wanted to narrow down troubleshooting as far as possible before suggesting something you might check into:

https://community.netgear.com/t5/Orbi-WiFi-6-AX-and-WiFi-6E-AXE/RBK-8-Series-Only-Unofficial-v4-6-6-11-Firmware-Experiences/m-p/2178954/highlight/true#M24956

Maybe worth trying...

---

FURRYe38 wrote:

Ok Thanks for confirming the setup process and configuration. 

 

IM curious if you turned OFF 1 RBS and left one ON wireless then connected it wired to the RBR if the RBS would still exhibit this issue..

 

That is a scenario I have tested and encountered the issue.   I have done so much testing the last couple of weeks.

 

What CAT# cables are you using between the RBR and RBS? CAT6 is recommended. Good Quality. 

You have swapped out LAN cables to test as well?

 

I am using CAT6 cable, and yes i tested two different types.

 

So with no Switches in the mix at all, RBS still fail when ethernet directly connected to the RBR is the correct? 

 

It's so difficult to find the time to test in complete isolation as i have a family of people wanting internet.  However, for a period yesterday, I definitely tested a single RBR and single RBS set up with NOTHING else connected and we encountered the issue.

 

I wanted to narrow down troubleshooting as far as possible before suggesting something you might check into:

https://community.netgear.com/t5/Orbi-WiFi-6-AX-and-WiFi-6E-AXE/RBK-8-Series-Only-Unofficial-v4-6-6-11-Firmware-Experiences/m-p/2178954/highlight/true#M24956

Maybe worth trying...

 

That is the software I installed this morning.

 

My main problem I have now is that I am back to work tomorrow.  So i need to go back to something reliable (ish) which is my old RBK50 setup.

 

 

 

---

So after updating to v11 and factory reset set everything, the problem still happens? 

If so, I recommend you contact NG support and let them know about this. You may have faulty RBS that need to be replaced. Ask about RMA options.

Hi Furry, 

Yes, still continues to happen after new firmware and full ERASE / reset.

The other weird thing is that I tried it with both satelittes individually and both had the same problem. Can't believe both are faulty, unless the error is actually with the RBR.

I am still within warranty with the supplier, so I may try a straight forward replace with them as the first step.

Its a mystery.......

Ya I was thinking maybe the RBR could be at fault thinking about it. Just seemed that wireless the RBS worked but ethernet didn't.

If you have an opportunity to return and get another, i'd go that route for sure while you can. 

Yep, going to give that a go next.  Still within the time period to return so i will be no worse off.

Will report back in a few days :-)

👍

Hi Furry

I did have one further question for you if you dont mind.

Would yoube able to jot down the exact process you follow to reset the RBR/RBS.  In particular, the process to add a Satellite wirelessly and then convert to Ethernet Backhaul.

Since our discussions earlier in the chat, I have been using the ERASE button on the gui to restart the RBR, then holding the reset on the Satellites for 15-20 seconds.  No doubt following this process clearer resets the RBR better as it no longer "remembers" previously connected satellites.

However, when it comes to adding a satellite wirelessly, i dont know whether to do this as part of the initial set up phase or after the RBR is up and running.  Recently I have been skipping during the initial set up and adding subsequently.

The probem i find is that following the portal instructions when clicking "add satellite" never seems to work.  For starters the RBS NEVER goes to a "solid white" as it states it should in the instructions, then when i press the "sync" button on the RBS and click the sync on the portal this just whirs away for a few minutes then states it does not complete.

I find that the RBS eventually adds itself anyway, or with a reboot of the main router, it then picks it up OK.

Just wondered what your process is as I would like to do the set up in the exact same way that you do.

Thanks

Andy

A 15 second press on the RBS then release should work. When they start to pulsate white, I would turn them OFF. 

Then use the ERASE on the RBR and set it up from scratch. 

Once it's fully set up, bring the RBS near or in same room as the RBR. Turn one RBS ON and when the front LED starts to pulsate white, Press the sync button on the RBS then on the RBR. 

The front LED should eventually turn BLUE. Give it time, say a good 5 minutes. While the RBS is syncing you can have the RBRs web page open on the connected devices page and refresh the page. The RBS should appear here and show GOOD 5G status. 

Once the RBS front LED turns OFF, you can turn it OFF and do same thing for next RBS. 

I recommend setting a IP address reservation for each RBS on the RBRs web page. Under Advanced tab/Setup/Lan Setup.

Once both RBS have been wirelessly synced, you can put them back in there remote locations. 

Power On and let them come to ready and should auto sync to the RBR. 
Once RBS front LED has turned BLUE, you can leave it or connect the RBS one at a time to a ethernet connection. 

H Furry

Just thought i would post an update.  Had a busy day today.

Disconnected all LAN switches on my network and added the two satellites in wireless mode.  Because of the positioning of the RBS's they have configured in a daisy chain model.

The ONLY two wired connections are directly with the RBR.  One is my work laptop (could not let the dodgy wireless impact my work) and the other was the HUE hub as it needs to be an Ethernet connection.

The wireless devices show good connectivity when you review either the RBR or the RBS portal screens (the occasional Out of Sync message but not too often).  Both connecting at 5ghz.

Every few hours or so, the RBS devices would drop, when i jumped on the portal I would see the connectivity type changing from 5ghz to Wired, even though the is NO wired connection going into either of the RBS devices.  After a little while they would settle back to 5Ghz and things would settle down again.

I am in the process of getting the devices replaced, however, I just thought I would post this in case it rung a bell on any other issues you have seen in the past.

Cheers

Andy

Ok, seems like this system is faulty. I'd get them replaced ASAP. 

FURRYe38 

So... here is the latest and greatest.

I ran further tests over the last few days, with a variety of combinations of satelites (one and both) and wireless and Ethernet backhaul and CAT6 cables and locations and so on and so on and so on ad infinitum.

I also spent some time on a call to Netgear, and as nice as the guy was, his attempts for me to roll back the firmware failed (it kept auto upgrading) and also his configuration changes made no difference.  The issues kept happening and my satellites continue to drop.

So, today... a nice shiny new box arrived with 3 new RBR / RBS boxes.

I quickly set it up, using the same locations cables as before, BUT IMPORTANTLY, I did NOT perform the upgrade.  The boxes remain at V3.2.16.22_1.4.9.  I have been running through the entire day and have had no dropping issues like before.  Just a single day is longer than i have ever achieved befrore.

So... i now have the ultimate quandary!!!  Do I assume my previous fault was a hardware one, and upgrade my system to 4.6.3.16 and run the risk of my 3 shiny boxes becoming as useless as the three I had previously.  Or do I leave it as it is.

Deep down, i kinda know the answer, leaving it is not really an option as I dont want to be stuck with a Product that I cant upgrade.... but given all the bad feedback of 4.6.3.16 on the forums I am 99% certain that the moment I upgrade, my issues will be back.

What's your thoughts?  Given your experience of the forums?

Did you update the old system to v4.6.6.11? 

Hi...

yes, I started on 4.6.3.16.  Hit the issue.  Then upgraded to v4.6.6.11 and still hit the issues.

Now i am on V3.2.16.22_1.4.9 with the new hardware, it is working.

so the horrible situation of upgrading and it still fails and knowing i can never go back to v3.

or assume it genuinely was a hardware fault (i find that so unlikely)... and the upgrade could work!  

what to do what to do what to do

You can try this which is new on the older system:

https://community.netgear.com/t5/Orbi-WiFi-6-AX-and-WiFi-6E-AXE/New-RBR850-RBS850-Firmware-Version-v4-6-7-5-Released/m-p/2182138/highlight/true#M25415

If same thing still happens, I would presume the old system is just faulty. 

thanks FURRYe38 

Is there any indication from Netgear that this release is due to address some of the connectivity issues people have experienced?

I see you say there are no release notes.

I've asked for some more info. 

New FW should help resolve these issues we've been seeing this last year. 

I haven't loaded it yet but with this last v11, mine and others has been working WAY better than before. So I can only presume NG has taken the complaints to heart and fixing things. 

Hey FURRYe38 

How are you.

Been an emotional couple of days for me!

I tried my new hardware, as described previously.  And at version 3 it was working OK.  My plan yesterday was to reconnect all my old hardware and upgrade to v4.6.7.5.  Then see if the issue persisted.  However, when i woke up my new hardware had auto updated to the latest official version 4.6.3.16.  Therefore, i thought i might as well upgrade the new hardware to the 4.6.7.5.

I followed all the appropriate instructions and the upgrade went well.  For the entire day my network was performing perfectly.  No issues encountered at all, all devices were operating as expected.  I left an amazon radio playing all day (as this would aways stop when the satellites lost connectivity) and it played all day no issues.  In this instance, i had two satellites connected over ethernet backhaul.

Then, late at night, my daughter calls from upstairs and sure enough, the same issue was happening again.  Devices dropping from satellites.  I immediately checked the portals and sure enough, wired connections to the satellites were showing as 5ghz for brief moments and on the satellites themselves, the message:

Your WIFI Orbi Satellite connection is up and running.

had changed to:

Move your Orbi Satellite closer to your Orbi network to improve connection.

Exactly the same situation as the previous hardware experienced and software experienced.  

We now have to accept that this has something to do with either a) the firmware or b) something in my house causing the issue.  Although in this setup with the new hardware I had all my network back in play, Ethernet LAN connected etc... I think we can be confident this is not the issue as I have seen the problems when all of this has been disconnected.

It is worth pointing out that whilst we experience the issues, ALL Ethernet LAN connected devices (connected to either the satellites via switches or the main router via switches) continue to run perfectly.  In addition, ALL devices connected wirelessly directly to the router continue to operate normally.

So, i thought i would look at the log and I see a rediculous number of MAC address IP Allocation throught the night.  is this normal, I have showns an example below but this continues through the night when everyone is asleep an you can see the same devices getting addresses allocated even within the same minute:

[DHCP IP: (192.168.1.11)] to MAC address FA:C9:33:8C:35:76, Sunday, Jan 09,2022 06:51:39
[Admin login] from source 192.168.1.16, Sunday, Jan 09,2022 06:50:05
[DHCP IP: (192.168.1.16)] to MAC address E4:A7:A0:4C:A6:F8, Sunday, Jan 09,2022 06:48:31
[DHCP IP: (192.168.1.11)] to MAC address FA:C9:33:8C:35:76, Sunday, Jan 09,2022 06:47:52
[Admin login] from source 192.168.1.37, Sunday, Jan 09,2022 06:47:42
[DHCP IP: (192.168.1.25)] to MAC address 8E:B1:09:E4:B7:DB, Sunday, Jan 09,2022 06:47:13
[DHCP IP: (192.168.1.11)] to MAC address FA:C9:33:8C:35:76, Sunday, Jan 09,2022 06:47:12
[DHCP IP: (192.168.1.10)] to MAC address 8C:CE:4E:EB:F3:E3, Sunday, Jan 09,2022 06:47:10
[DHCP IP: (192.168.1.16)] to MAC address E4:A7:A0:4C:A6:F8, Sunday, Jan 09,2022 06:46:53
[DHCP IP: (192.168.1.16)] to MAC address E4:A7:A0:4C:A6:F8, Sunday, Jan 09,2022 06:46:27
[DHCP IP: (192.168.1.16)] to MAC address E4:A7:A0:4C:A6:F8, Sunday, Jan 09,2022 06:46:12
[DHCP IP: (192.168.1.28)] to MAC address 6C:CD:D6:E9:90:6E, Sunday, Jan 09,2022 06:46:04
[DHCP IP: (192.168.1.13)] to MAC address A8:03:2A:D9:16:68, Sunday, Jan 09,2022 06:46:04
[DHCP IP: (192.168.1.37)] to MAC address 3A:A8:7E:E7:FE:CE, Sunday, Jan 09,2022 06:46:00
[DHCP IP: (192.168.1.36)] to MAC address 6C:CD:D6:E9:90:42, Sunday, Jan 09,2022 06:45:51
[DHCP IP: (192.168.1.28)] to MAC address 6C:CD:D6:E9:90:6E, Sunday, Jan 09,2022 06:45:49
[DHCP IP: (192.168.1.36)] to MAC address 6C:CD:D6:E9:90:42, Sunday, Jan 09,2022 06:45:45
[DHCP IP: (192.168.1.28)] to MAC address 6C:CD:D6:E9:90:6E, Sunday, Jan 09,2022 06:45:45
[DHCP IP: (192.168.1.10)] to MAC address 8C:CE:4E:EB:F3:E3, Sunday, Jan 09,2022 06:45:42
[DHCP IP: (192.168.1.28)] to MAC address 6C:CD:D6:E9:90:6E, Sunday, Jan 09,2022 06:45:42
[DHCP IP: (192.168.1.36)] to MAC address 6C:CD:D6:E9:90:42, Sunday, Jan 09,2022 06:45:41
[DHCP IP: (192.168.1.28)] to MAC address 6C:CD:D6:E9:90:6E, Sunday, Jan 09,2022 06:45:40
[DHCP IP: (192.168.1.36)] to MAC address 6C:CD:D6:E9:90:42, Sunday, Jan 09,2022 06:45:39
[DHCP IP: (192.168.1.28)] to MAC address 6C:CD:D6:E9:90:6E, Sunday, Jan 09,2022 06:45:38
[DHCP IP: (192.168.1.36)] to MAC address 6C:CD:D6:E9:90:42, Sunday, Jan 09,2022 06:45:36
[DHCP IP: (192.168.1.28)] to MAC address 6C:CD:D6:E9:90:6E, Sunday, Jan 09,2022 06:45:35
[DHCP IP: (192.168.1.16)] to MAC address E4:A7:A0:4C:A6:F8, Sunday, Jan 09,2022 06:45:34
[DHCP IP: (192.168.1.36)] to MAC address 6C:CD:D6:E9:90:42, Sunday, Jan 09,2022 06:45:34
[DHCP IP: (192.168.1.28)] to MAC address 6C:CD:D6:E9:90:6E, Sunday, Jan 09,2022 06:45:33
[DHCP IP: (192.168.1.36)] to MAC address 6C:CD:D6:E9:90:42, Sunday, Jan 09,2022 06:45:33
[DHCP IP: (192.168.1.28)] to MAC address 6C:CD:D6:E9:90:6E, Sunday, Jan 09,2022 06:45:32
[DHCP IP: (192.168.1.10)] to MAC address 8C:CE:4E:EB:F3:E3, Sunday, Jan 09,2022 06:45:09
[DHCP IP: (192.168.1.11)] to MAC address FA:C9:33:8C:35:76, Sunday, Jan 09,2022 06:44:08
[DHCP IP: (192.168.1.64)] to MAC address AC:9B:0A:B4:1C:1D, Sunday, Jan 09,2022 06:42:47
[DHCP IP: (192.168.1.11)] to MAC address FA:C9:33:8C:35:76, Sunday, Jan 09,2022 06:42:07
[DHCP IP: (192.168.1.62)] to MAC address 56:26:0A:B7:42:66, Sunday, Jan 09,2022 06:39:29
[DHCP IP: (192.168.1.11)] to MAC address FA:C9:33:8C:35:76, Sunday, Jan 09,2022 06:38:39
[DHCP IP: (192.168.1.62)] to MAC address 56:26:0A:B7:42:66, Sunday, Jan 09,2022 06:38:38
[DHCP IP: (192.168.1.11)] to MAC address FA:C9:33:8C:35:76, Sunday, Jan 09,2022 06:38:06
[DHCP IP: (192.168.1.11)] to MAC address FA:C9:33:8C:35:76, Sunday, Jan 09,2022 06:36:06
[DHCP IP: (192.168.1.62)] to MAC address 56:26:0A:B7:42:66, Sunday, Jan 09,2022 06:35:36
[DHCP IP: (192.168.1.64)] to MAC address AC:9B:0A:B4:1C:1D, Sunday, Jan 09,2022 06:33:53
[DHCP IP: (192.168.1.11)] to MAC address FA:C9:33:8C:35:76, Sunday, Jan 09,2022 06:32:55
[DHCP IP: (192.168.1.25)] to MAC address 8E:B1:09:E4:B7:DB, Sunday, Jan 09,2022 06:31:44
[DHCP IP: (192.168.1.54)] to MAC address 34:3E:A4:88:FA:FB, Sunday, Jan 09,2022 06:29:01
[DHCP IP: (192.168.1.11)] to MAC address FA:C9:33:8C:35:76, Sunday, Jan 09,2022 06:26:51
[Admin login] from source 192.168.1.16, Sunday, Jan 09,2022 06:25:06
[DHCP IP: (192.168.1.16)] to MAC address E4:A7:A0:4C:A6:F8, Sunday, Jan 09,2022 06:24:25
[DHCP IP: (192.168.1.17)] to MAC address C6:CB:FC:41:63:F1, Sunday, Jan 09,2022 06:24:14
[DHCP IP: (192.168.1.37)] to MAC address 3A:A8:7E:E7:FE:CE, Sunday, Jan 09,2022 06:24:03
[DHCP IP: (192.168.1.37)] to MAC address 3A:A8:7E:E7:FE:CE, Sunday, Jan 09,2022 06:22:43
[DHCP IP: (192.168.1.62)] to MAC address 56:26:0A:B7:42:66, Sunday, Jan 09,2022 06:22:42
[DHCP IP: (192.168.1.11)] to MAC address FA:C9:33:8C:35:76, Sunday, Jan 09,2022 06:22:30
[DHCP IP: (192.168.1.17)] to MAC address C6:CB:FC:41:63:F1, Sunday, Jan 09,2022 06:22:09
[DHCP IP: (192.168.1.25)] to MAC address 8E:B1:09:E4:B7:DB, Sunday, Jan 09,2022 06:20:49
[DHCP IP: (192.168.1.17)] to MAC address C6:CB:FC:41:63:F1, Sunday, Jan 09,2022 06:20:26
[DHCP IP: (192.168.1.31)] to MAC address 74:E2:0C:B6:06:24, Sunday, Jan 09,2022 06:20:26
[DHCP IP: (192.168.1.36)] to MAC address 6C:CD:D6:E9:90:42, Sunday, Jan 09,2022 06:20:24
[DHCP IP: (192.168.1.13)] to MAC address A8:03:2A:D9:16:68, Sunday, Jan 09,2022 06:20:22
[DHCP IP: (192.168.1.28)] to MAC address 6C:CD:D6:E9:90:6E, Sunday, Jan 09,2022 06:20:18
[DHCP IP: (192.168.1.17)] to MAC address C6:CB:FC:41:63:F1, Sunday, Jan 09,2022 06:20:12
[DHCP IP: (192.168.1.28)] to MAC address 6C:CD:D6:E9:90:6E, Sunday, Jan 09,2022 06:20:11
[DHCP IP: (192.168.1.36)] to MAC address 6C:CD:D6:E9:90:42, Sunday, Jan 09,2022 06:20:10
[DHCP IP: (192.168.1.28)] to MAC address 6C:CD:D6:E9:90:6E, Sunday, Jan 09,2022 06:20:06
[DHCP IP: (192.168.1.36)] to MAC address 6C:CD:D6:E9:90:42, Sunday, Jan 09,2022 06:20:06
[DHCP IP: (192.168.1.4)] to MAC address 68:C6:3A:C0:2B:D3, Sunday, Jan 09,2022 06:20:05
[DHCP IP: (192.168.1.36)] to MAC address 6C:CD:D6:E9:90:42, Sunday, Jan 09,2022 06:20:02
[DHCP IP: (192.168.1.28)] to MAC address 6C:CD:D6:E9:90:6E, Sunday, Jan 09,2022 06:20:01
[DHCP IP: (192.168.1.36)] to MAC address 6C:CD:D6:E9:90:42, Sunday, Jan 09,2022 06:20:00
[DHCP IP: (192.168.1.28)] to MAC address 6C:CD:D6:E9:90:6E, Sunday, Jan 09,2022 06:19:59
[DHCP IP: (192.168.1.10)] to MAC address 8C:CE:4E:EB:F3:E3, Sunday, Jan 09,2022 06:19:59
[DHCP IP: (192.168.1.36)] to MAC address 6C:CD:D6:E9:90:42, Sunday, Jan 09,2022 06:19:58
[DHCP IP: (192.168.1.28)] to MAC address 6C:CD:D6:E9:90:6E, Sunday, Jan 09,2022 06:19:56
[DHCP IP: (192.168.1.36)] to MAC address 6C:CD:D6:E9:90:42, Sunday, Jan 09,2022 06:19:55
[DHCP IP: (192.168.1.28)] to MAC address 6C:CD:D6:E9:90:6E, Sunday, Jan 09,2022 06:19:53
[DHCP IP: (192.168.1.36)] to MAC address 6C:CD:D6:E9:90:42, Sunday, Jan 09,2022 06:19:52
[DHCP IP: (192.168.1.28)] to MAC address 6C:CD:D6:E9:90:6E, Sunday, Jan 09,2022 06:19:52
[DHCP IP: (192.168.1.4)] to MAC address 68:C6:3A:C0:2B:D3, Sunday, Jan 09,2022 06:19:51
[DHCP IP: (192.168.1.8)] to MAC address E6:57:51:C6:66:20, Sunday, Jan 09,2022 06:19:30

 I honestly cant think of anything else to try.  I feel this must be something to do with my environment.  But I am at a total loss of what to try next.  I do have another solution arriving today (and ASUS MESH system) and will quickly set that up and see if the same problems exist.  That will determine 100% that this is my house and not the netgear setup.

Anyway, another long message.  Welcome your thoughts.

If this is happening with two systems, either this is a FW issue or something at your location is causing this. I'm thinking something at your location...

Can you provide us a diagram of how the Orbi system is configured and connected? Please include the ISP modem and any and all LAN switches. Please put in a list of devices thats connected at the RBR and RBS. 

And distances between the RBR and RBS. 

What CAT# cabling are you using?