jgtimperley
Up to speed
Joined 9 years ago
User Profile
User Widgets
Contributions
Re: IPv6 support on Virgin media
To try and add a bit more data to this, I'm on bagu-cmts-16 (which is a Cisco) and confirm I see NO router-advertisements from my Virgin Hub 3 in modem mode 😞. My area is a DOCSIS 3.1 area, as M1000 is showing as available at my address. In other news, I have tried a he.net IPv6 tunnel a few times over the past 4 years, and consistently get shocking (<20Mbit) performance on IPv6 traffic, while getting 370Mbit+ on IPv4. Routing a /64 over a Wireguard VPN to a Linode VPS gives me 350Mbit, presumably losing a bit due to the overhead. L2TP to the same Linode VPS was giving me 350Mbit for a little while, but then out of nowhere started behaving like the he.net 6in4 tunnel. It was fun to experiment, and I've been tempted to keep the Wireguard tunnel up and running, but I'm back to native v4-only at the moment. That said, I had no issues with the /64 that Linode gave me, and Netflix etc worked OK without detecting any VPN (and I did verify it was using the IPv6 block). Thankfully my area is OK congestion wise, and I believe I'm on a pretty quiet segment, so even the single-threaded nature of a tunnel wasn't causing any major loss in performance.14KViews0likes0CommentsRe: UDP issues on SuperHub3 - collective thread
I got an update to 9.1.1912.304 overnight, which is a minor bump from 9.1.1912.302, and relatively close to the last update. I purposefully avoid unnecesarry UDP traffic since discovering the original issue documented here, but wondering if anyone else on here has the new firmware, and is seeing any improvements. I'm not in a rush to test, as we both rely heavily on Teams/Zoom calls, which have been spot on since reducing UDP flows.2.9KViews1like43CommentsRe: UDP issues on SuperHub3 - collective thread
legacy1 wrote: Likely VM have a custom rate limiting on the hub to delay traffic the faster you go. I don't believe this is the case. Even a relatively small amount of UDP (as demonstrated on this thread) can cause the hub to choke. It's the same issue that causes 6in4 tunnels to have dire performance. It's yet another shortcoming of the Puma 6 in these modems.2.5KViews2likes0CommentsRe: UDP issues on SuperHub3 - collective thread
jphobbs wrote: I've just had a thought. I've been trying to reduce UDP usage over the last few days and have seen a massive improvement. A quick update from me, this is exactly what I've done too and it's made a massive improvement, including on firmware 9.1.1912.302, which was giving me issues before. I'm now back in modem mode and Teams calls are acceptable once again. The only thing I've changed is minimising UDP traffic. I even found that the DHT 'heartbeats' that torrent clients send out, even with no torrents active or added, were enough to cause the hub to grind to a halt in modem mode.2.6KViews2likes4CommentsRe: UDP issues on SuperHub3 - collective thread
jgtimperley wrote: Once I'm off this video call I'm going to try modem mode again, and see how it is. I'll report back. Now back in modem mode (on 9.1.1811.401), and typically, I start seeing errors on the RF side of the link. The Virgin guys look to be doing maintenance on the cabs (mostly seems to be the smaller cabs rather than the actual 'node' which is at the top of my street). When I'm not getting RF errors, things seem to be much much better on 9.1.1811.401. I'll keep it in modem mode for now and wait for the RF side to settle down. Things seem better though so far. I'll raise a seperate thread specifically about the firmware issues with modem mode, if things do appear to be down to 9.1.X firmware. Thank you for the input all.2.6KViews0likes0CommentsRe: UDP issues on SuperHub3 - collective thread
Eeeps wrote: jgtimperley wrote: OK, just put the Hub 3 into Modem mode and it's stayed on 9.1.1912.302. How long did yours take to revert - did it do it immediately, or overnight maybe? It'd didn't revert immediately but after a soft boot. Yesterday I tried modem mode and it stuck to 9.1.1912.302, even after a few reboots. I went back into router mode and left it overnight. Even in router mode, overnight, the hub had downgraded to 9.1.1811.401. Once I'm off this video call I'm going to try modem mode again, and see how it is. I'll report back.2.7KViews0likes1CommentRe: UDP issues on SuperHub3 - collective thread
>Have VM recognised this as a problem with the 9.1.1912.302 firmware in modem mode? >I normally use my SH3 in modem mode and it was on 9.1.1811.401 without significant issues. >I briefly put it into router mode and it upgraded to 9.1.1912.302. >When I placed it back into modem mode it down graded to 9.1.1811.401 which it is still on. This is *very* interesting. I'll give modem mode a try later on this evening and see if the firmware downgrades. On router mode I'm definitely still on 9.1.1912.302.2.8KViews0likes12CommentsRe: UDP issues on SuperHub3 - collective thread
>Unfortunately not in my case. Sure, router mode works 100x better, but it's only 100x better than "doesn't work at all" 🙂 What I'm saying is that I bet that someone at VM will at least think about dropping support for "modem mode" as to fix the issue, but that's not a viable fix or even workaround. Even in router mode SH3s are struggling with UDP, not as bad as in modem mode but still. All agreed. I've only ever had the Hub 3 (only got Virgin 4 years ago and this is my first experience with them). The backup Openreach FTTC is noticeably better in *every* aspect other than speed, and unfortunately 20Mbps down doesn't really cut it these days. If I could get 80Mbps, then I'd probably not even have the Virgin line, but at around 1km from the FTTC cab it's never going to be great. Also agreed that router mode isn't a fix, and it would be great to have modem mode back again, but for the time being I'll just wait this one out and stay in router mode. For reference, I'm on firmware 9.1.1912.302, and connect back to a Cisco CMTS (cmts 16 in Baguley).3.8KViews1like18Comments