This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
retain_dhcp_lease_info_after_a_reboot [2023/05/24 03:04] – -condense hogwild | retain_dhcp_lease_info_after_a_reboot [2023/06/08 06:28] – [Method 1: Store the lease database on permanent storage] -format hogwild | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Retain DHCP Lease Information after a Reboot ====== | ====== Retain DHCP Lease Information after a Reboot ====== | ||
- | By default, dnsmasq stores DHCP lease information | + | By default, dnsmasq stores DHCP lease data in (volatile) |
- | \\ | + | There are currently two common methods for dealing with this. |
- | There are currently two approaches to resolving this. The first approach does not use scripting. | ||
- | - Under Advanced, go to to [[:advanced-dhcpdns|DHCP/ | + | ===== Method 1: Store the lease database on permanent storage ===== |
- | dhcp-leasefile=/ | + | |
- | </ | + | The first method does not use scripting. The goal of the first method |
- | - Use a path relative to your own system. Click Save. \\ | + | |
- | - The goal here is to store the lease database on permanent storage. This can be useful, for example, when devices are connected to a switch. Using permanent storage means client devices won't lose connectivity if the router reboots. Moreover, they won't display in the Device List as having an active lease until their current lease expires, and they request a new one. FreshTomato will just continue where if left off. \\ | + | |
- | - You will notice that the example points to a USB device labelled " | + | |
\\ | \\ | ||
- | 2) A different approach is to keep the lease database in its default location and copy it to permanent storage at " | + | - Under Advanced, go to to [[: |
+ | dhcp-leasefile=/ | ||
+ | </ | ||
+ | - Use a path relative to your own system. | ||
+ | - Using permanent storage means client devices won't lose connectivity if the router reboots. Because the lease database is not stored in RAM, a reboot won't erase it. This can be useful, for example, when devices are connected to a switch. Moreover, clients won't display in the [[device_list|Device List]] as having an active lease until their current lease expires, and they' | ||
+ | - You will notice that the example points to a USB device labelled " | ||
+ | |||
+ | |||
+ | ===== Method 2: Copying the lease database to permanent storage at halt time ===== | ||
+ | |||
+ | \\ The second | ||
- | Administration/ | + | \\ \\ For example, in the //Administration// |
<code -> | <code -> | ||
Line 31: | Line 37: | ||
</ | </ | ||
- | Administration/ | + | \\ |
+ | |||
+ | \\ | ||
+ | |||
+ | In the same menu, in the Halt field, enter:\\ | ||
<code -> | <code -> | ||
Line 37: | Line 47: | ||
</ | </ | ||
- | This method | + | \\ |
+ | |||
+ | \\ | ||
+ | |||
+ | The second | ||
+ | |||
+ | \\ | ||
+ | |||
+ | \\ | ||