NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
gregsorbi
Mar 24, 2019Aspirant
RBR50 rebooting hourly
RBR50 w/ 1 RBS50 Satellite ~ 30 feet (synchs blue)
Firmware 2.3.1.44
Spectrum w/ Arris TM1602 modem
WPA2-PRK [AES]
House 2,700 sq ft
Edge of Neighbor's house ~110 feet can see their wifi ve...
gregsorbi
Mar 24, 2019Aspirant
A few of the times I've been sitting there when it starts pulsating white.
Yes, log looks like this, rarely see entries spanning longer than an hour.
[DoS Attack: ACK Scan] from source: 17.33.9.65, port 443, Sunday, March 24, 2019 16:38:00
[admin login] from source 192.168.1.9, Sunday, March 24, 2019 16:37:55
[DHCP IP: 192.168.1.7] to MAC address f0:98:9d:4b:df:85, Sunday, March 24, 2019 16:37:42
[DHCP IP: 192.168.1.9] to MAC address f8:2f:a8:da:2c:bb, Sunday, March 24, 2019 16:37:25
[DHCP IP: 192.168.1.5] to MAC address 7c:1c:4e:57:96:ea, Sunday, March 24, 2019 16:36:25
[DHCP IP: 192.168.1.4] to MAC address 08:02:8e:90:9b:c0, Sunday, March 24, 2019 16:36:15
[DHCP IP: 192.168.1.3] to MAC address 68:9a:87:bb:75:b6, Sunday, March 24, 2019 16:35:55
[DHCP IP: 192.168.1.2] to MAC address 68:9a:87:c4:a4:97, Sunday, March 24, 2019 16:35:53
[Time synchronized with NTP server] Sunday, March 24, 2019 16:35:35
[Initialized, firmware version: V2.3.1.44] Sunday, March 24, 2019 16:35:19
gregsorbi
Mar 24, 2019Aspirant
and again and this time it lost it's time zone. It's should be 17:51
[DHCP IP: 192.168.1.7] to MAC address f0:98:9d:4b:df:85, Sunday, March 24, 2019 16:52:45
[admin login] from source 192.168.1.9, Sunday, March 24, 2019 16:52:44
[admin login failure] from source 192.168.1.9, Sunday, March 24, 2019 16:52:41
[DHCP IP: 192.168.1.9] to MAC address f8:2f:a8:da:2c:bb, Sunday, March 24, 2019 16:52:22
[DHCP IP: 192.168.1.5] to MAC address 08:02:8e:90:9b:c0, Sunday, March 24, 2019 16:52:07
[DHCP IP: 192.168.1.9] to MAC address f8:2f:a8:da:2c:bb, Sunday, March 24, 2019 16:52:02
[DHCP IP: 192.168.1.4] to MAC address 7c:1c:4e:57:96:ea, Sunday, March 24, 2019 16:51:54
[DHCP IP: 192.168.1.6] to MAC address f8:95:ea:12:48:48, Sunday, March 24, 2019 16:51:52
[DHCP IP: 192.168.1.10] to MAC address 48:bf:6b:3f:b4:77, Sunday, March 24, 2019 16:51:50
[DHCP IP: 192.168.1.6] to MAC address f8:95:ea:12:48:48, Sunday, March 24, 2019 16:51:50
[DHCP IP: 192.168.1.10] to MAC address 48:bf:6b:3f:b4:77, Sunday, March 24, 2019 16:51:50
[DHCP IP: 192.168.1.3] to MAC address 68:9a:87:bb:75:b6, Sunday, March 24, 2019 16:51:47
[DHCP IP: 192.168.1.2] to MAC address 68:9a:87:c4:a4:97, Sunday, March 24, 2019 16:51:47
[Time synchronized with NTP server] Sunday, March 24, 2019 16:51:26
[Initialized, firmware version: V2.3.1.44] Sunday, March 24, 2019 16:51:11
- Chuck_MMar 25, 2019Mentor
Seems to me in this case, a factory reset would be the first steps I would take. You have the current firmware version according to your post.
- gregsorbiMar 25, 2019Aspirant
I've reset it a couple of times and it seems to have reset itself once as well...
- gr8shoMar 25, 2019Virtuoso
I like using the paperclip method after a cold start on each unit in the RBK5x and let the hardware do its thing. Base unit first of course. After everything's up, you can go into the web gui and make requisite settings changes.