pfSense not detecting when modem drops then reconnects to ISP.
-
Hi all.
This is my first post here, so I'm hoping I'm not breaking any etiquette with this post. My apologies if I am.
I've been using pfSense for a couple years now, and it's been working well. However, within the last few months I've been experiencing problems with it. I honestly think that some (most?) of my issues are with the ISP, but here's one that I think may be a pfSense issue.
Periodically, my cable modem loses connection with the ISP. pfSense detects this because if I connect to the pfSense web server, I will see an WAN IP address of something like 10.10.10.1 or such. According to the ISP tech and from what I've read online, the cable modem will offer this IP address to the client (i.e., pfSense) if the modem loses connection with the ISP. Ok, I get it.
The problem is that when the modem reconnects to the ISP, pfSense still uses the 10.10.10.1 IP address -- it doesn't pick up the new, correct, useful IP address. If I reboot pfSense, then it picks up the good IP address.
I'm curious as to why pfSense can detect the 'offline' IP address when the modem loses contact with the ISP, but pfSense doesn't pickup the good IP address when contact is reestablished.
I did see this sort-of-similar post:
- https://forum.netgate.com/topic/16217/howto-ping-hosts-and-reset-reboot-on-failure
I can implement something like that on my pfSense box, but it seems kind of like a brute force way of getting the IP back.
Any thoughts as to why pfSense doesn't pickup the new IP address?
Thanks.
-JS
-
@js50 Just release and renew the lease here.
-
@js50 said in pfSense not detecting when modem drops then reconnects to ISP.:
Periodically, my cable modem loses connection with the ISP. pfSense detects this because if I connect to the pfSense web server, I will see an WAN IP address of something like 10.10.10.1 or such. According to the ISP tech and from what I've read online, the cable modem will offer this IP address to the client (i.e., pfSense) if the modem loses connection with the ISP. Ok, I get it.
You're not using pfBlockerNG, right ?
Because, if so, this default pfBlockerNG setting will conflict :
-
@js50 said in pfSense not detecting when modem drops then reconnects to ISP.:
pfSense still uses the 10.10.10.1 IP address
You use a modem, right ?!
What about using the pfSense special 'modem' settings for the DHCP client on the (a) WAN port ?
Check this option :
Now read the option description of this one :
Up to you to, when you get this 10.10.10.x IP, to find the RFC1918 IP of the modem, and enter that IP.
From now, pfSense won't accept DHCP offers from your modem any more, just the DHCP offers coming in from ups stream == your ISP DHCP server. -
@gertjan Interesting ... I have a cable modem (Motorola) and when the service is down or disrupted, I get WAN n/a however, I have no RF1918 checked on WAN. Thanks for sharing, I learn something new today.
