3.111. <AddressAllocator DHCPv6> Previous topic Parent topic Child topic Next topic

AddressAllocator DHCPv6 works in conjunction with <AuthBy DYNADDRESS> (see Section 3.52. <AuthBy DYNADDRESS>) and a DHCPv6 server to dynamically allocate IPv6 addresses, IPv6 delegated prefixes and to request other configuration information from the DHCPv6 server.
AddressAllocator DHCPv6 has been tested with a number of DHCPv6 servers, however it has been mostly tested the DHCP server from the Internet Software Consortium (ISC). For more information, see ISC website Opens in new window. Version 4.3.3 or later is recommended.
AddressAllocator DHCPv6 makes the following allocation variables available for replies. The allocation variables names are case insensitive DHCPv6 option names without the leading ‘OPTION_’. These names can be by default used in MapAttribute in AuthBy DYNADDRESS.
An example AddressAllocator DHCPv6 configuration file can be found in the distribution in the file goodies/addressallocatordhcpv6.cfg.
An example ISC DHCP server configuration file can be found in the distribution in the file goodies/addressallocatordhcpv6-dhcpd.conf.
Because AddressAllocator DHCPv6 binds to the DHCPv6 server address, it is not possible to run the DHCPv6 server on the same host as Radiator.
PoolHint supplied in the AuthBy DYNADDRESS clause for the purposes of allocation is sent to the DHCPv6 server with OPTION_USER_CLASS. Some DHCPv6 servers may not be able to use this option. For this reason PoolHint is also sent with OPTION_CLIENTID. For more information, see Section 3.111.8. DHCPClientIdentifier.
Because the DHCPv6 address allocator binds to DHCPv6 client port 546, Radiator must be run as root, or at least with suitable privileges.