Send-Options

Test suite to validate DHCP client send options and identifier persistence.

The DHCP client can send identification information to the server: - DHCP Client Identifier: Uniquely identifies the client device - Hostname: Sends the system hostname for logging and identification

This test suite focuses on functionality NOT covered by existing tests: - Hostname send (zero coverage) - Identifier persistence (verifies same ID = same IP across releases)

Note: Basic client identifier functionality is already tested in tests/service/dhcp-server/class.robot (class matching scenarios).

Test Client Sends Hostname

Description

This scenario verifies that the DHCP client automatically sends the system hostname to the DHCP server. When a system hostname is configured, the DHCP client includes it in DHCP requests without requiring additional interface-specific configuration. The hostname appears in the server’s journal logs in DHCP messages like DHCPREQUEST/DHCPACK. When viewing DHCP logs, seeing “test-router” is more informative than seeing only MAC addresses. This aids in troubleshooting and network documentation. Verification includes packet capture to confirm hostname in DHCP packets.

Scenario

Step 1: Run the command system journal clear on DUT0 and expect the following output:

Step 2: Set the following configuration in DUT0 :

set interfaces ethernet eth0 address 172.16.0.1/24
set service dhcp-server shared-network dhcp subnet 172.16.0.0/24 start 172.16.0.5 stop 172.16.0.10
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'

Step 3: Set the following configuration in DUT1 :

set interfaces ethernet eth0 address dhcp
set system host-name test-router
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'

Step 4: Run the command interfaces ethernet eth0 show on DUT1 and check whether the output contains the following tokens:

172.16.0

Step 5: Run the command system journal show | cat on DUT0 and expect the following output:

Show output

May 19 17:03:16.277128 osdx systemd-journald[505760]: Runtime Journal (/run/log/journal/d1b141b298644f3ea5560bad25bf4943) is 1.9M, max 13.8M, 11.9M free.
May 19 17:03:16.278614 osdx systemd-journald[505760]: Received client request to rotate journal, rotating.
May 19 17:03:16.278658 osdx systemd-journald[505760]: Vacuuming done, freed 0B of archived journals from /run/log/journal/d1b141b298644f3ea5560bad25bf4943.
May 19 17:03:16.285951 osdx OSDxCLI[630910]: User 'admin' executed a new command: 'system journal clear'.
May 19 17:03:16.477473 osdx OSDxCLI[630910]: User 'admin' executed a new command: 'system coredump delete all'.
May 19 17:03:16.645908 osdx systemd-journald[505760]: Runtime Journal (/run/log/journal/d1b141b298644f3ea5560bad25bf4943) is 1.8M, max 13.8M, 11.9M free.
May 19 17:03:16.646617 osdx systemd-journald[505760]: Received client request to rotate journal, rotating.
May 19 17:03:16.646667 osdx systemd-journald[505760]: Vacuuming done, freed 0B of archived journals from /run/log/journal/d1b141b298644f3ea5560bad25bf4943.
May 19 17:03:16.653969 osdx OSDxCLI[630910]: User 'admin' executed a new command: 'system journal clear'.
May 19 17:03:16.783894 osdx OSDxCLI[630910]: User 'admin' entered the configuration menu.
May 19 17:03:16.862061 osdx OSDxCLI[630910]: User 'admin' added a new cfg line: 'set interfaces ethernet eth0 address 172.16.0.1/24'.
May 19 17:03:16.935558 osdx OSDxCLI[630910]: User 'admin' added a new cfg line: 'set service dhcp-server shared-network dhcp subnet 172.16.0.0/24 start 172.16.0.5 stop 172.16.0.10'.
May 19 17:03:16.992385 osdx OSDxCLI[630910]: User 'admin' added a new cfg line: 'show working'.
May 19 17:03:17.082734 osdx ubnt-cfgd[649078]: inactive
May 19 17:03:17.108147 osdx INFO[649090]: FRR daemons did not change
May 19 17:03:17.138615 osdx kernel: 8021q: adding VLAN 0 to HW filter on device eth0
May 19 17:03:17.185967 osdx WARNING[649163]: No supported link modes on interface eth0
May 19 17:03:17.187245 osdx modulelauncher[649163]: osdx.utils.xos cmd error: /sbin/ethtool -A eth0 autoneg on
May 19 17:03:17.187255 osdx modulelauncher[649163]: Command '/sbin/ethtool -A eth0 autoneg on' returned non-zero exit status 76.
May 19 17:03:17.188332 osdx modulelauncher[649163]: osdx.utils.xos cmd error: /sbin/ethtool -s eth0 autoneg on advertise Asym_Pause off Pause off --
May 19 17:03:17.188338 osdx modulelauncher[649163]: Command '/sbin/ethtool -s eth0 autoneg on advertise Asym_Pause off Pause off --' returned non-zero exit status 75.
May 19 17:03:17.278969 osdx systemd[1]: Started dhcpd@main.service - "DHCP Server Service instance main".
May 19 17:03:17.281983 osdx dhcpd[649184]: Wrote 0 leases to leases file.
May 19 17:03:17.322770 osdx dhcpd[649184]: Server starting service.
May 19 17:03:17.484756 osdx cfgd[1918]: [630910]Completed change to active configuration
May 19 17:03:17.532209 osdx OSDxCLI[630910]: User 'admin' committed the configuration.
May 19 17:03:17.552003 osdx OSDxCLI[630910]: User 'admin' left the configuration menu.
May 19 17:03:18.319489 osdx dhcpd[649184]: DHCPDISCOVER from de:ad:be:ef:6c:10 via eth0
May 19 17:03:19.319914 osdx dhcpd[649184]: DHCPOFFER on 172.16.0.5 to de:ad:be:ef:6c:10 (test-router) via eth0
May 19 17:03:19.320962 osdx dhcpd[649184]: DHCPREQUEST for 172.16.0.5 (172.16.0.1) from de:ad:be:ef:6c:10 (test-router) via eth0
May 19 17:03:19.341568 osdx dhcpd[649184]: DHCPACK on 172.16.0.5 to de:ad:be:ef:6c:10 (test-router) via eth0

