This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
retain_dhcp_lease_info_after_a_reboot [2023/05/24 03:35] – [Retain DHCP Lease Information after a Reboot] 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 12: | Line 12: | ||
\\ | \\ | ||
- | - Under Advanced, go to to [[: | + | - Under Advanced, go to to [[: |
dhcp-leasefile=/ | 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' |
- | - 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 " | - You will notice that the example points to a USB device labelled " | ||
+ | |||
===== Method 2: Copying the lease database to permanent storage at halt time ===== | ===== Method 2: Copying the lease database to permanent storage at halt time ===== |