Managed to get the ipv6 set up on my crappy Netgear nighthawk software.
Nice work Yayzi!
1 Like
Yeah, bang on. Once you have the WAN and LAN sides set up, you’re good to go.
Big thanks @Yayzi_Team for getting this out of the door!
1 Like
Glad to see you are enjoying it 
1 Like
This may be a very handy read up for most people, if you’re anyone like me that hasn’t really had to deal with IPv6 before:I Set up IPv6 at Home - Mark Allison
1 Like
Got it working on Opnsense, most difficult part was ensuring monitor IP was correct as it kept failing over to 4G
Well done @Yayzi_Team
2 Likes
Links to help check test
Sadly, GRC ‘Sheilds up’ does not test your firewall on IPv6, This is the best I have found :
1 Like
Hmm, this might take me a bit more work than I was anticipating as after enabling IPv6 my Exchange server connectivity got borked for my PCs - . I need to do some reading up on this too…!!
I’m guessing I’m going to need to assign my Exchange server a local fixed IPv6 to sit alongside the public address it gets from Yayzi/gateway? Then local IPv6 for my PCs too? Not sure why it can’t carry on working on IPv4 though, but there you go. Thought it was all too easy…!
I assume you are running a domain controller if its MS exchange, have you enabled Ipv6 on the DC, and added the v6 subnet to sites and services, also have DNS entries been registered?
In case this helps anyone else, I have an Omada router.
Setting IPv6 doesn’t appear to work, because no WAN IPv6 address is shown.
However, I decided to carry on through setting up LAN side IPv6 based on comments above about it not showing in other routers.
There was an interesting setting: IPV6 prefix ID. This is a value 0-15 which Omada hepfully tells you is “… determined by the Prefix Delegation Size or the Prefix Length received from the IPv6 address on the WAN ports”
Basically it comes from the fact that you need to extend the /60 by a further 4 bits (0-15) and assign a different prefix Id to each interface so that you don’t advertise the same /64 subnet on multiple interfaces.
I’ve set mine up and I’m now happily getting IPv6 addresses for devices on my LAN and test-IPv6.com is happy.
2 Likes
Awesome news!
Glad to see your online with IPv6
1 Like
Thanks for your moral support as I meandered though.
I would like a meaningful update from Yayzi about why this caused a 4.5hr outage.
As customers, I think it’s reasonable to be reassured that they have undertaken a root cause analysis so subsequent updates don’t have the same issue.
I wouldn’t expect to see the full details, but a little transparency wouldn’t hurt.
Excellent - my ER605 is now happy.
I was just going to post for help.
However - around lunchtime I’m expecting the Unifi USG-Max to arrive and will no doubt have the same setup issues 
1 Like
Yeah, IPv6 is enabled on the DC - has to be otherwise everything stops working! - but currently only have a link local address as my internal network is all IPv4. So, no internal IPv6 registered in DNS. I did see that the public addresses got registered in DNS to the DC and the couple of other Windows machines I still had IPv6 enabled on.
So, sounds like I’m going to have to assign static internal IPv6s to machines that already have a static IPv4 and then create an IPv6 scope in DHCP for all the DHCP clients? I was assuming that if they were all given an IP by Yayzi/gateway, they’d still all communicate fine on the LAN. Ho, hum.
Maybe I’ll stick with IPv4 as I just about understand that!!
UniFi is very very nice and easy to setup
On the WAN side you set the following:
On the LAN side you set the following:
1 Like
So just adding this doesn’t affect the LAN side as I’m not ready to start reconfiguring that yet.
yes, If you have IPv6 Disabled on your LAN Setting remains IPv4.
Just had a chat with Ubiquiti - the IPv6 Wan IP not displaying on the Internet setting page, is a bug - will be fixed in some future release.
2 Likes
With UniFi i learnt its not a bug its a feature
1 Like
Unifi users are permanent Beta testers.
4 Likes
