pfSense 2.4.3-p1 loses WAN connectivity after exactly 24 hours
-
Recently, I've been dealing with an issue where my pfSense router loses WAN connectivity after exactly 24 hours, on the dot. It's a fairly simple 1 WAN/1 LAN + OpenVPN client setup for home use, running off a whitebox with an Intel PRO/1000 PT quad-port card.
My ISP's DHCP lease happens to be 12 hours, and although the time-of-WAN-death coincides with the expiration time of the second lease, pfSense's DHCP client appears to be working properly. it sends out a DHCPREQUEST, gets a DHCPACK, and does a RENEW almost an hour before the lease expires.
After the WAN dies, the WAN gateway shows "offline" with 100% packet loss. The only way to restore connectivity is to do a manual release/renew on the interface or reboot the box.
I've already tried setting kern.ipc.nmbclusters to 1,000,000 as recommended, since I did see some dpinger error 55 errors in the log. However, this doesn't seem to have helped, other than getting rid of the error. I now see a lot of error 65 messages, which I guess isn't terribly surprising since the WAN is truly down.
-
Have you tried requesting a different lease time in the advanced options? That would at least prove it's a DHCP issue if it changes the time it takes to fail.
Steve
-
@stephenw10 said in pfSense 2.4.3-p1 loses WAN connectivity after exactly 24 hours:
Have you tried requesting a different lease time in the advanced options? That would at least prove it's a DHCP issue if it changes the time it takes to fail.
Steve
Would this be done by putting
dhcp-lease-time xxxxin the Request options box for advanced DHCP settings? -
@maroon2019 said in pfSense 2.4.3-p1 loses WAN connectivity after exactly 24 hours:
@stephenw10 said in pfSense 2.4.3-p1 loses WAN connectivity after exactly 24 hours:
Have you tried requesting a different lease time in the advanced options? That would at least prove it's a DHCP issue if it changes the time it takes to fail.
Steve
Would this be done by putting
dhcp-lease-time xxxxin the Request options box for advanced DHCP settings?I've put dhcp-lease-time 300 in the supersede options - let's see what happens.
-
I believe it should go in the 'send' field but it's not an option I use all that often.
https://www.freebsd.org/cgi/man.cgi?query=dhclient.conf&sektion=5#LEASE_REQUIREMENTS_AND_REQUESTSSteve
-
Update: looks like that did the trick! My dhcp-lease-time is currently set for 7200 (so a renewal happens every hour) and so far it hasn't dropped the connection.