Step 6: Run the command traffic dump monitor detail interface eth0 filter "port 67 or port 68" packets 10 on DUT0.

Step 7: Run the command service dhcp-client renew interface eth0 on DUT1 and expect the following output:

Test Serial Number Identifier Persistence

Description

This scenario verifies that using a serial number as the client identifier ensures IP address persistence across DHCP renewals and releases. When a client uses its serial number as identifier, the DHCP server associates the lease with this unique hardware ID rather than the MAC address. Even if the client releases and re-requests its IP, it should receive the same IP address as long as it uses the same serial number identifier. This is critical for maintaining consistent IP addressing in environments where devices may have changing MAC addresses or multiple network interfaces.

Scenario

Step 1: Set the following configuration in DUT0 :

set interfaces ethernet eth0 address 172.16.0.1/24
set service dhcp-server shared-network dhcp subnet 172.16.0.0/24 start 172.16.0.5 stop 172.16.0.10
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'

Step 2: Set the following configuration in DUT1 :

set interfaces ethernet eth0 address dhcp
set interfaces ethernet eth0 dhcp client send dhcp-client-identifier serial-number
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'

Step 3: Run the command interfaces ethernet eth0 show on DUT1 and check whether the output contains the following tokens:

172.16.0

Step 4: Run the command interfaces ethernet eth0 show on DUT1 and expect the following output:

Step 5: Modify the following configuration lines in DUT1 :

delete interfaces ethernet eth0 address

Step 6: Run the command interfaces ethernet eth0 show on DUT1 and expect the following output:

Step 7: Modify the following configuration lines in DUT1 :

set interfaces ethernet eth0 address dhcp

Step 8: Modify the following configuration lines in DUT1 : Step 9: Run the command interfaces ethernet eth0 show on DUT1 and expect the following output:

Step 10: Run the command interfaces ethernet eth0 show on DUT1 and check whether the output contains the following tokens:

172.16.0.5

Test Base-MAC Identifier Persistence

Description

This scenario verifies that using the base MAC address as the client identifier ensures IP address persistence. The base MAC is the primary hardware address of the device, independent of any VLAN or virtual interface configurations. When a client uses base-mac as its identifier, it maintains the same lease even when reconnecting through different sub-interfaces or after configuration changes. This is particularly useful in VLAN environments where each sub-interface has a different MAC but all share the same base MAC.

Scenario

Step 1: Set the following configuration in DUT0 :

set interfaces ethernet eth0 address 172.16.0.1/24
set service dhcp-server shared-network dhcp subnet 172.16.0.0/24 start 172.16.0.5 stop 172.16.0.10
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'

Step 2: Set the following configuration in DUT1 :

set interfaces ethernet eth0 address dhcp
set interfaces ethernet eth0 dhcp client send dhcp-client-identifier base-mac
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'

Step 3: Run the command interfaces ethernet eth0 show on DUT1 and check whether the output contains the following tokens:

172.16.0

Step 4: Run the command interfaces ethernet eth0 show on DUT1 and expect the following output:

Step 5: Modify the following configuration lines in DUT1 :

delete interfaces ethernet eth0 address

Step 6: Run the command interfaces ethernet eth0 show on DUT1 and expect the following output:

Step 7: Modify the following configuration lines in DUT1 :

set interfaces ethernet eth0 address dhcp

Step 8: Modify the following configuration lines in DUT1 : Step 9: Run the command interfaces ethernet eth0 show on DUT1 and expect the following output:

Step 10: Run the command interfaces ethernet eth0 show on DUT1 and check whether the output contains the following tokens:

172.16.0.5

Test String Identifier Persistence

Description

This scenario verifies that using a custom string as the client identifier ensures IP address persistence across DHCP operations. Custom string identifiers allow administrators to assign logical, human-readable names to devices (e.g., “router-branch-office-01”) independent of any hardware identifiers. This provides flexible device identification that survives hardware replacements - if a device is replaced but configured with the same string identifier, it will receive the same IP address. This test verifies that the server correctly tracks leases by the custom string identifier and maintains address consistency.

Scenario

Step 1: Set the following configuration in DUT0 :

set interfaces ethernet eth0 address 172.16.0.1/24
set service dhcp-server shared-network dhcp subnet 172.16.0.0/24 start 172.16.0.5 stop 172.16.0.10
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'

Step 2: Set the following configuration in DUT1 :

set interfaces ethernet eth0 address dhcp
set interfaces ethernet eth0 dhcp client send dhcp-client-identifier string my-persistent-device
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'

Step 3: Run the command interfaces ethernet eth0 show on DUT1 and check whether the output contains the following tokens:

172.16.0

Step 4: Run the command interfaces ethernet eth0 show on DUT1 and expect the following output:

Step 5: Modify the following configuration lines in DUT1 :

delete interfaces ethernet eth0 address

Step 6: Run the command interfaces ethernet eth0 show on DUT1 and expect the following output:

Step 7: Modify the following configuration lines in DUT1 :

set interfaces ethernet eth0 address dhcp

Step 8: Modify the following configuration lines in DUT1 : Step 9: Run the command interfaces ethernet eth0 show on DUT1 and expect the following output:

Step 10: Run the command interfaces ethernet eth0 show on DUT1 and check whether the output contains the following tokens:

172.16.0.5