Re: C6300 wifi problem

LuciferDN · ‎2017-07-17

Really tired about the router. it keeps disconnected only my wifi in every 10 to 15 minutes.

Anyone can help me solve this problem?

My Firmware Version is V2.01.18

The largest packet size from ping tests is 1472 which the mtu size is 1500

DarrenM · ‎2017-07-19

Hello luciferDN

is it all wifi or certain devices? have you tried to adjust the wireless channel?

DarrenM

LuciferDN · ‎2017-07-22

All the devices. I try to restarted it but it disconnected about 10 mins later.

DarrenM · ‎2017-07-26

Can you post the logs from the modem?

DarrenM

hawkeye7 · ‎2017-08-10

Same issue. Firmware v 2.01.18. Log files:

Time	Priority	Description
Aug 08 2017 21:47:53	Critical (3)	No Ranging Response received - T3 time-out
Aug 06 2017 21:23:04	Critical (3)	SYNC Timing Synchronization failure - Loss of Sync
Aug 06 2017 19:40:33	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out
Aug 06 2017 19:40:32	Warning (5)	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Aug 06 2017 19:34:14	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Aug 06 2017 19:32:13	Warning (5)	Lost MDD Timeout
Aug 06 2017 19:32:07	Critical (3)	SYNC Timing Synchronization failure - Loss of Sync
Aug 06 2017 19:14:49	Critical (3)	No Ranging Response received - T3 time-out
Aug 01 2017 15:26:10	Warning (5)	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Aug 01 2017 15:22:19	Critical (3)	No Ranging Response received - T3 time-out
Aug 01 2017 15:19:47	Critical (3)	No Maintenance Broadcasts for Ranging opportunities received - T2 time-out
Aug 01 2017 15:19:42	Warning (5)	Lost MDD Timeout
Aug 01 2017 15:19:38	Critical (3)	SYNC Timing Synchronization failure - Loss of Sync
Aug 01 2017 15:14:30	Critical (3)	No Ranging Response received - T3 time-out
Aug 01 2017 14:49:41	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Aug 01 2017 14:47:14	Warning (5)	Lost MDD Timeout
Aug 01 2017 14:47:08	Critical (3)	SYNC Timing Synchronization failure - Loss of Sync
Aug 01 2017 14:10:02	Warning (5)	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Jul 04 2017 15:47:15	Critical (3)	No Ranging Response received - T3 time-out
Jun 20 2017 05:15:07	Warning (5)	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Jun 20 2017 05:14:08	Critical (3)	No Ranging Response received - T3 time-out
Jun 20 2017 05:14:08	Critical (3)	Unicast Ranging Received Abort Response - initializing MAC
Jun 19 2017 11:38:52	Warning (5)	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Jun 10 2017 05:52:37	Critical (3)	No Ranging Response received - T3 time-out
Jun 05 2017 04:53:49	Warning (5)	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Jun 05 2017 04:52:38	Critical (3)	No Ranging Response received - T3 time-out
Jun 05 2017 04:52:38	Critical (3)	Unicast Ranging Received Abort Response - initializing MAC
Jun 05 2017 04:30:06	Critical (3)	No Ranging Response received - T3 time-out
Jun 05 2017 00:38:13	Warning (5)	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Jun 05 2017 00:37:45	Critical (3)	No Ranging Response received - T3 time-out
Jun 05 2017 00:17:31	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Jun 05 2017 00:15:11	Warning (5)	Lost MDD Timeout
Jun 05 2017 00:15:05	Critical (3)	SYNC Timing Synchronization failure - Loss of Sync
Jun 04 2017 13:34:56	Warning (5)	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Jun 01 2017 12:28:18	Critical (3)	No Ranging Response received - T3 time-out
May 31 2017 13:27:19	Warning (5)	Lost MDD Timeout
May 25 2017 15:59:14	Critical (3)	No Ranging Response received - T3 time-out
May 25 2017 12:43:56	Warning (5)	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
May 25 2017 12:43:37	Critical (3)	No Ranging Response received - T3 time-out
May 25 2017 12:43:14	Critical (3)	REG RSP not received
May 25 2017 12:43:14	Critical (3)	REG RSP not received
May 25 2017 12:43:14	Critical (3)	REG RSP not received
May 25 2017 12:43:14	Critical (3)	REG RSP not received
May 25 2017 12:43:14	Critical (3)	REG RSP not received
May 25 2017 12:43:14	Critical (3)	REG RSP not received
May 25 2017 12:43:14	Critical (3)	REG RSP not received
May 25 2017 12:43:14	Critical (3)	REG RSP not received
May 25 2017 12:43:14	Critical (3)	REG RSP not received
May 25 2017 12:43:14	Critical (3)	REG RSP not received
May 25 2017 12:43:14	Critical (3)	REG RSP not received
May 25 2017 12:43:14	Critical (3)	REG RSP not received
May 25 2017 12:43:14	Critical (3)	REG RSP not received
May 25 2017 12:43:14	Critical (3)	REG RSP not received
May 25 2017 12:43:14	Critical (3)	REG RSP not received
May 25 2017 12:43:14	Critical (3)	REG RSP not received
May 25 2017 12:43:14	Critical (3)	REG RSP not received
May 25 2017 12:43:14	Critical (3)	REG RSP not received
May 25 2017 12:43:14	Critical (3)	REG RSP not received

