<?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 4.2 UDP input with source IP: not working? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/4-2-UDP-input-with-source-IP-not-working/m-p/67828#M13701</link>
    <description>&lt;P&gt;EDIT: I've discovered this only happens if I specify more than one stanza on the same port -- different remote IPs, same UDP port. The way I read the docs, it sounded like you could overload a port by specifying the remote IPs. Is that not the case?&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[udp://10.1.168.158:7901]
host = myhostname
sourcetype = syslog
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Doesn't work. Am I m issing something? If I leave out the source IP specifier it works fine. Attempting to edit this entry in the GUI coughs up an error about the UDP port not being an integer.&lt;/P&gt;

&lt;P&gt;Per inputs.conf docs on splunk.com:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[udp://&amp;lt;remote server&amp;gt;:&amp;lt;port&amp;gt;]
* Similar to TCP, except that it listens on a UDP port.
* Configure Splunk to listen on a specific port. 
* If &amp;lt;remote server&amp;gt; is specified, the specified port will only accept data from that server.
* If &amp;lt;remote server&amp;gt; is empty - [udp://&amp;lt;port&amp;gt;] - the port will accept data sent from any server.
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;tcpdump confirms the source IP and destination port:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;14:41:30.773817 xxxxx &amp;gt; xxxxx, ethertype IPv4 (0x0800), length 198: 10.1.168.158.32774 &amp;gt; 10.5.130.206.7901: UDP
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Sat, 26 Mar 2011 01:39:00 GMT</pubDate>
    <dc:creator>twinspop</dc:creator>
    <dc:date>2011-03-26T01:39:00Z</dc:date>
    <item>
      <title>4.2 UDP input with source IP: not working?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/4-2-UDP-input-with-source-IP-not-working/m-p/67828#M13701</link>
      <description>&lt;P&gt;EDIT: I've discovered this only happens if I specify more than one stanza on the same port -- different remote IPs, same UDP port. The way I read the docs, it sounded like you could overload a port by specifying the remote IPs. Is that not the case?&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[udp://10.1.168.158:7901]
host = myhostname
sourcetype = syslog
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Doesn't work. Am I m issing something? If I leave out the source IP specifier it works fine. Attempting to edit this entry in the GUI coughs up an error about the UDP port not being an integer.&lt;/P&gt;

&lt;P&gt;Per inputs.conf docs on splunk.com:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[udp://&amp;lt;remote server&amp;gt;:&amp;lt;port&amp;gt;]
* Similar to TCP, except that it listens on a UDP port.
* Configure Splunk to listen on a specific port. 
* If &amp;lt;remote server&amp;gt; is specified, the specified port will only accept data from that server.
* If &amp;lt;remote server&amp;gt; is empty - [udp://&amp;lt;port&amp;gt;] - the port will accept data sent from any server.
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;tcpdump confirms the source IP and destination port:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;14:41:30.773817 xxxxx &amp;gt; xxxxx, ethertype IPv4 (0x0800), length 198: 10.1.168.158.32774 &amp;gt; 10.5.130.206.7901: UDP
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Sat, 26 Mar 2011 01:39:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/4-2-UDP-input-with-source-IP-not-working/m-p/67828#M13701</guid>
      <dc:creator>twinspop</dc:creator>
      <dc:date>2011-03-26T01:39:00Z</dc:date>
    </item>
    <item>
      <title>Re: 4.2 UDP input with source IP: not working?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/4-2-UDP-input-with-source-IP-not-working/m-p/67829#M13702</link>
      <description>&lt;P&gt;I just added the following input on my indexer via inputs.conf:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[udp://10.1.40.16:1514]
source = downvote
sourcetype = downvote
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Then I generated 3000 events. Prior to that I had the input set up like this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[udp://1514]
source = downvote
sourcetype = downvote
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;My event count is now sitting at 4000 on the 4.2 indexer where I sent the events. &lt;/P&gt;</description>
      <pubDate>Sat, 26 Mar 2011 02:24:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/4-2-UDP-input-with-source-IP-not-working/m-p/67829#M13702</guid>
      <dc:creator>jbsplunk</dc:creator>
      <dc:date>2011-03-26T02:24:29Z</dc:date>
    </item>
    <item>
      <title>Re: 4.2 UDP input with source IP: not working?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/4-2-UDP-input-with-source-IP-not-working/m-p/67830#M13703</link>
      <description>&lt;P&gt;Yes, without specifying the remote IP it works.&lt;/P&gt;</description>
      <pubDate>Sat, 26 Mar 2011 02:34:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/4-2-UDP-input-with-source-IP-not-working/m-p/67830#M13703</guid>
      <dc:creator>twinspop</dc:creator>
      <dc:date>2011-03-26T02:34:38Z</dc:date>
    </item>
    <item>
      <title>Re: 4.2 UDP input with source IP: not working?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/4-2-UDP-input-with-source-IP-not-working/m-p/67831#M13704</link>
      <description>&lt;P&gt;Change the sourcetype and/or source so you can tell which stanza is providing the data you're seeing. Also, add another stanza with a different remote IP (and souretype/source). The remote IP specific entries will go dormant.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Mar 2011 00:38:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/4-2-UDP-input-with-source-IP-not-working/m-p/67831#M13704</guid>
      <dc:creator>twinspop</dc:creator>
      <dc:date>2011-03-28T00:38:47Z</dc:date>
    </item>
  </channel>
</rss>

