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

    Upgrading 2.0.1

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    4 Posts 3 Posters 1.7k 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.
    • C Offline
      charlien
      last edited by

      I was running 2.0.1 and was having issues with traffic shaping rules. I was getting an error. Someone said it was fixed and I should use git to update it. Well I did and now have a non-working 2.0.2 RC. I'm willing to start over but don't want to end up with non working traffic shaping rules. Once I've done the base install of 2.0.1, how do I update it and not go to 2.0.2?

      1 Reply Last reply Reply Quote 0
      • stephenw10S Offline
        stephenw10 Netgate Administrator
        last edited by

        2.0.1 is the latest stable release.
        2.0.2 is imminent but has not yet been released, at all, even as a beta!
        You should not have been able to update to it. It seems to be a config carried over by upgrading to 2.0 final from an RC version.
        Did you do that? If so did you do this?
        2.1 snapshots are available: http://snapshots.pfsense.org/ but these are continuously in development so bugs may be introduced. YMMV!  ;)

        You can choose to update to snapshots or stable in System: Firmware: Settings using the drop down. If you don't check 'Allow auto-update firmware images with a missing or invalid digital signature to be used.' you won't get bad updates.

        Steve

        1 Reply Last reply Reply Quote 0
        • C Offline
          charlien
          last edited by

          I typed this in at normal shell: # pfSsh.php playback gitsync RELENG_2_0

          I thought it was only supposed to update the php code in the current release, which is 2.0.1.

          1 Reply Last reply Reply Quote 0
          • jimpJ Offline
            jimp Rebel Alliance Developer Netgate
            last edited by

            There were binary changes for 2.0.2 that are required to use it, it isn't just a source upgrade. If you gitsync to RELENG_2_0 it will most likely leave you with a broken system.

            You can gitsync back to RELENG_2_0_1 and get back to 2.0.1-RELEASE code.

            Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

            Need help fast? Netgate Global Support!

            Do not Chat/PM for help!

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