Router mode 'Managed' not working?
-
Hi,
we recently started rolling out IPv6, but it seems we're hitting what seems like a bug in PFSense.
We have Windows doing DHCPv6, and the pfsense as a router, and as far as I understand, in this setup, the router mode needs to be set to managed.
When configuring it like that, clients do not receive any IPs. Dhcpcd complains: "Ignoring RA (no public prefix, no managed address)", which is suggesting DHCPv6 is not working. But now, interestingly, when setting the mode to 'Assisted', we see clients getting both automatically configured addresses and leases from our DHCPv6 server.
On another interface, where we are using the same setup, except the pfsense is doing DHCPv6 as well, managed works as expected.
So my conclusion would be that the managed mode is somehow broken (bit not set?) if PFSense isn't also doing DHCPv6. Can anyone confirm this? And does anyone know of a fix?
Kind regards,
Bartosz -
I just diffed /var/etc/radvd.conf between the two settings, but the only difference is the value of 'AdvAutonomous' as ecpected, 'AdvManagedFlag' is 'on' in both cases. So i guess it's not the configuration itself then. Does anyone else see this behaviour, or have any clue as to what the issue could be?
We're on 2.3.2-RELEASE-p1
-
What version of Windows? Windows 10 has a known issue with its DHCPv6 client.
-
Works just fine here (unless the client is broken, in which case it just doesn't work at all and has nothing to do with pfSense. And yeah, W10 Anniversary Kaboom Edition is one of those.)
-
Hi,
indeed it turned out to be client I was testing it, which was using dhcpcd. It works on other machines here, including Windows 10, GNU/Linux (both with Connman, NetworkManager). Since I was getting DHCPv6 in assisted mode I never suspected the client. Sorry for bothering everyone, but this turns out not to be an issue with pfsense after all.
Kind regards,
Bartosz
