<?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 IPv6 subnets and splunk searchs in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/IPv6-subnets-and-splunk-searchs/m-p/37527#M178649</link>
    <description>&lt;P&gt;Splunk today is IPv4 subnet aware so that if you do a search with something like  ip_address = 10.0.0.0/24   .. splunk knows to look for items  10.0.0.0 thru 10.0.0.255  ... NICE ! 
Now what about IPV6  ... I think the answer is No.  my question is when or how can this be done &lt;/P&gt;

&lt;P&gt;example IPv6_ADDR = 2001:54FF::/48  would look for a whole lot of stuff but something like
2001:54FF:: to 2001:54FF:0000:FFFF:FFFF&lt;/P&gt;

&lt;P&gt;And this gets instresting as you can show the first part of the IPV6 address as 
2001:54FF:0000:0000
or 
2001:54ff::
or 
2001:54ff:0000::&lt;/P&gt;

&lt;P&gt;It depends on what the system sending the log spits out ...&lt;/P&gt;</description>
    <pubDate>Thu, 03 Feb 2011 03:00:18 GMT</pubDate>
    <dc:creator>g_prez</dc:creator>
    <dc:date>2011-02-03T03:00:18Z</dc:date>
    <item>
      <title>IPv6 subnets and splunk searchs</title>
      <link>https://community.splunk.com/t5/Splunk-Search/IPv6-subnets-and-splunk-searchs/m-p/37527#M178649</link>
      <description>&lt;P&gt;Splunk today is IPv4 subnet aware so that if you do a search with something like  ip_address = 10.0.0.0/24   .. splunk knows to look for items  10.0.0.0 thru 10.0.0.255  ... NICE ! 
Now what about IPV6  ... I think the answer is No.  my question is when or how can this be done &lt;/P&gt;

&lt;P&gt;example IPv6_ADDR = 2001:54FF::/48  would look for a whole lot of stuff but something like
2001:54FF:: to 2001:54FF:0000:FFFF:FFFF&lt;/P&gt;

&lt;P&gt;And this gets instresting as you can show the first part of the IPV6 address as 
2001:54FF:0000:0000
or 
2001:54ff::
or 
2001:54ff:0000::&lt;/P&gt;

&lt;P&gt;It depends on what the system sending the log spits out ...&lt;/P&gt;</description>
      <pubDate>Thu, 03 Feb 2011 03:00:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/IPv6-subnets-and-splunk-searchs/m-p/37527#M178649</guid>
      <dc:creator>g_prez</dc:creator>
      <dc:date>2011-02-03T03:00:18Z</dc:date>
    </item>
    <item>
      <title>Re: IPv6 subnets and splunk searchs</title>
      <link>https://community.splunk.com/t5/Splunk-Search/IPv6-subnets-and-splunk-searchs/m-p/37528#M178650</link>
      <description>&lt;P&gt;opps was a bit off this FFFF:FFFF in the that post that address should be  2001:54FF:0000:ffff:ffff:ffff:ffff:ffff&lt;BR /&gt;
got tired of typing ffff I guess.&lt;/P&gt;</description>
      <pubDate>Thu, 03 Feb 2011 08:22:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/IPv6-subnets-and-splunk-searchs/m-p/37528#M178650</guid>
      <dc:creator>g_prez</dc:creator>
      <dc:date>2011-02-03T08:22:15Z</dc:date>
    </item>
    <item>
      <title>Re: IPv6 subnets and splunk searchs</title>
      <link>https://community.splunk.com/t5/Splunk-Search/IPv6-subnets-and-splunk-searchs/m-p/37529#M178651</link>
      <description>&lt;P&gt;This search shows the problem.&lt;/P&gt;

&lt;P&gt;| stats count | eval ips="2001:54FF:0000:ffff:ffff:ffff:ffff:ffff,2002:54FF:0000:ffff:ffff:ffff:ffff:ffff,2003:54FF:0000:ffff:ffff:ffff:ffff:ffff" | rex field=ips "(?P[^,]+)" max_match=0 | mvexpand ip | table ip | search ip=2001:54FF::/48&lt;/P&gt;

&lt;P&gt;Splunk currently does not support ipv6 CIDR searching.&lt;/P&gt;

&lt;P&gt;BUT, because you are searching for a /48, these both work:&lt;/P&gt;

&lt;P&gt;| stats count | eval ips="2001:54FF:0000:ffff:ffff:ffff:ffff:ffff,2002:54FF:0000:ffff:ffff:ffff:ffff:ffff,2003:54FF:0000:ffff:ffff:ffff:ffff:ffff" | rex field=ips "(?P[^,]+)" max_match=0 | mvexpand ip | table ip | search ip=2001:54FF:*&lt;/P&gt;

&lt;P&gt;| stats count | eval ips="2001:54ff:0000:ffff:ffff:ffff:ffff:ffff,2002:54FF:0000:ffff:ffff:ffff:ffff:ffff,2003:54FF:0000:ffff:ffff:ffff:ffff:ffff" | rex field=ips "(?P[^,]+)" max_match=0 | mvexpand ip | table ip | search ip=2001:54FF:*&lt;/P&gt;

&lt;P&gt;As you can see, the capitalization does not matter.&lt;/P&gt;</description>
      <pubDate>Thu, 16 Apr 2015 10:59:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/IPv6-subnets-and-splunk-searchs/m-p/37529#M178651</guid>
      <dc:creator>bshuler_splunk</dc:creator>
      <dc:date>2015-04-16T10:59:57Z</dc:date>
    </item>
  </channel>
</rss>

