netgear router 1970 date

[nekar9113]

netgear router shows 'Thu Jan 01 00:00:46 1970' and constant DOS attacks

 

[kanewolf]

1970 is the default date when the router can't sync with an NTP source. Does the router have a good WAN connection with a DNS?

 

[Ralston18]

What Netgear model router?

Is the router secure: i.e., you have established your own login ID and password? Or could someone have done a factory reset on the router?

Do you have the User Guide/Manual? If not download via Netgear's website.

Disconnect router from your network and ISP.

Do a factory reset to defaults. Connect to your pc (not the internet) and login via the default login name and password. Usually something like "admin" and "password" or "admin" and "admin".

Select your own (not easily guessed) login name and password. The latter should be some mix of letters, numbers, and special characters per the router's User Guide/Manual.

Reconfigure your network devices to the now secured router. Once your network is up and running then reconnect to the internet via your ISP.

 

[nekar9113]

Thank you
I will try that.
The router is a netgear C3700-100NAS
below is the router log from Friday
(*note the failed admin login was my doing)
Description Count Last Occurrence Target Source
[admin login] from source 192.168.0.4 1 Sat Sep 30 14:07:31 2017 0.0.0.0:0 192.168.0.4:0
[admin login failure] from source 192.168.0.4 14 Sat Sep 30 14:05:51 2017 0.0.0.0:0 192.168.0.4:0
[DHCP IP: 192.168.0.2] to MAC address dc:0b:34:90:32:64 1 Sat Sep 30 14:02:55 2017 0.0.0.0:0 0.0.0.0:0
[UPnP set event: DeletePortMapping] from source 192.168.0.6 1 Sat Sep 30 14:00:07 2017 0.0.0.0:0 192.168.0.6:0
[DHCP IP: 192.168.0.5] to MAC address 90:c7:d8:ea:1b:99 1 Sat Sep 30 13:59:10 2017 0.0.0.0:0 0.0.0.0:0
[UPnP set event: GetExternalIPAddress] from source 192.168.0.6 1 Sat Sep 30 13:59:04 2017 0.0.0.0:0 192.168.0.6:0
[UPnP set event: GetSpecificPortMappingEntry] from source 192.168.0.6 1 Sat Sep 30 13:59:04 2017 0.0.0.0:0 192.168.0.6:0
[UPnP set event: AddPortMapping] from source 192.168.0.6 1 Sat Sep 30 13:59:04 2017 0.0.0.0:0 192.168.0.6:0
[UPnP set event: GetNATRSIPStatus] from source 192.168.0.6 1 Sat Sep 30 13:59:04 2017 0.0.0.0:0 192.168.0.6:0
[UPnP set event: GetConnectionTypeInfo] from source 192.168.0.6 1 Sat Sep 30 13:59:03 2017 0.0.0.0:0 192.168.0.6:0
[DHCP IP: 192.168.0.6] to MAC address 00:16:44:ca:dd:26 1 Sat Sep 30 13:59:02 2017 0.0.0.0:0 0.0.0.0:0
[DHCP IP: 192.168.0.34] to MAC address c8:9c:dc:e1:c4:38 1 Sat Sep 30 13:58:58 2017 0.0.0.0:0 0.0.0.0:0
[DHCP IP: 192.168.0.4] to MAC address 00:1d:09:32:ec:85 1 Sat Sep 30 13:58:58 2017 0.0.0.0:0 0.0.0.0:0
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Sat Sep 30 13:58:54 2017 68.231.22.2:49406 68.105.28.11:53
[DHCP IP: 192.168.0.8] to MAC address f0:25:b7:02:78:d0 1 Sat Sep 30 13:58:53 2017 0.0.0.0:0 0.0.0.0:0
[DHCP IP: 192.168.0.6] to MAC address 00:16:44:ca:dd:26 1 Sat Sep 30 13:58:51 2017 0.0.0.0:0 0.0.0.0:0
[DHCP IP: 192.168.0.34] to MAC address c8:9c:dc:e1:c4:38 1 Sat Sep 30 13:58:47 2017 0.0.0.0:0 0.0.0.0:0
[DHCP IP: 192.168.0.4] to MAC address 00:1d:09:32:ec:85 1 Sat Sep 30 13:58:47 2017 0.0.0.0:0 0.0.0.0:0
[Internet connected] IP address: 68.231.22.2 1 Sat Sep 30 13:58:44 2017 0.0.0.0:0 0.0.0.0:0
[DHCP IP: 192.168.0.6] to MAC address 00:16:44:ca:dd:26 1 Sat Sep 30 13:58:40 2017 0.0.0.0:0 0.0.0.0:0
[DHCP IP: 192.168.0.5] to MAC address 90:c7:d8:ea:1b:99 1 Sat Sep 30 13:58:39 2017 0.0.0.0:0 0.0.0.0:0
[DHCP IP: 192.168.0.34] to MAC address c8:9c:dc:e1:c4:38 1 Sat Sep 30 13:58:36 2017 0.0.0.0:0 0.0.0.0:0
[DHCP IP: 192.168.0.4] to MAC address 00:1d:09:32:ec:85 1 Sat Sep 30 13:58:36 2017 0.0.0.0:0 0.0.0.0:0
[DHCP IP: 192.168.0.8] to MAC address f0:25:b7:02:78:d0 1 Sat Sep 30 13:58:34 2017 0.0.0.0:0 0.0.0.0:0
[Time synchronized with ToD server] 1 Sat Sep 30 13:58:31 2017 0.0.0.0:0 0.0.0.0:0
[DHCP IP: 192.168.0.6] to MAC address 00:16:44:ca:dd:26 1 Thu Jan 01 00:00:39 1970 0.0.0.0:0 0.0.0.0:0
[DHCP IP: 192.168.0.8] to MAC address f0:25:b7:02:78:d0 1 Thu Jan 01 00:00:37 1970 0.0.0.0:0 0.0.0.0:0
[DHCP IP: 192.168.0.34] to MAC address c8:9c:dc:e1:c4:38 1 Thu Jan 01 00:00:34 1970 0.0.0.0:0 0.0.0.0:0
[DHCP IP: 192.168.0.4] to MAC address 00:1d:09:32:ec:85 1 Thu Jan 01 00:00:34 1970 0.0.0.0:0 0.0.0.0:0
[DHCP IP: 192.168.0.10] to MAC address 00:18:4d:ff:ff:07 1 Thu Jan 01 00:00:32 1970 0.0.0.0:0 0.0.0.0:0
[Initialized, firmware version: V2.02.08] 1 Thu Jan 01 00:00:31 1970 0.0.0.0:0 0.0.0.0:0
[UPnP set event: DeletePortMapping] from source 192.168.0.9 1 Sat Sep 30 05:04:50 2017 0.0.0.0:0 192.168.0.9:0
[UPnP set event: AddPortMapping] from source 192.168.0.9 1 Sat Sep 30 05:04:16 2017 0.0.0.0:0 192.168.0.9:0
[UPnP set event: GetExternalIPAddress] from source 192.168.0.9 1 Sat Sep 30 05:04:16 2017 0.0.0.0:0 192.168.0.9:0
[DHCP IP: 192.168.0.9] to MAC address fc:0f:e6:f2:00:e0 1 Sat Sep 30 05:04:15 2017 0.0.0.0:0 0.0.0.0:0
[DHCP IP: 192.168.0.2] to MAC address dc:0b:34:90:32:64 1 Sat Sep 30 03:47:47 2017 0.0.0.0:0 0.0.0.0:0
[DHCP IP: 192.168.0.2] to MAC address dc:0b:34:90:32:64 1 Sat Sep 30 03:40:32 2017 0.0.0.0:0 0.0.0.0:0
[DHCP IP: 192.168.0.34] to MAC address c8:9c:dc:e1:c4:38 1 Sat Sep 30 03:28:15 2017 0.0.0.0:0 0.0.0.0:0
[DHCP IP: 192.168.0.2] to MAC address dc:0b:34:90:32:64 1 Sat Sep 30 03:26:32 2017 0.0.0.0:0 0.0.0.0:0
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.29.11, port 53 1 Sat Sep 30 03:10:25 2017 68.231.22.2:64798 68.105.29.11:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Sat Sep 30 03:07:48 2017 68.231.22.2:60881 68.105.28.11:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.12, port 53 1 Sat Sep 30 03:03:24 2017 68.231.22.2:60509 68.105.28.12:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.29.11, port 53 1 Sat Sep 30 03:02:44 2017 68.231.22.2:52413 68.105.29.11:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Sat Sep 30 03:02:02 2017 68.231.22.2:56379 68.105.28.11:53
[DHCP IP: 192.168.0.6] to MAC address 00:16:44:ca:dd:26 1 Sat Sep 30 02:29:10 2017 0.0.0.0:0 0.0.0.0:0
[DHCP IP: 192.168.0.34] to MAC address c8:9c:dc:e1:c4:38 1 Sat Sep 30 02:29:06 2017 0.0.0.0:0 0.0.0.0:0
[DHCP IP: 192.168.0.4] to MAC address 00:1d:09:32:ec:85 1 Sat Sep 30 02:29:04 2017 0.0.0.0:0 0.0.0.0:0
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.29.11, port 53 1 Sat Sep 30 02:25:43 2017 68.231.22.2:60646 68.105.29.11:53
[DHCP IP: 192.168.0.8] to MAC address f0:25:b7:02:78:d0 1 Sat Sep 30 02:00:23 2017 0.0.0.0:0 0.0.0.0:0
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.12, port 53 1 Sat Sep 30 01:47:18 2017 68.231.22.2:63596 68.105.28.12:53
[DHCP IP: 192.168.0.2] to MAC address dc:0b:34:90:32:64 1 Sat Sep 30 01:08:53 2017 0.0.0.0:0 0.0.0.0:0
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Sat Sep 30 01:08:06 2017 68.231.22.2:61441 68.105.28.11:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.12, port 53 1 Sat Sep 30 01:01:25 2017 68.231.22.2:60604 68.105.28.12:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Fri Sep 29 23:57:52 2017 68.231.22.2:62773 68.105.28.11:53
[DHCP IP: 192.168.0.2] to MAC address dc:0b:34:90:32:64 1 Fri Sep 29 23:57:40 2017 0.0.0.0:0 0.0.0.0:0
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.29.11, port 53 1 Fri Sep 29 23:46:32 2017 68.231.22.2:50252 68.105.29.11:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Fri Sep 29 23:45:50 2017 68.231.22.2:51650 68.105.28.11:53
[DHCP IP: 192.168.0.2] to MAC address dc:0b:34:90:32:64 1 Fri Sep 29 23:35:51 2017 0.0.0.0:0 0.0.0.0:0
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.29.11, port 53 1 Fri Sep 29 23:09:13 2017 68.231.22.2:59394 68.105.29.11:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.12, port 53 1 Fri Sep 29 23:02:51 2017 68.231.22.2:64616 68.105.28.12:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Fri Sep 29 23:00:15 2017 68.231.22.2:62681 68.105.28.11:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.12, port 53 1 Fri Sep 29 22:46:03 2017 68.231.22.2:56724 68.105.28.12:53
[DoS attack: SYN Flood] from 151.101.26.49, port 80 1 Fri Sep 29 22:34:50 2017 192.168.0.4:52773 151.101.26.49:80
[DoS attack: SYN Flood] from 74.217.253.61, port 80 1 Fri Sep 29 22:34:46 2017 192.168.0.4:52729 74.217.253.61:80
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.29.11, port 53 1 Fri Sep 29 22:34:41 2017 68.231.22.2:50897 68.105.29.11:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Fri Sep 29 22:34:21 2017 68.231.22.2:63565 68.105.28.11:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Fri Sep 29 22:02:20 2017 68.231.22.2:52392 68.105.28.11:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.12, port 53 1 Fri Sep 29 21:53:29 2017 68.231.22.2:64036 68.105.28.12:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.29.11, port 53 1 Fri Sep 29 21:49:17 2017 68.231.22.2:59448 68.105.29.11:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Fri Sep 29 21:38:16 2017 68.231.22.2:52662 68.105.28.11:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.12, port 53 1 Fri Sep 29 21:34:53 2017 68.231.22.2:54834 68.105.28.12:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.12, port 53 1 Fri Sep 29 21:31:00 2017 68.231.22.2:65097 68.105.28.12:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Fri Sep 29 21:27:40 2017 68.231.22.2:64569 68.105.28.11:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Fri Sep 29 21:18:41 2017 68.231.22.2:64024 68.105.28.11:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Fri Sep 29 20:34:53 2017 68.231.22.2:59669 68.105.28.11:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.12, port 53 1 Fri Sep 29 20:14:14 2017 68.231.22.2:59031 68.105.28.12:53
[DoS attack: SYN Flood] from 152.163.13.6, port 443 1 Fri Sep 29 20:11:09 2017 192.168.0.4:65093 152.163.13.6:443
[DoS attack: SYN Flood] from 205.180.87.137, port 443 1 Fri Sep 29 20:11:05 2017 192.168.0.34:50821 205.180.87.137:443
[DoS attack: SYN Flood] from 205.180.87.137, port 443 1 Fri Sep 29 20:11:02 2017 192.168.0.34:50805 205.180.87.137:443
[DoS attack: SYN Flood] from 54.149.182.243, port 80 1 Fri Sep 29 20:10:58 2017 192.168.0.5:55449 54.149.182.243:80
[DoS attack: SYN Flood] from 34.192.56.110, port 80 1 Fri Sep 29 20:10:48 2017 192.168.0.4:64983 34.192.56.110:80
[DoS attack: SYN Flood] from 205.180.87.137, port 443 1 Fri Sep 29 20:10:41 2017 192.168.0.34:50788 205.180.87.137:443
[DoS attack: SYN Flood] from 52.55.187.233, port 80 1 Fri Sep 29 20:10:26 2017 192.168.0.4:64870 52.55.187.233:80
[DoS attack: SYN Flood] from 50.19.216.194, port 80 1 Fri Sep 29 20:10:23 2017 192.168.0.4:64859 50.19.216.194:80
[DoS attack: SYN Flood] from 205.180.86.169, port 443 1 Fri Sep 29 20:10:19 2017 192.168.0.34:50708 205.180.86.169:443
[DoS attack: SYN Flood] from 104.254.150.69, port 80 1 Fri Sep 29 20:10:13 2017 192.168.0.4:64753 104.254.150.69:80
[DoS attack: SYN Flood] from 162.208.20.184, port 80 1 Fri Sep 29 20:09:30 2017 192.168.0.4:64613 162.208.20.184:80
[DoS attack: SYN Flood] from 162.248.16.30, port 80 1 Fri Sep 29 20:09:20 2017 192.168.0.4:64557 162.248.16.30:80
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.12, port 53 1 Fri Sep 29 20:09:18 2017 68.231.22.2:63770 68.105.28.12:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.29.11, port 53 1 Fri Sep 29 20:08:12 2017 68.231.22.2:58787 68.105.29.11:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Fri Sep 29 20:07:55 2017 68.231.22.2:56838 68.105.28.11:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.29.11, port 53 1 Fri Sep 29 20:06:32 2017 68.231.22.2:57991 68.105.29.11:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Fri Sep 29 20:01:16 2017 68.231.22.2:52231 68.105.28.11:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Fri Sep 29 19:50:58 2017 68.231.22.2:56299 68.105.28.11:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.12, port 53 1 Fri Sep 29 19:49:47 2017 68.231.22.2:62771 68.105.28.12:53
[DHCP IP: 192.168.0.3] to MAC address 00:34:da:7a:c1:b0 1 Fri Sep 29 19:45:35 2017 0.0.0.0:0 0.0.0.0:0
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.12, port 53 1 Fri Sep 29 19:45:01 2017 68.231.22.2:49657 68.105.28.12:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Fri Sep 29 19:43:23 2017 68.231.22.2:49238 68.105.28.11:53
[DHCP IP: 192.168.0.3] to MAC address 00:34:da:7a:c1:b0 1 Fri Sep 29 19:43:13 2017 0.0.0.0:0 0.0.0.0:0
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Fri Sep 29 19:30:45 2017 68.231.22.2:54664 68.105.28.11:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Fri Sep 29 19:21:35 2017 68.231.22.2:63727 68.105.28.11:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.12, port 53 1 Fri Sep 29 19:17:32 2017 68.231.22.2:56169 68.105.28.12:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.29.11, port 53 1 Fri Sep 29 19:16:37 2017 68.231.22.2:58094 68.105.29.11:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Fri Sep 29 19:09:22 2017 68.231.22.2:54189 68.105.28.11:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.12, port 53 1 Fri Sep 29 19:06:39 2017 68.231.22.2:56070 68.105.28.12:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.12, port 53 1 Fri Sep 29 19:05:15 2017 68.231.22.2:56436 68.105.28.12:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Fri Sep 29 19:00:40 2017 68.231.22.2:62678 68.105.28.11:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Fri Sep 29 18:50:37 2017 68.231.22.2:61457 68.105.28.11:53
[DHCP IP: 192.168.0.5] to MAC address 90:c7:d8:ea:1b:99 1 Fri Sep 29 18:49:07 2017 0.0.0.0:0 0.0.0.0:0
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Fri Sep 29 18:47:13 2017 68.231.22.2:51667 68.105.28.11:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Fri Sep 29 17:59:03 2017 68.231.22.2:52944 68.105.28.11:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.12, port 53 1 Fri Sep 29 17:25:47 2017 68.231.22.2:56426 68.105.28.12:53
[DHCP IP: 192.168.0.3] to MAC address 00:34:da:7a:c1:b0 1 Fri Sep 29 15:57:27 2017 0.0.0.0:0 0.0.0.0:0
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Fri Sep 29 15:55:09 2017 68.231.22.2:65211 68.105.28.11:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Fri Sep 29 15:52:44 2017 68.231.22.2:34531 68.105.28.11:53
[DHCP IP: 192.168.0.5] to MAC address 90:c7:d8:ea:1b:99 1 Fri Sep 29 15:52:38 2017 0.0.0.0:0 0.0.0.0:0
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Fri Sep 29 15:24:51 2017 68.231.22.2:57873 68.105.28.11:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Fri Sep 29 15:04:21 2017 68.231.22.2:51229 68.105.28.11:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.12, port 53 1 Fri Sep 29 14:41:24 2017 68.231.22.2:51060 68.105.28.12:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Fri Sep 29 14:40:02 2017 68.231.22.2:50205 68.105.28.11:53
[DHCP IP: 192.168.0.2] to MAC address dc:0b:34:90:32:64 1 Fri Sep 29 14:31:01 2017 0.0.0.0:0 0.0.0.0:0
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Fri Sep 29 14:30:52 2017 68.231.22.2:65464 68.105.28.11:53
[DHCP IP: 192.168.0.8] to MAC address f0:25:b7:02:78:d0 1 Fri Sep 29 14:29:10 2017 0.0.0.0:0 0.0.0.0:0
[DHCP IP: 192.168.0.6] to MAC address 00:16:44:ca:dd:26 1 Fri Sep 29 14:29:08 2017 0.0.0.0:0 0.0.0.0:0
[DHCP IP: 192.168.0.4] to MAC address 00:1d:09:32:ec:85 1 Fri Sep 29 14:29:05 2017 0.0.0.0:0 0.0.0.0:0
[DHCP IP: 192.168.0.34] to MAC address c8:9c:dc:e1:c4:38 1 Fri Sep 29 14:29:04 2017 0.0.0.0:0 0.0.0.0:0
[DHCP IP: 192.168.0.8] to MAC address f0:25:b7:02:78:d0 1 Fri Sep 29 14:29:02 2017 0.0.0.0:0 0.0.0.0:0
[Internet connected] IP address: 68.231.22.2 1 Fri Sep 29 14:28:58 2017 0.0.0.0:0 0.0.0.0:0
[DHCP IP: 192.168.0.4] to MAC address 00:1d:09:32:ec:85 1 Fri Sep 29 14:28:54 2017 0.0.0.0:0 0.0.0.0:0
[DHCP IP: 192.168.0.34] to MAC address c8:9c:dc:e1:c4:38 1 Fri Sep 29 14:28:53 2017 0.0.0.0:0 0.0.0.0:0
[DHCP IP: 192.168.0.6] to MAC address 00:16:44:ca:dd:26 1 Fri Sep 29 14:28:53 2017 0.0.0.0:0 0.0.0.0:0
[DHCP IP: 192.168.0.8] to MAC address f0:25:b7:02:78:d0 1 Fri Sep 29 14:28:50 2017 0.0.0.0:0 0.0.0.0:0
[Time synchronized with ToD server] 1 Fri Sep 29 14:28:45 2017 0.0.0.0:0 0.0.0.0:0
[DHCP IP: 192.168.0.4] to MAC address 00:1d:09:32:ec:85 1 Thu Jan 01 00:00:48 1970 0.0.0.0:0 0.0.0.0:0
[DHCP IP: 192.168.0.34] to MAC address c8:9c:dc:e1:c4:38 1 Thu Jan 01 00:00:46 1970 0.0.0.0:0 0.0.0.0:0
[DHCP IP: 192.168.0.8] to MAC address f0:25:b7:02:78:d0 1 Thu Jan 01 00:00:43 1970 0.0.0.0:0 0.0.0.0:0
[DHCP IP: 192.168.0.2] to MAC address dc:0b:34:90:32:64 1 Thu Jan 01 00:00:39 1970 0.0.0.0:0 0.0.0.0:0
[DHCP IP: 192.168.0.10] to MAC address 00:18:4d:ff:ff:07 1 Thu Jan 01 00:00:32 1970 0.0.0.0:0 0.0.0.0:0
[DHCP IP: 192.168.0.4] to MAC address 00:1d:09:32:ec:85 1 Thu Jan 01 00:00:32 1970 0.0.0.0:0 0.0.0.0:0
[Initialized, firmware version: V2.02.08] 1 Thu Jan 01 00:00:30 1970 0.0.0.0:0 0.0.0.0:0
[DHCP IP: 192.168.0.34] to MAC address c8:9c:dc:e1:c4:38 1 Thu Jan 01 00:00:30 1970 0.0.0.0:0 0.0.0.0:0
[UPnP set event: DeletePortMapping] from source 192.168.0.9 1 Fri Sep 29 05:51:40 2017 0.0.0.0:0 192.168.0.9:0
[UPnP set event: AddPortMapping] from source 192.168.0.9 1 Fri Sep 29 05:51:28 2017 0.0.0.0:0 192.168.0.9:0
[UPnP set event: GetExternalIPAddress] from source 192.168.0.9 1 Fri Sep 29 05:51:27 2017 0.0.0.0:0 192.168.0.9:0
[DHCP IP: 192.168.0.9] to MAC address fc:0f:e6:f2:00:e0 1 Fri Sep 29 05:51:26 2017 0.0.0.0:0 0.0.0.0:0
[DoS attack: SYN Flood] from 52.201.18.112, port 443 1 Fri Sep 29 05:43:31 2017 192.168.0.34:65493 52.201.18.112:443
[DoS attack: SYN Flood] from 63.251.109.88, port 443 1 Fri Sep 29 05:43:27 2017 192.168.0.34:65452 63.251.109.88:443
[DoS attack: SYN Flood] from 146.20.132.218, port 80 1 Fri Sep 29 05:42:47 2017 192.168.0.34:65348 146.20.132.218:80
[DoS attack: SYN Flood] from 63.251.88.51, port 80 1 Fri Sep 29 05:41:02 2017 192.168.0.34:65166 63.251.88.51:80
[DoS attack: SYN Flood] from 130.211.115.4, port 443 1 Fri Sep 29 05:40:30 2017 192.168.0.34:65059 130.211.115.4:443
[DoS attack: SYN Flood] from 13.58.13.211, port 443 1 Fri Sep 29 05:40:24 2017 192.168.0.34:65015 13.58.13.211:443
[DoS attack: SYN Flood] from 54.215.154.233, port 443 1 Fri Sep 29 05:40:18 2017 192.168.0.34:64972 54.215.154.233:443
[DoS attack: SYN Flood] from 54.173.164.149, port 443 1 Fri Sep 29 05:35:57 2017 192.168.0.34:64511 54.173.164.149:443
[DoS attack: SYN Flood] from 162.208.20.184, port 443 1 Fri Sep 29 05:35:27 2017 192.168.0.34:64423 162.208.20.184:443
[DoS attack: SYN Flood] from 52.41.153.238, port 80 1 Fri Sep 29 05:35:22 2017 192.168.0.34:64350 52.41.153.238:80
[DoS attack: SYN Flood] from 52.73.213.215, port 80 1 Fri Sep 29 05:35:18 2017 192.168.0.34:64326 52.73.213.215:80
[DoS attack: SYN Flood] from 50.19.247.135, port 80 1 Fri Sep 29 05:33:26 2017 192.168.0.34:64102 50.19.247.135:80
[DoS attack: SYN Flood] from 52.216.131.187, port 80 1 Fri Sep 29 05:33:21 2017 192.168.0.34:64063 52.216.131.187:80
[DoS attack: SYN Flood] from 63.251.109.127, port 443 1 Fri Sep 29 05:32:47 2017 192.168.0.34:63989 63.251.109.127:443
[DoS attack: SYN Flood] from 184.27.130.178, port 443 1 Fri Sep 29 05:32:36 2017 192.168.0.34:63932 184.27.130.178:443
[DoS attack: SYN Flood] from 52.15.181.38, port 443 1 Fri Sep 29 05:31:22 2017 192.168.0.34:63789 52.15.181.38:443
[DoS attack: SYN Flood] from 52.85.83.229, port 80 1 Fri Sep 29 05:31:18 2017 192.168.0.34:63775 52.85.83.229:80
[UPnP set event: GetTotalBytesReceived] from source 192.168.0.6 1 Fri Sep 29 05:19:02 2017 0.0.0.0:0 192.168.0.6:0
[UPnP set event: GetTotalBytesSent] from source 192.168.0.6 1 Fri Sep 29 05:19:02 2017 0.0.0.0:0 192.168.0.6:0
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Fri Sep 29 04:50:22 2017 68.231.22.2:52040 68.105.28.11:53
[DHCP IP: 192.168.0.6] to MAC address 00:16:44:ca:dd:26 1 Fri Sep 29 03:57:16 2017 0.0.0.0:0 0.0.0.0:0
[DHCP IP: 192.168.0.34] to MAC address c8:9c:dc:e1:c4:38 1 Fri Sep 29 02:34:57 2017 0.0.0.0:0 0.0.0.0:0
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Fri Sep 29 02:09:54 2017 68.231.22.2:4615 68.105.28.11:53
[DHCP IP: 192.168.0.8] to MAC address f0:25:b7:02:78:d0 1 Fri Sep 29 02:06:10 2017 0.0.0.0:0 0.0.0.0:0
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Fri Sep 29 01:34:26 2017 68.231.22.2:53718 68.105.28.11:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Fri Sep 29 01:27:53 2017 68.231.22.2:40106 68.105.28.11:53
[DHCP IP: 192.168.0.5] to MAC address 90:c7:d8:ea:1b:99 1 Fri Sep 29 01:25:51 2017 0.0.0.0:0 0.0.0.0:0
[UPnP set event: DeletePortMapping] from source 192.168.0.7 1 Fri Sep 29 01:13:45 2017 0.0.0.0:0 192.168.0.7:0
[UPnP set event: GetExternalIPAddress] from source 192.168.0.7 1 Fri Sep 29 01:13:45 2017 0.0.0.0:0 192.168.0.7:0
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Fri Sep 29 00:45:00 2017 68.231.22.2:58729 68.105.28.11:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Fri Sep 29 00:41:17 2017 68.231.22.2:51731 68.105.28.11:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.12, port 53 1 Fri Sep 29 00:40:20 2017 68.231.22.2:55894 68.105.28.12:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.29.11, port 53 1 Fri Sep 29 00:37:44 2017 68.231.22.2:63395 68.105.29.11:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Fri Sep 29 00:27:42 2017 68.231.22.2:53312 68.105.28.11:53
[DoS attack: SYN Flood] from 198.23.90.60, port 443 1 Fri Sep 29 00:22:21 2017 192.168.0.4:58233 198.23.90.60:443
[DoS attack: SYN Flood] from 152.163.66.131, port 443 1 Fri Sep 29 00:21:56 2017 192.168.0.4:58028 152.163.66.131:443
[DoS attack: SYN Flood] from 169.60.66.38, port 443 1 Fri Sep 29 00:21:38 2017 192.168.0.4:57882 169.60.66.38:443
[DoS attack: SYN Flood] from 52.5.223.237, port 80 1 Fri Sep 29 00:21:29 2017 192.168.0.4:57844 52.5.223.237:80
[DoS attack: SYN Flood] from 23.55.204.40, port 80 1 Fri Sep 29 00:21:15 2017 192.168.0.4:57728 23.55.204.40:80
[DoS attack: SYN Flood] from 23.52.234.182, port 80 1 Fri Sep 29 00:21:04 2017 192.168.0.4:57612 23.52.234.182:80
[DoS attack: SYN Flood] from 77.234.42.252, port 80 1 Fri Sep 29 00:20:55 2017 192.168.0.4:57569 77.234.42.252:80
[DoS attack: SYN Flood] from 172.217.5.194, port 80 1 Fri Sep 29 00:20:45 2017 192.168.0.4:57527 172.217.5.194:80
[DoS attack: SYN Flood] from 54.230.86.197, port 80 1 Fri Sep 29 00:20:35 2017 192.168.0.4:57440 54.230.86.197:80
[DoS attack: SYN Flood] from 54.84.32.40, port 80 1 Fri Sep 29 00:20:13 2017 192.168.0.4:57298 54.84.32.40:80
[DoS attack: SYN Flood] from 104.254.150.37, port 443 1 Fri Sep 29 00:19:51 2017 192.168.0.4:57121 104.254.150.37:443
[DoS attack: SYN Flood] from 54.174.107.229, port 80 1 Fri Sep 29 00:19:30 2017 192.168.0.4:56976 54.174.107.229:80
[DoS attack: SYN Flood] from 204.2.197.201, port 80 1 Fri Sep 29 00:19:08 2017 192.168.0.4:56845 204.2.197.201:80
[DoS attack: SYN Flood] from 216.200.232.114, port 80 1 Fri Sep 29 00:18:47 2017 192.168.0.4:56740 216.200.232.114:80
[DoS attack: SYN Flood] from 52.39.233.38, port 80 1 Fri Sep 29 00:18:30 2017 192.168.0.4:56667 52.39.233.38:80
[DoS attack: SYN Flood] from 52.35.40.63, port 80 1 Fri Sep 29 00:18:26 2017 192.168.0.4:56624 52.35.40.63:80
[DoS attack: SYN Flood] from 204.2.197.211, port 80 1 Fri Sep 29 00:18:19 2017 192.168.0.4:56524 204.2.197.211:80
[DoS attack: SYN Flood] from 152.163.66.131, port 443 1 Fri Sep 29 00:18:09 2017 192.168.0.4:56491 152.163.66.131:443
[DoS attack: SYN Flood] from 173.241.250.220, port 80 1 Fri Sep 29 00:17:59 2017 192.168.0.4:56408 173.241.250.220:80
[DoS attack: SYN Flood] from 35.161.117.193, port 80 1 Fri Sep 29 00:17:37 2017 192.168.0.4:56312 35.161.117.193:80
[DoS attack: SYN Flood] from 204.2.197.211, port 80 1 Fri Sep 29 00:17:15 2017 192.168.0.4:56217 204.2.197.211:80
[DoS attack: SYN Flood] from 54.213.234.155, port 80 1 Fri Sep 29 00:17:05 2017 192.168.0.4:56182 54.213.234.155:80
[DoS attack: SYN Flood] from 139.61.74.125, port 80 1 Fri Sep 29 00:16:55 2017 192.168.0.4:56112 139.61.74.125:80
[DoS attack: SYN Flood] from 64.136.45.30, port 80 1 Fri Sep 29 00:16:49 2017 192.168.0.4:56067 64.136.45.30:80
[DoS attack: SYN Flood] from 38.106.10.132, port 443 1 Fri Sep 29 00:16:38 2017 192.168.0.4:55988 38.106.10.132:443
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Fri Sep 29 00:16:22 2017 68.231.22.2:60602 68.105.28.11:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Thu Sep 28 23:39:00 2017 68.231.22.2:6564 68.105.28.11:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Thu Sep 28 23:05:45 2017 68.231.22.2:55518 68.105.28.11:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Thu Sep 28 22:52:11 2017 68.231.22.2:41980 68.105.28.11:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Thu Sep 28 22:45:17 2017 68.231.22.2:34637 68.105.28.11:53
[DHCP IP: 192.168.0.5] to MAC address 90:c7:d8:ea:1b:99 1 Thu Sep 28 22:44:32 2017 0.0.0.0:0 0.0.0.0:0
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.29.11, port 53 1 Thu Sep 28 22:17:44 2017 68.231.22.2:63309 68.105.29.11:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Thu Sep 28 22:16:51 2017 68.231.22.2:56152 68.105.28.11:53
[UPnP set event: AddPortMapping] from source 192.168.0.7 1 Thu Sep 28 22:12:56 2017 0.0.0.0:0 192.168.0.7:0
[UPnP set event: GetExternalIPAddress] from source 192.168.0.7 1 Thu Sep 28 22:12:56 2017 0.0.0.0:0 192.168.0.7:0
[UPnP set event: DeletePortMapping] from source 192.168.0.7 1 Thu Sep 28 22:12:39 2017 0.0.0.0:0 192.168.0.7:0
[UPnP set event: GetExternalIPAddress] from source 192.168.0.7 1 Thu Sep 28 22:12:39 2017 0.0.0.0:0 192.168.0.7:0
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.12, port 53 1 Thu Sep 28 22:12:35 2017 68.231.22.2:51635 68.105.28.12:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.29.11, port 53 1 Thu Sep 28 22:12:30 2017 68.231.22.2:53822 68.105.29.11:53
[LAN access from remote] from 52.184.186.84:3544 to 192.168.0.7:3074 1 Thu Sep 28 22:10:44 2017 192.168.0.7:3074 52.184.186.84:3544
[UPnP set event: AddPortMapping] from source 192.168.0.7 1 Thu Sep 28 22:10:42 2017 0.0.0.0:0 192.168.0.7:0
[UPnP set event: GetExternalIPAddress] from source 192.168.0.7 1 Thu Sep 28 22:10:42 2017 0.0.0.0:0 192.168.0.7:0
[DHCP IP: 192.168.0.7] to MAC address b4:ae:2b:9b:c9:8b 1 Thu Sep 28 22:10:38 2017 0.0.0.0:0 0.0.0.0:0
[DHCP IP: 192.168.0.5] to MAC address 90:c7:d8:ea:1b:99 1 Thu Sep 28 22:09:18 2017 0.0.0.0:0 0.0.0.0:0
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Thu Sep 28 22:08:07 2017 68.231.22.2:57770 68.105.28.11:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Thu Sep 28 21:50:26 2017 68.231.22.2:54588 68.105.28.11:53
[DHCP IP: 192.168.0.2] to MAC address dc:0b:34:90:32:64 1 Thu Sep 28 21:39:50 2017 0.0.0.0:0 0.0.0.0:0
[DHCP IP: 192.168.0.2] to MAC address dc:0b:34:90:32:64 1 Thu Sep 28 21:26:24 2017 0.0.0.0:0 0.0.0.0:0
[DHCP IP: 192.168.0.2] to MAC address dc:0b:34:90:32:64 1 Thu Sep 28 21:26:18 2017 0.0.0.0:0 0.0.0.0:0
[DHCP IP: 192.168.0.3] to MAC address 00:34:da:7a:c1:b0 1 Thu Sep 28 21:19:12 2017 0.0.0.0:0 0.0.0.0:0
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.12, port 53 1 Thu Sep 28 21:07:44 2017 68.231.22.2:65293 68.105.28.12:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Thu Sep 28 21:02:00 2017 68.231.22.2:54035 68.105.28.11:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.12, port 53 1 Thu Sep 28 20:58:31 2017 68.231.22.2:58752 68.105.28.12:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Thu Sep 28 20:45:10 2017 68.231.22.2:65216 68.105.28.11:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Thu Sep 28 20:24:17 2017 68.231.22.2:58004 68.105.28.11:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.29.11, port 53 1 Thu Sep 28 20:19:20 2017 68.231.22.2:53001 68.105.29.11:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Thu Sep 28 20:18:11 2017 68.231.22.2:61302 68.105.28.11:53
[DoS attack: TCP- or UDP-based Port Scan] from 68.105.28.11, port 53 1 Thu Sep 28 19:13:32 2017 68.231.22.2:57847 68.105.28.11:53
[DoS attack: SYN Flood] from 23.36.201.225, port 80 1 Thu Sep 28 19:13:30 2017 192.168.0.6:60976 23.36.201.225:80
[DoS attack: SYN Flood] from 192.243.232.36, port 80 1 Thu Sep 28 19:13:22 2017 192.168.0.6:60932 192.243.232.36:80
[DoS attack: SYN Flood] from 23.36.201.174, port 80 1 Thu Sep 28 19:13:19 2017 192.168.0.6:60913 23.36.201.174:80
[DoS attack: SYN Flood] from 104.196.173.4, port 443 1 Thu Sep 28 19:13:10 2017 192.168.0.6:60844 104.196.173.4:443
[DoS attack: SYN Flood] from 52.10.56.29, port 80 1 Thu Sep 28 19:13:07 2017 192.168.0.6:60812 52.10.56.29:80
[DoS attack: SYN Flood] from 5.39.22.124, port 80 1 Thu Sep 28 19:12:43 2017 192.168.0.6:60680 5.39.22.124:80
[DoS attack: SYN Flood] from 184.173.164.235, port 80 1 Thu Sep 28 19:12:39 2017 192.168.0.6:60646 184.173.164.235:80
[DoS attack: SYN Flood] from 52.206.184.239, port 80 1 Thu Sep 28 19:12:35 2017 192.168.0.6:60608 52.206.184.239:80
[DoS attack: SYN Flood] from 50.112.255.244, port 80 1 Thu Sep 28 19:12:32 2017 192.168.0.6:60568 50.112.255.244:80
[DoS attack: SYN Flood] from 173.241.250.143, port 80 1 Thu Sep 28 19:10:24 2017 192.168.0.6:60216 173.241.250.143:80
[DoS attack: SYN Flood] from 52.7.85.172, port 80 1 Thu Sep 28 19:07:26 2017 192.168.0.6:59919 52.7.85.172:80
[DoS attack: SYN Flood] from 216.52.31.59, port 80 1 Thu Sep 28 19:07:23 2017 192.168.0.6:59884 216.52.31.59:80
[DoS attack: SYN Flood] from 63.251.210.243, port 80 1 Thu Sep 28 19:06:25 2017 192.168.0.6:59792 63.251.210.243:80
[DoS attack: SYN Flood] from 52.73.34.52, port 80 1 Thu Sep 28 19:06:21 2017 192.168.0.6:59765 52.73.34.52:80
[DoS attack: SYN Flood] from 23.52.242.106, port 80 1 Thu Sep 28 19:05:21 2017 192.168.0.6:59657 23.52.242.106:80
[UPnP set event: GetTotalBytesReceived] from source 192.168.0.6 1 Thu Sep 28 19:04:33 2017 0.0.0.0:0 192.168.0.6:0
[UPnP set event: GetTotalBytesSent] from source 192.168.0.6 1 Thu Sep 28 19:04:33 2017 0.0.0.0:0 192.168.0.6:0
[UPnP set event: GetTotalBytesReceived] from source 192.168.0.6 1 Thu Sep 28 19:04:33 2017 0.0.0.0:0 192.168.0.6:0
[UPnP set event: GetTotalBytesSent] from source 192.168.0.6 1 Thu Sep 28 19:04:33 2017 0.0.0.0:0 192.168.0.6:0

 

