NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi RBR50 + satellite drop internet over and over
Help! I am not tremendously computer literate but I bought Orbi system and 1 satellite in dec.2017 as supposed upgrade and to get better WiFi extension through whole house. This is second time I am h...
Hi FURRYe38, Thanks for the concern, but I'm done with spending any more time troubleshooting problems for Netgear. I've read thru all the forums, tried all the suggestions and still end up having the same issues. It may run for a few days or fail just after logging out of the setup wizard from a factory reset. I've spent literally 20-30 hours trying to isolate the problem. I'm a retired engineer from Lockheed Martin and have been programming computers since the CP/M-86 days. Netgear has a problem with their firmware, some setups work fine and others fail. Mine, unfortunately, fails with any update above 2.1.1.16 that was released in December. If I could just stop the auto updates I would be happy but unfortunately, Netgear forces this issue. This was my first personal Netgear product and will be my last. I'm sure they will solve the problem eventually but I'm done problem-solving.
Best regards,
Don
Update:
While working on the PC this morning, the Orbi network internet failed once again. I checked internet access via the router login; the internet status says GOOD, which it's false. I connected to the MoFI LTE Modem WiFi internet the internet works and modem status is ok. I just reflashed to V2.1.1.16 yesterday. Below are the logs after the Orbi auto updated to V2.1.4.10 when the internet failed. After that I restored it version V2.1.1.16 and everthing works as it should. The log says a DoS Attack is the problem using V2.1.4.10, but I don't have this problem when I flash back to V2.1.1.16. The many different IP's are cameras, PC's, TV's, Google Home, etc.
RBR50
Firmware Version V2.1.1.16
GUI Language Version V1.0.0.309
Operation Mode Router
LAN Port
MAC Address 0x:0x:8x:9x:5x:CA
IP Address 192.168.1.1
Reflashed back to 2.1.1.16 after auto update.
After flashing back to V2.1.1.16
[admin login] from source 192.168.1.23, Tuesday, May 29, 2018 05:50:18
[Time synchronized with NTP server] Tuesday, May 29, 2018 05:50:15
[DoS Attack: ACK Scan] from source: 77.234.41.34, port 80, Tuesday, May 29, 2018 05:49:37
[Initialized, firmware version: V2.1.1.16] Tuesday, May 29, 2018 05:48:56
Auto update to 2.1.4.10
[admin login] from source 192.168.1.23, Tuesday, May 29, 2018 05:42:45
[DoS Attack: ARP Attack] from source: 192.168.1.8, Tuesday, May 29, 2018 05:34:59
[DoS Attack: ARP Attack] from source: 192.168.1.136, Tuesday, May 29, 2018 05:34:58
[DoS Attack: ARP Attack] from source: 192.168.1.7, Tuesday, May 29, 2018 05:34:53
[DoS Attack: ARP Attack] from source: 192.168.49.1, Tuesday, May 29, 2018 05:34:52
[DoS Attack: ARP Attack] from source: 192.168.1.35, Tuesday, May 29, 2018 05:34:50
[DoS Attack: ARP Attack] from source: 192.168.1.128, Tuesday, May 29, 2018 05:34:49
[DoS Attack: ARP Attack] from source: 192.168.1.23, Tuesday, May 29, 2018 05:34:48
[DoS Attack: ARP Attack] from source: 192.168.1.35, Tuesday, May 29, 2018 05:34:47
[DoS Attack: ARP Attack] from source: 192.168.1.7, Tuesday, May 29, 2018 05:34:46
[DoS Attack: ARP Attack] from source: 192.168.1.136, Tuesday, May 29, 2018 05:34:45
[DoS Attack: ARP Attack] from source: 192.168.1.8, Tuesday, May 29, 2018 05:34:44
[DoS Attack: ARP Attack] from source: 192.168.1.136, Tuesday, May 29, 2018 05:34:43
[DoS Attack: ARP Attack] from source: 192.168.1.8, Tuesday, May 29, 2018 05:34:42
[DoS Attack: ARP Attack] from source: 192.168.1.136, Tuesday, May 29, 2018 05:34:41
[DoS Attack: ARP Attack] from source: 192.168.1.128, Tuesday, May 29, 2018 05:34:40
[DoS Attack: ARP Attack] from source: 192.168.1.8, Tuesday, May 29, 2018 05:34:39
[DoS Attack: ARP Attack] from source: 192.168.1.23, Tuesday, May 29, 2018 05:34:38
[DoS Attack: ARP Attack] from source: 192.168.1.8, Tuesday, May 29, 2018 05:34:37
[DoS Attack: ARP Attack] from source: 192.168.1.35, Tuesday, May 29, 2018 05:34:36
[DoS Attack: ARP Attack] from source: 192.168.1.23, Tuesday, May 29, 2018 05:34:35
[DoS Attack: ARP Attack] from source: 192.168.1.136, Tuesday, May 29, 2018 05:34:34
[DoS Attack: ARP Attack] from source: 192.168.1.8, Tuesday, May 29, 2018 05:34:33
[DoS Attack: ARP Attack] from source: 192.168.1.8, Tuesday, May 29, 2018 05:34:32
[DoS Attack: ARP Attack] from source: 192.168.1.8, Tuesday, May 29, 2018 05:34:31
[DoS Attack: ARP Attack] from source: 192.168.1.8, Tuesday, May 29, 2018 05:34:30
[DoS Attack: ARP Attack] from source: 192.168.1.3, Tuesday, May 29, 2018 05:34:29
[DoS Attack: ARP Attack] from source: 192.168.1.136, Tuesday, May 29, 2018 05:34:28
[DoS Attack: ARP Attack] from source: 192.168.1.8, Tuesday, May 29, 2018 05:34:27
[DoS Attack: ARP Attack] from source: 192.168.1.8, Tuesday, May 29, 2018 05:34:26
[DoS Attack: ARP Attack] from source: 192.168.1.8, Tuesday, May 29, 2018 05:34:25
[Time synchronized with NTP server] Tuesday, May 29, 2018 05:34:23
[DoS Attack: ARP Attack] from source: 192.168.1.35, Tuesday, May 29, 2018 05:34:23
[DoS Attack: ARP Attack] from source: 192.168.1.7, Tuesday, May 29, 2018 05:34:21
[DoS Attack: ARP Attack] from source: 192.168.1.7, Tuesday, May 29, 2018 05:34:20
[DoS Attack: ARP Attack] from source: 192.168.1.7, Tuesday, May 29, 2018 05:34:19
[DoS Attack: ARP Attack] from source: 192.168.1.8, Tuesday, May 29, 2018 05:34:18
[DoS Attack: ARP Attack] from source: 192.168.1.8, Tuesday, May 29, 2018 05:34:17
[DoS Attack: ARP Attack] from source: 192.168.1.7, Tuesday, May 29, 2018 05:34:16
[DoS Attack: ARP Attack] from source: 192.168.1.23, Tuesday, May 29, 2018 05:34:15
[DoS Attack: ARP Attack] from source: 192.168.1.8, Tuesday, May 29, 2018 05:34:14
[DoS Attack: ARP Attack] from source: 192.168.1.8, Tuesday, May 29, 2018 05:34:13
[DoS Attack: ARP Attack] from source: 192.168.1.8, Tuesday, May 29, 2018 05:34:12
[DoS Attack: ARP Attack] from source: 192.168.1.8, Tuesday, May 29, 2018 05:34:11
[DoS Attack: ARP Attack] from source: 192.168.1.8, Tuesday, May 29, 2018 05:34:10
[WLAN access rejected: incorrect security] from MAC address c4:e9:84:79:d9:65, Tuesday, May 29, 2018 05:34:09
[DoS Attack: ARP Attack] from source: 192.168.1.8, Tuesday, May 29, 2018 05:34:09
[DoS Attack: ARP Attack] from source: 192.168.1.8, Tuesday, May 29, 2018 05:34:08
[DoS Attack: ARP Attack] from source: 192.168.1.8, Tuesday, May 29, 2018 05:34:07
[DoS Attack: ARP Attack] from source: 192.168.1.23, Tuesday, May 29, 2018 05:34:06
[DoS Attack: ARP Attack] from source: 192.168.1.35, Tuesday, May 29, 2018 05:34:05
[DoS Attack: ARP Attack] from source: 192.168.1.35, Tuesday, May 29, 2018 05:34:04
[DoS Attack: ARP Attack] from source: 192.168.1.136, Tuesday, May 29, 2018 05:34:02
[DoS Attack: ARP Attack] from source: 192.168.1.8, Tuesday, May 29, 2018 05:34:01
[DoS Attack: ARP Attack] from source: 192.168.1.136, Tuesday, May 29, 2018 05:34:00
[DoS Attack: ARP Attack] from source: 192.168.1.35, Tuesday, May 29, 2018 05:33:59
[DoS Attack: ARP Attack] from source: 192.168.1.8, Tuesday, May 29, 2018 05:33:58
[DoS Attack: ARP Attack] from source: 192.168.1.8, Tuesday, May 29, 2018 05:33:57
[DoS Attack: ARP Attack] from source: 192.168.1.136, Tuesday, May 29, 2018 05:33:56
[DoS Attack: ARP Attack] from source: 192.168.1.136, Tuesday, May 29, 2018 05:33:55
[DoS Attack: ARP Attack] from source: 192.168.1.136, Tuesday, May 29, 2018 05:33:54
[DoS Attack: ARP Attack] from source: 192.168.1.136, Tuesday, May 29, 2018 05:33:53
[DoS Attack: ARP Attack] from source: 192.168.1.136, Tuesday, May 29, 2018 05:33:52
[DoS Attack: RST Scan] from source: 172.217.0.163, port 443, Tuesday, May 29, 2018 05:33:36
[DoS Attack: RST Scan] from source: 216.58.219.142, port 443, Tuesday, May 29, 2018 05:33:34
[DoS Attack: RST Scan] from source: 172.217.3.67, port 443, Tuesday, May 29, 2018 05:33:24
[admin login] from source 192.168.1.23, Tuesday, May 29, 2018 05:33:23
[Initialized, firmware version: V2.1.4.10] Tuesday, May 29, 2018 05:33:03
Update:
If I disconnect the satellite from the wired back haul it woks as it should- No DoS attacks or internet loss. I have the satellite in a metal building, which works fair as long as the shop doors are fully open. Once the doors are shut there is no siginal via the 5.G back haul channel. WiFi calling fails traveling from the office to the shop or vice versa unless I use the wired back haul. Something in the updated firmware is causing this problem with wired back haul as V2.1.1.16 does not have them issue.
- I was having similar issues where my Orbi RB50 would not provide stable WiFi connection. After one week of troubleshooting and replacing modem and Orbi, level 2 support provided me with a beta firmware which seems to have fixed the problem.
You might make contact with NG support and ask them about any available beta FW that would help for this...
MudMan wrote:
Update:
If I disconnect the satellite from the wired back haul it woks as it should- No DoS attacks or internet loss. I have the satellite in a metal building, which works fair as long as the shop doors are fully open. Once the doors are shut there is no siginal via the 5.G back haul channel. WiFi calling fails traveling from the office to the shop or vice versa unless I use the wired back haul. Something in the updated firmware is causing this problem with wired back haul as V2.1.1.16 does not have them issue.
Thanks again FURRYe38,
Evidently I've been BETA testing for Netgear all this time. I have already purchased another MESH product that works great.
Best Regards,
Don
FURRYe38 wrote:
Enjoy and good luck. :smileywink:
MudMan wrote:
Thanks again FURRYe38,
Grumpa48
CURIOUS - has Netgear manned up yet? I am living the same problem every day - Orbi worked for 11 months, updated to latest firmware and now it drops service. ISP has been here twice, tested their signal - all, ok. Orbi shows Wifi but drops the internet whenever it decides to. Am I a $300 BETA tester? If so, warn me next time and I will buy something that works.
Whats the problem? Need more details...
What FW is currently loaded?
What is the Mfr and model# of the IP modem the Orbi is connected too?
=
What is the size of your home? Sq Ft?
What is the distance between the router and satellite(s)? 30 feet is recommended in between them to begin with depending upon building materials.
What channels are you using? Auto? Try setting manual channel 1, 6 or 11 on 2.4Ghz and any unused channel on 5Ghz.
Any Wifi Neighbors near by? If so, how many?
Try disabling the following and see:
MIMO, Daisy Chain, Fast Roaming, IPv6 and Set 20/40Mhz Coexistence to 40Mhz only. Save settings and reboot the router and satellite(s).
Grumpa48 wrote:
CURIOUS - has Netgear manned up yet? I am living the same problem every day - Orbi worked for 11 months, updated to latest firmware and now it drops service. ISP has been here twice, tested their signal - all, ok. Orbi shows Wifi but drops the internet whenever it decides to. Am I a $300 BETA tester? If so, warn me next time and I will buy something that works.
Thanks for the reply and concern. I sold the Netgear ORBI many months ago because of the problems and switched to the Google WiFI three puck MESH. I'm very happy with the Google WiFI MESH system and have not had one problem since I switched.
