DHCP
DHCP gives endpoints addresses and default gateway information in labs. netverdict models DHCPv4 server/client/relay behaviour and a smaller DHCPv6 surface for IPv6 scenarios.
Support level
Section titled “Support level”| Area | Level | Notes |
|---|---|---|
| DHCPv4 server | Supported | Pools, exclusions, default-router, DNS options, lease allocation. |
| DHCPv4 client | Supported | Client requests address and installs received configuration. |
| DHCP relay | Supported | Helper-address style relay behaviour. |
| DHCP snooping integration | Behaviour model | ACKs can populate snooping bindings. |
| DHCPv6 | Behaviour model | IPv6 lease/config solver and CLI surface. |
Standards coverage
Section titled “Standards coverage”| Standard | Coverage | Notes |
|---|---|---|
| RFC 2131 | Behaviour model | DHCPv4 DORA lease semantics. |
| RFC 8415 | Partial | DHCPv6 concepts for supported scenarios. |
Feature matrix
Section titled “Feature matrix”| Feature | Status | Notes |
|---|---|---|
| Address pools | Supported | Network, range/exclusions, default router. |
| Option DNS | Supported | DNS server option. |
| Lease table | Supported | Active bindings. |
| Client default route | Supported | Installs route from default-router option. |
| Relay/helper address | Supported | Forwards client requests to server. |
| Snooping binding | Supported | Trusted ACKs create L2 security bindings. |
| DHCPv6 pool | Partial | Supported subset. |
Vendor command matrix
Section titled “Vendor command matrix”| Command | IOS-style | Junos-style | VyOS-style | Notes |
|---|---|---|---|---|
ip dhcp pool USERS | Supported | n/a | Partial | Pool definition. |
network 10.0.10.0 255.255.255.0 | Supported | n/a | Partial | Pool network. |
default-router 10.0.10.1 | Supported | n/a | Partial | Gateway option. |
ip helper-address 10.0.0.10 | Supported | n/a | Partial | Relay. |
ip address dhcp | Supported | n/a | Partial | Client mode. |
show ip dhcp binding | Supported | Partial | Partial | Lease table. |
Behaviour notes
Section titled “Behaviour notes”DHCP exchange is modelled as deterministic events. A client lease is stable for the same topology and pool state, which keeps labs replayable.
Examples
Section titled “Examples”Canonical example
configure terminalip dhcp excluded-address 10.0.10.1 10.0.10.20ip dhcp pool USERS network 10.0.10.0 255.255.255.0 default-router 10.0.10.1 dns-server 192.0.2.53interface GigabitEthernet0/1 ip address dhcpendshow ip dhcp bindingVendor styles
IOS-style
ip dhcp pool USERS network 10.0.10.0 255.255.255.0 default-router 10.0.10.1 dns-server 192.0.2.53interface GigabitEthernet0/1 ip address dhcpJunos-style
set system services dhcp-local-server group USERS interface ge-0/0/1.0set access address-assignment pool USERS family inet network 10.0.10.0/24set access address-assignment pool USERS family inet dhcp-attributes router 10.0.10.1VyOS-style
set service dhcp-server shared-network-name USERS subnet 10.0.10.0/24 option default-router 10.0.10.1set service dhcp-server shared-network-name USERS subnet 10.0.10.0/24 range 0 start 10.0.10.100set service dhcp-server shared-network-name USERS subnet 10.0.10.0/24 range 0 stop 10.0.10.200Known limits
Section titled “Known limits”Option overload, vendor-specific options, failover pairs, DHCP authentication, full DHCPv6 IA state, and lease-renewal races are not modelled in depth.