Skip to content

Add support for non-DHCP capable devices - #1618

Open
duncangreene wants to merge 2 commits into
google:mainfrom
duncangreene:feature/add-hardcoded-static-ip-address-fallback-to-startup-procedure
Open

Add support for non-DHCP capable devices#1618
duncangreene wants to merge 2 commits into
google:mainfrom
duncangreene:feature/add-hardcoded-static-ip-address-fallback-to-startup-procedure

Conversation

@duncangreene

Copy link
Copy Markdown

This feature adds support for non-DHCP devices to progress to the Monitoring phase by soliciting an ARP response from a hardcoded, pre-specified to the end user, IP address of 10.10.10.100/24.

image

The DHCP related tests are duly not run if a non-DHCP device is detected.

image

DHCP devices are unaffected and still able to progress to Monitoring as normal if detected.

… IP address of 10.10.10.100/24 and default gateway of 10.10.10.1

Update comments

Clear cached device.ip_addr from previous runs

This hadn't been required with DHCP-capable devices as device.ip_addr would be set in each run during the DHCP DORA process. With non-DHCP devices this process doesn't happen, and so requires clearing each time to avoid cached values.

Add active ARP solicitation to connection_switch_arp_inspection

Statically IP addressed devices may not offer a gratuitous ARP during boot and so this enhancement solicits an ARP response from the DUT if none are present during startup and monitoring captures

Add early return in the DHCP related tests to cater for non-DHCP devices

Remove superfluous ping from static IP check
@duncangreene duncangreene changed the title Feature/add hardcoded static ip address fallback to startup procedure Add support for non-DHCP capable devices Aug 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant