DHCP-WAN Renew lease
-
Whenever power interrupts cable modem and then it is restored, WAN behaves weirdly and seems to reject IP address...is this a bug? Renewing the lease from Status > Interface, one can see the request been honored, yet on the dashboard, the WAN interface goes from 0.0.0.0 to the IP address briefly, then rejects the IP, then goes to n/a.
-
When this happens, start a packet capture on WAN and see what's going on. Someone had this problem very recently, and IIRC after doing a sniff we saw that pfSense WAN was requesting an address and getting no reply from the ISP.
-
You could be hitting this: https://redmine.pfsense.org/issues/9267
This workaround might work for you if so: https://forum.netgate.com/post/854007
Steve
-
Hmm, the fix didn't make it into FreeBSD 12 release. That means a proper fix isn't coming until the first patch at the earliest.
-
@KOM said in DHCP-WAN Renew lease:
When this happens, start a packet capture on WAN and see what's going on. Someone had this problem very recently, and IIRC after doing a sniff we saw that pfSense WAN was requesting an address and getting no reply from the ISP.
KOM, in my case, I can see that the request was honored, WAN gets the correct network address, then an IP address for a few seconds and then rejects the address, just by switching between Status > Interface and Status > Dashboard. So, it's a pfSense thing.
-
@stephenw10 said in DHCP-WAN Renew lease:
You could be hitting this: https://redmine.pfsense.org/issues/9267
This workaround might work for you if so: https://forum.netgate.com/post/854007
Steve
Steve, my work around is to reset the modem by pressing the reset button while inserting the power supply, then reboot pfSense...it's a hit and missed approach though. Sometimes it takes three try.
-
Do what Steve recommends by increasing the timeout and you won't have to worry about it at all.
-
@KOM said in DHCP-WAN Renew lease:
Do what Steve recommends by increasing the timeout and you won't have to worry about it at all.
Okay KOM, I was hoping it would get fixed by pfSense 2.5 release but I might try that since my work-around seems to be a hit & missed.
-
Netgate is entirely reliant on FreeBSD to get its own house in order and FreeBSD didn't fix it in v12.0-RELEASE so you won't see it in pfSense until v2.5.1 at the earliest.
-
@KOM said in DHCP-WAN Renew lease:
Netgate is entirely reliant on FreeBSD to get its own house in order and FreeBSD didn't fix it in v12.0-RELEASE so you won't see it in pfSense until v2.5.1 at the earliest.
Wow, okay, thanks for sharing.
-
That's not entirely true. We have back-ported patches previously if they are sufficiently important. It's very inconvenient doing so though, any move away from stock FreeBSD introduces additional technical debt at every pfSense release. That's something we are very much moving away from.
Steve
