More on IPv6 and Hub 7+

[jak26]

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. 

[JimM11]

@jak26 You can also take a look when you are logged onto the Forum page and see all the connections you are making, just noticed first time it has thrown up my iPv6 and the iPv4 in the field... Going to delete it and see what happens later.

Personal - My settings - The EE Community

[jak26]

Thanks @JimM11 

I'm back to square one in trying to see any pattern in what I'm seeing

These are things happening right after the PC wakes from sleep or hibernate - 

a) sometimes I wasn't seeing the NAS hostname in network so lost access to folders - this fixed itself after some minutes but now it doesn't seem to happen much

b) waking from sleep there is a delay of 10s or so before Windows gets its internet connection but waking from hibernate it's only a couple of seconds

c) if I check Windows network info there's sometimes no IPv6 connectivity showing - only IPv4. 

- this seems to happen more when waking from sleep

- after some minutes IPv6 does seem to start working by itself

Sleep and hibernate aren't apples to apples as the PC is off for only a few hours in sleep but much longer when hibernating so time might be another factor making things hard to pin down 

[JimM11]

@jak26 I do not use hibernate at all, have it completely disabled and turned off for all Pc's one off the first thing's i do, sleep in general have no issues as all devices 99% of the time waken ok, but my sleep is up at 2hrs time which in general may only happen once or twice a day just depending on what i am doing, main desktop going to say been sleeping now at least 36hrs or so going to waken it up, never had any problems with that ever, will let you know in a couple mins, once i have a look at all the windows logs etc, only Nic connected just now with the wifi turned off on it currently! Pretty sure NIC is to the switch and switch is on the XT8, kept it that way after all the EE Hub NIC issues to get past all off that!

Desktop went sleepy 26/06/26 at 6:40pm appox, just woke it no issues, have done the forced button sleep now will give it an hour or so and waken it back up again later and also take a quick look.... 

May not be able to shed much light on this for you as using a real router on the connection...🤔 When i waken the PC up, going to hit edge/ee forum as quick as possible and see what transpires with it!

Edit added screen capture but the nic was up within 1 second of waken from sleep, took me longer to login, open get EE and passcode but no connection issues, say that was about 5 sec's or so.

Sleep to waken Desktop PC

[jak26]

Thanks again @JimM11 

What's causing this behaviour at resume from sleep is unclear, it might be some Windows issue - there are posts over the years about this - but my ATV 4K streaming box is also affected 

On resume from sleep a) it's slow (10s or so) to get internet connectivity (the icon stops flashing) and b) quite often Windows network info shows no IPv6 - but this can fix itself some minutes later

Some of this aligns with Router Solicitations (RS) and Router Advertisements (RA)

An RS from the PC at wake should provide the PC with IPv6 - no idea why this isn't working

A regular RA from the hub some minutes later ls likely why IPv6 fixes itself 'by magic'

After a chat with Copilot the following commands seem - perhaps by tiggering an RS - to instantly fix IPv6

netsh interface ipv6 set interface "Ethernet" routerdiscovery=disabled

netsh interface ipv6 set interface "Ethernet" routerdiscovery=enabled

I can try adding these commands to a startup script - perhaps with a delay to allow for the 10s spent trying to connect (the script is triggered by event 1 from Power-Troubleshooter seen in your event log )

[JimM11]

@jak26 Go for it, give it a try you got nothing to lose, just really hope that it's nothing to do with the Ethernet Nic port connection, i only had the EE Smart Hub 6+ version, connection and wake up was 30 second delay no matter what was done so just an easy spot at that time circa 2 years ago and on the latest FW just released EE are now addressing it, i just threw a Tp-Link switch on the EE Hub, kept the port always up and PC was an instant Ethernet connect through the switch. EE never admitted to the Pro version but many post's got sorted by the switch although the Pro was a fair bit quicker, highlighted the part below. March 2024 joined EE left March 2025 just had enough major FW End Feb2025 seriously oops'd the Hub operation...

Firmware version: r4.26.1

Deployment date: From April 2026

Hub Type: SH30A, SH31B, SH32B

Release notes: 

• Platform updates & security patches
• Improved WiFi stability/performance
• New - Digital Voice Contacts backup/export
• New - IPv6 DNS
• New - EE WiFi-Auto
• Fix - Microsoft Teams/UDP issues in some situations
• Fix - Pixelation/IPC6023 errors in some situations when viewing subscription EETV channels
• Fix - Ethernet/wired devices taking a long time to establish connection

[JimM11]

@jak26 Are you seeing the PM i send to you?

[jak26]

Thanks @JimM11

It doesnt feel like an NIC issue, in any case the PC is already connected via an Access Point (a router in AP mode ) but just in case the AP somehow messing things up this will be the unit I'll be replacing with a new Asus

Just 1 sec after the wake power-troubleshooter event 1,  there is  

event 100000 Network Connected

But it's a whole 13 secs later before  

event 4042 V4 Capability: ActiveHttpProbeSucceeded

- so it was actually more than 10 secs the network icon was flashing

After running those fix commands, the following is logged

event 4042 V6 Capability: ActiveHttpProbeSucceeded

[JimM11]

@jak26 oops my bad, forgot you had the Asus AP connected to the EE Plus, that would be keeping the port up.

[JimM11]

@jak26 Just took the look at the Good Ladies iPv6 Temp addresses, so Asus now has logged 32 entries against her and sure looks to be working as expected that way. The temp address is up and front for the wan connection and double check that, also re-enabled on my desktop but don't expect it to throw any curves at all!

[jak26]

Thanks  once again @JimM11 

Waking from hibernate I see the network icon stop flashing quickly - just like things used to do before switching to EE and the Hub 7+ 

This is confirmed by seeing event 4042 V4 logged just a couple of seconds after wake  and then event 4042 V6 a couple of seconds later.

Waking from sleep event 4042 V4 takes 13 secs and there's no event 4042 V6 so no IPv6 

A new ISP likely means new DNS, but setting a non-ISP DNS, or a static IP address, or playing with NIC power settings all have zero impact

Theories around temp IPv6 addresses haven't panned out either - there's something going on after wake from sleep I don't yet understand

Ive still got the older AP in the path - the swap to Asus unit is a future step