It would be really nice to be able to set long lease times to DHCP reservations. This would be handy when you have a ton of IoT devices, especially for battery powered IoT devices.
Hi Chris. It’s already there. :<) Start where you have configured your LAN segments (not “AP.”) Here’s an example from a Balance 20X:
- Rick
Thanks Rick,
It is true that you can set lease time at the LAN level but what I was really after was a way to set a more traditional lease time for dynamically assigned devices on the LAN (say 2 days for example) and then override that setting with a very long lease time for something I’m setting as a static IP address (90 days perhaps). This would be helpful for the proliferation of sensors that are battery operated.
I could work around this by setting up two VLANs for the static and dynamic IoT networks and set the lease times accordingly but it would be more convenient to have everything together and have an override.
Sorry if that use case wasn’t clear and thank you for the note.
A static address is set on the client and does not involve DHCP. However, some IOT/M2M/etc devices can’t do that so Peplink has provided a means to reserve an address for the client. And, that reservation will “hold” until you terminate it.
If, you go to Status → Client list you have the option of reserving the address the client is presently using.
Alternatively, if you navigate to Network → LAN → Network Settings → LAN → [specify the LAN] → DHCP Server → DHCP Reservation you can “manually” enter the MAC address of the client and the IP address top which you want it to be assigned in the future. Example:
In this example 192.168.52.38 will be assigned every time the associated MAC address is seen. The latter approach may also be useful in situations where you wish to change the IP address from that presently in use.
I’m wondering if the existing capability regarding address reservation may meet your requirements?
R
Sorry, I’m being a little sloppy with my terminology (though in fairness the column is named “Static IP” in the GUI).
What I’m ultimately trying to do is set a DHCP reservation for a myriad of IoT sensors that would be difficult to manage with client based static IPs. I also don’t want to have them pinging the DHCP server everyday which is the current DHCP lease time for the network and it’s also what gets sent along with DHCP reservations. I’d love to be able to set the DHCP reservation’s lease independent of the network’s DHCP lease time.
Though I will admit that a DHCP transaction is light, roughly 1KB per, With hundreds if not thousands of sensors in a system it can add up and they often expire in unison. More importantly, many of the sensors are battery powered and the network transmissions are a large part of the power consumption.
Sorry I was not being clear. I could definitely work around it by putting out separate VLANs for the battery powered sensors but that has it’s own set of drawbacks with security, IPC and a host of other configurations that would need to be duplicated and maintained.
Thank you for your input on this. I really appreciate the thoughtful consideration.
My best,
Chris
OK, Chris. Got it. Let’s let this stand as a feature request.