I'm having a STANGE problem when our traffic shaper is turned on.
When I run a continuous ping to the pfsense internal IP (192.168.3.1)
from the inside network (ping -t 192.168.3.1) while doing a
speedtest.net test, here is what I see with our pings:
Pinging 192.168.3.1 with 32 bytes of data:
Reply from 192.168.3.1: bytes=32 time<1ms TTL=64
Reply from 192.168.3.1: bytes=32 time<1ms TTL=64
Reply from 192.168.3.1: bytes=32 time=78ms TTL=64 <- beginning of download test
Reply from 192.168.3.1: bytes=32 time=163ms TTL=64
Reply from 192.168.3.1: bytes=32 time<1ms TTL=64
Reply from 192.168.3.1: bytes=32 time=58ms TTL=64
Reply from 192.168.3.1: bytes=32 time=152ms TTL=64
Reply from 192.168.3.1: bytes=32 time=247ms TTL=64
Reply from 192.168.3.1: bytes=32 time=340ms TTL=64
Reply from 192.168.3.1: bytes=32 time=435ms TTL=64
Reply from 192.168.3.1: bytes=32 time=523ms TTL=64
Reply from 192.168.3.1: bytes=32 time=622ms TTL=64
Reply from 192.168.3.1: bytes=32 time=711ms TTL=64
Reply from 192.168.3.1: bytes=32 time=750ms TTL=64
Reply from 192.168.3.1: bytes=32 time=731ms TTL=64
Reply from 192.168.3.1: bytes=32 time=735ms TTL=64
Reply from 192.168.3.1: bytes=32 time=745ms TTL=64
Reply from 192.168.3.1: bytes=32 time=589ms TTL=64 <- end of download test
Reply from 192.168.3.1: bytes=32 time<1ms TTL=64 <- beginning of upload test
Reply from 192.168.3.1: bytes=32 time<1ms TTL=64
Reply from 192.168.3.1: bytes=32 time<1ms TTL=64
Reply from 192.168.3.1: bytes=32 time<1ms TTL=64
Reply from 192.168.3.1: bytes=32 time<1ms TTL=64
Reply from 192.168.3.1: bytes=32 time<1ms TTL=64
Reply from 192.168.3.1: bytes=32 time<1ms TTL=64
Reply from 192.168.3.1: bytes=32 time<1ms TTL=64
Reply from 192.168.3.1: bytes=32 time<1ms TTL=64 <- end of upload test
Ping statistics for 192.168.3.1:
Packets: Sent = 31, Received = 31, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 750ms, Average = 222ms
Here is the image of our speedtest:
http://www.speedtest.net/result/469504995.png
1.3 Mb's down and 1.22 Mb's up
If I turn shaping OFF and run the same exact test, here are the results:
Pinging 192.168.3.1 with 32 bytes of data:
Reply from 192.168.3.1: bytes=32 time<1ms TTL=64
Reply from 192.168.3.1: bytes=32 time<1ms TTL=64
Reply from 192.168.3.1: bytes=32 time<1ms TTL=64 <- beginning of download test
Reply from 192.168.3.1: bytes=32 time<1ms TTL=64
Reply from 192.168.3.1: bytes=32 time<1ms TTL=64
Reply from 192.168.3.1: bytes=32 time<1ms TTL=64
Reply from 192.168.3.1: bytes=32 time<1ms TTL=64
Reply from 192.168.3.1: bytes=32 time<1ms TTL=64
Reply from 192.168.3.1: bytes=32 time<1ms TTL=64
Reply from 192.168.3.1: bytes=32 time<1ms TTL=64
Reply from 192.168.3.1: bytes=32 time<1ms TTL=64
Reply from 192.168.3.1: bytes=32 time<1ms TTL=64
Reply from 192.168.3.1: bytes=32 time<1ms TTL=64
Reply from 192.168.3.1: bytes=32 time<1ms TTL=64
Reply from 192.168.3.1: bytes=32 time<1ms TTL=64
Reply from 192.168.3.1: bytes=32 time<1ms TTL=64
Reply from 192.168.3.1: bytes=32 time<1ms TTL=64 <- end of download test
Reply from 192.168.3.1: bytes=32 time<1ms TTL=64 <- beginning of upload test
Reply from 192.168.3.1: bytes=32 time<1ms TTL=64
Reply from 192.168.3.1: bytes=32 time<1ms TTL=64
Reply from 192.168.3.1: bytes=32 time<1ms TTL=64
Reply from 192.168.3.1: bytes=32 time<1ms TTL=64
Reply from 192.168.3.1: bytes=32 time<1ms TTL=64
Reply from 192.168.3.1: bytes=32 time<1ms TTL=64
Reply from 192.168.3.1: bytes=32 time<1ms TTL=64
Reply from 192.168.3.1: bytes=32 time<1ms TTL=64
Reply from 192.168.3.1: bytes=32 time<1ms TTL=64
Reply from 192.168.3.1: bytes=32 time<1ms TTL=64
Reply from 192.168.3.1: bytes=32 time<1ms TTL=64
Reply from 192.168.3.1: bytes=32 time<1ms TTL=64 <- end of upload test
Ping statistics for 192.168.3.1:
Packets: Sent = 32, Received = 32, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Here is the image of our speedtest:
http://www.speedtest.net/result/469508581.png
1.38 Mb's down and 1.36 Mb's up
Somehow the shaping is introducing high latency into the download
portion of the test, but not the upload. When shaping is turned off,
the pfsense reacts normally to internal pings. Anyone have an idea of
what could be causing this?
Joe LaGreca
Founder & Owner, BIG Net Online
619-393-1733 x200 Office
619-318-3246 Cell
www.BIGnetOnline.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
Commercial support available - https://portal.pfsense.org
