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

AddressAllocator DHCP works in conjunction with <AuthBy DYNADDRESS> (see Section 3.52. <AuthBy DYNADDRESS>) and a DHCP server to dynamically allocate IP addresses.
AddressAllocator DHCP has been tested with a number of DHCP servers, however it works best with the latest versions of the DHCP server from the Internet Software Consortium (ISC) that support the Subnet Selection Option. For more information, see ISC website Opens in new window.
The RFC 3011 Subnet Selection Option allows server-to-server operation such as that supported by Radiator.
The PoolHint supplied in the AuthBy DYNADDRESS clause must be a subnet definition that is understood by the DHCP server for the purposes of address allocation.
AddressAllocator DHCP makes the following allocation variables available for replies. These names can be used in MapAttribute in AuthBy DYNADDRESS.
An example AddressAllocator DHCP configuration file can be found in the distribution in the file goodies/addressallocatordhcp.cfg.
Because AddressAllocator DHCP binds to the DHCP server address, it is not possible to run the DHCP server on the same host as Radiator.
Because the DHCP address allocator binds to port 67, Radiator must be run as root, or at least with root privileges.