NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
royalmarquis
Nov 18, 2017Aspirant
c6300 modem router micro wifi drops
Several times a day I would lose my wifi connection sporadically. It never auto connects back and I'd have to manually do it myself. I'm using a Mac running OS X Yosemite 10.10.5. Firmware of the model is V2.01.22.
My event log:
| Time | Priority | Description |
| Nov 05 2017 10:16:22 | Critical (3) | No Ranging Response received - T3 time-out |
| Nov 03 2017 20:56:57 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
| Time Not Established | Critical (3) | No Ranging Response received - T3 time-out |
| Nov 03 2017 20:48:01 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
| Nov 03 2017 20:43:54 | Notice (6) | SW download Successful - Via Config file |
| Nov 03 2017 20:42:49 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out |
| Nov 03 2017 20:42:28 | Notice (6) | SW Download INIT - Via Config file d11_m_c6300_walledgarden_c01.cm |
| Nov 03 2017 20:42:25 | Warning (5) | TCS Partial Service |
| Nov 03 2017 20:42:25 | Critical (3) | Unicast Maintenance Ranging attempted - No response - Retries exhausted |
| Nov 03 2017 20:42:25 | Critical (3) | Ranging Request Retries exhausted |
| Nov 03 2017 20:42:07 | Critical (3) | No Ranging Response received - T3 time-out |
| Nov 03 2017 20:42:04 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
| Time Not Established | Critical (3) | No Ranging Response received - T3 time-out |
2 Replies
- royalmarquisAspirant
[admin login] from source 192.168.0.20 2 Saturday, 18 Nov 2017 17:06:30 0.0.0.0 192.168.0.20 [DHCP IP: (192.168.0.24)] to MAC address f8:da:0c:0b:5c:f5 2 Saturday, 18 Nov 2017 16:37:37 0.0.0.0 0.0.0.0 [WLAN access rejected: incorrect security] from MAC: f8:da:0c:0b:5c:f5 12 Saturday, 18 Nov 2017 16:36:54 0.0.0.0 0.0.0.0 [DHCP IP: (192.168.0.24)] to MAC address f8:da:0c:0b:5c:f5 1 Saturday, 18 Nov 2017 16:25:11 0.0.0.0 0.0.0.0 [DHCP IP: (192.168.0.21)] to MAC address 6c:72:e7:20:f5:ef 1 Saturday, 18 Nov 2017 16:24:36 0.0.0.0 0.0.0.0 [DHCP IP: (192.168.0.20)] to MAC address 34:36:3b:c7:b3:48 3 Saturday, 18 Nov 2017 16:24:05 0.0.0.0 0.0.0.0 [admin login] from source 192.168.0.20 1 Saturday, 18 Nov 2017 16:21:19 0.0.0.0 192.168.0.20 [DHCP IP: (192.168.0.20)] to MAC address 34:36:3b:c7:b3:48 2 Saturday, 18 Nov 2017 16:21:16 0.0.0.0 0.0.0.0 [DoS attack] ICMP Flood from 46.234.125.89 1 Saturday, 18 Nov 2017 14:50:17 73.136.90.130 46.234.125.89 [DoS attack] ICMP Flood from 23.105.70.77 1 Saturday, 18 Nov 2017 13:32:58 73.136.90.130 23.105.70.77 [DHCP IP: (192.168.0.20)] to MAC address 34:36:3b:c7:b3:48 3 Saturday, 18 Nov 2017 13:21:50 0.0.0.0 0.0.0.0 [DoS attack] ICMP Flood from 59.59.178.192 1 Saturday, 18 Nov 2017 12:59:01 73.136.90.130 59.59.178.192 [DoS attack] ICMP Flood from 195.251.255.69 1 Saturday, 18 Nov 2017 11:47:38 73.136.90.130 195.251.255.69 [DoS attack] ICMP Flood from 129.82.138.44 1 Saturday, 18 Nov 2017 11:09:00 73.136.90.130 129.82.138.44 [DoS attack] ICMP Flood from 128.59.21.9 1 Saturday, 18 Nov 2017 11:02:59 73.136.90.130 128.59.21.9 [DHCP IP: (192.168.0.23)] to MAC address f0:6e:0b:5a:85:ee 1 Saturday, 18 Nov 2017 10:02:22 0.0.0.0 0.0.0.0 [WLAN access rejected: incorrect security] from MAC: f0:6e:0b:5a:85:ee 2 Saturday, 18 Nov 2017 10:02:21 0.0.0.0 0.0.0.0 [DHCP IP: (192.168.0.20)] to MAC address 34:36:3b:c7:b3:48 1 Saturday, 18 Nov 2017 09:33:46 0.0.0.0 0.0.0.0 [DHCP IP: (192.168.0.22)] to MAC address 3c:59:1e:b4:9d:9f 1 Saturday, 18 Nov 2017 09:28:55 0.0.0.0 0.0.0.0 [DoS attack] ICMP Flood from 192.172.226.137 1 Saturday, 18 Nov 2017 07:53:09 73.136.90.130 192.172.226.137 [DHCP IP: (192.168.0.21)] to MAC address 6c:72:e7:20:f5:ef 1 Saturday, 18 Nov 2017 07:39:22 0.0.0.0 0.0.0.0 [DoS attack] Port Scan PROTO:TCP SPT:65526 DPT:4147 1 Saturday, 18 Nov 2017 05:47:52 73.136.90.130 5.8.18.90 [DHCP IP: (192.168.0.20)] to MAC address 34:36:3b:c7:b3:48 1 Saturday, 18 Nov 2017 05:30:14 0.0.0.0 0.0.0.0 [DoS attack] ICMP Flood from 206.117.25.90 1 Saturday, 18 Nov 2017 02:51:08 73.136.90.130 206.117.25.90 [DHCP IP: (192.168.0.20)] to MAC address 34:36:3b:c7:b3:48 1 Saturday, 18 Nov 2017 01:26:23 0.0.0.0 0.0.0.0 - DarrenMSr. NETGEAR Moderator
I am seeing T3 timeouts in your logs this is typically related to a signal Issue I suggest contacting your ISP and have them check your lines and levels.
DarrenM