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

    Pfsense 2.1 February 17th version. Should I update it??

    Scheduled Pinned Locked Moved 2.1 Snapshot Feedback and Problems - RETIRED
    4 Posts 3 Posters 1.9k 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.
    • G
      greenpoise
      last edited by

      So, after a few months of learning pfsense/playing around/configuring it, I was able to run it under a production environment. I have been so tempted to upgrade but I am afraid to break it and I cant afford any downtime. What have you guys experiences been like? any out there running 2.1 in production? any reasons why should I upgrade to the latest? share your thoughts and input here. I am curious to know what has worked the best for you guys.

      thanks

      1 Reply Last reply Reply Quote 0
      • P
        phil.davis
        last edited by

        I have OpenVPN, gateway groups, various policy routing rules, dynamic DNS, a bunch of DNS forwarder hosts and overrides, DHCP with static mappings, multi-LAN, multi-WAN, wireless, running March 25 or later on small production systems and its fine. It has only got better in the last few months for all my stuff.
        But no Ipsec, no IPv6, no CARP, no bridging, no PPPoE connects - so I can't give an opinion if you are using those.

        As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
        If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

        1 Reply Last reply Reply Quote 0
        • N
          Nachtfalke
          last edited by

          In general nothing should be lost after an upgrade. But as long as pfsense 2.1 is beta/RC and not stable there could be always things which could break your system.

          If you are running it in production then I would suggest that you should NOT upgrade until you see any problems or errors.
          If you have the possiility to configure a second system then you could upgrade and if you see problems then switch back to your "old" system.

          1 Reply Last reply Reply Quote 0
          • G
            greenpoise
            last edited by

            @phil.davis:

            I have OpenVPN, gateway groups, various policy routing rules, dynamic DNS, a bunch of DNS forwarder hosts and overrides, DHCP with static mappings, multi-LAN, multi-WAN, wireless, running March 25 or later on small production systems and its fine. It has only got better in the last few months for all my stuff.
            But no Ipsec, no IPv6, no CARP, no bridging, no PPPoE connects - so I can't give an opinion if you are using those.

            Mine is a simpler setup. I was looking at the changes between Feb and March and I dont think my setup is being affected so I might stick around with what I have..just for now..Thanks for sharing.

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