.. _example_service_dhcp-server_lease-timers:
############
Lease-Timers
############
These scenarios check DHCP lease timer functionality.
DHCP leases have time-based behavior as defined in RFC 2131:
- T1 (Renewal Time): Client attempts to renew at 50% of lease time
- T2 (Rebinding Time): Client attempts to rebind at 87.5% of lease time
- Lease Expiration: After lease expires, client must release the IP
This test suite verifies temporal behavior of DHCP leases.
************************
Test Lease Renewal at T1
************************
Description
===========
This scenario checks that the DHCP client automatically renews its lease
at T1 (50% of lease time). With a 60-second lease, the client should
attempt renewal around 30 seconds. We verify the client still has the IP
after T1 time passes, confirming automatic renewal occurred.
Scenario
========
.. include:: lease-timers/testleaserenewalatt1
.. raw:: html
*********************************
Test Server Disable and Re-enable
*********************************
Description
===========
This scenario checks DHCP server disable/enable functionality.
When the server is disabled, clients cannot obtain or renew leases.
When re-enabled, clients can successfully obtain leases again.
This tests the server's ability to handle service interruption and recovery.
According to RFC 2131, clients continue attempting to renew expired leases,
so when the server comes back online, the client will successfully obtain
a new lease, resulting in active lease statistics.
Scenario
========
.. include:: lease-timers/testserverdisableandre-enable
.. raw:: html
**************************
Test Very Short Lease Time
**************************
Description
===========
This scenario checks DHCP behavior with very short lease times (10 seconds).
This is an edge case that tests rapid renewal cycles.
The client should successfully maintain connectivity despite
frequent renewal requirements.
Scenario
========
.. include:: lease-timers/testveryshortleasetime
.. raw:: html