[nekar9113]

I believe the wan connection is ok.
when I access the wan section on the netgeat geanie page it does not show any issues.

 

[nekar9113]

I also have the event log from the same date and time would that help?
It is below:
Time Priority Description
2017-9-29, 01:12:00 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:90:89:28;CMTS-MAC=00:1b:54:cb:ce:b0;CM-QOS=1.1;CM-VER=3.0;
2017-9-29, 01:25:57 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:90:89:28;CMTS-MAC=00:1b:54:cb:ce:b0;CM-QOS=1.1;CM-VER=3.0;
2017-9-29, 01:26:22 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=2c:30:33:90:89:28;CMTS-MAC=00:1b:54:cb:ce:b0;CM-QOS=1.1;CM-VER=3.0;
2017-9-29, 01:34:10 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:90:89:28;CMTS-MAC=00:1b:54:cb:ce:b0;CM-QOS=1.1;CM-VER=3.0;
2017-9-29, 01:34:25 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:90:89:28;CMTS-MAC=00:1b:54:cb:ce:b0;CM-QOS=1.1;CM-VER=3.0;
2017-9-29, 01:34:26 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:90:89:28;CMTS-MAC=00:1b:54:cb:ce:b0;CM-QOS=1.1;CM-VER=3.0;
2017-9-29, 01:34:27 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:90:89:28;CMTS-MAC=00:1b:54:cb:ce:b0;CM-QOS=1.1;CM-VER=3.0;
2017-9-29, 01:34:28 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:90:89:28;CMTS-MAC=00:1b:54:cb:ce:b0;CM-QOS=1.1;CM-VER=3.0;
2017-9-29, 01:34:29 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:90:89:28;CMTS-MAC=00:1b:54:cb:ce:b0;CM-QOS=1.1;CM-VER=3.0;
2017-9-29, 01:34:30 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:90:89:28;CMTS-MAC=00:1b:54:cb:ce:b0;CM-QOS=1.1;CM-VER=3.0;
2017-9-29, 01:34:31 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:90:89:28;CMTS-MAC=00:1b:54:cb:ce:b0;CM-QOS=1.1;CM-VER=3.0;
2017-9-29, 01:34:32 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:90:89:28;CMTS-MAC=00:1b:54:cb:ce:b0;CM-QOS=1.1;CM-VER=3.0;
2017-9-29, 01:34:33 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:90:89:28;CMTS-MAC=00:1b:54:cb:ce:b0;CM-QOS=1.1;CM-VER=3.0;
2017-9-29, 01:34:34 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:90:89:28;CMTS-MAC=00:1b:54:cb:ce:b0;CM-QOS=1.1;CM-VER=3.0;
2017-9-29, 01:34:35 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:90:89:28;CMTS-MAC=00:1b:54:cb:ce:b0;CM-QOS=1.1;CM-VER=3.0;
2017-9-29, 01:34:40 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=2c:30:33:90:89:28;CMTS-MAC=00:1b:54:cb:ce:b0;CM-QOS=1.1;CM-VER=3.0;
2017-9-29, 01:34:55 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:90:89:28;CMTS-MAC=00:1b:54:cb:ce:b0;CM-QOS=1.1;CM-VER=3.0;
2017-9-29, 02:32:54 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:90:89:28;CMTS-MAC=00:1b:54:cb:ce:b0;CM-QOS=1.1;CM-VER=3.0;
2017-9-29, 03:12:52 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=2c:30:33:90:89:28;CMTS-MAC=00:1b:54:cb:ce:b0;CM-QOS=1.1;CM-VER=3.0;
1970-1-1, 00:00:31 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:30:33:90:89:28;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:36 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=2c:30:33:90:89:28;CMTS-MAC=00:1b:54:cb:ce:b0;CM-QOS=1.0;CM-VER=3.0;
2017-9-29, 14:29:29 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=2c:30:33:90:89:28;CMTS-MAC=00:1b:54:cb:ce:b0;CM-QOS=1.1;CM-VER=3.0;
2017-9-29, 15:13:04 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:90:89:28;CMTS-MAC=00:1b:54:cb:ce:b0;CM-QOS=1.1;CM-VER=3.0;
2017-9-29, 19:34:27 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:30:33:90:89:28;CMTS-MAC=00:1b:54:cb:ce:b0;CM-QOS=1.1;CM-VER=3.0;
2017-9-29, 22:44:33 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:90:89:28;CMTS-MAC=00:1b:54:cb:ce:b0;CM-QOS=1.1;CM-VER=3.0;
2017-9-30, 00:14:00 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=2c:30:33:90:89:28;CMTS-MAC=00:1b:54:cb:ce:b0;CM-QOS=1.1;CM-VER=3.0;
2017-9-30, 00:14:00 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=2c:30:33:90:89:28;CMTS-MAC=00:1b:54:cb:ce:b0;CM-QOS=1.1;CM-VER=3.0;
2017-9-30, 00:25:29 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:90:89:28;CMTS-MAC=00:1b:54:cb:ce:b0;CM-QOS=1.1;CM-VER=3.0;
2017-9-30, 01:51:51 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:90:89:28;CMTS-MAC=00:1b:54:cb:ce:b0;CM-QOS=1.1;CM-VER=3.0;
2017-9-30, 02:28:28 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:90:89:28;CMTS-MAC=00:1b:54:cb:ce:b0;CM-QOS=1.1;CM-VER=3.0;
1970-1-1, 00:00:32 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:30:33:90:89:28;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:35 Notice (6) WiFi Interface [wl0] set to Channel 4 (Side-Band Channel:N/A) - Reason:INIT
1970-1-1, 00:00:35 Notice (6) WiFi Interface [wl1] set to Channel 153 (Side-Band Channel:149) - Reason:INIT
1970-1-1, 00:00:42 Notice (6) Honoring MDD; IP provisioning mode = IPv4
1970-1-1, 00:00:44 Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=2c:30:33:90:89:28;CMTS-MAC=00:1b:54:cb:ce:b0;CM-QOS=1.0;CM-VER=3.0;
2017-9-30, 13:58:33 Notice (6) TLV-11 - unrecognized OID;CM-MAC=2c:30:33:90:89:28;CMTS-MAC=00:1b:54:cb:ce:b0;CM-QOS=1.1;CM-VER=3.0;
2017-9-30, 13:59:15 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=2c:30:33:90:89:28;CMTS-MAC=00:1b:54:cb:ce:b0;CM-QOS=1.1;CM-VER=3.0;
2017-9-30, 14:04:29 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:90:89:28;CMTS-MAC=00:1b:54:cb:ce:b0;CM-QOS=1.1;CM-VER=3.0;
2017-9-30, 14:06:28 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=2c:30:33:90:89:28;CMTS-MAC=00:1b:54:cb:ce:b0;CM-QOS=1.1;CM-VER=3.0;
2017-9-30, 14:06:28 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=2c:30:33:90:89:28;CMTS-MAC=00:1b:54:cb:ce:b0;CM-QOS=1.1;CM-VER=3.0

 

