This knowledge base has moved to the documentation site. Please visit the knowledge base here for the most up to date content. This site is no longer maintained.

Configuring DHCP Relays

Follow

Issue

How do I configure an interface so it can make DHCP relay requests for IPv4 and IPv6?

Environment

  • Cumulus Linux 1.5.z - 2.5.z

Note: For Cumulus Linux and Cumulus RMP 3.0 and later, please read the Cumulus Linux user guide. 

Resolution

  1. Edit /etc/default/isc-dhcp-relay.
  2. Set SERVERS equal to the address of the DHCP server(s), in quotes and separated by spaces. For example:

    SERVERS="192.168.123.4"
    
  3. On the INTERFACES line, add both the client-facing and server-facing interfaces for the relay within the quotes, separated by spaces. For example, the client facing port is br0 and the server facing port is swp4.

    INTERFACES="br0 swp4"

    If you have multiple paths to the DHCP server or asymmetric routing, include all the incoming ports from which the DHCP response from the server may be received. Also, include the incoming port that receives the initial DHCP request from the host. For example, the host default gateway is br0, and swp4 and swp5 are equal cost paths to the DHCP server. Thus, a DHCP response may be received on swp4 or swp5.

    INTERFACES="br0 swp4 swp5"

    If using VLAN-aware bridges, apply addresses to switch virtual interfaces for VLANs that need relaying and specify the SVI bridge.tag interfaces in INTERFACES.

  4. Restart the DHCP relay service using init.d. The isc-dhcp-relay service points to /etc/default/isc-dhcp-relay as the default configuration file.
  5. cumulus@switch:~$ sudo /etc/init.d/isc-dhcp-relay restart

 

Comments

This support portal has moved

Cumulus Networks is now part of the NVIDIA Networking Business Unit! The NVIDIA Cumulus Global Support Services (GSS) team has merged its operations with the NVIDIA Mellanox support services team.

You can access NVIDIA Cumulus support content from the Mellanox support portal.

You open and update new cases on the Mellanox support portal. Any previous cases that have been closed have been migrated to the Mellanox support portal.

Cases that are still open on the Cumulus portal will continue to be managed on the Cumulus portal. Once these cases close, they will be moved to the Mellanox support portal.

Powered by Zendesk