Static DHCP Issues related to DHCP Lease Expires
For all of my dynamic DHCP leases the lease expire has 120 minutes.
For all of my static DHCP leases the lease expire has Expires : October 9, 2159 1:20:03 AM
Using router in standalone mode until all of the standalone features are available in the Omada Management Platform which as of this version of the firmware they are not.
I have seen reference to other consumer TP-Link routers having this issue of DHCP expiry times. 49710 days, 6 hours, 28 minutes, 15 seconds but related to that article, there was no solution given.
If you require additonal information, I can offer that to you.
Experienced network admin here so please ask appropriate questions.
Thanks.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
mlatta wrote
For all of my dynamic DHCP leases the lease expire has 120 minutes.
For all of my static DHCP leases the lease expire has Expires : October 9, 2159 1:20:03 AM
Using router in standalone mode until all of the standalone features are available in the Omada Management Platform which as of this version of the firmware they are not.
I have seen reference to other consumer TP-Link routers having this issue of DHCP expiry times. 49710 days, 6 hours, 28 minutes, 15 seconds but related to that article, there was no solution given.
If you require additonal information, I can offer that to you.
Experienced network admin here so please ask appropriate questions.
Thanks.
RFC1541 Section 3.3 answers your question, I believe.
datatracker.ietf(dot)org/doc/html/rfc1541ection-3.3
FFFF FFFF converts to 4294967295 decimal, which is in seconds.
4294967295 seconds converts to 136 years 70 days 6 hrs. 28 min. 15 sec.
This is expected per RFC1541.
- Copy Link
- Report Inappropriate Content
mlatta wrote
For all of my dynamic DHCP leases the lease expire has 120 minutes.
For all of my static DHCP leases the lease expire has Expires : October 9, 2159 1:20:03 AM
Using router in standalone mode until all of the standalone features are available in the Omada Management Platform which as of this version of the firmware they are not.
I have seen reference to other consumer TP-Link routers having this issue of DHCP expiry times. 49710 days, 6 hours, 28 minutes, 15 seconds but related to that article, there was no solution given.
If you require additonal information, I can offer that to you.
Experienced network admin here so please ask appropriate questions.
Thanks.
Interesting, mine has a lease till October 16, 2159.
Maybe that is to be expected when using DHCP reservations?
Is there any problems with having a lease expire that far in the future if you have reserved the IP address?
IPCONFIG / ALL
Ethernet adapter vEthernet (External Virtual Switch):
Connection-specific DNS Suffix . : lan
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #2
Physical Address. . . . . . . . . : D8-xxxxxxxxxxxxxxx
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : fda9:xxxxxxxxxxxxxxxxxxxxxxxxxxxx(Preferred)
Temporary IPv6 Address. . . . . . : fda9:xxxxxxxxxxxxxxxxxxxxxxxx(Preferred)
Link-local IPv6 Address . . . . . : fe80::xxxxxxxxxxxxxx(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.140(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Friday, September 8, 2023 2:00:50 AM
Lease Expires . . . . . . . . . . : Tuesday, October 16, 2159 12:57:16 AM
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . : 41xxxxxxx
DHCPv6 Client DUID. . . . . . . . : 00-xxxxxxxxxxxxxxxxxxxxx
DNS Servers . . . . . . . . . . . : 192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled
- Copy Link
- Report Inappropriate Content
Interesting, mine has a lease till October 16, 2159.
Maybe that is to be expected when using DHCP reservations?
Is there any problems with having a lease expire that far in the future if you have reserved the IP address?
IPCONFIG / ALLEthernet adapter vEthernet (External Virtual Switch):
Connection-specific DNS Suffix . : lan
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #2
Physical Address. . . . . . . . . : D8-xxxxxxxxxxxxxxx
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : fda9:xxxxxxxxxxxxxxxxxxxxxxxxxxxx(Preferred)
Temporary IPv6 Address. . . . . . : fda9:xxxxxxxxxxxxxxxxxxxxxxxx(Preferred)
Link-local IPv6 Address . . . . . : fe80::xxxxxxxxxxxxxx(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.140(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Friday, September 8, 2023 2:00:50 AM
Lease Expires . . . . . . . . . . : Tuesday, October 16, 2159 12:57:16 AM
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . : 41xxxxxxx
DHCPv6 Client DUID. . . . . . . . : 00-xxxxxxxxxxxxxxxxxxxxx
DNS Servers . . . . . . . . . . . : 192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled
ain't this virtual machine IP address? LOL.
i think virtual machine would get something like this, unless you modify its NAT mode.
Ethernet adapter vEthernet (External Virtual Switch):
- Copy Link
- Report Inappropriate Content
Hi @mlatta
Thanks for posting in our business forum.
Sorry that I don't understand the question.
First, if you are on static IP address, you don't have the lease time. If you are on the IP-MAC binding and DHCP reservation or fixed IP address, then it is normal to have a "permanent" IP. The lease time is 2159, that's right.
Lease time is set in the LAN settings.
- Copy Link
- Report Inappropriate Content
Tedd404 wrote
ain't this virtual machine IP address? LOL.
i think virtual machine would get something like this, unless you modify its NAT mode.
Ethernet adapter vEthernet (External Virtual Switch):
It is actually a Hyper-V virtual Host computer that runs virtual machines. But a VM will act the same as a bare metal computer when it comes to IP addresses and DCHP. They all look the same to the router.
- Copy Link
- Report Inappropriate Content
mlatta wrote
For all of my dynamic DHCP leases the lease expire has 120 minutes.
For all of my static DHCP leases the lease expire has Expires : October 9, 2159 1:20:03 AM
Using router in standalone mode until all of the standalone features are available in the Omada Management Platform which as of this version of the firmware they are not.
I have seen reference to other consumer TP-Link routers having this issue of DHCP expiry times. 49710 days, 6 hours, 28 minutes, 15 seconds but related to that article, there was no solution given.
If you require additonal information, I can offer that to you.
Experienced network admin here so please ask appropriate questions.
Thanks.
RFC1541 Section 3.3 answers your question, I believe.
datatracker.ietf(dot)org/doc/html/rfc1541ection-3.3
FFFF FFFF converts to 4294967295 decimal, which is in seconds.
4294967295 seconds converts to 136 years 70 days 6 hrs. 28 min. 15 sec.
This is expected per RFC1541.
- Copy Link
- Report Inappropriate Content
@jg1212 Thank you that does answer the question. Unfortunately, should that ethernet client (PC, MAC, Camera, etc) need to be placed on a different static DHCP IP in the future, you are now forced to reboot / renew the ethernet client to obtain the new static IP being assigned. Not the end of the world but good to know it was not a "bug".
It is good to know they are not breaking the RFC1541 setting for infinity but would be nice to have static DHCP IP ethernet clients to check as often as non-static DHCP ethernet clients as many other network vendors offer including TP-Link offers with other products that I have used in the past that have DHCP capabilities.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 1457
Replies: 6
Voters 0
No one has voted for it yet.