<?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: Identify IP address from host in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Identify-IP-address-from-host/m-p/119287#M24768</link>
    <description>&lt;P&gt;If you have configured Splunk to listen to udp:514, then you did configure Splunk to collect data on any server that sends syslog data on udp:514.&lt;/P&gt;</description>
    <pubDate>Thu, 03 Apr 2014 18:26:04 GMT</pubDate>
    <dc:creator>lukejadamec</dc:creator>
    <dc:date>2014-04-03T18:26:04Z</dc:date>
    <item>
      <title>Identify IP address from host</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Identify-IP-address-from-host/m-p/119285#M24766</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;We are seeing two suspicious servers which are sending syslogs in huge count.  &lt;/P&gt;

&lt;P&gt;and Upto my knowledge, we didn’t setup these two servers with forwarders or any splunk setup.&lt;/P&gt;

&lt;P&gt;So how we can find out original servers which are sending logs to indexer ?&lt;/P&gt;</description>
      <pubDate>Thu, 03 Apr 2014 16:24:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Identify-IP-address-from-host/m-p/119285#M24766</guid>
      <dc:creator>rameshlpatel</dc:creator>
      <dc:date>2014-04-03T16:24:29Z</dc:date>
    </item>
    <item>
      <title>Re: Identify IP address from host</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Identify-IP-address-from-host/m-p/119286#M24767</link>
      <description>&lt;P&gt;If you browse the syslog, you should be able to see host field. You can get IP of the server by doing nslookup.&lt;/P&gt;</description>
      <pubDate>Thu, 03 Apr 2014 18:24:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Identify-IP-address-from-host/m-p/119286#M24767</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2014-04-03T18:24:17Z</dc:date>
    </item>
    <item>
      <title>Re: Identify IP address from host</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Identify-IP-address-from-host/m-p/119287#M24768</link>
      <description>&lt;P&gt;If you have configured Splunk to listen to udp:514, then you did configure Splunk to collect data on any server that sends syslog data on udp:514.&lt;/P&gt;</description>
      <pubDate>Thu, 03 Apr 2014 18:26:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Identify-IP-address-from-host/m-p/119287#M24768</guid>
      <dc:creator>lukejadamec</dc:creator>
      <dc:date>2014-04-03T18:26:04Z</dc:date>
    </item>
    <item>
      <title>Re: Identify IP address from host</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Identify-IP-address-from-host/m-p/119288#M24769</link>
      <description>&lt;P&gt;Use Deploy Monitor app(All Forwarder View) for checking which are the forwarders sending data. &lt;/P&gt;

&lt;P&gt;In inputs.conf mention the ip address which should only be accepted from.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;acceptFrom = &amp;lt;network_acl&amp;gt; ...
* Lists a set of networks or addresses to accept connections from.
 These rules are separated by commas or spaces
* Each rule can be in the following forms:
*   1. A single IPv4 or IPv6 address (examples: "10.1.2.3", "fe80::4a3")
*   2. A CIDR block of addresses (examples: "10/8", "fe80:1234/32")
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Sat, 05 Apr 2014 07:38:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Identify-IP-address-from-host/m-p/119288#M24769</guid>
      <dc:creator>linu1988</dc:creator>
      <dc:date>2014-04-05T07:38:43Z</dc:date>
    </item>
  </channel>
</rss>

