<?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 address field extraction issue in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/IPV6-address-field-extraction-issue/m-p/22757#M3956</link>
    <description>&lt;P&gt;Hi everybody,&lt;/P&gt;

&lt;P&gt;I am trying to use splunk&amp;gt; to extract some information from a set of IIS log files. Basically, I am working on a IPV6 vs IPV4 report. Yesterday, I did some tests at home, and everything worked fine. However, today at customer site, I have detected an strange behavior on splunk&amp;gt;&lt;/P&gt;

&lt;P&gt;I have attached a picture so you can easily see what I am talking about:&lt;/P&gt;

&lt;P&gt;&lt;IMG src="http://i55.tinypic.com/mhx5i.png" alt="alt text" /&gt;&lt;/P&gt;

&lt;P&gt;Here it is the picture if does not fit on your browser:&lt;/P&gt;

&lt;P&gt;&lt;A href="http://i55.tinypic.com/mhx5i.png"&gt;http://i55.tinypic.com/mhx5i.png&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Apparently, splunk&amp;gt; tries to shrink the IPV6 address, but it uses :: even though the real address is not filled with zeros. And therefore, my regExp does not work fine, because it is for fully fledged IPV6 addresses. Anyway, I could work in other regExp but the main point is that I am afraid splunk&amp;gt; is not indexing the information properly, shrinking IPV6 addresses when is not allowed.&lt;/P&gt;

&lt;P&gt;Thanks in advance&lt;/P&gt;</description>
    <pubDate>Mon, 06 Jun 2011 12:31:59 GMT</pubDate>
    <dc:creator>mihe</dc:creator>
    <dc:date>2011-06-06T12:31:59Z</dc:date>
    <item>
      <title>IPV6 address field extraction issue</title>
      <link>https://community.splunk.com/t5/Splunk-Search/IPV6-address-field-extraction-issue/m-p/22757#M3956</link>
      <description>&lt;P&gt;Hi everybody,&lt;/P&gt;

&lt;P&gt;I am trying to use splunk&amp;gt; to extract some information from a set of IIS log files. Basically, I am working on a IPV6 vs IPV4 report. Yesterday, I did some tests at home, and everything worked fine. However, today at customer site, I have detected an strange behavior on splunk&amp;gt;&lt;/P&gt;

&lt;P&gt;I have attached a picture so you can easily see what I am talking about:&lt;/P&gt;

&lt;P&gt;&lt;IMG src="http://i55.tinypic.com/mhx5i.png" alt="alt text" /&gt;&lt;/P&gt;

&lt;P&gt;Here it is the picture if does not fit on your browser:&lt;/P&gt;

&lt;P&gt;&lt;A href="http://i55.tinypic.com/mhx5i.png"&gt;http://i55.tinypic.com/mhx5i.png&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Apparently, splunk&amp;gt; tries to shrink the IPV6 address, but it uses :: even though the real address is not filled with zeros. And therefore, my regExp does not work fine, because it is for fully fledged IPV6 addresses. Anyway, I could work in other regExp but the main point is that I am afraid splunk&amp;gt; is not indexing the information properly, shrinking IPV6 addresses when is not allowed.&lt;/P&gt;

&lt;P&gt;Thanks in advance&lt;/P&gt;</description>
      <pubDate>Mon, 06 Jun 2011 12:31:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/IPV6-address-field-extraction-issue/m-p/22757#M3956</guid>
      <dc:creator>mihe</dc:creator>
      <dc:date>2011-06-06T12:31:59Z</dc:date>
    </item>
    <item>
      <title>Re: IPV6 address field extraction issue</title>
      <link>https://community.splunk.com/t5/Splunk-Search/IPV6-address-field-extraction-issue/m-p/22758#M3957</link>
      <description>&lt;P&gt;I don't think that Splunk is mangling your field value but rather that the "c_ip" field is not extracted from the location you expect in the event :&lt;/P&gt;

&lt;P&gt;&lt;IMG src="http://i53.tinypic.com/awx8vc.png" alt="alt text" /&gt;&lt;/P&gt;

&lt;P&gt;It looks like some app that you have installed is performing the extraction of the "c_ip" field by default. I would recommend that you check the other fields extracted, as one of them might contain the value you care about but under a field name other than "c_ip".&lt;/P&gt;

&lt;P&gt;Finally, if the value you care for is not being extracted at all, I recommend that you create your own field extraction following these instructions from our online documentation :&lt;/P&gt;

&lt;P&gt;&lt;A href="http://www.splunk.com/base/Documentation/latest/Knowledge/Addfieldsatsearchtime"&gt;http://www.splunk.com/base/Documentation/latest/Knowledge/Addfieldsatsearchtime&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;...and using one of these fine regular expressions tailored for IPv6 addresses :&lt;/P&gt;

&lt;P&gt;&lt;A href="http://splunk-base.splunk.com/answers/8435/ipv6-addresses-parsed-properly"&gt;http://splunk-base.splunk.com/answers/8435/ipv6-addresses-parsed-properly&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jun 2011 10:31:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/IPV6-address-field-extraction-issue/m-p/22758#M3957</guid>
      <dc:creator>hexx</dc:creator>
      <dc:date>2011-06-07T10:31:23Z</dc:date>
    </item>
  </channel>
</rss>

