Force DHCPv6 instead of SLAAC



  • Hi, I have successfully implemented IPv6 on my pfSense through a HE tunnel. All the devices in my network are getting IPv6 addresses and can browse internet withouth problem.

    Currently almos all my devices are getting there IPv6 addresses through SLAAC, but I want to know how can I force my clients to get an IPv6 address from DHCPv6 and not SLAAC.

    I have configured DHCPv6 with a range of IPv6 adresses and I have configured RA as Assisted so that the Android devices can get an IPv6 with SLAAC as they don't support DHCPv6, but I want the other computers on the network to get an IPv6 from DHCP.

    But when I check the devices IPv6 addresses they are not in the range I have defined the DHCPv6 to lease and obvioulsy they are not in the DHCPv6 leases status page of pfSense.

    So, how can I force my clients that support it, to get and IPv6 address from DHCPv6 and not SLAAC?

    Thanks,
    Pablo


  • Banned

    There is no DHCPv6 implemented in Android. If you want DHCPv6 only, set RA to Managed. You won't have any IPv6 on Android at that point.



  • @doktornotor:

    There is no DHCPv6 implemented in Android. If you want DHCPv6 only, set RA to Managed. You won't have any IPv6 on Android at that point.

    Yes, I know there si no DHCP6 implementation in Android, thats why I configured RA in Assisted, mode so the devices that do support DHCP6 get them by DHCP6 and Androide devices get their IP by SLAAC, but it seems that almost every deveice is getting its IP by SLAAC



  • LAN_ONE == managed, DHCP6.
    LAN_TWO == unmanaged, SLAAC.



  • You can't control it centrally from pfSense. Each operating system does their own thing in selecting their preferred method for IPv6. The only thing you can do is set the unmanaged/managed/assisted setting and that just selects which methods are available for clients.



  • No DHCPv6 in XP either. That starts in Vista.

    Linux clients using NetworkManager can be set to Automatic (DHCP-only).



  • @severach:

    No DHCPv6 in XP either. That starts in Vista.

    Linux clients using NetworkManager can be set to Automatic (DHCP-only).

    I just went through this exercise myself and ended up enabling NetworkManager, but I'd rather not use it if possible.  My systems virtually never change which network they're on so NetworkManager always seemed to be overkill and I would disable in favor of the network service.

    Do you know how to get the basic network service set up to do DHCPv6 from pfSense?  I tried and it never seemed to work quite right.



  • Try this https://forum.pfsense.org/index.php?topic=101143.0

    It's exactly what I needed. Hope it helps.



  • DHCPv6 in pfSense seems a little flakey but I suspect what is happening is that DHCPv6 won't enable until it sees ipv6 on the WAN and Track Interface all fall into place. I use pfSense for DHCPv6 on my smaller networks. On my larger networks I've graduated to using dnsmasq directly. Once you get used to what all a fully configurable dnsmasq can do, the DHCP servers inside any router brand look like cheap toys. Even routers that use dnsmasq are no good. They don't expose but a tiny fraction of what dnsmasq can really do.


Log in to reply