An earnest appeal - please do fix APINGER in 2.2

naras

I understand why you are confused…

I use traceroute to monitor the wanted IP upstream to decide if the GW is down.

I use traceroute to locate the IP to monitor and then use the built in GW monitor tool in PFSense.

Works fine here.

OK, I did that several months ago, and with no use.
The next hop routers are always outside my wan subnet:(

Thanks anyway.

dennypage

I've been running into quite a few problems with apinger in the 2.1 series with a simple single wan configuration.

https://redmine.pfsense.org/issues/3692

I was thinking that I would try to debug it and went looking for the source code to apinger but wasn't able to find it in the 2.1.5 main or packages. Can someone send me a pointer to it?

Thanks

bmeeks

@dennypage:

I've been running into quite a few problems with apinger in the 2.1 series with a simple single wan configuration.

https://redmine.pfsense.org/issues/3692

I was thinking that I would try to debug it and went looking for the source code to apinger but wasn't able to find it in the 2.1.5 main or packages. Can someone send me a pointer to it?

Thanks

The source code is in the pfsense-tools repo. You must complete a couple of electronic documents in order to access it. Access is controlled via SSH public keys. It is based off the FreeBSD port here: http://www.freshports.org/net/apinger/

Information on what is required to get access is posted in a Sticky Thread at the top of the Development sub-forum here: https://forum.pfsense.org/index.php?topic=76132.0.

Bill

dennypage

@bmeeks:

The source code is in the pfsense-tools repo. You must complete a couple of electronic documents in order to access it. Access is controlled via SSH public keys. It is based off the FreeBSD port here: http://www.freshports.org/net/apinger/

Information on what is required to get access is posted in a Sticky Thread at the top of the Development sub-forum here: https://forum.pfsense.org/index.php?topic=76132.0.

Thanks. I downloaded what I thought was the packages distribution from

https://github.com/pfsense/pfsense-packages/releases/tag/RELENG_2_1_5

but apinger wasn't in there. Is there a different repo?

heper

the packages repo is only for optional addons. (stuff that is not included in a base-install from CD)

i believe bmeeks said in which repo you can find apinger, and how to access it

bmeeks

@heper:

the packages repo is only for optional addons. (stuff that is not included in a base-install from CD)

i believe bmeeks said in which repo you can find apinger, and how to access it

Correct. It's in the pfsense-tools repo which is NOT hosted on Github directly. It's hosted on a server operated by the pfSense team and you must follow the instructions in the link I posted above to gain access to the repo.

Bill

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.

Capture.PNG_thumb

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.

Capture.PNG_thumb

Capture1.PNG_thumb

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. :(

Capture.PNG_thumb

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.

pppoe_offline.PNG_thumb

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?

Capture.PNG_thumb

Capture1.PNG_thumb

Capture2.PNG_thumb

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