This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
retain_dhcp_lease_info_after_a_reboot [2023/06/08 06:33] – [Method 2: Copying the lease database to permanent storage at halt time] -format hogwild | retain_dhcp_lease_info_after_a_reboot [2023/08/09 15:41] – [Method 1: Store the lease database on permanent storage] -condense hogwild | ||
---|---|---|---|
Line 12: | Line 12: | ||
\\ | \\ | ||
- | - Under Advanced, go to to [[:advanced-dhcpdns|DHCP/ | + | - Under Advanced, go to the [[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 | + | - Notice |
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 [[admin-scripts|Scripts]] menu, in the Init field, enter:\\ | + | \\ \\ For example, |
<code -> | <code -> | ||
Line 41: | Line 41: | ||
\\ | \\ | ||
- | In the same menu, in the Halt field, enter:\\ | + | in the //Halt// field In the [[admin-scripts|Scripts]] menu, enter:\\ |
<code -> | <code -> | ||
Line 51: | Line 51: | ||
\\ | \\ | ||
- | The second method | + | Method 2 can be used with any type of storage, including JFFS. When using method 2 only with USB, an alternative is to enter the former set of configuration lines into the //Run after mounting// field and the latter set of lines in the //Run before unmounting// fields in the [[nas-usb|USB |
\\ | \\ |