When a DHCP client receives an IPv4 address, that address is normally not assigned permanently.
Instead, the DHCP server provides the address for a limited period called a:
DHCP Lease
Before that lease expires, the client attempts to extend it.
This process is called:
DHCP Lease Renewal
Two important timers control the process:
- T1 — Renewal Timer
- T2 — Rebinding Timer
These timers move the DHCP client through several states:
BOUND → RENEWING → REBINDING → EXPIRED
Understanding these states is extremely useful when troubleshooting situations where:
- A client initially receives an address but later loses connectivity
- DHCP renewal repeatedly fails
- The original DHCP server becomes unavailable
- A client broadcasts DHCPREQUEST messages unexpectedly
- A lease eventually expires
RFC 2131 defines T1 as the point where the client enters the RENEWING state and tries to contact the server that originally granted the lease. T2 marks the transition to REBINDING, where the client attempts to contact any available DHCP server. T1 must occur before T2, and T2 before lease expiration.

Understanding a DHCP Lease
Assume a DHCP server assigns the following configuration:
IPv4 Address:
192.168.10.50
Subnet Mask:
255.255.255.0
Default Gateway:
192.168.10.1
DNS Server:
192.168.10.10
Lease Duration:
8 Hours
The client does not normally own:
192.168.10.50
forever.
It can use the address while the lease remains valid.
Why DHCP Uses Leases
Leases allow addresses to be reused when devices:
- Disconnect
- Leave the network
- Move to another subnet
- Are replaced
- Remain offline for long periods
Without lease expiration, abandoned addresses could remain unavailable indefinitely.
Lease Time — Option 51
DHCP can communicate the lease duration using:
Option 51 — IP Address Lease Time
For example:
Option 51:
28800 Seconds
Equivalent:
8 Hours
RFC 2132 defines Option 51 as the IP Address Lease Time and specifies the value in seconds.
T1 and T2 Options
Two additional options can explicitly communicate the renewal timers.
| DHCP Option | Purpose |
|---|---|
| 58 | Renewal Time — T1 |
| 59 | Rebinding Time — T2 |
Option 58 defines the interval from address assignment until the client enters RENEWING.
Option 59 defines the interval until the client enters REBINDING.
T1 — Entering the RENEWING State
T1 is the first major renewal point.
When appropriate explicit timer values are not supplied, the commonly used RFC default for T1 is:
50% of the lease duration
For an eight-hour lease:
Lease Duration:
8 Hours
T1:
Approximately 4 Hours
At T1, the client moves from:
BOUND
to:
RENEWING
What Does the Client Do at T1?
The client still has a valid address.
For example:
Client Address:
192.168.10.50
It now tries to renew the lease with the DHCP server that originally granted it.
A simplified packet flow is:
Client
|
| DHCPREQUEST
v
Original DHCP Server
Original DHCP Server
|
| DHCPACK
v
Client
Is the T1 Request Broadcast?
Normally, no.
During RENEWING, the client knows the original DHCP server.
RFC 2131 specifies that at T1 the client sends a unicast DHCPREQUEST toward the server that originally granted the lease.
This is different from the initial DHCP DORA process, where broadcasts are commonly required.
Packet Behavior During RENEWING
A simplified renewal packet might look like:
State:
RENEWING
Message:
DHCPREQUEST
Client IP:
192.168.10.50
ciaddr:
192.168.10.50
Destination:
Original DHCP Server
Transmission:
Normally Unicast
One important difference from the initial DHCPREQUEST is the use of:
ciaddr
During renewal, the client already has a valid configured address.
RFC 2131 specifies that the client sets ciaddr to its current network address when renewing.
No Server Identifier During RENEWING
Another packet-analysis detail is important.
During the normal RENEWING state, RFC 2131 says the client must not include the DHCP Server Identifier option in the renewal DHCPREQUEST.
This helps distinguish a renewal request from the initial SELECTING-state DHCPREQUEST.

