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

    Speed decline

    Traffic Shaping
    5
    9
    7.5k
    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.
    • J
      j0sh
      last edited by

      I have pfsense installed on a celeron 533 w/256mb and a 4gb HD. I have a 1.5 up and 8.0 down connection. Plugged directly into the cable modem I get about 5.5 actual speed down. Plugged in through the pfsense box with default traffic shaping wizard rules my connection tops out at about 3.5 down. If I disable the traffic shaping I still only get about 4 down. The upload always gets a full 1.5. I have my speeds set to 1500 up and 8000 down. Is my hardware too slow? The network cards have been changed out. Any Idea why I lose so much bandwidth?

      1 Reply Last reply Reply Quote 0
      • S
        sullrich
        last edited by

        @j0sh:

        I have pfsense installed on a celeron 533 w/256mb and a 4gb HD. I have a 1.5 up and 8.0 down connection. Plugged directly into the cable modem I get about 5.5 actual speed down. Plugged in through the pfsense box with default traffic shaping wizard rules my connection tops out at about 3.5 down. If I disable the traffic shaping I still only get about 4 down. The upload always gets a full 1.5. I have my speeds set to 1500 up and 8000 down. Is my hardware too slow? The network cards have been changed out. Any Idea why I lose so much bandwidth?

        That should be plenty of juice to push 8 megabit.  a 266 megahertz wrap can push 28+ megabit.  You really need to tell us what nic types you have, etc.

        1 Reply Last reply Reply Quote 0
        • Z
          ZGamer
          last edited by

          @j0sh:

          I have a 1.5 up and 8.0 down connection.

          Damn, where'd ya get that pipe from?

          –------------------------------------------------------------------------------------
          pfSense Documentation Wiki
          Need Commercial Support?
          Personal Blog

          1 Reply Last reply Reply Quote 0
          • J
            j0sh
            last edited by

            It's an Adelphia business SB3 package.

            I think the problem is with this:
            Nov 15 20:04:02 kernel: calcru: negative runtime of -670163 usec for pid 279 (logger)
            Nov 15 20:04:02 kernel: calcru: negative runtime of -7500955 usec for pid 278 (tcpdump)
            Nov 15 20:04:02 kernel: calcru: negative runtime of -5475406 usec for pid 277 (pflogd)
            Nov 15 20:04:02 kernel: calcru: negative runtime of -4023938 usec for pid 223 (syslogd)
            Nov 15 20:04:02 kernel: calcru: negative runtime of -261 usec for pid 47 (nfsiod 1)
            Nov 15 20:04:02 kernel: calcru: negative runtime of -2050259 usec for pid 45 (syncer)
            Nov 15 20:04:03 kernel: calcru: negative runtime of -684085 usec for pid 44 (vnlru)
            Nov 15 20:04:02 kernel: calcru: runtime went backwards from 34125248 usec to 28366752 usec for pid 42 (pagezero)
            Nov 15 20:04:02 kernel: calcru: negative runtime of -684905 usec for pid 39 (pagedaemon)

            I get that stuff in my logs every few seconds….I tried lots of suggested fixes from google but nothing seems to work...

            1 Reply Last reply Reply Quote 0
            • S
              sullrich
              last edited by

              Yes, thats a sign that internal timekeeping is getting all fubar'd.

              Bios up to date?

              @j0sh:

              It's an Adelphia business SB3 package.

              I think the problem is with this:
              Nov 15 20:04:02 kernel: calcru: negative runtime of -670163 usec for pid 279 (logger)
              Nov 15 20:04:02 kernel: calcru: negative runtime of -7500955 usec for pid 278 (tcpdump)
              Nov 15 20:04:02 kernel: calcru: negative runtime of -5475406 usec for pid 277 (pflogd)
              Nov 15 20:04:02 kernel: calcru: negative runtime of -4023938 usec for pid 223 (syslogd)
              Nov 15 20:04:02 kernel: calcru: negative runtime of -261 usec for pid 47 (nfsiod 1)
              Nov 15 20:04:02 kernel: calcru: negative runtime of -2050259 usec for pid 45 (syncer)
              Nov 15 20:04:03 kernel: calcru: negative runtime of -684085 usec for pid 44 (vnlru)
              Nov 15 20:04:02 kernel: calcru: runtime went backwards from 34125248 usec to 28366752 usec for pid 42 (pagezero)
              Nov 15 20:04:02 kernel: calcru: negative runtime of -684905 usec for pid 39 (pagedaemon)

              I get that stuff in my logs every few seconds….I tried lots of suggested fixes from google but nothing seems to work...

              1 Reply Last reply Reply Quote 0
              • J
                j0sh
                last edited by

                BIOS is as up to date as it can be…It's a pretty old system. I just changed the CMOS battery and that didn't help either.

                1 Reply Last reply Reply Quote 0
                • B
                  billm
                  last edited by

                  @j0sh:

                  It's an Adelphia business SB3 package.

                  I think the problem is with this:
                  Nov 15 20:04:02 kernel: calcru: negative runtime of -670163 usec for pid 279 (logger)
                  Nov 15 20:04:02 kernel: calcru: negative runtime of -7500955 usec for pid 278 (tcpdump)
                  Nov 15 20:04:02 kernel: calcru: negative runtime of -5475406 usec for pid 277 (pflogd)
                  Nov 15 20:04:02 kernel: calcru: negative runtime of -4023938 usec for pid 223 (syslogd)
                  Nov 15 20:04:02 kernel: calcru: negative runtime of -261 usec for pid 47 (nfsiod 1)
                  Nov 15 20:04:02 kernel: calcru: negative runtime of -2050259 usec for pid 45 (syncer)
                  Nov 15 20:04:03 kernel: calcru: negative runtime of -684085 usec for pid 44 (vnlru)
                  Nov 15 20:04:02 kernel: calcru: runtime went backwards from 34125248 usec to 28366752 usec for pid 42 (pagezero)
                  Nov 15 20:04:02 kernel: calcru: negative runtime of -684905 usec for pid 39 (pagedaemon)

                  I get that stuff in my logs every few seconds….I tried lots of suggested fixes from google but nothing seems to work...

                  Not that this should affect the non-shaper results, but ouch, this will definitely mangle the shaper if the clock is that messed up.  The shaper needs an accurate clock or it'll give too much or too little bandwidth to traffic.

                  –Bill

                  pfSense core developer
                  blog - http://www.ucsecurity.com/
                  twitter - billmarquette

                  1 Reply Last reply Reply Quote 0
                  • T
                    thinair
                    last edited by

                    I also notice a fairly dramatic drop in throughput when I turn traffic shaping on.

                    When routing between two internal networks (LAN and DMZ) I get around 40-45Mb/s, when traffic shaping is on it's down to 3.5-3.6Mbps.  This is using NetCPS on either endpoint computer.  I have a 4.4Mb/s down and 0.8Mb/s up WAN link, so I just have kept traffic shaping off as well.

                    My hardware is a P3 500MHz Celeron, 128MB RAM, 256MB CF card, one 3com NIC.

                    Nelson Papel

                    1 Reply Last reply Reply Quote 0
                    • S
                      sullrich
                      last edited by

                      @thinair:

                      I also notice a fairly dramatic drop in throughput when I turn traffic shaping on.

                      When routing between two internal networks (LAN and DMZ) I get around 40-45Mb/s, when traffic shaping is on it's down to 3.5-3.6Mbps.  This is using NetCPS on either endpoint computer.  I have a 4.4Mb/s down and 0.8Mb/s up WAN link, so I just have kept traffic shaping off as well.

                      My hardware is a P3 500MHz Celeron, 128MB RAM, 256MB CF card, one 3com NIC.

                      There is a post in the forums that explains why this is the case.  It was written by Bill not even a few days ago.

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