I have a modem/router connected to the ISP which is directly connected to an RBR50 and two RBS50 operating in AP mode. I've been having problems keeping the network up. Every few days at the same time (~5pm) most, but not all, WiFi devices lose connectivity and I have to power cycle. The only device that stays connected is the laptop using Cisco VPN.
Firmware: V2.7.1.60 (did a factory reset after updating the firmware on all 3 devices)
Router to S1 Distance: ~40 ft
Router to S2 Distance: ~20 ft
All three have ethernet via 1Gb unmanaged hubs
Daisy chain is disabled and device is in AP mode.
When I look in the UI, nothing is connecting to the satellites, but the connection between the satellites and router say they are good. One seems to be using the ethernet backhaul, but the other is using 5G. I refuse to put the Orbi in router mode, since we have a couple of devices that have to stay connected to the Internet, and the WiFi has been too flaky.
My question is, when I telnet in and type `satelliteinfo wifi`, I get back an empty list ("[ ]"). I've seen this sort of inconsistent behavior repeatedly across the Web UI and the App (which is a piece of junk that Orbi should just retire).
These devices were fast and stable for a few months, and then went bonkers on me, and with as little support as there is to debug what's going on, I'm about half a step from getting Ubiquiti devices and doing an Office Space on the Orbi in the backyard and post to Amazon to warn people about getting a WiFi AP that doesn't actually like doing WiFi.
Any suggestions? Before posting remember I've already updated the firmware and did a factory reset. Why does the commandline not show any connectivity between the router and the satellites?
My question is, when I telnet in and type `satelliteinfo wifi`, I get back an empty list ("[ ]"). I've seen this sort of inconsistent behavior repeatedly across the Web UI and the App (which is a piece of junk that Orbi should just retire).
My first impression is that 'satelliteinfo wifi' will report the WiFi connection status. As the two satellites are connected with ethernet, there is no WiFi connection status to report. This is easy to confirm. Unplug one of the satellite ethernet connections. Give the system at least five minutes to discover the link is down and bring the WiFi link back up. Then, telnet in again and check 'satelliteinfo wifi'
(Enabling ethernet backhaul on my Orbi involves dragging a 75' ethernet cord down the hall, down the stairs, across the room, etc. which the family finds entertaining for only a short time. [The CAT finds it fascinating forever.])
Every few days at the same time (~5pm) most, but not all, WiFi devices lose connectivity and I have to power cycle. The only device that stays connected is the laptop using Cisco VPN.
In Access Point (AP) mode, devices get their IP information (address, subnet mask, gateway, DNS server) from the router that the Orbi is connected to. If that router produces a log file, my first step would be to look in that log and see what is going on about 5pm. (When in router mode, the Orbi log file reports each time a device is assigned an IP using DHCP.) When I want to look at things like this, I use the Orbi 'debug page' to capture all internal and external traffic and then look at it using Wireshark. (http://orbilogin.net/debug.htm)
I cannot put my Orbi into AP mode, so I do not know if the Orbi debug log captures traffic the same way as when in router mode. If it does, I would look at the WAN capture and filter the Wireshark display by 'dhcp' to see if devices are asking for IP lease renewal about 5pm and not getting it.
I have a modem/router connected to the ISP which is directly connected to an RBR50 and two RBS50 operating in AP mode. I've been having problems keeping the network up. Every few days at the same time (~5pm) most, but not all, WiFi devices lose connectivity and I have to power cycle. The only device that stays connected is the laptop using Cisco VPN.
I neglected some other information gathering steps:
When devices lose connectivity, are you able to access the Orbi router and display "Attached Devices"? Or, does the Orbi itself appear to be "out of touch"?
Are any of these devices things you can interrogate? (i.e. laptops, PC's, smartphones, tablets) It would be useful to know what IP configuration the devices have when they are unable to communicate. For example, many devices revert to a "default" IP configuration when they cannot get what they need via DHCP, and this default setting simply will not do anything on a network. https://www.webopedia.com/TERM/A/APIPA.html
When devices lose connectivity, are you able to access the Orbi router and display "Attached Devices"? Or, does the Orbi itself appear to be "out of touch"?
The Orbi itself is also out of touch, even to an Ethernet connected laptop.
Are any of these devices things you can interrogate? (i.e. laptops, PC's, smartphones, tablets) It would be useful to know what IP configuration the devices have when they are unable to communicate.
They do lose their DHCP connection. It was much worse when I had it in router mode. In AP mode, some devices can stay connected.
In answer to a previous post, I will take a look at the CenturyLink router (AC3000) the next time there is an event to see if there are logs there, but the only thing that has shown up is that phones keep disconnecting and connecting, probably from going to sleep and waking up again. The AC3000 has a newer firmware, but I can't upgrade it for a week due to needing the internet uninterrupted during that time.
It's been fairly stable since the last time I posted, but we haven't been stressing the network as much. Will let you know if it recurs after Sunday.
I have a modem/router connected to the ISP which is directly connected to an RBR50 and two RBS50 operating in AP mode. I've been having problems keeping the network up. Every few days at the same time (~5pm) most, but not all, WiFi devices lose connectivity and I have to power cycle. The only device that stays connected is the laptop using Cisco VPN.
Firmware: V2.7.1.60 (did a factory reset after updating the firmware on all 3 devices)
Router to S1 Distance: ~40 ft
Router to S2 Distance: ~20 ft
All three have ethernet via 1Gb unmanaged hubs
Daisy chain is disabled and device is in AP mode.
When I look in the UI, nothing is connecting to the satellites, but the connection between the satellites and router say they are good. One seems to be using the ethernet backhaul, but the other is using 5G. I refuse to put the Orbi in router mode, since we have a couple of devices that have to stay connected to the Internet, and the WiFi has been too flaky.
My question is, when I telnet in and type `satelliteinfo wifi`, I get back an empty list ("[ ]"). I've seen this sort of inconsistent behavior repeatedly across the Web UI and the App (which is a piece of junk that Orbi should just retire).
These devices were fast and stable for a few months, and then went bonkers on me, and with as little support as there is to debug what's going on, I'm about half a step from getting Ubiquiti devices and doing an Office Space on the Orbi in the backyard and post to Amazon to warn people about getting a WiFi AP that doesn't actually like doing WiFi.
Any suggestions? Before posting remember I've already updated the firmware and did a factory reset. Why does the commandline not show any connectivity between the router and the satellites?
I really can't get them too much further away, and there is a heavy wooden cabinet and 3 walls between the two.
The firmware is 2.7.1.60 so it might be the arp storm, but the router hasn't picked that up yet. I'll try to get a wire sniffer on it sometime this weekend to see.
However, I think I found the problem. I had notified the issue happened when I would disconnect my MacBook from a USB-C hub with Ethernet (AUKEY USB C Hub 8-in-1). I only did this at night normally, but today had to disconnect around lunchtime and the same issue occurred. It turns out others are complaining that the Ethernet on this device is "dangerously unstable" and also noted the same issue of losing the entire network. I guess I'm going to have to get a different usb-c hub. I'll update in another week on the results of not using the device.
