<?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: HowTo handle DHCP Log reverse IP addresses in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/HowTo-handle-DHCP-Log-reverse-IP-addresses/m-p/79549#M181745</link>
    <description>&lt;P&gt;Yeah I've seen that too, Microsoft's DHCP server seems to have a weird behaviour with that.&lt;/P&gt;

&lt;P&gt;If you have the original IP in a field, let's call it &lt;CODE&gt;ip&lt;/CODE&gt;, you could reorder the octets with a &lt;CODE&gt;rex&lt;/CODE&gt; statement.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;... | rex mode=sed field=ip "s/(\d+)\.(\d+)\.(\d+)\.(\d+)/\4.\3.\2.\1/"
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Thu, 04 Oct 2012 08:15:47 GMT</pubDate>
    <dc:creator>Ayn</dc:creator>
    <dc:date>2012-10-04T08:15:47Z</dc:date>
    <item>
      <title>HowTo handle DHCP Log reverse IP addresses</title>
      <link>https://community.splunk.com/t5/Splunk-Search/HowTo-handle-DHCP-Log-reverse-IP-addresses/m-p/79548#M181744</link>
      <description>&lt;P&gt;Hi, &lt;/P&gt;

&lt;P&gt;I'm looking for a possibility to join DHCP events together with &lt;EM&gt;transaction&lt;/EM&gt; command. Join fields are IP and MAC address.&lt;/P&gt;

&lt;P&gt;Unfortunately DHCP Log contains in some cases the IP in reverse. &lt;BR /&gt;
As an example:&lt;BR /&gt;
&lt;BR /&gt;&lt;EM&gt;TIMESTAMP,DNS Update Request,66.1.168.192,MachinName,,&lt;/EM&gt;&lt;BR /&gt;
&lt;BR /&gt;Correct IP in this case would be 192.168.1.66.&lt;/P&gt;

&lt;P&gt;Is there any way to reverse the IP to allow matching with the rest of the IP entries in this field?&lt;/P&gt;

&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Thu, 04 Oct 2012 08:05:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/HowTo-handle-DHCP-Log-reverse-IP-addresses/m-p/79548#M181744</guid>
      <dc:creator>tyralla</dc:creator>
      <dc:date>2012-10-04T08:05:44Z</dc:date>
    </item>
    <item>
      <title>Re: HowTo handle DHCP Log reverse IP addresses</title>
      <link>https://community.splunk.com/t5/Splunk-Search/HowTo-handle-DHCP-Log-reverse-IP-addresses/m-p/79549#M181745</link>
      <description>&lt;P&gt;Yeah I've seen that too, Microsoft's DHCP server seems to have a weird behaviour with that.&lt;/P&gt;

&lt;P&gt;If you have the original IP in a field, let's call it &lt;CODE&gt;ip&lt;/CODE&gt;, you could reorder the octets with a &lt;CODE&gt;rex&lt;/CODE&gt; statement.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;... | rex mode=sed field=ip "s/(\d+)\.(\d+)\.(\d+)\.(\d+)/\4.\3.\2.\1/"
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 04 Oct 2012 08:15:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/HowTo-handle-DHCP-Log-reverse-IP-addresses/m-p/79549#M181745</guid>
      <dc:creator>Ayn</dc:creator>
      <dc:date>2012-10-04T08:15:47Z</dc:date>
    </item>
    <item>
      <title>Re: HowTo handle DHCP Log reverse IP addresses</title>
      <link>https://community.splunk.com/t5/Splunk-Search/HowTo-handle-DHCP-Log-reverse-IP-addresses/m-p/79550#M181746</link>
      <description>&lt;P&gt;Works perfect - Thanks!&lt;/P&gt;</description>
      <pubDate>Thu, 04 Oct 2012 14:34:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/HowTo-handle-DHCP-Log-reverse-IP-addresses/m-p/79550#M181746</guid>
      <dc:creator>tyralla</dc:creator>
      <dc:date>2012-10-04T14:34:36Z</dc:date>
    </item>
  </channel>
</rss>