hawkeye7 · ‎2017-08-10

Description	Count	Last Occurrence	Target	Source
[UPnP set event: urn:schemas-upnp-org:service:WANIPConnection:1#GetNATRSIPStatus] from source 192.168.0.24	1	Thursday, 10 Aug 2017 15:18:59	0.0.0.0	0.0.0.0
[UPnP set event: urn:schemas-upnp-org:service:WANIPConnection:1#GetConnectionTypeInfo] from source 192.168.0.24	1	Thursday, 10 Aug 2017 15:18:57	0.0.0.0	0.0.0.0
[admin login] from source 192.168.0.34	1	Thursday, 10 Aug 2017 15:15:07	0.0.0.0	192.168.0.34
[UPnP set event: urn:schemas-upnp-org:service:WANIPConnection:1#GetNATRSIPStatus] from source 192.168.0.24	1	Thursday, 10 Aug 2017 15:05:10	0.0.0.0	0.0.0.0
[UPnP set event: urn:schemas-upnp-org:service:WANIPConnection:1#GetConnectionTypeInfo] from source 192.168.0.24	1	Thursday, 10 Aug 2017 15:05:09	0.0.0.0	0.0.0.0
[admin login] from source 192.168.0.34	1	Thursday, 10 Aug 2017 15:01:33	0.0.0.0	192.168.0.34
[UPnP set event: urn:schemas-upnp-org:service:WANIPConnection:1#GetNATRSIPStatus] from source 192.168.0.24	1	Thursday, 10 Aug 2017 14:58:42	0.0.0.0	0.0.0.0
[UPnP set event: urn:schemas-upnp-org:service:WANIPConnection:1#GetConnectionTypeInfo] from source 192.168.0.24	1	Thursday, 10 Aug 2017 14:58:41	0.0.0.0	0.0.0.0
[admin login] from source 192.168.0.34	1	Thursday, 10 Aug 2017 14:51:46	0.0.0.0	192.168.0.34
[DHCP IP: (192.168.0.34)] to MAC address 80:00:0b:48:c8:44	1	Thursday, 10 Aug 2017 14:51:42	0.0.0.0	0.0.0.0
[UPnP set event: urn:schemas-upnp-org:service:WANIPConnection:1#GetNATRSIPStatus] from source 192.168.0.24	1	Thursday, 10 Aug 2017 14:51:41	0.0.0.0	0.0.0.0
[UPnP set event: urn:schemas-upnp-org:service:WANIPConnection:1#GetConnectionTypeInfo] from source 192.168.0.24	1	Thursday, 10 Aug 2017 14:51:39	0.0.0.0	0.0.0.0
[DHCP IP: (192.168.0.24)] to MAC address 00:24:b2:0e:52:69	1	Thursday, 10 Aug 2017 14:51:36	0.0.0.0	0.0.0.0
[admin login] from source 192.168.0.34	1	Thursday, 10 Aug 2017 14:51:13	0.0.0.0	192.168.0.34
[UPnP set event: urn:schemas-upnp-org:service:WANIPConnection:1#GetNATRSIPStatus] from source 192.168.0.24	1	Thursday, 10 Aug 2017 14:45:21	0.0.0.0	0.0.0.0
[UPnP set event: urn:schemas-upnp-org:service:WANIPConnection:1#GetConnectionTypeInfo] from source 192.168.0.24	1	Thursday, 10 Aug 2017 14:45:20	0.0.0.0	0.0.0.0
[admin login] from source 192.168.0.34	1	Thursday, 10 Aug 2017 14:41:55	0.0.0.0	192.168.0.34
[DoS attack] ICMP Flood from 128.10.18.52	1	Thursday, 10 Aug 2017 14:39:35	24.98.137.22	128.10.18.52
[DoS attack] ICMP Flood from 129.22.150.78	1	Thursday, 10 Aug 2017 14:39:14	24.98.137.22	129.22.150.78
[DoS attack] ICMP Flood from 129.10.120.193	1	Thursday, 10 Aug 2017 14:38:46	24.98.137.22	129.10.120.193
[UPnP set event: urn:schemas-upnp-org:service:WANIPConnection:1#GetNATRSIPStatus] from source 192.168.0.24	1	Thursday, 10 Aug 2017 14:38:44	0.0.0.0	0.0.0.0
[UPnP set event: urn:schemas-upnp-org:service:WANIPConnection:1#GetConnectionTypeInfo] from source 192.168.0.24	1	Thursday, 10 Aug 2017 14:38:42	0.0.0.0	0.0.0.0
[DoS attack] ICMP Flood from 128.8.126.111	1	Thursday, 10 Aug 2017 14:38:19	24.98.137.22	128.8.126.111
[DoS attack] ICMP Flood from 165.230.49.118	1	Thursday, 10 Aug 2017 14:37:51	24.98.137.22	165.230.49.118
[DoS attack] ICMP Flood from 128.223.8.113	1	Thursday, 10 Aug 2017 14:36:57	24.98.137.22	128.223.8.113
[DoS attack] ICMP Flood from 129.110.125.52	1	Thursday, 10 Aug 2017 14:36:29	24.98.137.22	129.110.125.52
[DoS attack] ICMP Flood from 198.133.224.147	1	Thursday, 10 Aug 2017 14:36:01	24.98.137.22	198.133.224.147
[DoS attack] ICMP Flood from 129.110.125.52	1	Thursday, 10 Aug 2017 14:35:35	24.98.137.22	129.110.125.52
[admin login] from source 192.168.0.34	1	Thursday, 10 Aug 2017 14:34:20	0.0.0.0	192.168.0.34
[UPnP set event: urn:schemas-upnp-org:service:WANIPConnection:1#GetNATRSIPStatus] from source 192.168.0.24	1	Thursday, 10 Aug 2017 14:31:23	0.0.0.0	0.0.0.0
[UPnP set event: urn:schemas-upnp-org:service:WANIPConnection:1#GetConnectionTypeInfo] from source 192.168.0.24	1	Thursday, 10 Aug 2017 14:31:22	0.0.0.0	0.0.0.0
[DoS attack] ICMP Flood from 128.10.18.52	1	Thursday, 10 Aug 2017 14:30:52	24.98.137.22	128.10.18.52
[DoS attack] ICMP Flood from 170.140.119.70	1	Thursday, 10 Aug 2017 14:29:37	24.98.137.22	170.140.119.70
[DoS attack] ICMP Flood from 156.56.250.227	1	Thursday, 10 Aug 2017 14:29:09	24.98.137.22	156.56.250.227
[DoS attack] ICMP Flood from 137.165.1.114	1	Thursday, 10 Aug 2017 14:28:41	24.98.137.22	137.165.1.114
[DoS attack] ICMP Flood from 129.22.150.78	1	Thursday, 10 Aug 2017 14:28:16	24.98.137.22	129.22.150.78
[DoS attack] ICMP Flood from 129.10.120.193	1	Thursday, 10 Aug 2017 14:27:46	24.98.137.22	129.10.120.193
[DoS attack] ICMP Flood from 128.8.126.111	1	Thursday, 10 Aug 2017 14:27:19	24.98.137.22	128.8.126.111
[DoS attack] ICMP Flood from 165.230.49.118	1	Thursday, 10 Aug 2017 14:26:54	24.98.137.22	165.230.49.118
[DoS attack] ICMP Flood from 128.223.8.113	1	Thursday, 10 Aug 2017 14:25:57	24.98.137.22	128.223.8.113
[UPnP set event: urn:schemas-upnp-org:service:WANIPConnection:1#GetNATRSIPStatus] from source 192.168.0.24	1	Thursday, 10 Aug 2017 14:25:42	0.0.0.0	0.0.0.0
[UPnP set event: urn:schemas-upnp-org:service:WANIPConnection:1#GetConnectionTypeInfo] from source 192.168.0.24	1	Thursday, 10 Aug 2017 14:25:41	0.0.0.0	0.0.0.0
[UPnP set event: urn:schemas-upnp-org:service:WANIPConnection:1#GetNATRSIPStatus] from source 192.168.0.24	1	Thursday, 10 Aug 2017 14:25:38	0.0.0.0	0.0.0.0
[UPnP set event: urn:schemas-upnp-org:service:WANIPConnection:1#GetConnectionTypeInfo] from source 192.168.0.24	1	Thursday, 10 Aug 2017 14:25:37	0.0.0.0	0.0.0.0

DarrenM · ‎2017-08-16

Hello Hawkeye7

You have alot of T3 timeouts this maybe a cable line issue I suggest contacting your ISP and having them come out and check your lines.

DarrenM

hawkeye7 · ‎2017-08-16

Thanks, I will follow your advice. My more immediate issue is dropping the wireless connection. Still looking for a solution.

George78734 · ‎2017-10-15

Version:1.0 StartHTML:000000260 EndHTML:000002860 StartFragment:000002009 EndFragment:000002824 StartSelection:000002009 EndSelection:000002824 SourceURL:https://forum1.netgear.com/t5/forums/replypage/board-id/home-cable-modems-routers/message-id/9652

I'm on my second C6300, the first one began dropping WiFi about six months ago and was replaced. Now the replacement unit is doing the same thing. I've diligently looked for a solution on the Internet, but Netgear offers nothing--not even a response to these issues when raised in their own forums! I have been a loyal customer for many years and will never buy another Netgear product! It's truly disgraceful that such a large company would not address such a pervasive issue--they should at least offer a swap-out program or credit to those who trusted them enough to buy their defective merchandise. I'm convinced it is a hardware flaw that they refuse to accept responsibility for. Vote with your dollars. Tell your friends. This company deserves to lose market share for the way they've handled this situation.