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

    BandwidthD Not showing correct version.

    Scheduled Pinned Locked Moved pfSense Packages
    3 Posts 2 Posters 1.1k 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.
    • R
      raidscsi
      last edited by

      As seen here. https://forum.pfsense.org/index.php?topic=78175  BandwidthD had a bug that was patched. And the experts in that thread said to use 2.0.1_6 which should be pushed to the packages page to install, but when I go to packages the _5 is the version and does not work.

      bandwidthd System BETA 2.0.1_5 pkg v.0.5 platform: 1.2.1

      My pfSense install is running this version.
      2.1.5-RELEASE (i386)
      built on Mon Aug 25 07:44:26 EDT 2014
      FreeBSD 8.3-RELEASE-p16

      You are on the latest version.

      1 Reply Last reply Reply Quote 0
      • R
        raidscsi
        last edited by

        Well, too late now, noob mistake.

        I am running 2.1.5 and the patched version is for 2.2.

        So which file should I use to update? What's the difference from BETA to DEVELOPMENT? Any reason not to move from 2.1.5 to a test version?

        https://snapshots.pfsense.org/FreeBSD_stable/10/i386/pfSense_HEAD/updates/?C=M;O=D

        1 Reply Last reply Reply Quote 0
        • C
          charliem
          last edited by

          pfSense 2.2 is a rather big change from 2.1, due to the change from FreeBSD 8.3 to 10.1.  This brings benefits of better hardware support.  2.2 has been fairly stable for me, but I don't use many packages or advanced features of pfSense.  If 2.1.5 is running and you're happy, stick with it.  If you have hardware not supported in 2.1.x, or you like to test and report issues as you find them, try out 2.2.

          Keep a copy of your 2.1.5 configuration as a backup in case you need to downgrade; you can update 2.1.x -> 2.2, but AFAIK you can't use a 2.2 config to go back to 2.1.x

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