An earnest appeal - please do fix APINGER in 2.2

[eri--]

I pushed a fix.

Please try with next snapshots and see if you still get the same issues.

[applerule]

@ermal:

I pushed a fix.

Please try with next snapshots and see if you still get the same issues.

Still broken for me. :(  See attachment.  Let me know if there is anything else I can provide.

[eman_resu]

Any update on the matter ?

My box just went dark after apinger decided that the wan is not up and then remained stuck with a cpu load of 99% denying to be restarted.

[Roots0]

APINGER does't cope well with my WAN flapping whenever this happens my HENET ipv6 gateway starts reporting loss forever even though the ipv6 tunnel is backup and stable!

[grandrivers]

why wouldn't adding some other methods of detection be a good idea had a xincom (same as syswan) that did 3 different means of detection (imcp ping, http heartbeat, traffic flow, DPD
(RFC3706) ) years ago the was like a $250 router which was nice cause my isp use to block imcp

[eman_resu]

@naras:

+1
This is a quite annoying issue.

and the outcome in my case is a nonfunctional apinger with miles of logentries like: apinger: No usable targets found, exiting

[applerule]

I'm having better luck with the 9/15 build.  I am not sure if something changed between 9/13 and 9/15 that would have affected apinger, but the status seems to be working better.  Still not 100% correct though.  Before, the connection would show insanely high RTT in the console; now, that isn't the case.  However, when I look at the logs I am getting a lot of apinger "down" log messages.

[applerule]

@applerule:

I'm having better luck with the 9/15 build.

Nevermind.  I've been checking it off and on and haven't seen it go "Latency" or "Offline" today.  It finally did.  Typical stuck at really high RTT and jumps between latency and offline.  I got too excited considering it hadn't gotten "stuck" for nearly a day.  :(

[naras]

Still no luck with Sep 14 09:09:38 CDT 2014 build, two pppoe links are online before my isp resets my connections, after the reset, default gw gets online normally, but the opt1 gets stuck although the link reconnected successfully.

And the OPT1 gets online again after I restart apinger.

[eri--]

Ok can you please try next snapshots.
I put a fix for recovering from down state.

[applerule]

It definitely appears to recover better now than it ever did before.  As you can tell from times on screenshots below, I did successfuly recover from a "down" state.  You do occasionally catch it in a down state in the GUI when it isn't really down.  Also, still getting the APINGER down log messages, but I assume that is normal?

[eri--]

Does your interface flap a lot or what is the reason you get all those down events?

Just to understand that you say it marks down occasionally.

[applerule]

I'm pretty confident those are false down notifications.  I use nagios/centreon to monitor the same gateway host, and it never sends me a down alert.  Of course maybe one packet dropped from pfSense but it didn't from my monitoring system, but even if it did I wouldn't expect it to take that long to recover.

In the screenshot I posted where it was down, I was able to ping the monitoring IP from the console successfully while it was showing the gateway down.

Just to give you a better idea of my setup, I am using the following:

Gateway IP is google DNS (8.8.8.8) - I know some suggest using first hop…don't know if that is contributing but I wouldn't think so.
I am also a hyper-v user (Server 08 R2).  I've been building my own kernels for 2.1, but I am just using stock release since I've been running 2.2 alpha snapshots.

Since I am using a non-traditional setup, perhaps it would be better to see if someone else is also having the problems I am before digging much deeper into it.

[mgiammarco]

I do not understand how to try the new apinger.
Do I need to update to pfsense 2.2 beta? Can I just install the apinger package?
Can you provide a short explanation for me?

Thanks,
Mario

[eri--]

Just upgrade to latest snapshots from the system->Firmware.

[mgiammarco]

Just got "image file is corrupt error" :-(

[naras]

Just Successfully recovered from ISP reset on bulid Sep 19 23:21:59 CDT 2014, all online now, will keep an eye on …

Someone may  want to know this.

[naras]

And the Sep 23‘s new build don't work well for me, rebooted twice, and opt1 is always at offline status until apinger  being restarted manually.

[eri--]

What kind of interface is OPT1?
Can you share some more details from your system log in what happened with this interface?

[naras]

WAN and  OPT1 are both pppoe from same ISP.

The last two logs are created after apinger was restarted manually.