IPV6 not working

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

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.

In reply to a post by Mike_Williams_UK:

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)

In reply to a post by AyeUp:

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.

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.

Edited by jchamier (Tue 17-Dec-24 16:14:28)

In reply to a post by jpm:

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.

In reply to a post by aidanh:

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.

In reply to a post by DFScale:

In reply to a post by aidanh:

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.