The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
NoteThis module is relevant only when the DHCPv6 Lease Query LEG is installed on the Cisco Service Control Subscriber Manager server.
The DHCP Forwarder application acts as a bridge between the DHCPv6 Lease Query LEG and the DHCPv6 servers. The DHCPv6 Lease Query LEG sends a request to the DHCP Forwarder, which then forwards the request to the appropriate DHCP server. The DHCP Forwarder passes the replies from the DHCP servers to the LEG. The LEG signals the forwarder on which the server should receive each request. Therefore, no special configuration is needed for this application.
The DHCP Forwader Application is enhanced to handle the DHCPv6 messages.
The DHCP Forwarder runs with root privileges because only those applications that have root privileges can open ports below 1024. DHCPv6 uses ports 546 and 547. No other application must use these ports.
NoteIf the DHCPv6 Lease Query LEG is enabled and is configured to use the DHCP Forwarder application, the IPv6 loopback address should not be [::1] and the host string localhost6 should be configured in the /etc/hosts file with full 128-bit IPv6 address of the Cisco Service Control Subscriber Manager, for example, 2607:f0d0:1002:11::2 localhost6.localdomain6 localhost6).
For installation, start, and stop operations, see the “DHCP Forwarder Application” chapter.