[Ralston18]

The Event log posting indicate an entirely different situation: e.g. the T3 time-out(s).

Probably more in alignment with Kanewolf's post....

Reference:

http/www.dslreports.com/faq/13055

Maybe the DOS attacks interfered with the NTP.

[Note: (full disclosure) have now gone out of my normal comfort zones.... Will defer further comment and speculation to others who may be following this thread.]

You can also google "Who is ---.---.---.--- to identify the attacking IP's. However, probably meaningless as the IP's are very likely spoofs.

Be sure that your router is secure and has up-to-date firmware.

Go to:

https/www.whatismyip.net/

Learn (but do not post) your public IP.

If the DOS attacks continue contact your ISP to learn how to change your public IP. Sometimes just disconnecting the router for some period of time will do so.

And please keep in mind that there are many such attacks underway at any given time. That cannot really be prevented.

Your goal is to keep the attacks from succeeding.

 

[nekar9113]

Thank you
The internet access is very sporadic. I do believe that something is wrong but not sure where to start. You mentioned running the OP's through Whois - would this be the source IP's or the target IP's? (of course - not the ones I recognize).

 

[kanewolf]

Here is a discussion of T3 timeouts (from TimeWarner cable) -- http/forums.timewarnercable.com/t5/Connectivity/T3-TImeout-Errors-Solution/td-p/5395 Your modem seems to be having issues. Is this a cable modem situation? If so you could have bad coax between your modem and the outside of the house or low signal at the house. I would recommend you ask your ISP to check your signal levels.

 

[Ralston18]

Regarding "Who is"....

Just a tool to hopefully discover who the "owner" of any entered IP may be. May or may not be the true source due to a spoof.

Occasionally I note some IP appearing somewhere and wish to find out more. E.g. Someone provides an IP address versus a URL.

"Who is" may provide a company name that fits things together and I know all is well.

Or that the IP address is in the Ukraine.....