Apinger only working on wan 8/6/13 64bit 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?

doktornotor

@athurdent:

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

Hmmm, indeed… same here. No wonder it shows insane figures, LOL.

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

jimp

This should be fixed in the next snapshot (later tonight)

doktornotor

Thanks, will test ASAP. :)

kejianshi

Oh - That will make lots of people happy maybe. :)

NOYB

lo0 interface numbers are faster. Can you please change it back?

Appearances are everything.

doktornotor

@jimp:

This should be fixed in the next snapshot (later tonight)

Fixed in Aug 26 16:51:36 EDT 2013

kejianshi

So, is your internet nice and laggy again? haha

doktornotor

@kejianshi:

So, is your internet nice and laggy again? haha

Ah yeah, about 3ms slower than localhost. I guess I'll switch back to the buggy one. :D ;D