Hourly disconnects
 

Hi all,

Looking for some advice really... Bit of a long story..

Was on 100Mb with a SH2AC, everything running along fine. Upgraded the TV to a V6 and still running fine for several weeks.

Then started getting disconnects where the internet light would go red for 30 seconds or so. This was happening pretty much hourly. I have a thinkbroadband monitor in place which was showing packet loss every hour on the hour. Tracked this down (thanks to some help on the VM Forum) to an hourly DHCP lease.

This became a problem for streaming etc, especially with 2 kids in the house!

Called VM and got a technician out who swapped the SH2AC for a Hub 3.

After he left and I finally got into the web management on the Hub 3 (man it's slow on the interface !) and saw that I was still getting hourly DHCP renews despite the change in equipment and IP address.

The Hub 3 seems to handle things better in that I don't get a total drop in service every hour but it's one of those things that really bug me and I'd like it fixed. This is where the problems kick in...

I have called 150 several times, getting India each time, and been talked through rebooting the hub (and told that if I can get to bbc.co.uk after it's working fine) and also told that my wifi may be poor (!).

I have a thread on the official forum ( http://community.virginmedia.com/t5/...541763#M175100 ) which VM have roundly ignored for 3 weeks now and just don't know what to do to get this resolved.

Hoping one of you guys may have some advice....?

Thanks

Bri

Re: Hourly disconnects
 

I feel you've put 2+2 together and got 5 a little bit. Those hourly DHCP renewals aren't anything to worry about and over time they'll get longer. As long as your IP isn't changing every hour, a DHCP renewal won't cause a drop in connection - it's an entirely normal thing and all of your devices will be doing the same, not just your hub.

I suspect the hourly renewal previously was a result of a separate issue, a symptom rather than a cause. If your connection is stable and good now, then don't worry about it.

Re: Hourly disconnects
 

Thanks Kushan,

I was definitely getting hourly disconnects on the SH2AC, we couldn't stream from iplayer etc reliably as the connection did a full drop followed by a DHCP renewal and reconnect. This also showed as an hourly spike of packet loss on the thinkbroadband quality monitor (can be seen on the official VM Forum link in my first post).

The Hub 3 seems to handle it much more gracefully but the logs are just full of DHCP renewals every 45 minutes or so:

Network Log
Date And Time Error Number Event Description
2017-10-25 15:51:16.00 68010100 DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-10-25 16:00:18.00 68010400 DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-10-25 16:00:18.00 68010600 DHCP Renew - lease parameters tftp file-cmreg-vmdg505-rtsl10016u-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-10-25 16:33:16.00 68010100 DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-10-25 16:42:19.00 68010400 DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-10-25 16:42:19.00 68010600 DHCP Renew - lease parameters tftp file-cmreg-vmdg505-rtsl10016u-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

This has been happening for a month solid and compared to my previous DHCP leases of 5 - 7 days seems a bit weird...?

Thanks again

Bri

Re: Hourly disconnects
 

Do you have a free www.thinkbroadband.com monitor?

https://www.thinkbroadband.com/broad...toring/quality

Re: Hourly disconnects
 

Hi Taf,

Yes, the graph from my 2AC is in the VM forum (link to thread in first post).

I have one setup for my new IP (when the Hub 3 got installed) which is much better with just a couple of small packet losses in the early hours.

Thanks
Bri

Re: Hourly disconnects
 

This is what I'm saying, this disconnect is what caused your DHCP renew, not the other way around. Ignore DHCP, it's not an issue here.

Re: Hourly disconnects
 

Are you using OpenDNS? Some months ago I had a similar problem and thought I had a virus but couldn't find anything.

After a lot of help from someone on the Malwarebytes Forums and finding nothing he suggested trying OpenDNS or Google DNS. I was already using OpenDNS so switched to Google and the problem stopped.

Google DNS
8.8.8.8
8.8.4.4

Re: Hourly disconnects
 

Hi,

It's not my internal network DHCP with an hourly lease, it's the modem / VM DHCP.

It's been going on for a month now and I'm unfortunately not getting anywhere with getting it back to a week's lease so I guess I'll just ignore it for now. If there is a connection issue as Kushan thinks then unfortunately it's not showing in any of the other stats which all appear to be fine.

Thanks again

Re: Hourly disconnects
 

I get those DHCP errors all the time on my SH3, and it doesn't cause my any disconnects so I'm inclined to agree with Kush here.

Re: Hourly disconnects
 

I have had a look at your graph and it's amazing that it happens every hour like clockwork. Can you post stats in here out of curiosity. If you don't know what to do click here. Have you got a spare 3rd party router so you can put the shub into modem mode and use another router?

Re: Hourly disconnects
 

Hi General,

No problem, stats below:

Downstream bonded channels
Channel Frequency(Hz) Power(dBmV) SNR(dB) Modulation Channel ID
1 299000000 2.4 38.6 256 qam 13
2 323000000 1.7 40.3 256 qam 16
3 315000000 2 40.3 256 qam 15
4 307000000 2.4 40.3 256 qam 14
5 291000000 2.5 40.3 256 qam 12
6 283000000 2 40.3 256 qam 11
7 275000000 2.4 40.3 256 qam 10
8 267000000 2.2 38.9 256 qam 9
9 259000000 2.7 38.9 256 qam 8
10 251000000 2.5 38.9 256 qam 7
11 243000000 3 38.9 256 qam 6
12 235000000 3 38.6 256 qam 5
13 227000000 3.7 40.3 256 qam 4
14 219000000 3.5 40.9 256 qam 3
15 211000000 4 40.3 256 qam 2
16 203000000 4.3 40.3 256 qam 1

Upstream bonded channels
Channel ID Frequency(Hz) Mode Power
(dBmV) Modulation Channel Bandwidth(Hz) Symbol Rate (ksps)
2 39400000 ATDMA 41.8 64 qam 6400000 5120
1 46200000 ATDMA 41.8 64 qam 6400000 5120

Operational Configuration
General Configuration Value
Network access Enabled
Maximum Number of CPEs 1
Baseline Privacy Enabled
Docsis Mode Docsis30
Config file ;kfoA,.iyewrkldJKDHSUBsgvca69
Primary Downstream Service Flow SFID 438
Max Traffic Rate 115000000
Primary Upstream Service Flow SFID 437
Max Traffic Rate 6320000

Network Log
Date And Time Error Number Event Description
2017-10-27 15:26:22.00 68010400 DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-10-27 15:26:22.00 68010600 DHCP Renew - lease parameters tftp file-cmreg-vmdg505-rtsl10016u-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-10-27 15:59:28.00 68010100 DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-10-27 16:08:33.00 68010400 DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-10-27 16:08:33.00 68010600 DHCP Renew - lease parameters tftp file-cmreg-vmdg505-rtsl10016u-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-10-27 16:41:22.00 68010100 DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-10-27 16:50:24.00 68010400 DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-10-27 16:50:24.00 68010600 DHCP Renew - lease parameters tftp file-cmreg-vmdg505-rtsl10016u-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-10-27 17:23:29.00 68010100 DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-10-27 17:32:33.00 68010400 DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-10-27 17:32:33.00 68010600 DHCP Renew - lease parameters tftp file-cmreg-vmdg505-rtsl10016u-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-10-27 18:05:23.00 68010100 DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-10-27 18:14:23.00 68010400 DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-10-27 18:14:23.00 68010600 DHCP Renew - lease parameters tftp file-cmreg-vmdg505-rtsl10016u-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-10-27 18:47:27.00 68010100 DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-10-27 18:56:32.00 68010400 DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-10-27 18:56:32.00 68010600 DHCP Renew - lease parameters tftp file-cmreg-vmdg505-rtsl10016u-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-10-27 19:29:22.00 68010100 DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-10-27 19:38:24.00 68010400 DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-10-27 19:38:24.00 68010600 DHCP Renew - lease parameters tftp file-cmreg-vmdg505-rtsl10016u-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;


The thinkbroadband graph you saw was from the SH2AC and suddenly started getting a 1 hour DHCP lease from VM, upon renewal it would disconnect and reconnect causing dropouts and the hourly packet loss.

The Hub 3 seems to handle things more gracefully but has been installed for two weeks now and still getting an hour DHCP lease.

I do have an old Cisco E4200v1 somewhere which I might dig out over the weekend if I get a minute (2 kids makes troubleshooting a little tricky !)

Thanks

Bri

Re: Hourly disconnects
 

absolutely dude, the E4200 as old as it is now will handle the download speed no probs so you don't need to worry about a performance decrease. Your power levels are fine which makes me think it is a more serious problem up the network but I am very curious to see what will happen when the shub gets put in modem mode.
The thing is that if it was a problem higher up like at the cmts, it should be affecting everybody and you would think a lot of people would notice hourly disconnects and be ringing up and VM would be aware of it.

I would suggest hooking up the Linksys asap this morning so you can leave it connected all weekend and have a solid two days of graphing for diagnostic purposes. When you put the shub in modem mode your Linksys is going to get a completely different ip address (which is a good thing in your case) so you'll need to update the info for your TBB graph. When you do can you share the live graph (not a snapshot) in this thread. I'll be watching it this weekend and there are many forum users who are far more knowledgeable than me (including VM network techs) who I am sure will be keeping an eye on it as well).

Re: Hourly disconnects
 

I think there's been a misunderstanding. I was saying your previous connection issues were causing the DHCP requests then, but as you're currently not having connection issues then I Wouldn't worry about it.