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

    Firewall log bug - wrong rule listed, states ipv4 when its ipv6, etc.

    Scheduled Pinned Locked Moved 2.1 Snapshot Feedback and Problems - RETIRED
    3 Posts 2 Posters 1.3k 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.
    • johnpozJ
      johnpoz LAYER 8 Global Moderator
      last edited by

      Ok so there is something not right with the firewall logs and how it parses which rule was used

      So in the below log and rules, you can see that in the log for the ipv6 block to :123 (that does not match my allow for 123 to my ipv6 box serving up ntp, so it should fall through to the default block.  But clearly its IPv6 not ipv4 and lists ipv4 default deny as the rule that blocked it.

      But what is stranger is the allows into my ssh box 192.168.1.7:22 yes that should be allowed but its stating the rule that allowed it is the one above the actual allow rule.

      Currently using
      2.1-BETA1 (i386)
      built on Fri Dec 28 20:54:16 EST 2012
      FreeBSD 8.3-RELEASE-p5

      Its a couple weeks old sure, I normally update to new snap every couple of weekends.  But I don't see anything in the rss feed about commits that would fix this.

      firelog.jpg
      firelog.jpg_thumb
      firefules.jpg
      firefules.jpg_thumb

      An intelligent man is sometimes forced to be drunk to spend time with his fools
      If you get confused: Listen to the Music Play
      Please don't Chat/PM me for help, unless mod related
      SG-4860 24.11 | Lab VMs 2.7.2, 24.11

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

        The firewall log display gets the rule number from the log and then looks up the rule number in the current set of pf rules in use. If you make mods to your rules, or have timed rules, or anything to change the current running ruleset, then a display of old log data before the ruleset change will have the mapping between rule number and rule text out-of-date.
        There is no database kept of the ruleset in effect at each point in time, so there is currently no way to match up rule numbers in "old" logs with the text of the rule at the time.

        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
        • johnpozJ
          johnpoz LAYER 8 Global Moderator
          last edited by

          Thanks for the details - that makes sense ;)  And yeah I had just added some rules.  Will keep an eye on it.

          An intelligent man is sometimes forced to be drunk to spend time with his fools
          If you get confused: Listen to the Music Play
          Please don't Chat/PM me for help, unless mod related
          SG-4860 24.11 | Lab VMs 2.7.2, 24.11

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