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 command system journal clear at DUT0 and expect this 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 command interfaces ethernet eth0 show at DUT1 and check if output contains the following tokens:

172.16.0

Step 5: Run command system journal show | cat at DUT0 and expect this output:

Show output

Mar 05 21:12:59.000227 osdx systemd-timedated[847455]: Changed local time to Thu 2026-03-05 21:12:59 UTC
Mar 05 21:12:59.000774 osdx systemd-journald[466780]: Time jumped backwards, rotating.
Mar 05 21:12:59.002146 osdx OSDxCLI[820874]: User 'admin' executed a new command: 'set date 2026-03-05 21:12:59'.
Mar 05 21:12:59.337871 osdx systemd-journald[466780]: Runtime Journal (/run/log/journal/78445f9299f9414990e66dc8aa510838) is 1.9M, max 13.8M, 11.9M free.
Mar 05 21:12:59.340761 osdx systemd-journald[466780]: Received client request to rotate journal, rotating.
Mar 05 21:12:59.340818 osdx systemd-journald[466780]: Vacuuming done, freed 0B of archived journals from /run/log/journal/78445f9299f9414990e66dc8aa510838.
Mar 05 21:12:59.349297 osdx OSDxCLI[820874]: User 'admin' executed a new command: 'system journal clear'.
Mar 05 21:12:59.612088 osdx OSDxCLI[820874]: User 'admin' executed a new command: 'system coredump delete all'.
Mar 05 21:12:59.801714 osdx systemd-journald[466780]: Runtime Journal (/run/log/journal/78445f9299f9414990e66dc8aa510838) is 1.9M, max 13.8M, 11.8M free.
Mar 05 21:12:59.804755 osdx systemd-journald[466780]: Received client request to rotate journal, rotating.
Mar 05 21:12:59.804849 osdx systemd-journald[466780]: Vacuuming done, freed 0B of archived journals from /run/log/journal/78445f9299f9414990e66dc8aa510838.
Mar 05 21:12:59.810616 osdx OSDxCLI[820874]: User 'admin' executed a new command: 'system journal clear'.
Mar 05 21:12:59.933329 osdx OSDxCLI[820874]: User 'admin' entered the configuration menu.
Mar 05 21:13:00.032937 osdx OSDxCLI[820874]: User 'admin' added a new cfg line: 'set interfaces ethernet eth0 address 172.16.0.1/24'.
Mar 05 21:13:00.148626 osdx OSDxCLI[820874]: 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'.
Mar 05 21:13:00.215130 osdx OSDxCLI[820874]: User 'admin' added a new cfg line: 'show working'.
Mar 05 21:13:00.305624 osdx ubnt-cfgd[847495]: inactive
Mar 05 21:13:00.332343 osdx INFO[847506]: FRR daemons did not change
Mar 05 21:13:00.364791 osdx kernel: 8021q: adding VLAN 0 to HW filter on device eth0
Mar 05 21:13:00.415496 osdx WARNING[847577]: No supported link modes on interface eth0
Mar 05 21:13:00.417151 osdx modulelauncher[847577]: osdx.utils.xos cmd error: /sbin/ethtool -A eth0 autoneg on
Mar 05 21:13:00.417162 osdx modulelauncher[847577]: Command '/sbin/ethtool -A eth0 autoneg on' returned non-zero exit status 76.
Mar 05 21:13:00.418316 osdx modulelauncher[847577]: osdx.utils.xos cmd error: /sbin/ethtool -s eth0 autoneg on advertise Pause off Asym_Pause off --
Mar 05 21:13:00.418323 osdx modulelauncher[847577]: Command '/sbin/ethtool -s eth0 autoneg on advertise Pause off Asym_Pause off --' returned non-zero exit status 75.
Mar 05 21:13:00.501033 osdx systemd[1]: Started dhcpd@main.service - "DHCP Server Service instance main".
Mar 05 21:13:00.502449 osdx cfgd[1863]: [820874]Completed change to active configuration
Mar 05 21:13:00.503583 osdx dhcpd[847603]: Wrote 0 leases to leases file.
Mar 05 21:13:00.513828 osdx OSDxCLI[820874]: User 'admin' committed the configuration.
Mar 05 21:13:00.528869 osdx OSDxCLI[820874]: User 'admin' left the configuration menu.
Mar 05 21:13:00.569160 osdx dhcpd[847603]: Server starting service.
Mar 05 21:13:01.438822 osdx dhcpd[847603]: DHCPDISCOVER from de:ad:be:ef:6c:10 via eth0
Mar 05 21:13:02.439568 osdx dhcpd[847603]: DHCPOFFER on 172.16.0.5 to de:ad:be:ef:6c:10 (test-router) via eth0
Mar 05 21:13:02.439893 osdx dhcpd[847603]: DHCPREQUEST for 172.16.0.5 (172.16.0.1) from de:ad:be:ef:6c:10 (test-router) via eth0
Mar 05 21:13:02.460138 osdx dhcpd[847603]: DHCPACK on 172.16.0.5 to de:ad:be:ef:6c:10 (test-router) via eth0

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

Step 7: Run command service dhcp-client renew interface eth0 at DUT1 and expect this 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 command interfaces ethernet eth0 show at DUT1 and check if output contains the following tokens:

172.16.0

Step 4: Run command interfaces ethernet eth0 show at DUT1 and expect this output:

Step 5: Modify the following configuration lines in DUT1 :

delete interfaces ethernet eth0 address

Step 6: Run command interfaces ethernet eth0 show at DUT1 and expect this 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 command interfaces ethernet eth0 show at DUT1 and expect this output:

Step 10: Run command interfaces ethernet eth0 show at DUT1 and check if 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 command interfaces ethernet eth0 show at DUT1 and check if output contains the following tokens:

172.16.0

Step 4: Run command interfaces ethernet eth0 show at DUT1 and expect this output:

Step 5: Modify the following configuration lines in DUT1 :

delete interfaces ethernet eth0 address

Step 6: Run command interfaces ethernet eth0 show at DUT1 and expect this 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 command interfaces ethernet eth0 show at DUT1 and expect this output:

Step 10: Run command interfaces ethernet eth0 show at DUT1 and check if 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 command interfaces ethernet eth0 show at DUT1 and check if output contains the following tokens:

172.16.0

Step 4: Run command interfaces ethernet eth0 show at DUT1 and expect this output:

Step 5: Modify the following configuration lines in DUT1 :

delete interfaces ethernet eth0 address

Step 6: Run command interfaces ethernet eth0 show at DUT1 and expect this 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 command interfaces ethernet eth0 show at DUT1 and expect this output:

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

172.16.0.5