Menu
Reply
  • 3
  • 0
  • 0
dezzadirk
Joining in
143 Views
Message 1 of 6
Flag for a moderator

Regular Wifi dropouts

Hi

Since swapping to a new superhub3 a few months ago after my old router died, I am regularly suffering connection dropouts.  My log files are below:

 Network Log

2017-03-09 18:47:48.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-09 18:58:37.0068010100DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-09 20:51:16.0068010400DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-09 20:51:16.0068010600DHCP Renew - lease parameters tftp file-Vaf7a6c3bcff8bf08.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-12 19:27:13.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-13 01:46:44.0068010100DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-13 02:47:51.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-13 12:16:08.0068010100DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-13 20:20:12.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-13 21:26:50.0068010100DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-13 22:45:34.0068010400DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-13 22:45:34.0068010600DHCP Renew - lease parameters tftp file-Vaf7a6c3bcff8bf08.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-13 22:53:57.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-18 08:41:58.0068010100DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-18 08:51:11.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-18 23:08:45.0068010100DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-19 00:12:22.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-19 06:22:10.0068010100DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-19 07:09:45.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-19 09:58:52.0068010100DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 

Upstream

Channel ID Frequency(Hz) Mode Power
(dBmV) Modulation Channel Bandwidth(Hz) Symbol Rate (ksps)

437600000ATDMA3464 qam64000005120
531000000ATDMA3416 qam64000005120

 

Downstream

Channel Frequency(Hz) Power
(dBmV) SNR
(dB) Modulation Channel ID

12990000004.538.9256 qam13
23230000004.538.6256 qam16
33150000004.538.9256 qam15
43070000004.540.3256 qam14
52910000004.538.9256 qam12
62830000004.538.9256 qam11
72750000004.538.9256 qam10
82670000004.338.6256 qam9
9259000000438.9256 qam8
102510000004.138.9256 qam7
11243000000438.9256 qam6
12235000000438.9256 qam5
132270000003.738.6256 qam4
14219000000438.9256 qam3
152110000004.138.6256 qam2
162030000004.138.6256 qam1

 

Can anyone see any problems? Hope you can help!

Thanks.

0 Kudos
Reply
  • 1.22K
  • 92
  • 229
stevedh2
Knows their stuff
127 Views
Message 2 of 6
Flag for a moderator

Re: Regular Wifi dropouts

Your levels seem ok, however to diagnose if this is a wifi or an internet problem, do you get the same problem with a wired connection?

0 Kudos
Reply
  • 3
  • 0
  • 0
dezzadirk
Joining in
115 Views
Message 3 of 6
Flag for a moderator

Re: Regular Wifi dropouts

Thanks.

I rarely use wired now, but it seems the drops are mainly WiFi. I don't recall issues when using my ethernet connected computer.

However, I'm also using an additional powerline connected WiFi downstairs which is linked to ethernet upstairs. This also regularly drops. This is why im wondering if the problem is occurring before the signal is pushed out as WiFi.
0 Kudos
Reply
  • 9.96K
  • 291
  • 624
Forum Team
Forum Team
92 Views
Message 4 of 6
Flag for a moderator

Re: Regular Wifi dropouts

Hey there dezzadirk,

Thanks for joining the community Smiley Happy

Sorry to hear about your connection problems. I don't see anything obviously out of place when I test your connection this evening. I can see you're connected in Modem Mode, are you able to perform network tests hard-wired direct off your Hub without any 3rd party routers or other devices connected?

Hope to catch up with you soon,

Take care.

Heather_J

Tech fan? Have you read our Digital life blog yet? Check it out


0 Kudos
Reply
  • 3
  • 0
  • 0
dezzadirk
Joining in
77 Views
Message 5 of 6
Flag for a moderator

Re: Regular Wifi dropouts

Hi Heather

Thanks for getting back to me.  I have since changed channels which seems to improved things a little, but i'm still suffering intermittent drops.

Details when taken from a wired PC:

2017-03-18 08:51:11.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-18 23:08:45.0068010100DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-19 00:12:22.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-19 06:22:10.0068010100DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-19 07:09:45.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-19 09:58:52.0068010100DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-19 13:35:36.0068010400DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-19 13:35:36.0068010600DHCP Renew - lease parameters tftp file-Vaf7a6c3bcff8bf08.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-20 01:10:40.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-20 10:28:53.0084000700RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-20 10:28:53.0084000500SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-20 10:28:53.0084000700RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-20 10:28:54.0084000500SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-20 10:28:58.0084020200Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-20 10:29:26.0082000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-20 10:32:48.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-25 06:02:39.0068010100DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-26 13:32:43.0068010400DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-26 13:32:43.0068010600DHCP Renew - lease parameters tftp file-Vaf7a6c3bcff8bf08.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-27 13:49:14.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 

Downstream bonded channels Channel Frequency(Hz) Power
(dBmV) SNR
(dB) Modulation Channel ID

12990000004.538.6256 qam13
23230000004.638.9256 qam16
33150000004.538.6256 qam15
43070000004.538.9256 qam14
52910000004.338.9256 qam12
62830000004.338.9256 qam11
72750000004.138.6256 qam10
8267000000438.9256 qam9
92590000003.738.9256 qam8
10251000000438.9256 qam7
112430000003.938.6256 qam6
122350000003.738.9256 qam5
132270000003.738.6256 qam4
14219000000438.9256 qam3
15211000000438.6256 qam2
16203000000438.9256 qam1

 

Upstream bonded channels Channel ID Frequency(Hz) Mode Power
(dBmV) Modulation Channel Bandwidth(Hz) Symbol Rate (ksps)

437600000ATDMA34.364 qam64000005120
531000000ATDMA34.364 qam64000005120

 

Hope this helps.

Dezza

0 Kudos
Reply
  • 9.96K
  • 291
  • 624
Forum Team
Forum Team
56 Views
Message 6 of 6
Flag for a moderator

Re: Regular Wifi dropouts

Hey Dezza,

Thanks for the update Smiley Happy

Good to hear you've noticed an improvement. Everything still looks good from our end so I'm hoping your connection starts to settle down. If this continues to happen, it might be a good idea to set up a BQM so we can take a closer look.

Catch up with you soon,

Take care.

Heather_J

Tech fan? Have you read our Digital life blog yet? Check it out


0 Kudos
Reply