IPv6 Gateway/Router DHCP issue
Anybody experienced this?
I have Purple setup in Router mode and it is getting IPv6 address and gateway from the ISP (I know this because prior to this setup, I was using a NetGate and was getting full IPv6 connection). Unfortunately, Purple is not sending the IPv6 Gateway to the clients.
Any ideas?
-
I remember something like this happening when I first got my Firewalla earlier this year.
I had been using pfSense and then OPNSense and had IPv6 working with both. I was sending a prefix hint for a /56 to my ISP and that worked.
When I got Firewalla, I saw that it was, by default, sending for a /60. I figured I could change that to a /56 like I had used previously, but that didn't work properly. I wound up going back to Firewalla's default of a /60 and it's been working fine ever since.
Some of the symptoms were that Firewalla wasn't passing along the correct info to the clients on my network. I don't remember if that involved the gateway or not, so I don't really know if you're seeing the same kind of issue.
If you did change the hint to something other than the default, I'd recommend changing it back and seeing what happens.
-
@Rom
Can you double check if the box itself gets the IPv6 address allocated from ISP? (Box main screen -> Network -> WAN, you should see IPv6 address here if allocated)
Also check if IPv6 is turned on for LAN network as well and type is "Prefix Delegation". And if you have multiple LANs, for now it can only be delegated to one LAN.
-
Thanks @Stuart and @Support Team
I was using a combination of Unbound + DOH with DNS Boost on select clients, when I turned off Unbound and enabled DNS Boost on *ALL* clients, somehow, the LAN clients were able to get the full IPv6 configuration (not sure if that fixed it, though). Now IPv6 works on the LAN.
Thanks.
-
@Rom
Thanks for the update. From what you described, it could be coincidence. The DNS and DHCP functions are running independently. Turning on/off Unbound/DoH/DNS Booster should not impact how ipv6 address is allocated to devices.
If you run into this issue again, you may send email to help@firewalla.com, so that we can take a look.
Please sign in to leave a comment.
Comments
4 comments