How long is IP address lease period/expired DHCP feature GR10 and GX20.

Solved
hiwamaru2
Here to help

How long is IP address lease period/expired DHCP feature GR10 and GX20.

Hello Specialist,

Operate GR10 in NAT / DHCP mode enable.
How long is the lease period/expired of local IP address assigned to the DHCP client (Wi-Fi PC) by the DHCP feature of GR10 ?

And Operate GX20 in NAT / DHCP mode enable (GR10 is running Bridge mode).
How long is the lease period/expired of local IP address assigned to the DHCP client (Wired PC) by the DHCP feature of GX20 ?

Thanks,

1 Accepted Solution
hidden0
Meraki Alumni (Retired)
Meraki Alumni (Retired)

Hello @hiwamaru2 

 

My apologies for the delayed reply here - I realize the community can't easily address this one.

 

GR series access points default lease time in NAT / DHCP mode: 24 hours.

GX20 in NAT / DHCP mode (or routed mode as we call it - it's only mode) default lease time: 24 hours.

View solution in original post

9 Replies 9
hidden0
Meraki Alumni (Retired)
Meraki Alumni (Retired)

Hello @hiwamaru2 

 

My apologies for the delayed reply here - I realize the community can't easily address this one.

 

GR series access points default lease time in NAT / DHCP mode: 24 hours.

GX20 in NAT / DHCP mode (or routed mode as we call it - it's only mode) default lease time: 24 hours.

Higgins0
New here

what do you mean when saying default lease time : is there a setting somewhere?

hiwamaru2
Here to help

The expiration date specified when the DHCP server function of the Meraki Go device provides an IP address.

Meraki Go has no items to setting (default specify) these lease time.  

Therefore, I asked about the lease time when Meraki Go provided an IP address (DHCP) for client.

hidden0
Meraki Alumni (Retired)
Meraki Alumni (Retired)

Good question @Higgins0 - I like your username by the way.

 

We could certainly make this an adjustable configuration (consider it a feature request as of today) - the default is 24 hours and nobody has desired to change it thus far.

Do you want to change it, and why? In most cases, 24 hours is a standard value to use here but I could see there being some minor concerns for larger networks.

Burt_Macklin
Conversationalist

Hello, what is the status of this feature request? We tend to set a shorter lease time for high traffic Public networks.

hidden0
Meraki Alumni (Retired)
Meraki Alumni (Retired)

Hey @Burt_Macklin 

 

We don't have the UX in the app for easy configuration of DHCP lease timers, but... we do support custom DHCP options now. I suppose in theory you could manually set DHCP option 58 and 59 to control your lease times?

 

The simple input/dropdown to set the lease timer is still on our to-do list as under consideration. 


FYI @hiwamaru2 and @Higgins0 

Burt_Macklin
Conversationalist

Hello, could you please give an example of this for an 8 hour lease time?

hiwamaru2
Here to help

Thank you for your answer.

I wanted to know 24hour.

speakerfritz
A model citizen

Setting a shorter lease time is good if you are on a border of an ip range and don’t want to open more ip avail addresses.  The less avail ips you have the tighter your security.

 

for example …./26 sub mask is 61 available addresses and and /27 is 29 avail addresses.

 
lets say you have 22 always active ip addresses and 10 roaming ip addresses of which 5 to 7 are onsite at any given time.

 

having a short ip address lease would there for be good if folks are in and out all day and the ip’s on their phones and laptops could be released after 2 hours instead of 24.

 

 

 

 

 

Get notified when there are additional replies to this discussion.