This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
I'm having the same rebooting issue, I recevied my RBK50 yesterday (bought through Amazon USA) and it's been rebooting ever since I set it up. I tried everything but to no avail, I hope this won't be a hardware issue since it might cost me a lot to send back the unit to Amazon US cause I live in the Middle East.
I'm having the same rebooting issue, I recevied my RBK50 yesterday (bought through Amazon USA) and it's been rebooting ever since I set it up. I tried everything but to no avail, I hope this won't be a hardware issue since it might cost me a lot to send back the unit to Amazon US cause I live in the Middle East.
I'm having the same rebooting issue, I recevied my RBK50 yesterday (bought through Amazon USA) and it's been rebooting ever since I set it up. I tried everything but to no avail, I hope this won't be a hardware issue since it might cost me a lot to send back the unit to Amazon US cause I live in the Middle East.
Try to change the Orbi region from US to Middle East and see if it makes a difference.
The power adapter is rated for 110-240volts so that's not the issue. Also, I highly doubt this issue has anything to do with the router region being set to North America, i'm using the standard 2.4GHz channels and 36 for 5GHz.
I'm having the same rebooting issue, I recevied my RBK50 yesterday (bought through Amazon USA) and it's been rebooting ever since I set it up. I tried everything but to no avail, I hope this won't be a hardware issue since it might cost me a lot to send back the unit to Amazon US cause I live in the Middle East.
Try to change the Orbi region from US to Middle East and see if it makes a difference.
Changed the region to ME but the problem remains 😞
I noticed the router logging a lot of DoS Attack events, here's an example:
[DoS Attack: SYN/ACK Scan] from source: 178.248.232.65, port 443, Saturday, December 21, 2019 00:50:22 [DoS Attack: ARP Attack] from source: 192.168.1.6, Saturday, December 21, 2019 00:41:34 [DoS Attack: RST Scan] from source: 203.205.239.188, port 80, Saturday, December 21, 2019 00:37:58
Those log entries meant the Orbi is doing its job, not the source for reboot. Is there anything else in the log other than those?
Do you have any wired clients attached to Orbi or Satellite LAN ports? If yes, remove all of them. If the reboot still happens, shutdown the Satellite and see if that makes a difference.
...and for good measure, please get a new cat5e/cat6 cable and swap it with the current cable, which is connecting Orbi yellow WAN port to ISP box.
I unplugged the satellite, had no other clients connected using ethernet, changed the cable, still reboots. Here's the last log I copied before it restarted the last time:
[DHCP IP: 192.168.1.7] to MAC address 90:61:ae:aa:c2:60, Saturday, December 21, 2019 02:23:38 [admin login] from source 192.168.1.7, Saturday, December 21, 2019 02:22:09 [DHCP IP: 192.168.1.7] to MAC address 90:61:ae:aa:c2:60, Saturday, December 21, 2019 02:21:15 [DoS Attack: Teardrop] from source: 134.0.216.42, Saturday, December 21, 2019 02:20:19 [DoS Attack: Jolt2] from source: 134.0.216.42, Saturday, December 21, 2019 02:20:19 [DoS Attack: Teardrop] from source: 134.0.216.42, Saturday, December 21, 2019 02:20:18 [DoS Attack: Jolt2] from source: 134.0.216.42, Saturday, December 21, 2019 02:20:18 [DoS Attack: Teardrop] from source: 134.0.216.42, Saturday, December 21, 2019 02:20:17 [DoS Attack: Jolt2] from source: 134.0.216.42, Saturday, December 21, 2019 02:20:17 [DoS Attack: Teardrop] from source: 134.0.216.42, Saturday, December 21, 2019 02:20:16 [DoS Attack: Jolt2] from source: 134.0.216.42, Saturday, December 21, 2019 02:20:16 [DoS Attack: Teardrop] from source: 134.0.216.42, Saturday, December 21, 2019 02:20:15 [DoS Attack: Jolt2] from source: 134.0.216.42, Saturday, December 21, 2019 02:20:15 [DoS Attack: Teardrop] from source: 134.0.216.42, Saturday, December 21, 2019 02:20:14 [DoS Attack: Jolt2] from source: 134.0.216.42, Saturday, December 21, 2019 02:20:14 [DoS Attack: Teardrop] from source: 134.0.216.42, Saturday, December 21, 2019 02:20:13 [DoS Attack: Jolt2] from source: 134.0.216.42, Saturday, December 21, 2019 02:20:13 [DoS Attack: Teardrop] from source: 134.0.216.42, Saturday, December 21, 2019 02:20:12 [DoS Attack: Jolt2] from source: 134.0.216.42, Saturday, December 21, 2019 02:20:12 [DoS Attack: Teardrop] from source: 134.0.216.42, Saturday, December 21, 2019 02:20:11 [DoS Attack: Jolt2] from source: 134.0.216.42, Saturday, December 21, 2019 02:20:11 [DoS Attack: Teardrop] from source: 134.0.216.42, Saturday, December 21, 2019 02:20:10 [DoS Attack: Jolt2] from source: 134.0.216.42, Saturday, December 21, 2019 02:20:10 [DoS Attack: Teardrop] from source: 134.0.216.42, Saturday, December 21, 2019 02:20:09 [DoS Attack: Jolt2] from source: 134.0.216.42, Saturday, December 21, 2019 02:20:09 [DoS Attack: Teardrop] from source: 134.0.216.42, Saturday, December 21, 2019 02:20:08 [DoS Attack: Jolt2] from source: 134.0.216.42, Saturday, December 21, 2019 02:20:08 [DoS Attack: Teardrop] from source: 134.0.216.42, Saturday, December 21, 2019 02:20:07 [DoS Attack: Jolt2] from source: 134.0.216.42, Saturday, December 21, 2019 02:20:07 [DoS Attack: Teardrop] from source: 134.0.216.42, Saturday, December 21, 2019 02:20:06 [DoS Attack: Jolt2] from source: 134.0.216.42, Saturday, December 21, 2019 02:20:06 [DoS Attack: Teardrop] from source: 134.0.216.42, Saturday, December 21, 2019 02:20:05 [DoS Attack: Jolt2] from source: 134.0.216.42, Saturday, December 21, 2019 02:20:05 [DoS Attack: Teardrop] from source: 134.0.216.42, Saturday, December 21, 2019 02:20:04 [DoS Attack: Jolt2] from source: 134.0.216.42, Saturday, December 21, 2019 02:20:04 [DoS Attack: Teardrop] from source: 134.0.216.42, Saturday, December 21, 2019 02:20:03 [DoS Attack: Jolt2] from source: 134.0.216.42, Saturday, December 21, 2019 02:20:03 [DoS Attack: Teardrop] from source: 134.0.216.42, Saturday, December 21, 2019 02:20:02 [DoS Attack: Jolt2] from source: 134.0.216.42, Saturday, December 21, 2019 02:20:02 [DoS Attack: Teardrop] from source: 134.0.216.42, Saturday, December 21, 2019 02:20:01 [DoS Attack: Jolt2] from source: 134.0.216.42, Saturday, December 21, 2019 02:20:01 [DoS Attack: Teardrop] from source: 134.0.216.42, Saturday, December 21, 2019 02:20:00 [DoS Attack: Jolt2] from source: 134.0.216.42, Saturday, December 21, 2019 02:20:00 [DoS Attack: Teardrop] from source: 134.0.216.42, Saturday, December 21, 2019 02:19:59 [DoS Attack: Jolt2] from source: 134.0.216.42, Saturday, December 21, 2019 02:19:59 [DoS Attack: Teardrop] from source: 134.0.216.42, Saturday, December 21, 2019 02:19:58 [DoS Attack: Jolt2] from source: 134.0.216.42, Saturday, December 21, 2019 02:19:58 [DoS Attack: Teardrop] from source: 134.0.216.42, Saturday, December 21, 2019 02:19:57 [DoS Attack: Jolt2] from source: 134.0.216.42, Saturday, December 21, 2019 02:19:57 [DoS Attack: Teardrop] from source: 134.0.216.42, Saturday, December 21, 2019 02:19:56 [DoS Attack: Jolt2] from source: 134.0.216.42, Saturday, December 21, 2019 02:19:56 [DoS Attack: Teardrop] from source: 134.0.216.42, Saturday, December 21, 2019 02:19:55 [DoS Attack: SYN/ACK Scan] from source: 159.69.54.223, port 443, Saturday, December 21, 2019 02:19:36 [DHCP IP: 192.168.1.8] to MAC address 94:7b:e7:86:87:e5, Saturday, December 21, 2019 02:15:13 [DHCP IP: 192.168.1.7] to MAC address 90:61:ae:aa:c2:60, Saturday, December 21, 2019 02:15:00 [DHCP IP: 192.168.1.6] to MAC address 00:9e:c8:b5:98:63, Saturday, December 21, 2019 02:14:43 [DHCP IP: 192.168.1.4] to MAC address 28:80:88:ef:d2:0f, Saturday, December 21, 2019 02:14:30 [admin login] from source 192.168.1.107, Saturday, December 21, 2019 02:14:23 [DHCP IP: 192.168.1.3] to MAC address be:ea:1a:ab:af:e1, Saturday, December 21, 2019 02:14:12 [Time synchronized with NTP server] Saturday, December 21, 2019 02:14:01 [Initialized, firmware version: V2.5.1.8] Saturday, December 21, 2019 02:13:42
134.0.216.42 - Оман - Oman Telecommunications Company ...
https://www.proxydocker.com › iplookup › 134.0.216.42 - Translate this page
134.0.216.42 is IPv4 address owned by Oman Telecommunications Company (S.A.O.G) and located in Oman.
This ip address have a good reputation.
Really? You might want to contact your ISP about this IP address and show them the log?
134.0.216.42 - Оман - Oman Telecommunications Company ...
https://www.proxydocker.com › iplookup › 134.0.216.42 - Translate this page
134.0.216.42 is IPv4 address owned by Oman Telecommunications Company (S.A.O.G) and located in Oman.
This ip address have a good reputation.
Really? You might want to contact your ISP about this IP address and show them the log?
That's just one of hundreds of random IP's from all over the world! I'm still getting reboots even when "Disable Port Scan and DoS Protection" is checked. This is getting frustrating already, I wasted an entire day trying to diagnose this problem.
P.S: It just rebooted as I am typing this, will have to wait for it come back online so I can post this. 😞
Yes, I'll contact Amazon tomorrow and hopefully they'll be able to refund me the return shipment fee. Again, it just rebooted while I'm typing this on my phone. :S
From all my troubleshooting and discussion with Netgear, the Orbi should not reboot due to settings in firmware. Connect Netgear for support via phone. You are entitled to this for 3 months from purchase. You can also RMA it directly with them on their website (this should be postage paid although not sure about Middle East), rather than sending it back to Amazon if that is too expensive.
