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

    Security Onion does not collect logs from firewall rules with action==match

    Scheduled Pinned Locked Moved Firewalling
    3 Posts 2 Posters 196 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.
    • T
      trickery3169
      last edited by

      Security Onion does not collect logs from firewall rules with action==match. The reason is the format of the syslog messages that pfsense generates for firewall rules with action=Match.
      Here is what the syslog messages look like for rules with action==Block or action==Pass or action==Reject :
      Firewall rule with action Pass:
      163,,,1745940852,vtnet1.50,match,pass,in,4,0x0,,128,32369,0,none,1,icmp,60,10.100.4.10,1.1.1.1,request,3,1804340
      Firewall rule with action Reject:
      163,,,1745940852,vtnet1.50,match,block,in,4,0x0,,128,32361,0,none,1,icmp,60,10.100.4.10,1.1.1.1,request,3,1803240
      Firewall rule with action Block:
      163,,,1745940852,vtnet1.50,match,block,in,4,0x0,,128,32357,0,none,1,icmp,60,10.100.4.10,1.1.1.1,request,3,1802840
      And here how it look like for the rule with action==Match
      Firewall rule with action Match:
      163,,,1745940852,vtnet1.50,match,unkn(%u),in,4,0x0,,128,32365,0,none,1,icmp,60,10.100.4.10,1.1.1.1,request,3,1803940

      Security Onion pipeline pfsense integration contains a pattern that expects to see WORD characters in the 7th log field, but in the log from a firewall rule with action=Match it gets unkn(%u) which causes it to discard such logs.

      I've generated a bug report on github for elastic integrations, but it seems more logical to fix the problem in pfsense log output than to add a parsing exception on the elastic integrations side.
      A possible solution would be if a firewall rule with action Match generated a message like this one
      163,,,1745940852,vtnet1.50,match,match,in,4,0x0,,128,32365,0,none,1,icmp,60,10.100.4.10,1.1.1.1,request,3,1803940
      or
      163,,,1745940852,vtnet1.50,match,inspect,in,4,0x0,,128,32365,0,none,1,icmp,60,10.100.4.10,1.1.1.1,request,3,1803940

      It would also be an additional small improvement if the logs from Firewall rule with action Reject contained reject instead of block.

      1 Reply Last reply Reply Quote 0
      • bmeeksB
        bmeeks
        last edited by bmeeks

        If you want the pfSense developer team to see your report and potentially act upon it, it would be better if you open a Redmine issue here: https://redmine.pfsense.org/projects/pfsense.

        The forum is primarily for users to post requests for help from other users. Occasionally the developer team chimes in, but all software bugs need to be reported to Redmine.

        T 1 Reply Last reply Reply Quote 0
        • T
          trickery3169 @bmeeks
          last edited by

          @bmeeks got it, thank you

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