dpinger: sendto error: 65
-
Apologies if this is better in the DHCP sub-forum... I did some searching and found some similar posts but never found a solution/fix.
I'm on pfSense 2.6 CE and the system was working well for many months. A few weeks ago, my ISP changed my cable modem which I connected to ensure it was registering with their system. After this, I immediately put it into bridge mode and connected it to my pfSense box. pfSense began pulling a WAN IP and then would disconnect (and repeat). My fix was to reboot the pfSense box and everything settled.
It seems that, after the modem swap, if pfSense is looking to bring up a WAN connection and then the modem becomes ready (power cycle, bump on the ISP side, etc), pfSense can't recover/establish the WAN connection. If I manually reboot pfSense while not touching the modem, everything immediately comes up fine.
This is new behaviour that started IMMEDIATELY with the introduction of the new modem. I'm not strong enough in my networking to debug. Any help would be appreciated. I have been looking at the recent DHCPD, SYSTEM, and GATEWAY log files and can pinpoint the time the ISP connection bumped and pfSense failed to recover.
-
Is it pulling a local IP from the modem before it syncs upstream?
If so you can add that IP to reject leases from the the WAN DHCP settings.
Steve
-
@stephenw10 said in dpinger: sendto error: 65:
Is it pulling a local IP from the modem before it syncs upstream?
If so you can add that IP to reject leases from the the WAN DHCP settings.
That's an interesting question that I'd not considered. I will check the dhcpd log and share a piece, if necessary. This doesn't really explain why this behavior didnt happen for many months and then IMMEDIATELY presented when the new modem from the ISP was installed.
-
The new modem may have new firmware and different behaviour.
-
OK... I had a closer look at the DHCPD log and I may have found something...
In the log, I found where:
- in the log where the ISP connection is lost... no clue why but the WAN connection went down
- DHCLIENT immediately starts looking for a new lease (i.e. reconnect) but times out (i.e. ISP still down)
- there is an attempt to reconnect to the "recorded lease" which is the original WAN IP address (this seems to fail)
- another DHCLIENT request goes out and gets a DHCPACK response comes back with what looks like a NEW WAN IP address
but... pfSense then seems to be trying to configure the interface with the OLD WAN IP address... not the NEW WAN IP address. This cycle then seems to repeat until I manually reboot the router. On reboot, it successfully connects to the WAN but using the OLD address.
Of course, I can upload the logs. Maybe I'm misreading but I don't understand why pfSense isn't picking up the new WAN IP address and wants to go back to the old. Stranger still is why is the connection via the old WAN IP successful upon reboot. Thoughts?
-
Correction: I misunderstood the format of the DHCPACK message... It seems the interface is being given the same IP from my ISP under a renewed lease.
Something further down the chain is then immediately disconnected and the process repeats. :(
-
Hmm, you might try adjusting the dhcp protocol timing options in the advanced DHCP config options. We have seen edge cases where a modems boot time hit's pfSense's still booting WAN and the client ignores it.
Steve
