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. 

[DougChandler]

Yes it is an EE Smart Hub 6 Plus.

[JimM11]

@DougChandler Then hang your Asus on it wan/lan connected, no reason to not do so unless you think Nat may be a issue that you cannot work around. Had mine both ways direct and connected. Posting originally is for the EE 7 Plus version not your 6 Plus.

[DougChandler]

Thanks, I might actually do that and just use it as a dumb modem and ATA.

[JimM11]

@DougChandler Certainly worth considering for sure. Never ever had a wan issue iPv4 or iPv6 with the 6 Plus although was 18 months ago now well before the latest round off FW updates, one day they will get it right. Hopefully your Asus behaves as well as my XT8's did.

[bobpullen]

@DougChandler - I strongly suspect your issue would 'go away' following a full factory reset of the hub as reported elsewhere round these parts. If so, it perhaps suggests some sort of issue/corruption when the hub was last upgraded (they pretty much all upgrade within several mins of being connected for the first time).