Successful Renewal with DHCPACK
If the original DHCP server receives the renewal request and allows the client to continue using the address, it responds with:
DHCPACK
For example:
DHCPREQUEST
192.168.10.50 → 192.168.10.5
DHCPACK
192.168.10.5 → 192.168.10.50
The client returns to:
BOUND
and continues using its configuration.
Conceptually:
Old Lease Remaining:
4 Hours
Renewal Successful:
Yes
New Lease:
8 Hours
State:
BOUND
The lease timers are then calculated again using the renewed lease information.
RFC 2131 states that after a valid DHCPACK, the client successfully reacquires its network address and returns to the BOUND state.
Important Point
A successful lease renewal does not normally require:
- DHCPDISCOVER
- DHCPOFFER
The renewal may simply be:
DHCPREQUEST
DHCPACK
What Happens If T1 Renewal Fails?
Suppose the client reaches T1 and sends:
DHCPREQUEST
but receives no response.
Possible causes include:
- Original DHCP server unavailable
- Routing problem
- DHCP server service stopped
- Packet loss
- Firewall or ACL issue
- Relay-related problem in some network designs
- Server failover issue
The important point is:
The client does not immediately lose its address.
Its existing lease is still valid.
It can continue using:
192.168.10.50
while attempting renewal.
Renewal Retransmissions
If no reply arrives, the client can retry its DHCPREQUEST while the lease remains valid.
RFC 2131 recommends retry timing based on a portion of the remaining time until the next lease-state transition, with a minimum retransmission interval.
The exact packet timings seen in a real capture may therefore vary between clients.
T2 — Entering the REBINDING State
If the client still cannot successfully renew with the original server, it eventually reaches:
T2
When explicit values are not otherwise supplied, the commonly used default is approximately:
87.5% of the lease duration
For an eight-hour lease:
Lease Duration:
8 Hours
T1:
Approximately 4 Hours
T2:
Approximately 7 Hours
At T2, the client moves from:
RENEWING
to:
REBINDING
What Changes at T2?
At T1, the client tries:
The original DHCP server
At T2, the client is effectively saying:
“My original server has not renewed my lease. Can any DHCP server help me?”
This changes the packet behavior.
The DHCPREQUEST is normally sent more broadly so that any appropriate DHCP server can respond.
RFC 2131 defines T2 as the point where the client enters REBINDING and attempts to contact any DHCP server.
Packet Behavior During REBINDING
A simplified exchange is:
Client
|
| Broadcast DHCPREQUEST
v
Available DHCP Servers
The client still has its existing address:
ciaddr:
192.168.10.50
but it is no longer depending exclusively on the original DHCP server.

Rebinding with Another DHCP Server
Suppose the original server:
192.168.10.5
is unavailable.
Another DHCP server:
192.168.10.6
may be able to process the rebinding request if the DHCP environment is designed to support it.
The sequence may appear as:
Client → Broadcast:
DHCPREQUEST
Server B → Client:
DHCPACK
The client can then continue using the lease according to the configuration returned by the responding DHCP server.
DHCPNAK During Renewal or Rebinding
Not every DHCPREQUEST receives DHCPACK.
A DHCP server may determine that the client’s existing configuration is no longer valid.
It can respond with:
DHCPNAK
Possible situations include:
- Client moved to another subnet
- Address is no longer valid for the current network
- Lease information is no longer acceptable
- Server policy rejects the configuration
A simplified exchange:
Client:
DHCPREQUEST
Server:
DHCPNAK
The client should no longer continue assuming that the requested address remains valid.
This can force the client back toward DHCP initialization and address acquisition.
Lease Expiration
The final boundary is:
Lease Expiration
RFC 2131 requires:
T1 < T2 < Lease Expiration.
For the eight-hour example:
Lease Start:
00:00
T1:
04:00
T2:
07:00
Expiration:
08:00
If the client reaches the expiration point without receiving a valid DHCPACK, the situation changes completely.
The leased address is no longer valid for continued use.
RFC 2131 states that if the lease expires before the client receives DHCPACK, the client moves to INIT and must stop using the expired network configuration.
What Happens Next?
The client normally returns to the address-acquisition process.
Conceptually:
Lease Expires
↓
Stop Using Leased Address
↓
INIT
↓
DHCPDISCOVER
↓
DHCPOFFER
↓
DHCPREQUEST
↓
DHCPACK

