Hardware: GL.iNet GL-AR150
Gargoyle: 1.12.0 (recently upgraded to 1.14)
Any power cut results in DHCP no longer working after restart.
I suspect stale/corrupt DHCP leases. Depending on the device router connectivity is lost, windows clients handling it very poorly and always losing connection.
Gargolyle router persists DHCP leases in the file /tmp/dhcp.leases
Steps to fix DHCP after power cut:
Configure the connecting computer to use a static IP address.
Login to Gargoyle router
Connection > DHCP
Untick "LAN DHCP Server Enabled", Save
Tick "LAN DHCP Server Enabled", Save
Reconfigure the connecting computer to use DHCP.
My permanent solution to prevent stale/corrupt DHCP leases following a power cut is to edit the options in /etc/config/dhcp :
$ ssh root@192.168.1.1
vim /etc/config/dhcp
find line as below
option leasefile '/tmp/dhcp.leases'
change to
option leasefile ''
Note: I am not sure if editing /etc/config/dhcp as a solution has any negative side-effects, but I haven't encountered any on 1.12 or 1.14
Please consider fixing this as the steps to fix DHCP after power cut are frustrating and error prone and therefore power cuts can cause long downtime. Also not everyone will know how to fix this after a power cut and even fewer will know how to permanently fix the issue via ssh.
Hardware: GL.iNet GL-AR150
Gargoyle: 1.12.0 (recently upgraded to 1.14)
Any power cut results in DHCP no longer working after restart.
I suspect stale/corrupt DHCP leases. Depending on the device router connectivity is lost, windows clients handling it very poorly and always losing connection.
Gargolyle router persists DHCP leases in the file /tmp/dhcp.leases
Steps to fix DHCP after power cut:
Configure the connecting computer to use a static IP address.
Login to Gargoyle router
Connection > DHCP
Untick "LAN DHCP Server Enabled", Save
Tick "LAN DHCP Server Enabled", Save
Reconfigure the connecting computer to use DHCP.
My permanent solution to prevent stale/corrupt DHCP leases following a power cut is to edit the options in /etc/config/dhcp :
$ ssh root@192.168.1.1
vim /etc/config/dhcpfind line as below
option leasefile '/tmp/dhcp.leases'change to
option leasefile ''Note: I am not sure if editing /etc/config/dhcp as a solution has any negative side-effects, but I haven't encountered any on 1.12 or 1.14
Please consider fixing this as the steps to fix DHCP after power cut are frustrating and error prone and therefore power cuts can cause long downtime. Also not everyone will know how to fix this after a power cut and even fewer will know how to permanently fix the issue via ssh.