dpinger error codes

cybis

Hi,

I'm looking for a documention of the dpinger error codes. Unforunately not all error codes are listed at https://docs.netgate.com/pfsense/en/latest/troubleshooting/gateway-errors.html

For example, what's the meaning of error code 50?

dpinger 	9302 	WAN_DHCP xxx.xxx.xxx.xxx: sendto error: 50

BR

cmcdonald

@cybis sendto error 50 usually indicates that the interface is down. Are you sure the interface is up?

cybis

@cmcdonald Thanks a lot for your input.

I have a site-to-site OpenVPN connection between siteA (server with WAN IP xxx.xxx.xxx.xxx) and siteB (client with WAN IP yyy.yyy.yyy.yyy) on the tunnel network ccc.ccc.ccc.0 which drops and re-establishes at least once every one to two weeks unfortunately. I have a lot of those dpinger error messages when this happens.

Sometimes the WAN interface seems to get a link-local address temporarily, i.e. the interface seems to go down and up again (on 2021-07-21 at 14:20:14 for example). However, this is not always the case. The last time my VPN connection was "renewed" was on 2021-07-22 09:20:15 where only siteB reported a lot of dpinger errors without any interface messages at neither of the sites.

Here are the gateway and OpenVPN logs for both sites:
gateways_siteA.txt
openvpn_siteA.txt
gateways_siteB.txt
openvpn_siteB.txt

I'm not sure how to further debug this issue. I was hoping to get more insight with a proper dpinger error code documentation as I'm not sure whether this is an ISP issue (both sites have the same ISP), a pfsense configuration issue or even a firewall hardware issue (both sites have the same type/model of a Protectli box).

Derelict

@cybis It's not a dpinger error code. It's a standard error code.

This lists the ones people typically encounter:

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

Error 50 isn't included there so:

https://www.freebsd.org/cgi/man.cgi?query=errno&apropos=0&sektion=2&manpath=FreeBSD+12.2-stable&arch=default&format=html

50 ENETDOWN Network is down. A socket operation encountered a dead network.

You can look at the system log, etc and look for link down messages, etc. Or examine the network while the problem is occurring.

cybis

@derelict Thanks for the clarification an the FreeBSD link.