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

    FreeBSD bug #222126 "pf is not clearing expired states" - could this be affecting SG-3100?

    Scheduled Pinned Locked Moved Official Netgate® Hardware
    4 Posts 2 Posters 498 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.
    • luckman212L
      luckman212 LAYER 8
      last edited by

      see: bug #222126 - 'pf is not clearing expired states'

      It's marked as Closed/FIXED (but only in 12.0-CURRENT, in commit: r338272)

      I don't know about the internals of the Netgate hardware, so just asking if this is something that could potentially affect SG-3100, and upcoming SG-1100 etc...

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

        I don't think we've seen any reports of states piling up like that.

        Searching a bit I don't see any recent threads that match the symptoms.

        It's possible it takes a specific set of circumstances to trigger, and perhaps our default rulesets and limits work around it somehow. It's not exactly clear what it takes to replicate from the FreeBSD PR, just seems to hit some people and not others.

        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
        • luckman212L
          luckman212 LAYER 8
          last edited by

          👍 Ok, seemed like one worth peeking at, so I was just checking.

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

            Looking through more comments on that PR, it looks like for some people still seeing the issue it was actually a clock/timekeeping problem and not a bug. Maybe it hasn't hit pfSense because nobody is using that specific hardware or setup that had the clock issue.

            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.