Apinger only working on wan 8/6/13 64bit snapshot

jimp

@jimp:

I pulled up another VM that has a better multi-WAN config and it was still OK there.

Though when I was experiencing problems before the latest round of fixes, it was worse with high-latency gateways, so it's possible that the issue is compounded by the actual latency there. To reproduce it you may have to artificially induce the same level of latency.

Did you try to test failover?
As I state on this thread http://forum.pfsense.org/index.php/topic,65455.0.html, on RC1-20130812 failover does not work anymore (in my case).
Thanks
FV

It does appear as though the filter reload at the end of the apinger event isn't doing what it should there. I'll need to run some more tests to narrow it down though.

ggzengel

I updated pfsense1.
While the first minutes a didn't see growing latencies.
But WAN still has 0ms in RRD and is less than real 0.4ms.

jimp

The lack of failover working seems to be this:
http://redmine.pfsense.org/issues/3146

phil.davis

2.1-RC1 (i386)
built on Wed Aug 14 14:47:24 EDT 2013
FreeBSD 8.3-RELEASE-p9

Looking good so far. Someone was downloading on our 1Mbps link speed for an hour or so. Latency went up to around 930ms. When the download finished the latency dropped back to under 200ms. The backup link latency is hovering around 300ms. During all this time there was no "panic" from apinger, check_reload_status or anything else to failover links.

At another site, latency on one link is changing in a range from 400 to 1100ms (people working it hard) and another 120ms (less used). apinger is coping fine.

ggzengel

After updating to the latest release
2.1-RC1 (amd64)
built on Thu Aug 15 03:12:29 EDT 2013
FreeBSD 8.3-RELEASE-p9

the fast interfaces still shows 0ms instead of 0.400 on dashboard and RRD.

Raul Ramos

Hi

To ggzengel: have you "Disable Gateway Monitoring"?

mastahfr

@ggzengel:

After updating to the latest release
2.1-RC1 (amd64)
built on Thu Aug 15 03:12:29 EDT 2013
FreeBSD 8.3-RELEASE-p9

the fast interfaces still shows 0ms instead of 0.400 on dashboard and RRD.

Same here, 2 of my 3 gateways show 0ms but they should show respectivly arround 14ms and 1ms.
My main gateway (Wan) is showing 1ms, which is correct.

ggzengel

It's not exactly 0ms and it goes up on some interfaces.

1.png_thumb

2.png_thumb

3.png_thumb

4.png_thumb

5.png_thumb

6.png_thumb

phil.davis

2.1-RC1 (i386)
built on Thu Aug 15 16:30:19 EDT 2013
FreeBSD 8.3-RELEASE-p9

2 multi-WAN systems are on this snap now. Gateway status is reporting reasonable latency numbers, and RRD quality numbers also look OK. I only have IPv4 and 2 gateways on each, so I can't speak for IPv6 or more complex systems with more gateways.

vielfede

@jimp:

The lack of failover working seems to be this:
http://redmine.pfsense.org/issues/3146

2.1-RC1 (amd64)
built on Thu Aug 15 16:30:12 EDT 2013
FreeBSD 8.3-RELEASE-p9

Failover (internet) is working again!

Unfortunately squid proxy failover (http://forum.pfsense.org/index.php/topic,60977.0.html) does not.
Maybe this is off topic (it's not due to apinger issues) but I cant find any help to get it works on 2.1.

jimp

It's not related. Keep it out of this thread.

NOYB

@ggzengel:

After updating to the latest release
2.1-RC1 (amd64)
built on Thu Aug 15 03:12:29 EDT 2013
FreeBSD 8.3-RELEASE-p9

the fast interfaces still shows 0ms instead of 0.400 on dashboard and RRD.

Same here. But on today's snapshot.
2.1-RC1 (i386)
built on Fri Aug 16 16:28:22 EDT 2013

Up-until now it had been working okay.
It works with a manually entered alternate monitoring address. But not with the interfaces' gateway. The WAN interface is working okay. But the optional interface is reporting 0ms. Reality is about 0.35ms.

Both interfaces are VLAN's on the same physical interface (bfe0).

doktornotor

Still showing 0ms everywhere with the Aug 17 snapshot…

jimp

After Ermal's last changes it should have been back to normal there, it was on my test VM. I was seeing 0.3-0.8ms reported. I rebuilt apinger again on the snapshot builders to see if maybe I missed rebuilding it one of them yesterday. Try it again later tonight/tomorrow when the next snap shows up.

grandrivers

on latest sbapshot
2.1-RC1 (amd64)
built on Sun Aug 18 19:11:51 EDT 2013
FreeBSD 8.3-RELEASE-p9

my ipv6 tunnel is wrong 0.3 ms instead of 70 ish it normally is

was fine on the 16th snapshot

doktornotor

Yeah the thing seems to invent completely random figures between 0-1ms. Haven't seen any sane reality-matching value since the major rewrites started.

athurdent

@grandrivers:

on latest sbapshot
2.1-RC1 (amd64)
built on Sun Aug 18 19:11:51 EDT 2013
FreeBSD 8.3-RELEASE-p9

my ipv6 tunnel is wrong 0.3 ms instead of 70 ish it normally is

was fine on the 16th snapshot

Just upgraded to
2.1-RC1 (i386)
built on Thu Aug 22 23:23:02 EDT 2013
FreeBSD 8.3-RELEASE-p10

from Aug 1 snapshot.

My IPv6 tunnel now shows 0.2ms instead of the usual 12-14ms.

kejianshi

Sounds like whatever is being pinged, it ain’t your gateway…

athurdent

@kejianshi:

Sounds like whatever is being pinged, it ain’t your gateway…

Nice catch, you're right. It should ping out on gif0 but it's just pinging itself on lo0:

tcpdump -nvvi lo0 icmp6
tcpdump: listening on lo0, link-type NULL (BSD loopback), capture size 96 bytes
09:14:14.703602 IP6 (hlim 64, next-header ICMPv6 (58) payload length: 24) 2001:4dd0:xxxx:xxxx::2 > 2001:4dd0:xxxx:xxxx::2: [icmp6 sum ok] ICMP6, echo request, length 24, seq 26906
09:14:14.703847 IP6 (hlim 64, next-header ICMPv6 (58) payload length: 24) 2001:4dd0:xxxx:xxxx::2 > 2001:4dd0:xxxx:xxxx::2: [icmp6 sum ok] ICMP6, echo reply, length 24, seq 26906

According to the config it should not:

target "2001:4dd0:xxxx:xxxx::1" {
        description "WAN_SixXS"
        srcip "2001:4dd0:xxxx:xxxx::2"
        alarms override "loss","delay","down";
        rrd file "/var/db/rrd/WAN_SixXS-quality.rrd"
}

kejianshi

I'd say your follow-up was nicer than my guess - glad it panned out.
Well - That makes perfect sense now. :D
I'd guess knowing that makes it easier for a dev to fix?