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/06/08 06:28] – [Method 1: Store the lease database on permanent storage] -format hogwild | retain_dhcp_lease_info_after_a_reboot [2023/08/05 19:19] – [Method 1: Store the lease database on permanent storage] -condense, fix broken links hogwild | ||
---|---|---|---|
Line 12: | Line 12: | ||
\\ | \\ | ||
- | - Under Advanced, go to to [[:advanced-dhcpdns|DHCP/ | + | - Under Advanced, go to to [[advanced-dhcpdns|DHCP/ |
dhcp-leasefile=/ | dhcp-leasefile=/ | ||
- | </ | + | </ |
- Use a path relative to your own system. | - 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' | + | - 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 [[status-devices|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 " | + | - You will notice that the example points to a USB device labelled " |
Line 24: | Line 24: | ||
\\ The second approach is to keep the lease database in its default location and copy it to permanent storage at " | \\ The second approach is to keep the lease database in its default location and copy it to permanent storage at " | ||
- | \\ \\ For example, in the // | + | \\ \\ For example, in the [[admin-scripts|Scripts]] menu, in the Init field, enter:\\ |
<code -> | <code -> | ||
Line 51: | Line 51: | ||
\\ | \\ | ||
- | The second method can be used with any storage including JFFS. included, where for USB (only) an alternative is to performed the save/copy within the '' | + | The second method can be used with any storage, including JFFS. included, where for USB (only) an alternative is to performed the save/copy within the //Run after mounting///Run before unmounting on the [[nas-usb|USB page]] instead than the generic script section. |
\\ | \\ |