Apinger only working on wan 8/6/13 64bit snapshot
-
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.
-
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 -
I have 2 pfsense with this.
1. pfsense:
2.1-RC1 (amd64)
built on Thu Aug 8 14:25:22 EDT 2013
FreeBSD 8.3-RELEASE-p9
1 WAN (0.4ms) (always green). The apinger shows 0ms which is wrong since update (pfsense1_WAN.png).
2 OpenVPN Server (23ms + 16ms) which have growing latencies. The corresponding clients at the other sides are green.2. pfsense:
2.1-RC1 (amd64)
built on Wed Aug 7 20:59:21 EDT 2013
FreeBSD 8.3-RELEASE-p9
2 WANs: static WAN (1.4ms) + DSL (22ms). The DSL has growing latency. WAN shows less latency (pfsense2_WAN.png).
2 OpenVPN Server. Both have growing latency.
1 OpenVPN Client which has growing latency, too.
-
Those snapshots are known to have apinger issues, upgrade to a current snapshot.
-
I forgot to write:
The LAN shows strange values, too. -
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
FVIt 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.
-
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. -
The lack of failover working seems to be this:
http://redmine.pfsense.org/issues/3146 -
2.1-RC1 (i386)
built on Wed Aug 14 14:47:24 EDT 2013
FreeBSD 8.3-RELEASE-p9Looking 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.
-
After updating to the latest release
2.1-RC1 (amd64)
built on Thu Aug 15 03:12:29 EDT 2013
FreeBSD 8.3-RELEASE-p9the fast interfaces still shows 0ms instead of 0.400 on dashboard and RRD.
-
Hi
To ggzengel: have you "Disable Gateway Monitoring"?
-
After updating to the latest release
2.1-RC1 (amd64)
built on Thu Aug 15 03:12:29 EDT 2013
FreeBSD 8.3-RELEASE-p9the 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. -
It's not exactly 0ms and it goes up on some interfaces.
-
2.1-RC1 (i386)
built on Thu Aug 15 16:30:19 EDT 2013
FreeBSD 8.3-RELEASE-p92 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.
-
The lack of failover working seems to be this:
http://redmine.pfsense.org/issues/31462.1-RC1 (amd64)
built on Thu Aug 15 16:30:12 EDT 2013
FreeBSD 8.3-RELEASE-p9Failover (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. -
It's not related. Keep it out of this thread.
-
After updating to the latest release
2.1-RC1 (amd64)
built on Thu Aug 15 03:12:29 EDT 2013
FreeBSD 8.3-RELEASE-p9the 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 2013Up-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).
-
Still showing 0ms everywhere with the Aug 17 snapshot…
-
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.
-
on latest sbapshot
2.1-RC1 (amd64)
built on Sun Aug 18 19:11:51 EDT 2013
FreeBSD 8.3-RELEASE-p9my ipv6 tunnel is wrong 0.3 ms instead of 70 ish it normally is
was fine on the 16th snapshot
