VirginMedia - Modem Mode packet loss

toms88

Ive been having issues for months now since VM released a new fw for the superhub. Ive found countless other people on the virgin forums, reddit and elsewhere all with the same problem. VM Modem mode and PFsense. A variety of purpose built and custom hw, and various versions but issue is the same

BQM Test Graph

I have few options left than dumping pfsense for another router, i tried a cheap TPLink router for test and the issue went away immediately.

The only time i got things working was when virgin replaced my hub but once that picked up the new fw again a week later the issue was back again.

chrisgtl

@toms88 What firmware is your pfSense on?

toms88

@chrisgtl latest stable 2.4.5 i think it is. Was on 2.4.4 before and the upgrade didnt help.

toms88


Last 50 Gateways Log Entries. (Maximum 50)
Jun 8 06:56:44	dpinger		WAN_DHCP 86.20.72.1: Alarm latency 426960us stddev 198763us loss 21%
Jun 8 06:56:54	dpinger		WAN_DHCP 86.20.72.1: Clear latency 430956us stddev 196685us loss 16%
Jun 8 06:57:09	dpinger		WAN_DHCP 86.20.72.1: Alarm latency 425389us stddev 206892us loss 21%
Jun 8 06:57:52	dpinger		WAN_DHCP 86.20.72.1: Clear latency 259339us stddev 273359us loss 17%
Jun 8 07:01:38	dpinger		WAN_DHCP 86.20.72.1: Alarm latency 83680us stddev 129446us loss 21%
Jun 8 07:04:04	dpinger		WAN_DHCP 86.20.72.1: Clear latency 88779us stddev 149591us loss 13%
Jun 8 07:04:49	dpinger		WAN_DHCP 86.20.72.1: Alarm latency 91254us stddev 156650us loss 22%
Jun 8 07:06:29	dpinger		WAN_DHCP 86.20.72.1: Clear latency 159098us stddev 206518us loss 18%
Jun 8 07:06:34	dpinger		WAN_DHCP 86.20.72.1: Alarm latency 192726us stddev 218777us loss 21%
Jun 8 07:10:38	dpinger		WAN_DHCP 86.20.72.1: Clear latency 95432us stddev 159900us loss 12%
Jun 8 07:11:57	dpinger		WAN_DHCP 86.20.72.1: Alarm latency 63818us stddev 132470us loss 22%
Jun 8 07:14:18	dpinger		WAN_DHCP 86.20.72.1: Clear latency 46343us stddev 111998us loss 14%
Jun 8 07:15:25	dpinger		WAN_DHCP 86.20.72.1: Alarm latency 45420us stddev 107473us loss 22%
Jun 8 07:22:14	dpinger		WAN_DHCP 86.20.72.1: Clear latency 135567us stddev 175058us loss 18%
Jun 8 07:22:16	dpinger		WAN_DHCP 86.20.72.1: Alarm latency 132164us stddev 184311us loss 21%
Jun 8 07:26:11	dpinger		WAN_DHCP 86.20.72.1: Clear latency 114141us stddev 160384us loss 16%
Jun 8 07:27:07	dpinger		WAN_DHCP 86.20.72.1: Alarm latency 112021us stddev 153845us loss 21%
Jun 8 07:28:20	dpinger		WAN_DHCP 86.20.72.1: Clear latency 89617us stddev 149985us loss 13%
Jun 8 07:28:49	dpinger		WAN_DHCP 86.20.72.1: Alarm latency 40786us stddev 89870us loss 22%
Jun 8 07:31:54	dpinger		WAN_DHCP 86.20.72.1: Clear latency 134201us stddev 181937us loss 15%
Jun 8 07:34:46	dpinger		WAN_DHCP 86.20.72.1: Alarm latency 90256us stddev 133158us loss 22%
Jun 8 07:36:56	dpinger		WAN_DHCP 86.20.72.1: Clear latency 193545us stddev 215197us loss 14%
Jun 8 07:37:21	dpinger		WAN_DHCP 86.20.72.1: Alarm latency 115041us stddev 174381us loss 21%
Jun 8 07:40:30	dpinger		WAN_DHCP 86.20.72.1: Clear latency 92946us stddev 163492us loss 11%
Jun 8 07:41:19	dpinger		WAN_DHCP 86.20.72.1: Alarm latency 106380us stddev 145955us loss 21%
Jun 8 07:48:16	dpinger		WAN_DHCP 86.20.72.1: Clear latency 123022us stddev 175782us loss 13%
Jun 8 07:49:06	dpinger		WAN_DHCP 86.20.72.1: Alarm latency 67062us stddev 120763us loss 21%
Jun 8 07:50:36	dpinger		WAN_DHCP 86.20.72.1: Clear latency 84720us stddev 145984us loss 15%
Jun 8 07:50:54	dpinger		WAN_DHCP 86.20.72.1: Alarm latency 85372us stddev 158662us loss 21%
Jun 8 07:51:58	dpinger		WAN_DHCP 86.20.72.1: Clear latency 29223us stddev 74969us loss 10%
Jun 8 07:52:41	dpinger		WAN_DHCP 86.20.72.1: Alarm latency 100649us stddev 146143us loss 21%
Jun 8 07:53:52	dpinger		WAN_DHCP 86.20.72.1: Clear latency 91621us stddev 149611us loss 14%
Jun 8 07:54:30	dpinger		WAN_DHCP 86.20.72.1: Alarm latency 118639us stddev 170397us loss 21%
Jun 8 07:55:49	dpinger		WAN_DHCP 86.20.72.1: Clear latency 128044us stddev 172372us loss 17%
Jun 8 07:56:00	dpinger		WAN_DHCP 86.20.72.1: Alarm latency 129800us stddev 178581us loss 21%
Jun 8 07:57:59	dpinger		WAN_DHCP 86.20.72.1: Clear latency 83519us stddev 137705us loss 15%
Jun 8 07:58:30	dpinger		WAN_DHCP 86.20.72.1: Alarm latency 59173us stddev 120838us loss 22%
Jun 8 08:00:45	dpinger		WAN_DHCP 86.20.72.1: Clear latency 83957us stddev 148826us loss 15%
Jun 8 09:09:27	dpinger		WAN_DHCP 86.20.72.1: Alarm latency 202394us stddev 210462us loss 21%
Jun 8 09:11:15	dpinger		WAN_DHCP 86.20.72.1: Clear latency 253879us stddev 232518us loss 16%
Jun 8 12:37:02	dpinger		WAN_DHCP 86.20.72.1: Alarm latency 123710us stddev 184948us loss 21%
Jun 8 12:38:13	dpinger		WAN_DHCP 86.20.72.1: Clear latency 108613us stddev 166153us loss 9%
Jun 8 12:40:31	dpinger		WAN_DHCP 86.20.72.1: Alarm latency 207558us stddev 207142us loss 21%
Jun 8 12:41:15	dpinger		WAN_DHCP 86.20.72.1: Clear latency 87790us stddev 159434us loss 17%
Jun 8 13:10:55	dpinger		WAN_DHCP 86.20.72.1: Alarm latency 195056us stddev 226868us loss 21%
Jun 8 13:11:47	dpinger		WAN_DHCP 86.20.72.1: Clear latency 211431us stddev 245564us loss 15%
Jun 8 13:39:05	dpinger		WAN_DHCP 86.20.72.1: Alarm latency 456379us stddev 129511us loss 22%
Jun 8 13:39:40	dpinger		WAN_DHCP 86.20.72.1: Clear latency 199691us stddev 237870us loss 16%
Jun 8 13:45:53	dpinger		WAN_DHCP 86.20.72.1: Alarm latency 72115us stddev 144726us loss 21%
Jun 8 13:46:51	dpinger		WAN_DHCP 86.20.72.1: Clear latency 130424us stddev 211412us loss 9%
pfSense is developed and maintained by Netgate. © ESF 2004 - 2020 View license.

toms88

also getting tons of these every 20sec or so

Jun 8 16:02:54	dhclient	36334	DHCPREQUEST on em0 to 62.253.131.63 port 67
Jun 8 16:03:10	dhclient	36334	DHCPREQUEST on em0 to 62.253.131.63 port 67
Jun 8 16:03:30	dhclient	36334	DHCPREQUEST on em0 to 62.253.131.63 port 67

crucialguy

What is your pfsense build running on? Is it virtualised by any chance?

It may not be the same issue as mine, but I had EXACTLY the same symptoms you are seeing with Virgin Media and their 'super hub' - turned out that it was the Virtual NIC driver which was causing the issues. I wasn't using the latest VMNX3 driver on this specific VM, so I changed that and just like magic all those issues disappeared.

As i say, it may be totally unrelated to you but I thought I'd share in case it helped.