After Cable modem power down WAN Interface gets no ip
-
@stephenw10 I clicked on release lease and then on renew. Isn't there some kind of pinger wich would detect that situation and toggle Interface down and up?
-
Not that I'm aware of.
Can you test a 2.5 snapshot? I don't think that fix has gone in yet but if it's something else it may already be fixed there.
Steve
-
@stephenw10 OK will do that in a couple of hours... So I'll just go to "System Update" and select the 2.5 development snapshot. I'll take a config backup before. Any thing else?
-
@Ognian said in After Cable modem power down WAN Interface gets no ip:
I clicked on release lease and then on renew. Isn't there some kind of pinger wich would detect that situation and toggle Interface down and up?
Given that the DHCP process is starting indicates pfSense is seeing the modem come back. It's already sending out the requests which are not being responded to. There's nothing else it can do, so the problem is elsewhere. What happens if you plug a computer in? Does it get an address or not? This would indicate whether it's a pfSense problem.
BTW, a DHCP release simply tells the server to release an address, it doesn't get anotther, as that's part of the normal DHCP process. You'd then have to do a renew to get an address.
-
@JKnott I'm nearly 100% sure that the problem is the way the modem comes up ;-) But if I want to have Internet in the 2 million people city I live, I have to accept this particular modem. No other way. So I'm searching for a pragmatic solution for this... In a couple of hours I'll have (hopefully) some time to check the 2.5 version; If there is no other way to do it I'll need a script pinging the first gateway and in case that it can't be reached toggling wan if down and up... I just thought that there is something like this already ...
-
This :
can't be used to make pfSense wait for slow-to-start upstream WAN devices ? -
@stephenw10 Upgrade to
2.5.0-DEVELOPMENT (amd64)
built on Wed Jul 17 07:35:05 EDT 2019
FreeBSD 12.0-RELEASE-p7
went more or less smooth: after the last reboot there was no internet connection since the default gateway was on automatic instead of WAN_DHCP, but after that manual change it works like before.
And yes it behaves exactly like with the 2.4.4 release, if the cable modem is powered down and again up the WAN interface ends with no ip. Looking on the dashboard after the gateway gets red, the WAN Interface gets an DHCP IP but after some time it drops to n/a...
Shall I try to manually patch the script, or do you plan to have soon a new development version? -
@Gertjan said in After Cable modem power down WAN Interface gets no ip:
This :
can't be used to make pfSense wait for slow-to-start upstream WAN devices ?I had problem similar to this
Jul 17 13:21:21 dhclient 79311 No DHCPOFFERS received. Jul 17 13:21:16 dhclient 79311 DHCPDISCOVER on igb0 to 255.255.255.255 port 67 interval 5 Jul 17 13:21:03 dhclient 79311 DHCPDISCOVER on igb0 to 255.255.255.255 port 67 interval 13 Jul 17 13:20:55 dhclient 79311 DHCPDISCOVER on igb0 to 255.255.255.255 port 67 interval 8where pfSense by default do DHCPDISCOVER no long enough compared to how long my modem starts. So setting timeout to 900 fixed it for me (in WAN interface options). Of course I can't tell that this will work for you. But it is worth the try :)
-
@Gertjan @tomashk Thank you so much! This works!!
I've tried to search for the default value and the unit of this parameter; looks like the units are seconds and the default value is 60 seconds (from my log it looks like it waits 80 seconds, before it gives up). Changing this to 900 (15 minutes) should give plenty time to reconnect... And after changing it I can see that the cable modem needs almost 3 minutes to get online...So this looks like a good workaround for one time failures. Of course this https://redmine.pfsense.org/issues/9267 should do the rest
-
Nice!
