Skip to main content
Forum FAQ's
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Smart Hub 7 Plus: IPv6 Router Advertisements not emitted after reboot

patters
Investigator
Investigator

‎04-08-2026 02:54 PM - edited ‎04-08-2026 03:05 PM

Expected behaviour:

In IPv6 Stateless mode, the Hub should advertise the delegated LAN prefix using IPv6 Router Advertisements (RAs), allowing LAN devices to automatically configure global IPv6 addresses.

Observed behaviour:

The Hub shows:

  • IPv6 status: Enabled
  • IPv6 LAN prefix/address present

but does not emit Router Advertisements.

Packet capture on the NAS:

tcpdump -i eth0 -nn 'icmp6 and ip6[40] == 134'

shows no Router Advertisements.

The result is that LAN devices only have link-local addresses:

fe80::/10

(which are generated independently of RAs), but do not receive a globally routable IPv6 address.

A workaround I found:

  • Hub Manager → Advanced Settings → IPv6 → Configuration → Reset to default

Or if that doesn't make a change:

  • Toggle IPv6 allocation mode (for example Stateless → Off → Stateless)
  • Save/apply

After this, the Hub starts sending RAs again on a 1-9 minute interval and the NAS receives a global address, for example:

2a00:1234:5678:9abc:0211:32ff:fe2d:750f

However, after a reboot the Smart Hub will pick up new IPv6 addressing and will subsequently fail to emit any RAs.

 

Firmware version: r4.27.1-R-1862254-PROD-84001

App version: 3.14.5

0 Helpful
13 REPLIES 13
patters
Investigator
Investigator

‎04-08-2026 03:22 PM - edited ‎04-08-2026 03:24 PM

I understand that ISP-supplied routers are not full featured, but when the TCP/IP stack doesn't even work properly: that's a major concern. I am paying to rent this equipment after all.

Please can a moderator forward this information to the appropriate people in EE. I would raise a support request, but there is no way to include this level of technical information and their remit is mainly resolving issues with basic connectivity.

0 Helpful
JimM11
Community Hero
Community Hero
In response to patters

‎04-08-2026 05:23 PM

@patters Have you done a Factory reset to the system since that EE Hub was last FW updated 4-6weeks ago yet?

0 Helpful
patters
Investigator
Investigator

‎04-08-2026 06:12 PM - edited ‎04-08-2026 06:17 PM

@JimM11  Not yet - I saw there was a suggestion that might fix some of the IPv6 issues. But what kind of firmware change is that, that can't migrate an existing config!?

I'm away from home at the moment so it'll have to wait unfortunately.

I did run into this issue several months ago also, so I doubt this recent firmware was the start of it.

0 Helpful
JimM11
Community Hero
Community Hero
In response to patters

‎04-08-2026 06:17 PM

@patters No problems, just going to link the pinned post, and the list off FW updates currently, the 7 Plus still has a few oops on it currently so may take a little while to get there, all off the Hubs had DNS played with so expect the unexpected to say the least.

EE Hub firmware versions - The EE Community

Smart Hub 7 Plus
FW: r3.29.4-R-1511690-PROD-84001 and the gui is at App version 3.7.4 19/12/2025
FW: r3.35.15-R-1597208-PROD-84001 and the gui is at App version 3.11.2 19/12/2025
FW: r3.35.24-R-1648110-PROD-84001 and the gui is at App version 3.11.3 23/01/2026
FW: r4.27.1-R-1862254-PROD-84001 and the gui is at App version 3.14.5 13/07/2026

0 Helpful
JimM11
Community Hero
Community Hero
In response to patters

‎04-08-2026 10:41 PM

@patters Leave it with you, if the Factory Reset does work and hold it's own let the Forum know that fact, did see your other post as well on the pinholes, personally you just cannot trust the FW writers to get it right anytime and if they do not break it or cause issues further subsequent updates.

0 Helpful
Katie_J
EE Community Support Team
In response to patters

‎05-08-2026 08:21 AM

Hi @patters. 

We have passed this thread over to the relevant team.

Could you please confirm how exactly you are restarting the hub? Is this with the physical on/off switch OR using the restart option in the Hub Manager?

Speak soon, 

Katie

patters
Investigator
Investigator

‎05-08-2026 11:16 AM

Hi @Katie_J

Restarted via Hub Manager since I am remote from home at the moment. But to be clear, the default state was broken. I 'fixed it' by resetting/toggling IPv6 but it reverts to broken on next boot.

I will see if this issue is resolved by performing a factory reset when I am back from holiday. Perhaps this is why these issues arise, because maybe the firmwares are tested as clean setups, and not as upgrades from older versions with existing configs.

There is also the other misleading statement in the IPv6 Status page - 'IPv6 network status: Disabled' when it clearly is enabled, but this has also been reported before I notice:
https://community.ee.co.uk/t5/Broadband-Landline/Smart-Hub-Pro-and-IPV6/td-p/1527624
https://community.ee.co.uk/t5/Broadband-Landline/More-on-IPv6-and-Hub-7/m-p/1625315

jak26
Established Contributor
Established Contributor

