Sento Error 64
-
My friend's new install of pfSense so far had experienced two nights around 9.25pm a scenario where WAN still has an IP but is offline and the log is sento error 64. The doc says:
sendto error: 64
64 EHOSTDOWN
Host is down.
A socket operation failed because the destination host was down.In this case, the firewall is unable to reach the a target host directly connected at layer 2 (No ARP response), or it received a similar error response from an upstream source. Generally this only happens due to remote problems, indicating that the target is actually down or the L1/L2 link to the target is down.
Is there anything we could do at L1/L2 level on our end to prevent this? A reboot restores WAN. My friend is not pfSense savvy and will find this annoying for his wife. So, I am wondering whether a DHCP time increase could resolve
-
Like it says that means there's something not responding to ARP. Does the gateway IP disappear from the ARP table when that happens?
A DHCP lease time decrease is more likely to resolve it I would think. Though it could be something more basic like something upstream losing link. If you disconnect/reconnect the WAN does it start working again?Steve
-
@stephenw10 I see if it does it again tonight and if it does, I'll check the ARP table and disconnect/reconnect. Some say disable monitoring or auto negotiate or manual MTU, but auto negotiate (speed and duplex) and MTu are already default.
-
Well, late yesterday up till 19 minutes and 44 sec pass midnight, we were getting lots of sent to error 65 and some latency alarm; so, this morning spoke with ISP and it was their fault doing some update. We have fiber and no modem. It appears all is good.