Complete Eight-Hour Lease Example
Consider:
Client:
192.168.10.50
DHCP Server:
192.168.10.5
Lease:
8 Hours
00:00 — Lease Begins
The client receives:
DHCPACK
It enters:
BOUND
Lease Remaining:
8 Hours
The client communicates normally.
04:00 — T1
Approximately 50% of the lease has passed.
The client enters:
RENEWING
It sends:
192.168.10.50 → 192.168.10.5
DHCPREQUEST
Normally this is unicast toward the original DHCP server.
Scenario A — Server Responds
192.168.10.5 → 192.168.10.50
DHCPACK
The client returns to:
BOUND
The lease is refreshed.
Scenario B — No Response
If the server does not respond, the client continues using its still-valid address and retries according to DHCP behavior.
Eventually it reaches T2.
07:00 — T2
The client enters:
REBINDING
It now sends a DHCPREQUEST more broadly:
DHCPREQUEST
Client → Broadcast
Any appropriate DHCP server may potentially respond.
Scenario C — Another Server Responds
Server B → Client
DHCPACK
The lease is renewed.
The client returns to:
BOUND
Scenario D — No Server Responds
The client continues using the address until:
08:00
when the lease expires.
08:00 — Expiration
Without a valid DHCPACK:
- Lease is no longer valid
- Client must stop using the expired configuration
- Client returns to INIT
- DHCP acquisition starts again

Packet-by-Packet Renewal Analysis
Now consider an actual packet-analysis workflow.
Initial Lease
Client:
192.168.10.50
Original DHCP Server:
192.168.10.5
Lease Time:
28800 Seconds
T1:
14400 Seconds
T2:
25200 Seconds
Packet 1 — T1 DHCPREQUEST
Message:
DHCPREQUEST
State:
RENEWING
Source:
192.168.10.50
Destination:
192.168.10.5
ciaddr:
192.168.10.50
Transport:
Unicast
Interpretation:
The client still has a valid lease and is attempting to renew it with the original DHCP server.
Packet 2 — DHCPACK
Message:
DHCPACK
Server:
192.168.10.5
Client:
192.168.10.50
Result:
Lease Renewed
Interpretation:
Renewal succeeded.
There should normally be no DHCPDISCOVER or DHCPOFFER in this successful T1 exchange.
Failed T1 Example
A capture may show:
DHCPREQUEST
DHCPREQUEST
DHCPREQUEST
with no DHCPACK.
Interpretation:
The original server is not successfully renewing the lease.
Check:
- DHCP server availability
- Routing
- Firewall
- ACLs
- Packet loss
- DHCP server logs
T2 Packet
Later, the capture may show:
Message:
DHCPREQUEST
State:
REBINDING
ciaddr:
192.168.10.50
Destination:
Broadcast
Purpose:
Reach any available DHCP server
This is a major clue that the client has passed T1 without a successful renewal.
Wireshark and tcpdump Analysis
Wireshark Filter
A useful display filter is:
dhcp
You can also filter DHCPv4 UDP ports:
udp.port == 67 || udp.port == 68
Linux tcpdump
sudo tcpdump -nn -i any 'udp port 67 or udp port 68'
For additional packet details:
sudo tcpdump -nn -vvv -i any 'udp port 67 or udp port 68'
What to Inspect
During renewal analysis, check:
- DHCP message type
- Source and destination IP
- Whether DHCPREQUEST is unicast or broadcast
ciaddr- Transaction ID
- DHCPACK or DHCPNAK response
- Option 51 lease duration
- Option 58 T1
- Option 59 T2
- Server Identifier when applicable
- Relay information where applicable

