|
|
My VM nexfibre connection went live recently, speeds are great
However
I am not getting an IPV6 address
Looking at the logs in my Hub5x I see this repeated many times
"Gateway ipv6 address is empty"
In the DHCP settings the hub is set with it's DHCPv6 server "Auto configuration type" set to "Stateless".
Do I need to change this to Stateful?
If so what should be filled in for the Start address
If IPV6 is not yet supported, how can I disable this in the hub?
/Mike Williams
----
2024: Virgin FTTP 1g/100m
2015: plusnet VDSL 80m/20m
2012: Orange WBC 20m/1m
2003: Demon 8m/448k
Edited by Mike_Williams_UK (Tue 10-Dec-24 15:22:20)
|
|
|
VM doesn't provide IPV6 as yet, they've been saying for years they were going to roll it out but nothing.
Regards
JM
|
|
|
If IPV6 is not yet supported, how can I disable this in the hub?
I don't think you need to worry about that. The fact that they have this on and enabled within the hub is probably a good thing. Presumably whenever they get around to enabling this (which won't be any time soon if past behaviour is anything to go by) it'll just start working overnight whenever they flip the switch.
Edited by aidanh (Wed 11-Dec-24 23:26:11)
|
|
Register (or login) on our website and you will not see this ad.
|
|
|
VM doesn't provide IPV6 as yet, they've been saying for years they were going to roll it out but nothing.
I suspect that you are 100% right there.
BUT
Why is their latest hub the Hub5x wasting precious resouces constantly trying to obtain an IPV6 address and also flooding the logs.
There ought to be a way to disable this functiaonality until VM support it.
2024: Virgin FTTP (nexfibre) 1g/100m
2015: plusnet VDSL 80m/20m
2012: Orange WBC 20m/1m
2003: Demon 8m/448k
|
|
|
|
It's not wasting resources in any way that would impact your connection, modern SoCs are optimised for the job they're sold to do and looking for IPv6 neighbours is not going to cause it to break a sweat.
|
|
|
their latest hub the Hub5x wasting precious resouces constantly trying to obtain an IPV6 address and also flooding the logs.
As its only nexfibre areas that use the 5x it seems obvious that the firmware team is over stretched, since no modem mode on 5x compared to the DOCSIS 5. Also a strange decision to not use an ONT and let you use your own router.
25 years of broadband connectivity since Sep 1999 trial - Live BQM
Edited by jchamier (Tue 17-Dec-24 16:14:28)
|
|
|
It's not wasting resources in any way that would impact your connection, modern SoCs are optimised for the job they're sold to do and looking for IPv6 neighbours is not going to cause it to break a sweat.
This is also a job every modern network device does anyway unless you go out of your way to disable IPv6, which you shouldn't do but some devices still do. It's completely normal for your Internet Protocol supporting device to try to configure itself to use the Internet. It's not a waste for it to probe for this, one day it might actually be able to use the Internet.
I found out recently my Android phone (Pixel 7a) supports IPv6 on the Three network but the APN my device was using by default did not have it enabled. When I manually inputted the setting it just started working as you'd expect. It's a good thing most services dual-stack because most people aren't going to be able to figure this out.
|
|
|
I found out recently my Android phone (Pixel 7a) supports IPv6 on the Three network but the APN my device was using by default did not have it enabled. When I manually inputted the setting it just started working as you'd expect. It's a good thing most services dual-stack because most people aren't going to be able to figure this out.
I know my Android phone does ipv6 on my own network. So very little doubt it would do the same for mobile data if I had an APN which supported it.
|
|
|
I found out recently my Android phone (Pixel 7a) supports IPv6 on the Three network but the APN my device was using by default did not have it enabled. When I manually inputted the setting it just started working as you'd expect. It's a good thing most services dual-stack because most people aren't going to be able to figure this out.
I know my Android phone does ipv6 on my own network. So very little doubt it would do the same for mobile data if I had an APN which supported it.
The APN has to say "APN Protocol: IPv6" and "APN Roaming Protocol: IPv6". By default it used to be set to IPv4 only and I did not get IPv6 until I manually changed it by making a new APN (you can't edit the default, you can only view the settings it's using) although if I check it again now it's correctly set to IPv4/IPv6 and I just changed it back to that and can confirm IPv6 still works. I don't know where these defaults come from but they matter.
|
|
|
|
Ah, found that. My APN protocol is ipv4/ipv6, but my roaming profile is ipv4. And i can see how to set up a new APN. So I might try this later.
|
|
|
It's not wasting resources in any way that would impact your connection, modern SoCs are optimised for the job they're sold to do and looking for IPv6 neighbours is not going to cause it to break a sweat.
Agreed the impact of this is probably pretty small in the big scale of things...
BUT
As the Network log is being flooded with entries "Gateway ipv6 address is empty" it becomes as useful as the proverbial chocolate tea pot.
Even more so because the entries shown in the UI are in a random order.
2024: Virgin FTTP (nexfibre) 1g/100m
2015: plusnet VDSL 80m/20m
2012: Orange WBC 20m/1m
2003: Demon 8m/448k
Edited by Mike_Williams_UK (Wed 18-Dec-24 15:26:38)
|
|
|
As the Network log is being flooded with entries "Gateway ipv6 address is empty" it becomes as useful as the proverbial chocolate tea pot.
Agreed. If it looks for ipv6, it should look and report just the once, perhaps followed an extended process of looking which is reported once more. But not flooding the log. This indicates a poorly thought through event model in that area of the software. Looking for an ipv6 gateway should only be prompted by power on or restoring a broken connection, not by a repeating timer.
|
|
|
As the Network log is being flooded with entries "Gateway ipv6 address is empty" it becomes as useful as the proverbial chocolate tea pot.
Agreed. If it looks for ipv6, it should look and report just the once, perhaps followed an extended process of looking which is reported once more. But not flooding the log. This indicates a poorly thought through event model in that area of the software. Looking for an ipv6 gateway should only be prompted by power on or restoring a broken connection, not by a repeating timer.
In the UI (Admin -> Info) it shows an IPv4 and IPv6 lease expiry date, that should be the trigger for the new query. My IPv6 lease expire is currently set to "Sun Jan 25 15:34:12 2161" wheras my IPv4 lease expire is set to "Wed Dec 25 10:29:32 2024", which is realistic being 33 days.
2024: Virgin FTTP (nexfibre) 1g/100m
2015: plusnet VDSL 80m/20m
2012: Orange WBC 20m/1m
2003: Demon 8m/448k
|
|
|
VM doesn't provide IPV6 as yet, they've been saying for years they were going to roll it out but nothing. So, basically a complete lack of competence.
My ISP - IDNet - has been providing it for 20 years now. On the couple of occasions when I've needed assistance setting up my email server they have shown complete understanding and competence.
This is why I'd never switch to an ISP that didn't offer IPv6. Some ISPs just play at it and want your money. Other ISPs know what they are doing and that's those that offer IPv6.
---
Andrue Cope
Brackley, UK
Edited by Andrue (Thu 19-Dec-24 12:20:02)
|
|
|
|
I could be mistaken but I think VM were going to deploy as DS-Lite but changed their minds and now appear to be doing very little.
|
|
|
This is why I'd never switch to an ISP that didn't offer IPv6.
I had the choice of 40 Mbps down and 3 Mbps up with an IPv6 capable ISP, or 300 Mbps down and 36 Mbps up with IPv4 only, and about same price. I preferred speed. Not everyone would make same call. 
25 years of broadband connectivity since Sep 1999 trial - Live BQM
|
|
|
As the Network log is being flooded with entries "Gateway ipv6 address is empty" it becomes as useful as the proverbial chocolate tea pot.
Agreed. If it looks for ipv6, it should look and report just the once, perhaps followed an extended process of looking which is reported once more. But not flooding the log. This indicates a poorly thought through event model in that area of the software. Looking for an ipv6 gateway should only be prompted by power on or restoring a broken connection, not by a repeating timer.
Welcome to modern software development, the standard these days seems to be brute force until it works rather than logical thought on when things should be triggered.
|
|
|
Logical choice, I kept my IPv6 and static IPv4 when I was on VM via L2TP to AAISP anyway.
Edited by Chrysalis (Thu 19-Dec-24 15:31:40)
|
|
|
I’m a fan of the L2TP service but don’t need static at home. Too much cloud now 🙄
25 years of broadband connectivity since Sep 1999 trial - Live BQM
|
Pages in this thread: 
Print Thread
