(RBK50) Wifi devices randomly don't recieve data for short periods of time.

---

KobeW50 wrote:
So there's no AP mode or any of that.

---

In the current setup:

• There is one RBR50 router connected to the Internet Service Provider device.
  This router is broadcasting WiFi.
• There is another RBR50 router  connected to the first router using an Ethernet cable.
  This second router is also in the default 'router mode.'
• There are two RBS50 satellites, which are connected using WiFi to....which router?
  The first one, the second one, or perhaps one to each?

Putting the second router into Access Point (AP) mode achieved one goal:  all devices, both wired and WiFi, are in one IP subnet.  The first router assigns IP addresses to every device.

If router number two is now in 'router' mode, then it really matters which Orbi device they connect to. Sometimes they may be able to communicate with other devices because they are in the same IP subnet, and other times they cannot because they are in a different IP subnet.  With both routers using the same WiFi credentials, devices may connect to one router and then switch to the other router. It is really unpredictable.

If the only usage is to access the internet, then this would not even be noticed.

What this sounds like is a service disruption from the ISP.  (They will almost certainly deny it.)  There have been recorded instances of faulty cable wiring causing errors that mysteriously "went away" when the drop cables were replaced.  This may be a suitable problem for a "divide and conquer" approach.

• If the ISP connection is unreliable, no amount of changing the router network will help.
• If the ISP connection is rock solid, that points at the local network.

One tool that might be useful is to record the reliability of the ISP connection over a period of time using something like PingInfoView by Nirsoft (free) https://www.nirsoft.net/utils/multiple_ping_tool.html Set the program to ping three common DNS servers, such as Google (8.8.8.8), Cloudflare (1.1.1.1) and OpenDNS (208.67.222.222) once every second.  As long as the ISP connection is good, the counters should march up steadily. (I have run it for an entire week.)  If some devices are being frozen for 5-10 seconds, then there should be instances of "failures to respond".  I used the Advanced Options to record the failures to a file.  DNS uses UDP packets, which are not 100% reliable.  It is not unexpected to have a failure now and then.  But regular instances of 4-5 failures in a row.... Not Good.