[Not an issue]AX6000 DHCP server ignores lease time setting (fw 1.1.1 and 1.2.0)

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

[Not an issue]AX6000 DHCP server ignores lease time setting (fw 1.1.1 and 1.2.0)

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
[Not an issue]AX6000 DHCP server ignores lease time setting (fw 1.1.1 and 1.2.0)
[Not an issue]AX6000 DHCP server ignores lease time setting (fw 1.1.1 and 1.2.0)
2021-02-10 22:42:19 - last edited 2021-02-12 21:14:17

I think that my AX6000 DHCP server has two problems:

1/ The configured DHCP address lease time is ignored

2/ The default lease time is 120 seconds, not 120 minutes

 

I've checked this with the current 1.1.1 firmware and the 1.2.0 that is currently posted for testing in this forum.

 

I have my AX6000 set up in Access Point mode and with DHCP turned on.

 

In the web UI there is a Network > DHCP settings page, and I have entered 720 into the "Address lease time minutes" box.

 

I have saved the settings and rebooted the AX6000. Revisiting the web UI I can see that the DHCP lease time has been remembered. 

 

When I query the DHCP server configuration with this (Linux) command line

sudo nmap --script broadcast-dhcp-discover

I always see that the lease time is 2 minutes (120):

Starting Nmap 7.70 ( https://nmap.org ) at 2021-02-10 22:20 GMT
Pre-scan script results:
| broadcast-dhcp-discover: 
|   Response 1 of 1: 
|     IP Offered: 192.168.0.117
|     DHCP Message Type: DHCPOFFER
|     Server Identifier: 192.168.0.253
|     IP Address Lease Time: 2m00s
|     Renewal Time Value: 1m00s
|     Rebinding Time Value: 1m45s
|     Subnet Mask: 255.255.255.0
|     Broadcast Address: 192.168.0.255
|     Domain Name Server: 194.168.8.100, 8.8.4.4
|_    Router: 192.168.0.1

 

Is there a way to log this with the Web UI team?

 

  0      
  0      
#1
Options
1 Reply
Re:AX6000 DHCP server ignores lease time setting (fw 1.1.1 and 1.2.0)
2021-02-12 21:12:15 - last edited 2021-02-12 21:24:53

Likely this is just an issue with the way I've checked the DHCP configuration, using nmap.

(The broadcast-dhcp-discover.nse tends to return very low lease times from DHCP servers: https://github.com/nmap/nmap/issues/2197)

 

When I look at the actual leases given to my PCs they have the expected lease times.

 

In Linux, typing journalctl I can find these lines

Feb 10 18:37:20 rpi-tv dhcpcd[455]: eth0: offered 192.168.0.11 from 192.168.0.253
Feb 10 18:37:20 rpi-tv dhcpcd[455]: eth0: probing address 192.168.0.11/24
Feb 10 18:37:25 rpi-tv dhcpcd[455]: eth0: leased 192.168.0.11 for 7200 seconds
Feb 10 18:37:25 rpi-tv dhcpcd[455]: eth0: adding route to 192.168.0.0/24
Feb 10 18:37:25 rpi-tv dhcpcd[455]: eth0: changing default route via 192.168.0.1

 

192.168.0.253 is my TP-Link AX6000, and the lease was 7200 seconds, or 120 minutes.

 

After changing the lease time to 720 minutes I can see the correct lease time in windows by typing ipconfig /all:

Ethernet adapter Ethernet 2:

...
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
...
   IPv4 Address. . . . . . . . . . . : 192.168.0.17(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : 12 February 2021 14:50:51
   Lease Expires . . . . . . . . . . : 13 February 2021 02:50:51
...
    DHCP Server . . . . . . . . . . . : 192.168.0.253

 

My mistake - not an issue!

  0  
  0  
#2
Options