24-06-2026 12:51 PM
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.
24-06-2026 01:31 PM - edited 24-06-2026 01:31 PM
@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!
24-06-2026 01:55 PM - edited 24-06-2026 01:57 PM
@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.
25-06-2026 01:33 PM
Thanks @bobpullen and @JimM11
Thanks @bobpullen for checking the main WIFI turning back on - it's not a major problem - just need to remember to toggle these settings back off after each restart
---
Coming from PN, IPv6 is new to me so I don't know the significance of the hub DNS showing 'IPv4 only' on the hub but I can say -
- my PC and other devices do get an IPv6 DNS server as well as IPv6 address(es) and an IPv6 gateway (as well as an IPv4 versions) - this is easy to check in W11 advanced network settings -> Hardware and connection properties
- after the hub has been running for 5-6 days then when the PC next starts it doesn't show any of those IPv6 items - it's entirely IPv4. Those quick fixed seem to bring IPv6 back but it needs a hub restart to fully fix for another week.
- right after joining, the IPv6 test site was only scoring 9/10 failing on 'ISP DNS doesn't have IPv6 access' but this changed in the last couple of weeks and now scores 10/10
---
I was only saying I'm still on older f/w version for clarity but with so many irritants already I might just go with another router - normally I stick with ISP router which makes support calls easier and the PN hub 2 was glitch free - i use an AP anyway so don't need WIFI 7 etc from the ISP router - just reliability
25-06-2026 02:13 PM - edited 25-06-2026 02:23 PM
@jak26 Are you using a DV Digital Voice landline on your connection, also did PN request you send them your old PN Hub back? When the IpV6 address disappears on the PC, have you looked at the Hub with the web manager interface, to see if any other devices are still receiving IpV6 addresses at that time, possible to look on your mobile etc to see if that is being issued correctly etc.... Just wonder if they are not being passed through on your AP but the Hub thinks everything is ok that way!
Honestly do not remember any issues on IpV6 at all 18months ago, but was using the EE Smart Hub 6+ version and the Asus hanging on the EE Hub or direct on the ONT, both seemed fine.
26-06-2026 06:14 PM
I have a further observation as learning more about IPv6 behaviours
The PC gets two IPv6 addresses (plus the link local addr) - a IPv6 address - and a temporary IPv6 address which changes each time the PC wakes - the idea being a changing address helps privacy
From scratch, the two addresses seen in Windows match the two GUAs seen when viewing network info via the hub dashboard
On next wake the PC gets a new temp IPv6 address but the hub is not forgetting the old one - so there are now 3 GUAs listed - the current addr + current temp addr but also the old temp addr . This accumulation continues with each PC wake.
It's early days but it's possible the issue with IPv6 seeming to no longer be allocated happens after around 5 wakes - i.e. after around 6 GUAs have been accumulated in the hub for the PC
I don't know the process by which previous temp IPv6 addresses are meant to be cleared/forgotten by the hub
26-06-2026 07:07 PM - edited 26-06-2026 07:33 PM
@jak26 Correct, i have my Laptop and desktop pc Temp ones disabled as need to keep the one access. search below will show you how if you wish to do it you can always re-enable when needed, just search the text below and use the netsh to do so. Then again use the Asus router, but do see the multiples off the wifes etc does not appear to be an issue, will keep a count on them to see, think you may be onto something with the 7+ hub though.
windows 11 disable Temporary IPv6 Address
What the Asus Router thinks iPv6 wise.....
On Laptop one she is sitting at 30 entries.
On Laptop two she is sitting at 5 entries, that one i have been working on as there is a screen flicker driver issue with win11 trying to pin that down....
Will find the perm and the temp on that one and reboot so i know....
You would not believe it but both are being exercised by her just now, so will get on it when she goes to bed later!
Mine screen link is good below, only one entry as you will see.
Re: Anyone actually getting anywhere near 900MB? - Page 3 - The EE Community
27-06-2026 12:45 PM - edited 27-06-2026 01:02 PM
Thanks @JimM11
So far it seems to be when the PC wakes from sleep state that the hub keeps the previous temp IPv6 address and accumulates them each day - on wake from hibernate or restart I'm not seeing this happen
The accumulation of old temp addresses is only seen in the network info in the hub dashboard - the Windows network info like your post always shows just 2+link local IPv6 addresses (until IPv6 goes wrong)
Wake from sleep is less common for desktop PCs but quite common for laptop users - but it does need someone to look at IPv6 network info to notice the problem.
The next thing for me to try is to confirm it's when the number of accumulated GUAs reaches some number (such as 6) that I get the IPv6 issue needing a hub restart
Then I will try a work-around like
Set-NetIPv6Protocol -UseTemporaryAddresses Disable
Other useful commands are
ipconfig
netsh interface ipv6 show privacy
I'm going to swap my slightly older Access Point with a new Asus tri-band Wifi 7 (on offer right now) and along with the hub f/w update (if I ever get it) see what happens
Then I might have to get another Asus to replace the hub if all else fails
27-06-2026 01:15 PM
@jak26 Pure Asus user myself, 2-XT8's and 2-RP-AX58's in use with a little powerline for the awkward spot's, the wife's 30 plus Temp iPv6 that the Asus records does not seem to care about them in the logging, will be about right amount as Router is up 41 day's and it is her additional Laptop for when she moves about the home, one downstairs and one upstairs....
Me only got the one as turned TEMP off, no need for me to have it on!
27-06-2026 06:50 PM
Cheers @JimM11
For now my plan to see if there's a pattern to the PC stopping getting IPv6 - like after some number of days or restarts - has failed as the PC's stuck on not getting IPv6 on startup - but then after a minute or so it magically gets IPv6
Things working after a delay prob means when I thought I'd tiggered IPv6 myself was just co-incidence - it had just fixed itself after the delay
These aren't the only things I've noticed seem to happen after some strange delay - add this to not having much confidence in what either the app or the dashboard say
But these are minor irritants I suppose - things do work in comparison with other people's bigger issues so will have to learn to ignore these glitches