"sendto error: 65" after 2.5.0

chudak

I see

Feb 24 02:41:10	dpinger	24661	WAN_DHCP XYX: Clear latency 8097us stddev 36481us loss 5%
Feb 24 02:40:10	dpinger	24661	WAN_DHCP XYZ: sendto error: 65

after upgrading to 2.5.0 and not sure if I should worry or this is something that be addressed soon?

Thx

SteveITS

https://docs.netgate.com/pfsense/en/latest/troubleshooting/gateway-errors.html

"sendto error: 65

65 EHOSTUNREACH
No route to host.
A socket operation was attempted to an unreachable host.

Either there is no possible route to the target locally, or status information was received from an upstream router that indicated the same condition elsewhere along the path to the target."

Is the 5% packet loss consistent? That's presumably the cause of the failed connection.

chudak

@teamits said in "sendto error: 65" after 2.5.0:

https://docs.netgate.com/pfsense/en/latest/troubleshooting/gateway-errors.html

I get daily emails and see "packet loss" once in a while, nothing to worry about, not too often

"sendto error: 65" started seeing after 2.5.0 upgrade.

That IP ping-able and seems fine. How do I troubleshoot it ?

Checked with my ISP and they confirmed that I have no issues , so 2.5.0 thingy maybe ?

chudak

can this be related to https://forum.netgate.com/topic/161391/arpresolve-can-t-allocate-llinfo-for-gw_ip-on-igb0 ?!

genuine

Try to change the gateway monitoring ip to a dns of your isp see if thats better or take a public one example 4.2.2.1

chudak

@genuine said in "sendto error: 65" after 2.5.0:

Try to change the gateway monitoring ip to a dns of your isp see if thats better or take a public one example 4.2.2.1

I added my gw monitoring ip to Rejected Leases =>

And that error was gone.

Trying to understand which is a better solution?

Thx for the reply