Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    High latency on downloads with shaping

    Scheduled Pinned Locked Moved Traffic Shaping
    2 Posts 2 Posters 3.3k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • L Offline
      lagreca
      last edited by

      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?

      1 Reply Last reply Reply Quote 0
      • J Offline
        jigpe
        last edited by

        Can you post your Firewall: Shaper: Queues please? thanks

        jigp
        Davao City

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.