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

    Fix old SNMP bindlan setting - Redmine #3883

    Scheduled Pinned Locked Moved 2.2.5 Snapshot Feedback and Issues
    3 Posts 3 Posters 2.4k 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.
    • P
      phil.davis
      last edited by

      A fix for this for RELENG_2_2 is in PR https://github.com/pfsense/pfsense/pull/2000 - has been there a few days. Maybe it has missed the boat for 2.2.5.

      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
      • D
        David_W
        last edited by

        It looks like the decision has been taken to prepare 2.2.5 for release in the next couple of days: https://github.com/pfsense/pfsense/commit/b31b713d683ecda6940fdba1bd0c4717bcdc0f21 (though there have been some subsequent commits to pfsense and pfsense-tools).

        As we both know, Phil, it's impossible to fix every bug. There are so many worthwhile improvements in 2.2.5 as it stands that it's worth releasing. I guess, too, that the pfSense team want to shift their focus onto accelerating the release of 2.3.-

        cmb / anyone - is the plan that 2.2.5 is the last 2.2 release unless a serious security issue or erratum arises before 2.3 is ready to release? It would be useful to know, as there is little point submitting further pull requests against RELENG_2_2 once 2.2.5 has released if there is no intention to make any further 2.2 releases.

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

          @David_W:

          cmb / anyone - is the plan that 2.2.5 is the last 2.2 release unless a serious security issue or erratum arises before 2.3 is ready to release? It would be useful to know, as there is little point submitting further pull requests against RELENG_2_2 once 2.2.5 has released if there is no intention to make any further 2.2 releases.

          That is the plan, though for small but beneficial things we may still accept a PR or put a fix on RELENG_2_2, so long as it's not a binary change someone could use gitsync to pull in things fixed post-2.2.5 even if we don't roll an official release.

          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.