sendto error: 65

newUser2pfSense

So this is really affecting me. Any idea how to do what is mentioned in this post?
https://redmine.pfsense.org/issues/9267

stephenw10

You would need to apply those patches, rebuild the binaries on an equivalent FreeBSD system and upload them to pfSense. A non-trivial task.

newUser2pfSense

Any ideas on what I can do in the mean time?

foreigner

@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

stephenw10

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

foreigner

This post is deleted!

foreigner

@stephenw10

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

foreigner

@foreigner

Good news

The issue was solved for me, it was due to a damaged ethernet cable

techvic

@stephenw10 I'm having the same issue on 2.5.2, is that still not fixed in pfsense itself?

stephenw10

This? https://redmine.pfsense.org/issues/9267
Yes, that's been in since 2.4.5.

Steve