<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Linux firewalld TA in Splunk Enterprise Security</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Linux-firewalld-TA/m-p/758055#M12834</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/170906"&gt;@livehybrid&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;thanks for your post. The problem is case on multiline; after I updated my props.conf in a single line all running as expected.&lt;/P&gt;</description>
    <pubDate>Fri, 06 Feb 2026 07:38:20 GMT</pubDate>
    <dc:creator>biroby</dc:creator>
    <dc:date>2026-02-06T07:38:20Z</dc:date>
    <item>
      <title>Linux firewalld TA</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Linux-firewalld-TA/m-p/758013#M12828</link>
      <description>&lt;P&gt;Hello community,&lt;/P&gt;&lt;P&gt;I'm new to Splunk Custom TA and would like to collect the Linux firewall log. I've searched the web to see if anyone has already done this, but I can't find anything.&lt;/P&gt;&lt;P&gt;I created a TA structure, but I have a problem: the PROTO field in the log can be numeric or string (I find TCP, UDP, or 1, 2, 47, etc.) and I want everything to be a descriptive string placed in the "transport" field.&lt;BR /&gt;I added this code to the props.conf, but it doesn't seem to work:&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;&lt;EM&gt;# -------------------------------&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;# Normalize transport (numeric + string proto)&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;# -------------------------------&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;EVAL-transport = case(&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;lower(proto)=="tcp" OR proto=="6", "tcp",&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;lower(proto)=="udp" OR proto=="17", "udp",&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;lower(proto)=="icmp" OR proto=="1", "icmp",&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;lower(proto)=="igmp" OR proto=="2", "igmp",&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;proto=="47", "gre",&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;proto=="50", "esp",&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;proto=="51", "ah",&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;lower(proto)=="icmp6" OR proto=="58", "icmp",&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;proto=="89", "ospf",&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;proto=="108", "ipip",&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;proto=="112", "vrrp",&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;proto=="115", "l2tp",&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;proto=="132", "sctp",&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;proto=="137", "mpls",&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;true(), "unknown"&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;)&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;If I use the single EVAL instead, it works:&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;&lt;EM&gt;EVAL-transport = lower(proto)&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Could you help me?&lt;BR /&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Thu, 05 Feb 2026 10:45:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/Linux-firewalld-TA/m-p/758013#M12828</guid>
      <dc:creator>biroby</dc:creator>
      <dc:date>2026-02-05T10:45:33Z</dc:date>
    </item>
    <item>
      <title>Re: Linux firewalld TA</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Linux-firewalld-TA/m-p/758017#M12829</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/315514"&gt;@biroby&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you put it on one-line does it work?&lt;/P&gt;&lt;P&gt;You could also check with btool that its picking up correctly:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;$SPLUNK_HOME/bin/splunk cmd btool props list &amp;lt;yourSourceType&amp;gt;&lt;/LI-CODE&gt;&lt;P&gt;Check that you see the full eval returned.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Another thing to check is running the eval as SPL in your search to ensure that you get the correct values returned, this is a good way to check without having to tweak and restart each time.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":glowing_star:"&gt;🌟&lt;/span&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Did this answer help you?&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;If so, please consider:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Adding karma to show it was useful&lt;/LI&gt;&lt;LI&gt;Marking it as the solution if it resolved your issue&lt;/LI&gt;&lt;LI&gt;Commenting if you need any clarification&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Your feedback encourages the volunteers in this community to continue contributing&lt;/P&gt;</description>
      <pubDate>Thu, 05 Feb 2026 12:33:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/Linux-firewalld-TA/m-p/758017#M12829</guid>
      <dc:creator>livehybrid</dc:creator>
      <dc:date>2026-02-05T12:33:39Z</dc:date>
    </item>
    <item>
      <title>Re: Linux firewalld TA</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Linux-firewalld-TA/m-p/758039#M12833</link>
      <description>&lt;P&gt;Wouldn't it be easier to do it with a lookup?&lt;/P&gt;</description>
      <pubDate>Thu, 05 Feb 2026 21:20:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/Linux-firewalld-TA/m-p/758039#M12833</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2026-02-05T21:20:12Z</dc:date>
    </item>
    <item>
      <title>Re: Linux firewalld TA</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Linux-firewalld-TA/m-p/758055#M12834</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/170906"&gt;@livehybrid&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;thanks for your post. The problem is case on multiline; after I updated my props.conf in a single line all running as expected.&lt;/P&gt;</description>
      <pubDate>Fri, 06 Feb 2026 07:38:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/Linux-firewalld-TA/m-p/758055#M12834</guid>
      <dc:creator>biroby</dc:creator>
      <dc:date>2026-02-06T07:38:20Z</dc:date>
    </item>
  </channel>
</rss>

