LAN Clients Won't Receive IPv6 Addresses/RA Not Working?
-
Hey Folks,
I think this is my first post after spending literally a year trying to get my clients on the LAN to receive an IPv6 address.
Let me give you the setup.
pfSense 2.4.1
ISP: Comcast Business
WAN IPv4: Static
WAN IPv6: DHCPv6
LAN IPv4: Static
LAN IPv6: Track Interface
DHCPv6: Disabled
RA: Assisted, Priority: HighI am able to receive an IP on both the WAN and LAN interfaces on pfSense and have no issues routing out from there but left with an issue of being clients not grabbing an IPv6 address. I know I probably have not given enough information here but I am happy to provide more when asked and looking for a starting point to troubleshoot further. Thank you!
-
I see the exact same problem on 2.4.1.
Used to work perfectly prior to upgrading to 2.4.x.
-
DHCPv6: Disabled
RA: Assisted, Priority: HighIf you don't want to run DHCPv6 on your LAN you should set Router Mode to "Unmanaged".
-
I'm actually running DHCPv6 and Assisted RA, but no IP on the clients after the upgrade.
-
DHCPv6: Disabled
RA: Assisted, Priority: HighIf you don't want to run DHCPv6 on your LAN you should set Router Mode to "Unmanaged".
Assisted still allows for SLAAC since it leaves the Prefix Autonomous Flag to 1, AND the Managed Flag to 1, this just tells the client they can do DHCPv6 as well, not that they must, and not that can can't to SLAAC with the prefix marked with A 1.
I means I believe you should set it right/appropriate but, its not stopping SLAAC.
-
I'm actually running DHCPv6 and Assisted RA, but no IP on the clients after the upgrade.
Run wireshark, look for the RAs, you can filter with "ICMP6"
-
I did some more debugging with wireshark today, and found out that it was actually my wireless solution that filtered the RA and made the problems.
-
My clients stopped getting IPV6 when I replaced the router. I restored the previous config so everything should be the same but the clients do not get an address. They did prior. WAN and LAN have IPV6 and I can ping IPV6 addresses from within pfSense but obviously not from a client.