Gateway Status - 26% Packet loss

tokiebonilla

Hi,

I'm a noob to PFSense and still getting my way to use the product, we have a setup here having 2 ISP for fail over. I have a Fiber and ADSL line setup.

My Fiber Connection is giving me a warning with a Packet loss of 26%, but how ever when I try to Ping a URL there's no packet loss whatsoever,

Ping Results

C:\Users\Abrahamb>ping -n 20 www.google.com

Pinging www.google.com [74.125.239.146] with 32 bytes of data:
Reply from 74.125.239.146: bytes=32 time=168ms TTL=54
Reply from 74.125.239.146: bytes=32 time=245ms TTL=54
Reply from 74.125.239.146: bytes=32 time=168ms TTL=54
Reply from 74.125.239.146: bytes=32 time=168ms TTL=54
Reply from 74.125.239.146: bytes=32 time=168ms TTL=54
Reply from 74.125.239.146: bytes=32 time=168ms TTL=54
Reply from 74.125.239.146: bytes=32 time=168ms TTL=54
Reply from 74.125.239.146: bytes=32 time=203ms TTL=54
Reply from 74.125.239.146: bytes=32 time=168ms TTL=54
Reply from 74.125.239.146: bytes=32 time=204ms TTL=54
Reply from 74.125.239.146: bytes=32 time=214ms TTL=54
Reply from 74.125.239.146: bytes=32 time=203ms TTL=54
Reply from 74.125.239.146: bytes=32 time=184ms TTL=54
Reply from 74.125.239.146: bytes=32 time=171ms TTL=54
Reply from 74.125.239.146: bytes=32 time=168ms TTL=54
Reply from 74.125.239.146: bytes=32 time=168ms TTL=54
Reply from 74.125.239.146: bytes=32 time=168ms TTL=54
Reply from 74.125.239.146: bytes=32 time=168ms TTL=54
Reply from 74.125.239.146: bytes=32 time=180ms TTL=54
Reply from 74.125.239.146: bytes=32 time=169ms TTL=54

Ping statistics for 74.125.239.146:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 168ms, Maximum = 245ms, Average = 181ms

C:\Users\Abrahamb>

KOM

Pfft. You don't get to play with the big boys until your apinger packet loss is >100%.

This is a known issue that only affects some users. Restarting apinger seems to clear it, if I remember.

tokiebonilla

@KOM:

Pfft. You don't get to play with the big boys until your apinger packet loss is >100%.

This is a known issue that only affects some users. Restarting apinger seems to clear it, if I remember.

Thank you, That helps.