<?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: How do I do a CIDR match with an inputlookup? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/How-do-I-do-a-CIDR-match-with-an-inputlookup/m-p/454916#M128702</link>
    <description>&lt;P&gt;Gold! thank you, and to be clear... I'm not actually issuing a search with "makeresults"?&lt;/P&gt;</description>
    <pubDate>Wed, 06 Feb 2019 19:37:42 GMT</pubDate>
    <dc:creator>adepasquale</dc:creator>
    <dc:date>2019-02-06T19:37:42Z</dc:date>
    <item>
      <title>How do I do a CIDR match with an inputlookup?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-do-I-do-a-CIDR-match-with-an-inputlookup/m-p/454912#M128698</link>
      <description>&lt;P&gt;Hi All, &lt;/P&gt;

&lt;P&gt;I have a lookup that currently works. I've set match_type to CIDR(netRange) in my transforms file and everything works when I pass it an IP address to find in the range. &lt;/P&gt;

&lt;P&gt;However, I'm looking to use this lookup table without a search. So I went with the creating command &lt;CODE&gt;inputlookup&lt;/CODE&gt;, but for the life of me, I cannot get a CIDR match to work. I want to pass it an IP, and have it find the matching CIDR notation in netRange. &lt;/P&gt;

&lt;P&gt;Is there no way to do this with the inputlookup command — why is it not honoring my transform?&lt;/P&gt;

&lt;P&gt;This works:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index="main" | eval cip="1.1.1.1" | lookup IP2ASN netRange AS cip
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This does not work&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;|inputlookup IP2ASN where netRange=1.1.1.1
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Wed, 06 Feb 2019 18:57:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-do-I-do-a-CIDR-match-with-an-inputlookup/m-p/454912#M128698</guid>
      <dc:creator>adepasquale</dc:creator>
      <dc:date>2019-02-06T18:57:36Z</dc:date>
    </item>
    <item>
      <title>Re: How do I do a CIDR match with an inputlookup?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-do-I-do-a-CIDR-match-with-an-inputlookup/m-p/454913#M128699</link>
      <description>&lt;P&gt;@adepasquale Try this-&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;|inputlookup IP2ASN  | where netRange="1.1.1.1"
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Wed, 06 Feb 2019 19:26:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-do-I-do-a-CIDR-match-with-an-inputlookup/m-p/454913#M128699</guid>
      <dc:creator>Vijeta</dc:creator>
      <dc:date>2019-02-06T19:26:56Z</dc:date>
    </item>
    <item>
      <title>Re: How do I do a CIDR match with an inputlookup?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-do-I-do-a-CIDR-match-with-an-inputlookup/m-p/454914#M128700</link>
      <description>&lt;P&gt;This doesn't work either. netRange has values like 1.0.0.0/24, 1.0.1.0/24, 1.1.1.0/24, etc...&lt;/P&gt;</description>
      <pubDate>Wed, 06 Feb 2019 19:32:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-do-I-do-a-CIDR-match-with-an-inputlookup/m-p/454914#M128700</guid>
      <dc:creator>adepasquale</dc:creator>
      <dc:date>2019-02-06T19:32:27Z</dc:date>
    </item>
    <item>
      <title>Re: How do I do a CIDR match with an inputlookup?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-do-I-do-a-CIDR-match-with-an-inputlookup/m-p/454915#M128701</link>
      <description>&lt;P&gt;Try this&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;| makeresults | eval cip="1.1.1.1" | lookup IP2ASN netRange AS cip
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Wed, 06 Feb 2019 19:33:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-do-I-do-a-CIDR-match-with-an-inputlookup/m-p/454915#M128701</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2019-02-06T19:33:59Z</dc:date>
    </item>
    <item>
      <title>Re: How do I do a CIDR match with an inputlookup?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-do-I-do-a-CIDR-match-with-an-inputlookup/m-p/454916#M128702</link>
      <description>&lt;P&gt;Gold! thank you, and to be clear... I'm not actually issuing a search with "makeresults"?&lt;/P&gt;</description>
      <pubDate>Wed, 06 Feb 2019 19:37:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-do-I-do-a-CIDR-match-with-an-inputlookup/m-p/454916#M128702</guid>
      <dc:creator>adepasquale</dc:creator>
      <dc:date>2019-02-06T19:37:42Z</dc:date>
    </item>
    <item>
      <title>Re: How do I do a CIDR match with an inputlookup?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-do-I-do-a-CIDR-match-with-an-inputlookup/m-p/454917#M128703</link>
      <description>&lt;P&gt;You're running a search command that generates a dummy row (not searching actual indexes). Technically it's still a search.&lt;/P&gt;</description>
      <pubDate>Wed, 06 Feb 2019 19:55:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-do-I-do-a-CIDR-match-with-an-inputlookup/m-p/454917#M128703</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2019-02-06T19:55:37Z</dc:date>
    </item>
    <item>
      <title>Re: How do I do a CIDR match with an inputlookup?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-do-I-do-a-CIDR-match-with-an-inputlookup/m-p/454918#M128704</link>
      <description>&lt;P&gt;It'll do, thanks again.&lt;/P&gt;</description>
      <pubDate>Wed, 06 Feb 2019 20:09:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-do-I-do-a-CIDR-match-with-an-inputlookup/m-p/454918#M128704</guid>
      <dc:creator>adepasquale</dc:creator>
      <dc:date>2019-02-06T20:09:32Z</dc:date>
    </item>
  </channel>
</rss>

