Hi, Where can I find this setting to increase DHCP Leasetime? This simple setting it seems its not include in the firmware? Why is that? This is a basic setting that should in the firmware.
Please explain what for exactly... DHCP renewal is a fully transparent process, no need to reconnect or the like. No matter if we talk of 60 minutes, 480 minutes, 1440 minutes or longer.
A correct working DHCP client is able to refresh it's allocated IP address virtually forever - without ever expiring. Certainly as long as the DHCP server is not restarted or reset. And without going through a DHCP Discover process assigning the DHCP client a new IP address
Fancy some excursion into the DHCP process? Here you go:
---- 1. When the lease reaches 50% (T1) of its validity period, the DHCP client unicasts a DHCP Request message to the DHCP server to request lease renewal. If the server renews the lease (counted from 0), it sends a DHCP Ack message to the client. If the server rejects the renewal request, it sends a DHCP Nak message to the client, which must then send a DHCP Discover message to apply for a new IP address.
2. If no response is received from the DHCP server when the lease reaches 87.5% (T2) of its validity period, the DHCP client broadcasts a DHCP Request message to request lease renewal. Similar to T1, if the client receives a DHCP Ack message, the server has renewed the lease; if the client receives a DHCP Nak message, the client must send a DHCP Discover message to apply for a new IP address.
3. If no response is received when the lease expires, the client stops using the IP address and sends a DHCP Discover message to apply for a new IP address. When a DHCP client no longer needs to use its allocated IP address and the lease has not expired, the client sends a DHCP Release message to the DHCP server to request IP address release. The server saves the configuration of this client and records the IP address in the allocated IP address list. The IP address can then be allocated to this client or other clients. To request a configuration update, a client can send a DHCP Inform message to the server. ---
Curious what you expect to happen after this one day or 1440 minutes expiration time? I expect the DHCP client will retain it's assigned IP address forever.
When the lease reaches 50% (T1) of its validity period, the DHCP client unicasts a DHCP Request message to the DHCP server to request lease renewal. If the server renews the lease (counted from 0), it sends a DHCP Ack message to the client.
So after 12 hours, the DHCP server gives an ack an does start another period, reset the timer. This can continue for days, weeks, months.
Some people like a very short least time, like 2 hours or so, in places where lots of clients come and go so that the DHCP pool doesn't get exhausted that easy. Of course there are ways around that, but just saying. I don't know why you'd want to increase the lease beyond a day time.
Some people like a very short least time, like 2 hours or so, in places where lots of clients come and go so that the DHCP pool doesn't get exhausted that easy. ...
Yes, this is a very valid reason! But not what was requested here in the subject.
How is the DNS problem drops being in this release?
What DNS dropping problem, what Netgear product, and which firmware version number? Please open a new thread in the appropriate community section, and provide the essential information.
I want to it decrease my lease time for example to 1 hour instead of 24Hours. How to achieve that?
It is automatically that the DHCP lease time is 24Hours, but I want to de-crease it to 1 hour.
Facing a problem with a DHCP running out due to a lot of walk-in visitors as @microchip8 says? Either way, it won't magically fix the unspecified DNS issues you are apparently behind.
Some people like a very short least time, like 2 hours or so, in places where lots of clients come and go so that the DHCP pool doesn't get exhausted that easy.
I just want to de-crease the DHCP lease time to 1 hour instead of 24H.
Why?
When trying to fix problems, it is usually a good idea to start with a description of the destination you want to reach rather than running up here with questions about how to get there. That avoids the risk of getting the "If I wanted to get there, I wouldn't start from here" answer to that old joke about someone asking a stranger for directions.
So far you have simply restated the original question several times. Is there any reason why you don't want to answer the question that @schumaku and @microchip8 have asked.
If you can answer the "why?" question, they may be able to offer suggestions on how to achieve whatever it is that you want to do.
Okay, I want to de-crease the DHCP Lease time because of the guest network I want a shorter lease time periode of 8Hours. That's why. So don't discuss with me ''Thats not need it, Etc. Etc. '' This is a option what I want for guest network a shorter lease time periode.
So why is this basic-option not availble for us? While other brands have this option. I was on different brands have this option.
As I mentioned in my very first post, there is no option to control the lease time. It has been requested long ago but NG appears not to be willing to add it.
Also, in your OP post, you want to increase the lease time but now you want to decrease it. Which one is it?
I see. Never know that this a thing on Netgear products.
It doesn't matter which I want, the only thing I want is the control over it. In my guest network I want to de-crease the DHCP lease time and in my other router I want to increase the lease time.
So again it doesn't matter which one I suggest, I need both to increase and to de-crease it in the other product...
I was hoping that this was a bug or a feature that was forgotten, but now I read more that Netgear is not giving the control to their customers.
Well, on the R7800 you can install Voxel's firmware and enable SSH. Then you can adjust the lease time in some file (no idea which one). That's the only way to do it. On the R7000, you can try enabling Telnet access in debug.htm (if they haven't removed it)
One could try OpenWRT or DD-WRT FW and see if there is a least time UI option with in those FW variants for the R7000. Those FWs have more granular advanced UIs than NG has. Those would be more up to date as the R7000 is getting up in age and highly doubt if NG will be spending any money to add features in just for one user. I believe the R7000 is already headed towards EoL from NGs side.
Lets keep it simple: The R7000 is a consumer router, supporting one LAN, one IP subnet, and one DHCP server. The Guest network is just a L2 isolated network.
Just to avoid some misunderstandings here: The DHCP expiration time is in no aspect a control limiting the possible connection or association time. The only reason for a shorter expiration time is to free-up no longer active DHCP associations, because of the device is no longer connected to the network.
Already explained, an active DHCP client device connection is refreshed repeatedly, the address reservation will be refreshed again and again (as defined by the T1, T2, T3) - it will remain active forever ... until its no longer required.
Not sure if I follow, but there's only one DHCP server for both your own LAN the the Guest one. So you can't keep the lease time for your LAN but modify the one for the Guest. If you set your own lease value, it will be for both your LAN and the Guest. The Guest is not an entirely seperate network with its own DHCP. It's mostly made of iptables rules and virtual interfaces.
@Hot54321 wrote: In my guest network I want to de-crease the DHCP lease time and in my other router I want to increase the lease time.
You have two routers on one network? ... Curiouser and curiouser.
The imagination on these moving targets is on us ... I -guess- there are two routers in place, each to cover a dedicated [W]LAN and the guest [W]LAN.
Decreasing the DHCP lease time in an environment with a big number of clients to prevent shortages on the DHCP pool is one thing.
The "why" increase the lease time is more a "because I want to configure what I want and Netgear does not allow".
Equally, no response on the "How is the DNS problem drops being in this release?" also brought on the table, but at least denied later on.
I'm not even convinced the OP did understood why we had some questions before. Wonder what new moving targets will arrive to this discussion soon.
Reminds me to the request for longer DHCP expiration times (on some systems defaulting to 8 hours) "because we are often gaming in sessions longer than eight hours and don't want to be disconnected" we've seen before. Exactly this does not happen! But this is why we're asking ugly questions 8-)
