OPNsense Forum

Archive => 17.7 Legacy Series => Topic started by: jmcc on October 21, 2017, 02:32:43 am

Title: Persistent apinger issues
Post by: jmcc on October 21, 2017, 02:32:43 am
Hello!
I have two pppoe connections, one set as a failover (tier 2, much slower than tier 1). Gateway monitoring interval is set to 10s on each gateway. I constantly get incorrect values for the gateway monitoring, which I've come to find out through reading on this forum - is through apinger. Attached is a typical result for the gateway monitoring value. If I ping directly, it's always a much different value. Monitoring is broken for both interfaces; both will read strange values at any given time. This leads to gateway switchovers quite frequently and a logfile filled with apinger alarms. After I restart it, the value seems to stay close to reality for a few minutes, then goes rogue again. Is there any way to fix this? I saw a post where someone had a cron job that restarted apinger every 60s, but I feel like there has to be a better way.
Title: Re: Persistent apinger issues
Post by: jmcc on October 23, 2017, 05:53:37 pm
More information and testing:
I saw some comments about ntpd being a source of some of these problems. I disabled that and there was no change in the issue. I also saw some comments about that being a source of problems with opnsense being installed in a VM. It's worth noting that my install is on actual hardware, not in a VM.

I read every possible thread and bit of information here on the forums and found that apinger was replaced with dpinger on pfsense. I switched out my SSD with another and installed pfsense on the same hardware. It seems to be fine and doesn't report weird values. It seems to consistently report the correct value over an approximate 18H timespan.

To be honest, I'd rather run opnsense than pfsense. Is there a relatively straightforward way to replace apinger with dpinger? I found this thread: https://forum.opnsense.org/index.php?topic=2072.0 (https://forum.opnsense.org/index.php?topic=2072.0) in which someone asked about it, but their problem was related to the VM install and that was where it ended. I noticed franco's comment that there is no current plan to replace apinger, but given the amount of problems with apinger, doesn't it seem like a worthwhile solution?
Title: Re: Persistent apinger issues
Post by: grandrivers on November 07, 2017, 01:11:08 am
apinger is terrible needs replaced !!
Title: Re: Persistent apinger issues
Post by: mimugmail on November 07, 2017, 05:18:55 am
I'd also see this replaced with dpinger, when you have more than one WAN with pppoe or dhcp there are really strange problems with apinger.
Title: Re: Persistent apinger issues
Post by: GOCE on December 06, 2017, 03:36:09 am
Add me to the list, apinger is really a pain. Please replace it with something that works.
Title: Re: Persistent apinger issues
Post by: franco on December 06, 2017, 06:45:08 am
Sure, who will contribute time and effort to do it?
Title: Re: Persistent apinger issues
Post by: marjohn56 on December 26, 2017, 08:07:04 pm
I'll start to take a look at it...
Title: Re: Persistent apinger issues
Post by: nivek1612 on December 26, 2017, 08:40:25 pm
Nice one Marjohn. Its causing me a few issues at the present as you know. Hoping the arrival of my new shinny qotom will remove them
Title: Re: Persistent apinger issues
Post by: mimugmail on December 26, 2017, 09:40:39 pm
Do you experience this with pppoe/dhcp?
Title: Re: Persistent apinger issues
Post by: nivek1612 on December 26, 2017, 10:07:02 pm
I'm using pppoe and keep getting huge latency on the monitored gateway for no apparent reason

Restarting apinger clears the issue