NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Orbi loosing Internet Connection
Hello - I have had my Orbi installed for less than a week. 3 time now it has lost all connection to the internet. I have to reboot, unplug, both the Orbi and my modem multiple time before I can get...
Hello Everyone
We have release firmware version 1.12.0.18 this firmware has fixes for disconnects and many more I posted the release notes below.
https://kb.netgear.com/000044171/RBR50-Firmware-Version-1-12-0-18
If you are still having issues after updating your Orbi unit you may want to factory reset the Orbi and test again. If you are still having disconnect issues or other issues with this firmware please create a new thread or contact our support team.
http://www.netgear.com/support/contact.aspx
Thanks
DarrenM
I haven't had a disconnect in the last couple of days, but there is a lot of "stuff" in the log. I cleared the log on Saturday morning and have a daily e-mail of the log set up now. The network was not changed; no equipment powered down or added. The whole family was actually away for the weekend so the house was empty. I am not posting everything as it is too long but here are some snippets. So my questions:
- lots of DoS Attacks. Are those real? And if so anything else I should set up on the router to make security tighter?
- lots of DHCP to MAC address messages. What is that?
UPnP set event: add_nat_rule] from source 192.168.1.14, Sunday, March 26, 2017 00:49:04
[UPnP set event: del_nat_rule] from source 192.168.1.14, Sunday, March 26, 2017 00:30:47
[DoS Attack: SYN/ACK Scan] from source: 144.217.34.171, port 80, Saturday, March 25, 2017 23:56:31
[DoS Attack: SYN/ACK Scan] from source: 144.217.34.213, port 80, Saturday, March 25, 2017 23:52:28
[DoS Attack: SYN/ACK Scan] from source: 144.217.34.171, port 80, Saturday, March 25, 2017 23:49:08
[DoS Attack: SYN/ACK Scan] from source: 144.217.34.213, port 80, Saturday, March 25, 2017 23:45:18
[DoS Attack: SYN/ACK Scan] from source: 144.217.34.171, port 80, Saturday, March 25, 2017 23:44:44
[DHCP IP: 192.168.1.12] to MAC address 00:0e:58:3d:a2:be, Saturday, March 25, 2017 22:11:21
[DHCP IP: 192.168.1.11] to MAC address 00:0e:58:7c:b3:90, Saturday, March 25, 2017 22:10:13
[DoS Attack: SYN/ACK Scan] from source: 178.32.40.147, port 21008, Saturday, March 25, 2017 21:50:37
[DHCP IP: 192.168.1.13] to MAC address a0:2b:b8:71:c4:53, Saturday, March 25, 2017 21:06:47
[DoS Attack: RST Scan] from source: 104.16.103.24, port 80, Saturday, March 25, 2017 20:47:53
[DoS Attack: SYN/ACK Scan] from source: 178.32.40.147, port 21008, Saturday, March 25, 2017 20:41:09
[DoS Attack: TCP/UDP Chargen] from source: 184.105.139.97, port 26984, Saturday, March 25, 2017 20:34:13
[DHCP IP: 192.168.1.17] to MAC address cc:95:d7:85:86:17, Saturday, March 25, 2017 18:59:50
[DHCP IP: 192.168.1.23] to MAC address 70:b1:4e:e8:f3:18, Saturday, March 25, 2017 18:00:46
[DHCP IP: 192.168.1.23] to MAC address 70:b1:4e:e8:f3:18, Saturday, March 25, 2017 18:00:37
[DHCP IP: 192.168.1.23] to MAC address 70:b1:4e:e8:f3:18, Saturday, March 25, 2017 18:00:17
[DHCP IP: 192.168.1.23] to MAC address 70:b1:4e:e8:f3:18, Saturday, March 25, 2017 17:59:34
[DoS Attack: SYN/ACK Scan] from source: 183.131.49.9, port 80, Saturday, March 25, 2017 17:58:50
[DoS Attack: SYN/ACK Scan] from source: 183.131.49.23, port 80, Saturday, March 25, 2017 17:58:50
[DoS Attack: SYN/ACK Scan] from source: 183.131.49.212, port 80, Saturday, March 25, 2017 17:58:50
[DoS Attack: SYN/ACK Scan] from source: 183.131.49.139, port 80, Saturday, March 25, 2017 17:58:50
[DoS Attack: SYN/ACK Scan] from source: 183.131.49.99, port 80, Saturday, March 25, 2017 17:58:49
[DoS Attack: SYN/ACK Scan] from source: 183.131.49.75, port 80, Saturday, March 25, 2017 17:58:48
[DoS Attack: SYN/ACK Scan] from source: 183.131.49.143, port 80, Saturday, March 25, 2017 17:58:48
[DHCP IP: 192.168.1.23] to MAC address 70:b1:4e:e8:f3:18, Saturday, March 25, 2017 17:58:10
[DoS Attack: SYN/ACK Scan] from source: 183.131.49.63, port 80, Saturday, March 25, 2017 17:55:53
[DHCP IP: 192.168.1.23] to MAC address 70:b1:4e:e8:f3:18, Saturday, March 25, 2017 17:55:22
[DHCP IP: 192.168.1.23] to MAC address 70:b1:4e:e8:f3:18, Saturday, March 25, 2017 17:49:45
[DoS Attack: SYN/ACK Scan] from source: 183.131.49.101, port 80, Saturday, March 25, 2017 17:48:53
[DoS Attack: SYN/ACK Scan] from source: 183.131.49.37, port 80, Saturday, March 25, 2017 17:48:04
[DHCP IP: 192.168.1.7] to MAC address 00:0e:58:8e:a7:54, Saturday, March 25, 2017 17:41:20
[DHCP IP: 192.168.1.8] to MAC address 00:0e:58:8d:93:98, Saturday, March 25, 2017 17:41:18
[DHCP IP: 192.168.1.10] to MAC address 00:0e:58:5b:fd:3a, Saturday, March 25, 2017 17:40:19
[DHCP IP: 192.168.1.9] to MAC address 00:0e:58:7c:b3:3e, Saturday, March 25, 2017 17:40:14
[DoS Attack: SYN/ACK Scan] from source: 183.131.49.50, port 80, Saturday, March 25, 2017 17:38:41
[DHCP IP: 192.168.1.23] to MAC address 70:b1:4e:e8:f3:18, Saturday, March 25, 2017 17:38:30
[DoS Attack: SYN/ACK Scan] from source: 183.131.49.145, port 80, Saturday, March 25, 2017 17:36:58
[DoS Attack: SYN/ACK Scan] from source: 183.131.49.15, port 80, Saturday, March 25, 2017 17:36:20
[DoS Attack: SYN/ACK Scan] from source: 183.131.49.97, port 80, Saturday, March 25, 2017 17:36:18
[DoS Attack: SYN/ACK Scan] from source: 183.131.49.115, port 80, Saturday, March 25, 2017 17:33:32
[DoS Attack: SYN/ACK Scan] from source: 183.131.49.71, port 80, Saturday, March 25, 2017 17:32:59
[DoS Attack: SYN/ACK Scan] from source: 183.131.49.148, port 80, Saturday, March 25, 2017 17:30:52
[DoS Attack: SYN/ACK Scan] from source: 45.113.194.10, port 80, Saturday, March 25, 2017 17:16:31
hi pat
that dos attack stuff is a bit weird are you ding any torrent type stuff ? as this could be causing you issues , looking at some of those ip addresses though it does look like chineese traffic which is quite suspect
the device 192.168.1.23 seems to connect a lot , it belongs to ARRIS Group, Inc which sounds like an upstream router which means you running the orbi in dual nat , if this is the case and you cant bridge the upstream modem i suggest you run the orbi in AP mode
other than that your logs dont look bad at all
peteytesting wrote:hi pat
that dos attack stuff is a bit weird are you ding any torrent type stuff ? as this could be causing you issues
the device 192.168.1.23 seems to connect a lot , it belongs to ARRIS Group, Inc which sounds like an upstream router which means you running the orbi in dual nat , if this is the case and you cant bridge the upstream modem i suggest you run the orbi in AP mode
other than that your logs dont look bad at all
Thanks for the reply
Nope, not running any torrents or anything like that. I also don't have any other routers in the system. 192.168.1.23 is one of my DirecTV DVRs, I do have 4 of them connected in.
well i would be looking hard at those dvr's esp that one on 192.168.1.23 as its doing something weird to Chinese ip addresses and the orbi routers not liking it
its ether that or you are getting ddosed and you may want to ask your isp for a new ip address if fixed or restart your orbi so it gets a new wan ip address if your on a dynamic plan
