NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
ORBI RBR50/RBS50 lost Internet connection (FW v2.5.0.38)
SW_ wrote: Feature/Security vs. Stability/Usability? ... A quick and effective way to recover from this Orbi split brain problem is to reboot the Orbi, but that solution would only last a day or ...
Forcing Orbi (AP Mode) to use fixed IP Address, which was a reserved IP Address on the Asus Router, seems to be the answer for me.
Logs:
====
[admin login] from source 192.168.1.100, Tuesday, October 29, 2019 09:16:12
[Time synchronized with NTP server] Monday, October 28, 2019 09:45:37
[admin login failure] from source 192.168.1.100, Monday, October 28, 2019 08:21:33
[admin login] from source 192.168.1.100, Monday, October 28, 2019 08:19:42
[admin login failure] from source 192.168.1.100, Sunday, October 27, 2019 22:41:40
[admin login] from source 192.168.1.100, Sunday, October 27, 2019 22:21:04
[admin login failure] from source 192.168.1.100, Sunday, October 27, 2019 22:06:41
[admin login] from source 192.168.1.100, Sunday, October 27, 2019 21:57:29
[admin login failure] from source 192.168.1.40, Sunday, October 27, 2019 15:23:59
[admin login] from source 192.168.1.40, Sunday, October 27, 2019 15:22:41
[admin login failure] from source 192.168.1.40, Sunday, October 27, 2019 14:55:27
[admin login] from source 192.168.1.40, Sunday, October 27, 2019 14:45:37
[admin login] from source 192.168.1.40, Sunday, October 27, 2019 14:37:39
[admin login] from source 192.168.1.40, Sunday, October 27, 2019 13:55:10
[admin login failure] from source 192.168.1.40, Sunday, October 27, 2019 13:16:28
[admin login] from source 192.168.1.40, Sunday, October 27, 2019 13:08:00
[admin login] from source 192.168.1.40, Sunday, October 27, 2019 13:07:32
[Time synchronized with NTP server] Sunday, October 27, 2019 09:45:36
[admin login failure] from source 192.168.1.40, Sunday, October 27, 2019 09:15:23
[admin login] from source 192.168.1.40, Sunday, October 27, 2019 09:06:00
[admin login failure] from source 192.168.1.40, Sunday, October 27, 2019 08:51:04
[admin login] from source 192.168.1.40, Sunday, October 27, 2019 08:45:54
[admin login failure] from source 192.168.1.100, Saturday, October 26, 2019 22:09:27
[admin login] from source 192.168.1.100, Saturday, October 26, 2019 21:58:03
[admin login failure] from source 192.168.1.100, Saturday, October 26, 2019 21:45:12
[admin login] from source 192.168.1.100, Saturday, October 26, 2019 21:41:26
[admin login failure] from source 192.168.1.40, Saturday, October 26, 2019 20:12:42
[admin login] from source 192.168.1.40, Saturday, October 26, 2019 20:09:44
[admin login failure] from source 192.168.1.40, Saturday, October 26, 2019 18:36:56
[admin login] from source 192.168.1.40, Saturday, October 26, 2019 18:26:00
[admin login] from source 192.168.1.40, Saturday, October 26, 2019 17:28:17
[admin login] from source 192.168.1.40, Saturday, October 26, 2019 16:11:56
[admin login] from source 192.168.1.40, Saturday, October 26, 2019 13:48:33
[admin login failure] from source 192.168.1.40, Saturday, October 26, 2019 10:38:02
[admin login] from source 192.168.1.40, Saturday, October 26, 2019 10:36:27
[admin login failure] from source 192.168.1.40, Saturday, October 26, 2019 10:36:09
[admin login] from source 192.168.1.40, Saturday, October 26, 2019 10:33:16
[admin login failure] from source 192.168.1.40, Saturday, October 26, 2019 10:18:55
[admin login] from source 192.168.1.40, Saturday, October 26, 2019 10:16:54
[admin login failure] from source 192.168.1.40, Saturday, October 26, 2019 09:55:29
[admin login] from source 192.168.1.40, Saturday, October 26, 2019 09:46:02
[Time synchronized with NTP server] Saturday, October 26, 2019 09:45:34
[Initialized, firmware version: V2.5.0.38] Saturday, October 26, 2019 09:45:10
Please start your debug log capture along with Enable LAN/WAN Packet Capture on the RBR:
You can start the RBS debug capture aswell. Reproduce this again and immediately go in and select Save Debug Log button on the RBR and RBS debug web page. Then send off to NG support.
This is not a complex setup and if NG can't replicate this issue in house, that will be really scary!
The simple test setup:
=================
1. Orbi RBR50 in Router or AP Mode
2. Daisy-Chain disabled /w 3 Advanced WiFi featured check boxes ticked/enabled
3. NAS/Wired clients connected to Satellite-1 via NG switch
4. Wireless Nest IoT devices/doorbell camera connected to Orbi Router or Orbi Satellites
5. Start Amazon/Netflix streaming traffics to all the Orbi boxes for 48-hours...
Monitor the status of IoT devices, streaming clients, and Orbi logs and verify that there's no issue, i.e. missing log from previous days or notification about Nest doorbell camera going offline. This is one of the test cases that I would expect from NG QA to perform prior to releasing new FW.
Forcing Orbi (AP Mode) to use fixed IP Address, which was a reserved IP Address on the Asus Router, seems to be the answer for me.
Logs:
====
[admin login] from source 192.168.1.100, Tuesday, October 29, 2019 09:16:12
[Time synchronized with NTP server] Monday, October 28, 2019 09:45:37
[admin login failure] from source 192.168.1.100, Monday, October 28, 2019 08:21:33
[admin login] from source 192.168.1.100, Monday, October 28, 2019 08:19:42
[admin login failure] from source 192.168.1.100, Sunday, October 27, 2019 22:41:40
[admin login] from source 192.168.1.100, Sunday, October 27, 2019 22:21:04
[admin login failure] from source 192.168.1.100, Sunday, October 27, 2019 22:06:41
[admin login] from source 192.168.1.100, Sunday, October 27, 2019 21:57:29
[admin login failure] from source 192.168.1.40, Sunday, October 27, 2019 15:23:59
[admin login] from source 192.168.1.40, Sunday, October 27, 2019 15:22:41
[admin login failure] from source 192.168.1.40, Sunday, October 27, 2019 14:55:27
[admin login] from source 192.168.1.40, Sunday, October 27, 2019 14:45:37
[admin login] from source 192.168.1.40, Sunday, October 27, 2019 14:37:39
[admin login] from source 192.168.1.40, Sunday, October 27, 2019 13:55:10
[admin login failure] from source 192.168.1.40, Sunday, October 27, 2019 13:16:28
[admin login] from source 192.168.1.40, Sunday, October 27, 2019 13:08:00
[admin login] from source 192.168.1.40, Sunday, October 27, 2019 13:07:32
[Time synchronized with NTP server] Sunday, October 27, 2019 09:45:36
[admin login failure] from source 192.168.1.40, Sunday, October 27, 2019 09:15:23
[admin login] from source 192.168.1.40, Sunday, October 27, 2019 09:06:00
[admin login failure] from source 192.168.1.40, Sunday, October 27, 2019 08:51:04
[admin login] from source 192.168.1.40, Sunday, October 27, 2019 08:45:54
[admin login failure] from source 192.168.1.100, Saturday, October 26, 2019 22:09:27
[admin login] from source 192.168.1.100, Saturday, October 26, 2019 21:58:03
[admin login failure] from source 192.168.1.100, Saturday, October 26, 2019 21:45:12
[admin login] from source 192.168.1.100, Saturday, October 26, 2019 21:41:26
[admin login failure] from source 192.168.1.40, Saturday, October 26, 2019 20:12:42
[admin login] from source 192.168.1.40, Saturday, October 26, 2019 20:09:44
[admin login failure] from source 192.168.1.40, Saturday, October 26, 2019 18:36:56
[admin login] from source 192.168.1.40, Saturday, October 26, 2019 18:26:00
[admin login] from source 192.168.1.40, Saturday, October 26, 2019 17:28:17
[admin login] from source 192.168.1.40, Saturday, October 26, 2019 16:11:56
[admin login] from source 192.168.1.40, Saturday, October 26, 2019 13:48:33
[admin login failure] from source 192.168.1.40, Saturday, October 26, 2019 10:38:02
[admin login] from source 192.168.1.40, Saturday, October 26, 2019 10:36:27
[admin login failure] from source 192.168.1.40, Saturday, October 26, 2019 10:36:09
[admin login] from source 192.168.1.40, Saturday, October 26, 2019 10:33:16
[admin login failure] from source 192.168.1.40, Saturday, October 26, 2019 10:18:55
[admin login] from source 192.168.1.40, Saturday, October 26, 2019 10:16:54
[admin login failure] from source 192.168.1.40, Saturday, October 26, 2019 09:55:29
[admin login] from source 192.168.1.40, Saturday, October 26, 2019 09:46:02
[Time synchronized with NTP server] Saturday, October 26, 2019 09:45:34
[Initialized, firmware version: V2.5.0.38] Saturday, October 26, 2019 09:45:10