Gateway packet loss % incorrect

eri--

Math can be weird at times :).
It will recover itself after some successful pings and the same issue has been there since 2.0.x when apinger got introduced just not so visible due to apinger getting killed and restarted and now only reloading the config.

It will be correctly fixed for 2.1.x+ to avoid these oddities.
Its just math issue not more from the value point of view.

Is it triggering any alarms due to this?

smanders

This can't be good… ::) Anybody figure anything out on this one?

pfsense-gw.jpg_thumb

johnpoz

And what version are you running - the same as the OP?

2.1-RC2 (amd64)
built on Thu Sep 5 21:38:32 EDT 2013

Or the current build?

smanders

@johnpoz:

And what version are you running - the same as the OP?

2.1-RC2 (amd64)
built on Thu Sep 5 21:38:32 EDT 2013

Or the current build?

2.1-RELEASE (i386)
built on Wed Sep 11 18:16:50 EDT 2013
FreeBSD 8.3-RELEASE-p11

bullet92

i've got the same issue.

Version:
2.1-RELEASE (amd64)
built on Wed Sep 11 18:17:48 EDT 2013
FreeBSD 8.3-RELEASE-p11

to fix i restart the apinger services, but it isn't a permanent fix, after some hour the issue come back.

coolspot

Looks like I may have the same issue on 2.1.1; pinging from the command line I get no packet loss, but apinger/pfSense reports 2% packet loss or higher!

Harvy66

Are you pinging the same device as apinger? I regularly get packet-loss to my ISP's gateway because it has an ICMP limit. It doesn't actually reflect my connection's packet-loss.

soulrat

I have the same behavior in pfSense 2.1.3, after restart the apinger service everything is fine.
But it is not a permanent solution for me that i have to restart the apinger service serval times a month … :-(

Currently, there are no permanent solution?

3zzz

Seeing the same in pfSense 2.1.4 - packet loss was showing 179% and restarting the apinger service cleared it up

sahuagin

Just experienced a similar problem. Gateways had failed to OPT1 from WAN, WAN showing 36% packet loss. RRD showed packet loss happening for proceeding 7 hrs. Console checking showed no packet loss. Reset of apinger reset gateway monitor, failover, and rrd graphs from that point forward. Both WAN and WAN_Ipv6 showed same results. NOTE: Comcast buried the cable at least 8 hrs earlier. It's possible that there was an interruption at some point, but I can't reproduce it.

2.1.4-RELEASE(amd64) nanobsd(4g) running on AMD G-T40E.

bennyc

I encountered consistent massive 308% packet loss on WAN gateway. Restarted cable modem first, re-plugged all cables in chain, just to be sure, but no avail. pfSense reboot cured it…
Stumbled upon this thread afterwards... :( So for the statistics I'm adding to this thread, who knows it helps.
Next time I'll try to restart the apinger service seperately.

2.1.4-RELEASE(amd64) running on APU1C

KOM

There's a "Four Yorkshiremen" sketch in here somewhere…

"308% packet loss?? LUXURY!! Our router was a wet paper bag in the middle of the road! We had to get up two hours before we went to bed, craft the packets by hand, send them uphill both ways..."

bennyc

@KOM:

"308% packet loss?? LUXURY!!

I must admit I'm spoiled with my ISP for a home gateway… 160/8 isn't that bad ;D But shhh... don't tell them ;)