Common Renewal Problems
T1 Request Gets No Response
Possible causes:
- Original DHCP server down
- Server unreachable
- ACL blocking traffic
- Routing failure
- Server overloaded
- DHCP service stopped
The client can normally continue using the current address because the lease has not yet expired.
T1 Fails but T2 Works
Example:
T1:
Unicast DHCPREQUEST → No Response
T2:
Broadcast DHCPREQUEST
Another DHCP Server:
DHCPACK
This suggests:
- Original server was unavailable
- Another server was available
- Rebinding succeeded
Client Reaches Expiration
If you observe:
- Repeated DHCPREQUEST
- No DHCPACK
- T2 reached
- No responding server
then eventually the lease expires.
Investigate:
- DHCP service availability
- Network routing
- Relay path
- Failover configuration
- ACL/firewall policy
- Scope availability
DHCPACK Arrives but Lease Still Looks Wrong
Verify the values supplied in:
- Option 51
- Option 58
- Option 59
Do not automatically assume the client is using exact 50% and 87.5% timers.
The server can provide explicit timer values.
RFC 2131 also allows timer values to include some random variation to reduce synchronized client renewal behavior.
T1 and T2 Are Not Always Exactly 50% and 87.5%
The commonly taught values are:
T1:
50%
T2:
87.5%
These are useful defaults for understanding DHCP.
However, administrators and DHCP servers can supply explicit renewal and rebinding values.
RFC 2132 provides:
- Option 58 for T1
- Option 59 for T2
Therefore:
DHCP Renewal Through a Relay
In enterprise networks, DHCP clients and servers may be separated by Layer 3 boundaries.
A DHCP Relay Agent may therefore participate in the DHCP exchange.
Example:
Client:
192.168.10.50
Client Network:
192.168.10.0/24
Gateway / Relay:
192.168.10.1
DHCP Server:
10.10.10.20
Whether a specific renewal travels directly or involves relay behavior depends on the client’s state, addressing, topology, and implementation.
When troubleshooting a relayed DHCP environment, inspect:
- Client packet behavior
- Relay interface
- Relay destination
- Routing to DHCP server
- Return path
giaddr- Server scope
- Server logs
RENEWING vs REBINDING
| Feature | RENEWING | REBINDING |
|---|---|---|
| Starts At | T1 | T2 |
| Typical Default | ~50% | ~87.5% |
| Existing Lease Valid? | Yes | Yes |
| Target | Original DHCP server | Any appropriate DHCP server |
| Typical Request | Unicast | Broadcast |
Client Uses ciaddr |
Yes | Yes |
| Success Response | DHCPACK | DHCPACK |
| Final Failure | Move toward T2 | Lease eventually expires |
Easy Way to Remember
T1 = Renew
“Can my original server extend my lease?”
T2 = Rebind
“Can any available DHCP server extend my lease?”
Expiration
“No server renewed the lease. Stop using the address.”
Key Takeaways
- A DHCP IPv4 address is normally assigned for a limited lease duration.
- T1 controls when the client enters the RENEWING state.
- T2 controls when the client enters the REBINDING state.
- T1 must occur before T2, and T2 must occur before final lease expiration.
- The commonly taught default T1 value is approximately 50% of the lease.
- The commonly taught default T2 value is approximately 87.5% of the lease.
- During RENEWING, the client normally unicasts DHCPREQUEST to the original DHCP server.
- During REBINDING, the client attempts to reach any appropriate DHCP server.
- The client normally continues using its existing address while the lease is still valid.
- A successful renewal usually requires only:
DHCPREQUEST
DHCPACK
rather than a complete DORA exchange.
- During renewal,
ciaddrcommonly contains the client’s currently assigned IPv4 address. - DHCP Option 51 identifies lease duration, Option 58 identifies T1, and Option 59 identifies T2.
- If the client receives DHCPACK, it returns to the BOUND state.
- If renewal fails until T2, the client enters REBINDING.
- If the lease finally expires without DHCPACK, the client must stop using the expired address and return toward DHCP initialization.
The most important troubleshooting principle is to identify the client’s current DHCP state.
Ask:
Is the client still BOUND?
Has it reached T1 and entered RENEWING?
Has it reached T2 and started REBINDING?
Has the lease actually expired?
Then inspect the packet behavior.
A unicast DHCPREQUEST to the original server suggests normal renewal.
A broader DHCPREQUEST later in the lease can indicate rebinding.
Repeated requests with no DHCPACK indicate a renewal path or server problem.
Once you understand the relationship between the lease timer, T1, T2, DHCPREQUEST, DHCPACK and expiration, DHCP renewal problems become much easier to isolate.
Useful Links and References
SanchitGurukul Resources
Official Technical References
Your feedback matters
Was this post helpful?
Discussion
0 approved comments
No approved comments yet. You can start the discussion below.
Leave a Comment
No login is required. Name and email are used for moderation/security. Your email is never displayed publicly. All comments require administrator approval.
Discover more from SanchitGurukul
Subscribe to get the latest posts sent to your email.
