topic Re: More on IPv6 and Hub 7+ in Broadband & Landline

More on IPv6 and Hub 7+

jak26 — Wed, 24 Jun 2026 11:51:57 GMT

Although it's hard to be certain about what's going on, I've noticed the following a couple of times -

After 5-6 days of the hub left running, when a PC is next started it's no longer given an IPv6 address / DNS - as can be seen in Windows network info or an IPv6 test website or the hub info for the PC device.

Strangely just viewing the address table in Advanced -> My Network in the hub dashboard seems to trigger the PC getting IPv6 - as does togging Allocation mode off and on - but these seem to be temporary as next time the PC starts it again got no IPv6

A more permanent fix was to restart the hub - but 5-6 days or so later I noticed the issue happening again - plus every hub restart is somewhat disruptive and turns main WiFi back on.

---

The overall IPv6 situation is confusing with the hub saying "IPv6 network status: Disabled" and "DNS: IPv4 only" which was mentioned last year in https://community.ee.co.uk/t5/Broadband-Landline/Smart-Hub-Pro-and-IPV6/td-p/1527624

I've still not had the r4.27.1 firmware listed as 'From May' which mentions "New - IPv6 DNS" in case that's at all relevant - but this is another disappointment with the hub.

Re: More on IPv6 and Hub 7+

JimM11 — Wed, 24 Jun 2026 12:31:59 GMT

@jak26 Have you checked with EE as to wither the FW update for the 7+ was pulled or not, with all the issues that were going on it may have been. Was waiting on EE replying but that's a long wait.....

Try a https://whatismyipaddress.com and see what it thinks the device is at just incase, it may be your PC DHCPV6 server at issue and not the hub, also look on the web manager at devices, those that expect to get an iPv6 address should also be showing.....

Think Bob Pullen is going to have a quick look at the Main WiFi restarting when he get's some time to set up his 7+ hub and see how it goes, don't have anything EE wise or i would have done it for you also!

Re: More on IPv6 and Hub 7+

bobpullen — Wed, 24 Jun 2026 12:57:36 GMT

@jak26 wrote:
Strangely just viewing the address table in Advanced -> My Network in the hub dashboard seems to trigger the PC getting IPv6 - as does togging Allocation mode off and on...

First of these is very bizarre. The second might be explained by the fact that toggling the allocation mode restarts either the PPPoE broadband connection, or the hub itself i.e. it's similar to powering the hub off/back on. Is it just the Windows device exhibiting this problem? You might need to delve into the event logs to try and work out what's going on.

The overall IPv6 situation is confusing with the hub saying "IPv6 network status: Disabled" and "DNS: IPv4 only" which was mentioned last year in https://community.ee.co.uk/t5/Broadband-Landline/Smart-Hub-Pro-and-IPV6/td-p/1527624

The status thing is a bug for sure. I see it too. IPv6 is working for me though. I think I've mentioned elsewhere but DNS showing 'IPv4 only' is entirely expected. That information is under the heading IPv6 WAN details i.e. the DNS assigned to the WAN/Internet interface of the router.

Look under Advanced Settings > Broadband and you'll see the DNS addresses assigned to the WAN interface at the bottom of the page; they are both IPv4 addresses. I predict this might change at some point in the future but for now, the EE DNS servers only operate over IPv4.

I've still not had the r4.27.1 firmware listed as 'From May' which mentions "New - IPv6 DNS" in case that's at all relevant - but this is another disappointment with the hub.

The firmware is still being rolled out. Rollouts can take months from the first pilot stages to the point that they've reached everybody.

I doubt your complaints are related as the change looks to be LAN side i.e. old firmware your devices obtain an IPv6 address and an IPv4 DNS address. Post firmware, your devices obtain an IPv6 address and an IPv6 DNS server address. The WAN interface of the hub itself will still only have an IPv4 DNS address.

Edit: @JimM11 - yep, going to try the main WiFi re-enabling thing later today.