‎05-08-2026 12:43 PM - edited ‎05-08-2026 12:45 PM

When first using Hub 7+ I did have some probs with a PC taking a while to get its internet connection - the network icon flashing - esp. when waking from sleep or hib - often showing no IPv6 address at first. Then some minutes later it would get IPv6 - I assume it picked up a router advertisement. There also seemed to be delays with device discovery - e.g. getting a NAS hostname.

That PC was connected via an older Access Point - a router in AP mode connected via LAN cable to the hub to provide LAN sockets and good WIFI where devices are located.

When I swapped to a newer Asus AP those PC issues disappeared - it's instantly got v4 and v6 connectivity ever since and my other devices have had no particular connectivity issues either - all connected to the Hub either via LAN, comp WiFi, or the AP.

It's true there are oddities about what's displayed on the Hub status page - but IPv6 test websites etc all show no actual issues with IPv6 connectivity.

There are other quirks with the Hub 7+ like Main WIFI turning back on after a restart - so if EE support do look at threads then there are plenty of others that might also be forwarded to relevant teams

bobpullen
Star Contributor
Star Contributor
In response to patters

‎12-08-2026 05:16 PM

@patters - FWIW, I've just been fiddling with my 7 Plus and I don't seem to be able to replicate what you're seeing so maybe a factory reset will help with things?

Started with a Linux laptop not connected to any network and my 7 Plus powered off.

Checked my wireless NIC did not have any addresses assigned: -

~$ ip -6 addr show dev wlp0s20f3
~$

I then fired up tcpdump to listen for RA's: -

~$ sudo tcpdump -i wlp0s20f3 -vv icmp6 and 'ip6[40] == 134'
tcpdump: listening on wlp0s20f3, link-type EN10MB (Ethernet), snapshot

And powered the hub up. Within seconds of the laptop associating with the hub (trimmed): -

length 262144 bytes
13:34:52.808814 IP6 (flowlabel 0x9db3a, hlim 255, next-header ICMPv6
(58) payload length: 120) _gateway > nix-lappy: [icmp6 sum ok] ICMP6,
router advertisement, length 120
hop limit 64, Flags [managed, other stateful], pref medium, router
lifetime 1800s, reachable time 0ms, retrans timer 0ms
source link-address option (1), length 8 (1): 60:8d:26:d1:53:78
0x0000: 608d 26d1 5378
mtu option (5), length 8 (1): 1492
0x0000: 0000 0000 05d4
prefix info option (3), length 32 (4): 2a00:[REDACTED]::/64,
...

^C
3 packets captured
3 packets received by filter
0 packets dropped by kernel

And then re-checking the the v6 allocation on the laptop, I can see it has addresses assigned: -

~$ ip -6 addr show dev wlp0s20f3
3: wlp0s20f3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
state DOWN group default qlen 1000
inet6 2a00:[REDACTED]::4f3/128 scope global dynamic noprefixroute
valid_lft 86360sec preferred_lft 86360sec
inet6 2a00:[REDACTED]:763c:fa13:7f32:e201/64 scope global
temporary dynamic
valid_lft 604760sec preferred_lft 86331sec
inet6 2a00:[REDACTED]:a67e:d58:aff3:207a/64 scope global
dynamic mngtmpaddr noprefixroute
valid_lft 2147427sec preferred_lft 604765sec
inet6 fe80::d849:f31a:9f20:33d/64 scope link noprefixroute
valid_lft forever preferred_lft forever
...

Then for good measure, I repeated a similar test using a wired Windows machine. This one was already associated with the 7 Plus and had valid v6 assignment: -

> ipconfig /all

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . : lan
Description . . . . . . . . . . . : Intel(R) Ethernet Connection (16) I219-LM
IPv6 Address. . . . . . . . . . . : 2a00:[REDACTED]::1e2(Preferred)
Lease Obtained. . . . . . . . . . : 12 August 2026 12:44:26
Lease Expires . . . . . . . . . . : 13 August 2026 12:44:26
IPv6 Address. . . . . . . . . . . : 2a00:[REDACTED]:2a1f:2fe5:100a:44b8(Preferred)
Temporary IPv6 Address. . . . . . : 2a00:[REDACTED]:356a:9d6:50c8:5464(Preferred)
Link-local IPv6 Address . . . . . : fe80::9b7e:6d37:def6:9cbd%15(Preferred)

This time I fired up Wireshark and then restarted the 7 Plus via the Hub Manager.

At the point of restart I saw two RA packets. I then saw a bunch more once the hub restarted and the laptop reconnected: -

download.png

And ipconfig looks good: -

> ipconfig /all

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . : lan
Description . . . . . . . . . . . : Intel(R) Ethernet Connection (16) I219-LM
IPv6 Address. . . . . . . . . . . : 2a00:[REDACTED]:2a1f:2fe5:100a:44b8(Preferred)
Temporary IPv6 Address. . . . . . : 2a00:[REDACTED]:fcaa:f02d:65e0:7899(Preferred)
Link-local IPv6 Address . . . . . : fe80::9b7e:6d37:def6:9cbd%15(Preferred)