WAN DHCP doesn't like renewing
-
Periodically my 2.0.3 box releases it's WAN IP or it times out and just never renews itself. Everything else getting IP's from that DHCP server renews without issue, and when I log in to pfSense and manually renew it everything is sunshine and rainbows, until it happens again. I feel like I shouldn't need a cron job to DHCP renew this thing. Thoughts?
-
Perhaps dhclient is telling you something signicant through the system log: Status -> System Logs or (better) pfSense shell command:```
clog /var/log/system.log | grep dhclient -
Thanks for the tip! Seems my ISP has two DHCP servers battling for control of my network segment and pfSense is smarter than the other routers I have plugged in which don't seem to care about such foolishness. I may just put a dumb gateway between the modem and pfSense to bypass their weirdness.
-
Seems my ISP has two DHCP servers battling for control of my network segment
Some readers have reported their cable modems act as a local DHCP server when the cable link goes down. So when the cable link goes down pfSense can get an IP address from the modem but apparently not attempt to get a new lease when the cable link comes up.
It could be useful to see the dhclient logs from your system to see if you have a different problem or your logs can shed some light on the problem I mentioned.
-
Thanks for the tip! Seems my ISP has two DHCP servers battling for control of my network segment and pfSense is smarter than the other routers I have plugged in which don't seem to care about such foolishness. I may just put a dumb gateway between the modem and pfSense to bypass their weirdness.
FWIW, this is a valid means of deploying redundant DHCP. The expectation is that hosts will use the first answer to arrive. This is why they include the source of the lease so that it can query the issuing dhcp server for renewals.