IPv6 Trial Update

[#1]

Hi everyone,

The change has just gone out to add IPv6 addresses to everyone that's volunteered to take part. You'll probably need to disconnect and reconnect or reboot your router to pick up the IPv6 prefix. For those on a Hub2 it should just pick it up, other routers may need it enabling.

This site is a good start to test it out: https://test-ipv6.com/

The Plusnet DNS servers support IPv6 AAAA records but only run over IPv4 at the moment as such we're also assigning a he.net IPv6 DNS server address which will should mean the test above gets 10/10.

Please note that any device on your network that supports IPv6 will be assigned an IPv6 address so recoommend checking that the firewall on your router is enabled to stop any external access to your devices. If you want to run an IPv6 server like a web server then on the Hub 2 you can create a pinhole in the firewall which will allow traffic through.

We don't have a specific test plan at the moment so feel free to give things a go and post any issues in this forum and we can take a look into it.

[#2]

Hi Dave,

Can confirm IPV6 is working and all I needed to do was enable IPV6 on the Asus router and disconnect & reconnect!

So far no issues what so ever but if anything comes up I'll let you know! 👍

[#3]

All working for me on a Draytek 2925 will try tp link next!

[#4]

Here is the page from the TP Link router that doesn't seem so keen to connect

[#5]

Hi Dave,

Hub2 user - I left it until this morning but it had not automatically picked up the assigned IP6 range.  Maybe if I'd have had more patience, it would have...

A quick reboot later and the Hub2 has picked it up the IP6 allocation of a /56 as expected.

I have a bit of work to do for further testing as when I had dual-WAN, I disabled the Hub2's DHCP service and I am using an internal DHCP server instead .  ( I needed to set customised IP4 routes and the Hub2 firmware doesn't allow for that ).

All looking good so far!

Thanks,

Mark

[#6]

@zpeterk based on an assumption that the Tplink is almost certainly running some form of Openwrt and my experience with my native Openwrt router..

I'd suggest setting the 'Get Ipv6 addess' to DHCPv6 and the 'Prefix delegation' to Enable

Let us know if that makes a difference

[#7]

Following up on other initial testing:

* Unable to ping6 the Hub2 ip6 address from the lan.  Neighbour solicitation is being sent, but no replies are being received.

* Unable to ping6 the Hub2 ip6 address from the internet.

I'm speculating that the Hub2 needs its DHCP service enabled for IP6 addresses to be assigned to the interfaces.

Cheers,

Mark

08:44:55.868709 IP6 2a02:16c8:xxxx:xx00::yy > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has 2a02:16c8:xxxx:xx00::1, length 32

08:44:56.892549 IP6 2a02:16c8:xxxx:xx00::yy > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has 2a02:16c8:xxxx:xx00::1, length 32

[#8]

Thanks @dave! All enabled on Unifi Gateway and working fine so far. For Unifi I had to enable it on the WAN settings, and then again on each LAN, clients are getting IPv6 addresses. IPv6 test shows 10/10, I am using cloud flare DNS.

[#9]

All working now.  PEBKAC.

I'd got the IP6 address allocation turned off on the hub2.  Allocations are working fine with that turned back on (without turning on the IP4 DHCP service on the hub2).

[#10]

Still no connection

[#11]

Thanks Dave (and colleagues) for this - really great to see IPv6 back on the menu!

Up and running here with a Draytek Vigor 2862 and so far so good. IPv6-enabled clients seem to be doing well, including 10/10 results at test-ipv6.com,  but I need to do some more work on the DNS side of things to get the servers using it in both directions.

[#12]

@zpeterk These are the settings I'm using.

I don't understand why the IPv6 address seems to be a link local one but when I set up the Lan as below, I seem to have IPv6 connectivity.

I hope that helps.

Ian

[#13]

@IMM 

don't understand why the IPv6 address seems to be a link local one but when I set up the Lan as below, I seem to have IPv6 connectivity.

AIUI the WAN connection doesnt get an IP as such, rather it just gets a static prefix which it delegates. Your LAN looks fine and is allocating IPv6 addresses fine.

For info this is what my IPv6 WAN shows

Note, I have manually assigned the OpenDNS IPv6 DNS servers

[#14]

If you are using 3rd party IPv6 DNS provider, you can temporarily disable IPv4 on a device and test some websites. The ipv6 test website should report all good and ipv4 disabled, and get 10/10. A lot of websites and services will not work this way though, so only recommended as a test.

[#15]

Thanks Dave

Can confirm all working with Unifi Gateway Max.

Simple to setup, just enabled DHCPv6 on the WAN with the Prefix Delegation set at 56 .

On the LAN side just Enabled Prefix Delegation for Interface Type, set the correct WAN interface for Prefix Delegation an then set Client Address Assignment to SLAAC. All started working after a reboot of the Gateway.