sendto error: 65
-
It just hit me to ask. Since this issue affects the user base of pfSense, have the pfSense developers thought of releasing a fix at least just for this issue before the next version of pfSense is released? This would at least alleviate a lot of restart frustration. Just wondering.
-
In System > Update, would anyone happen to know if the fix for the dhclient is in the "Latest 2.4.x development version (2.4.5)", Latest Base System 2.4.5.a.20101222.1312? I would be willing to install just to fix the issue.
When I login to the terminal, would anyone know what the release/renew command is so I don't have to keep restarting?
Thanks.
-
It doesn't look like it made 11 stable so not in 2.4.5 either:
https://github.com/pfsense/FreeBSD-src/commits/RELENG_2_4_5/sbin/dhclient/dhclient.cSteve
-
So this is really affecting me. Any idea how to do what is mentioned in this post?
https://redmine.pfsense.org/issues/9267 -
You would need to apply those patches, rebuild the binaries on an equivalent FreeBSD system and upload them to pfSense. A non-trivial task.
-
Any ideas on what I can do in the mean time?
-
@newuser2pfsense said in sendto error: 65:
https://forum.netgate.com/topic/96923/pfsense-not-recovering-from-wan-failure
I am having the same issue using 2.5.1-RELEASE
After around 8 hrs of use, I cannot reach internet, neither pfsense through LAN interface
This is happening since I installed the latest version of pfsense
On Status/System Logs/System/Gateways I see this error:
WAN_DHCP 8.8.8.8: Alarm latency 3143us stddev 155us loss 21%I don't see any additional info in the logs that can help
I am using suricata, I wouldn't want to disable it, but I will try to disable service by service to try to find the guilty
Thanks
-
You are seeing the DHCP client timeout and stop requesting a lease?
As shown in the now resolved bug: https://redmine.pfsense.org/issues/9267 ?
If not then you're seeing something different and replying on this thread is just confusing.
Steve
-
This post is deleted! -
Hi
My pfsense is presenting the same sympthons as the others: the "sendto error: 65" error, but as someone pointed out, it is just dpinger showing there is not connectivity
I was using DHCP for WAN. Looking for a workaround I set up a static IP on WAN, and I set up my modem to use another range of IPs, where my WAN IP is not part of. I did that because someone commented that maybe it was due to a DHCP lease problem
But unfurtanately the issue continues happening
One question, those patches that you mentioned, were not already implemented somehow in 2.5.1-RELEASE?
Maybe if I install pfsense in another appliance will solve it
Thanks guys
-
-
@stephenw10 I'm having the same issue on 2.5.2, is that still not fixed in pfsense itself?
-
This? https://redmine.pfsense.org/issues/9267
Yes, that's been in since 2.4.5.Steve
