<?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: Getting Splunk to work with Syslog UDP 514 in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Getting-Splunk-to-work-with-Syslog-UDP-514/m-p/93702#M19482</link>
    <description>&lt;P&gt;Not sure but it works now. Could have been just going over steps needs to make this work.&lt;BR /&gt;
thanks&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;configured iptables to take udp 514&lt;/LI&gt;
&lt;LI&gt;restarting iptables&lt;/LI&gt;
&lt;LI&gt;adding data input udp 514&lt;/LI&gt;
&lt;/OL&gt;

&lt;P&gt;BTW: i still don't see syslog "port 514" activity in the metrics.log but it works.&lt;/P&gt;</description>
    <pubDate>Fri, 11 Oct 2013 22:26:45 GMT</pubDate>
    <dc:creator>fletch13</dc:creator>
    <dc:date>2013-10-11T22:26:45Z</dc:date>
    <item>
      <title>Getting Splunk to work with Syslog UDP 514</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Getting-Splunk-to-work-with-Syslog-UDP-514/m-p/93694#M19474</link>
      <description>&lt;P&gt;I've been reading and trying to figure this out. But i'm stomped.&lt;/P&gt;

&lt;P&gt;I configured a device to send syslog events to the splunk server via udp:514&lt;BR /&gt;
i can see the traffic (on splunk server)with tcpdump port 514. I've tested this by trigger an event on the device and seeing the event on the splunk server (via tcpdump.&lt;/P&gt;

&lt;P&gt;./splunk list udp cli shows 514&lt;BR /&gt;
I've tailed "metics.log" and i do not see the related syslog event getting there.&lt;/P&gt;

&lt;P&gt;Looks like everything is good. but nothing in searches or indexes.. &lt;BR /&gt;
running splunk ver 6.&lt;/P&gt;</description>
      <pubDate>Thu, 10 Oct 2013 21:16:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Getting-Splunk-to-work-with-Syslog-UDP-514/m-p/93694#M19474</guid>
      <dc:creator>fletch13</dc:creator>
      <dc:date>2013-10-10T21:16:50Z</dc:date>
    </item>
    <item>
      <title>Re: Getting Splunk to work with Syslog UDP 514</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Getting-Splunk-to-work-with-Syslog-UDP-514/m-p/93695#M19475</link>
      <description>&lt;P&gt;How have you configured Splunk to listen on that port?&lt;/P&gt;</description>
      <pubDate>Thu, 10 Oct 2013 22:00:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Getting-Splunk-to-work-with-Syslog-UDP-514/m-p/93695#M19475</guid>
      <dc:creator>lukejadamec</dc:creator>
      <dc:date>2013-10-10T22:00:43Z</dc:date>
    </item>
    <item>
      <title>Re: Getting Splunk to work with Syslog UDP 514</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Getting-Splunk-to-work-with-Syslog-UDP-514/m-p/93696#M19476</link>
      <description>&lt;P&gt;Disable your firewall.  And/or add rules to allow UDP/514.&lt;/P&gt;

&lt;P&gt;Using tcpdump is a great test, but it is misleading with UDP packets.  The libpcap libraries sit in the network stack below iptables.  So it is entirely possible that you will see a packet arrive with tcpdump and it will be dropped by iptables before it makes it to the process.  And because it's UDP there is no broken session setup to observe.&lt;/P&gt;</description>
      <pubDate>Fri, 11 Oct 2013 05:32:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Getting-Splunk-to-work-with-Syslog-UDP-514/m-p/93696#M19476</guid>
      <dc:creator>dwaddle</dc:creator>
      <dc:date>2013-10-11T05:32:17Z</dc:date>
    </item>
    <item>
      <title>Re: Getting Splunk to work with Syslog UDP 514</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Getting-Splunk-to-work-with-Syslog-UDP-514/m-p/93697#M19477</link>
      <description>&lt;P&gt;Dwaddle nailed it, but I'd also check to see if another process, like syslog or syslog-ng, is already using UDP 514.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;lsof -i :514
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Fri, 11 Oct 2013 17:17:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Getting-Splunk-to-work-with-Syslog-UDP-514/m-p/93697#M19477</guid>
      <dc:creator>twinspop</dc:creator>
      <dc:date>2013-10-11T17:17:55Z</dc:date>
    </item>
    <item>
      <title>Re: Getting Splunk to work with Syslog UDP 514</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Getting-Splunk-to-work-with-Syslog-UDP-514/m-p/93698#M19478</link>
      <description>&lt;P&gt;yes. Splunk has been configured to listen to udp 514&lt;/P&gt;</description>
      <pubDate>Fri, 11 Oct 2013 17:38:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Getting-Splunk-to-work-with-Syslog-UDP-514/m-p/93698#M19478</guid>
      <dc:creator>fletch13</dc:creator>
      <dc:date>2013-10-11T17:38:12Z</dc:date>
    </item>
    <item>
      <title>Re: Getting Splunk to work with Syslog UDP 514</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Getting-Splunk-to-work-with-Syslog-UDP-514/m-p/93699#M19479</link>
      <description>&lt;P&gt;okay. i double checked and iptables files is configured to accept port 514. plus restarted iptables.&lt;BR /&gt;
-A INPUT -p udp -m udp --dport 514 -j ACCEPT&lt;/P&gt;</description>
      <pubDate>Fri, 11 Oct 2013 17:43:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Getting-Splunk-to-work-with-Syslog-UDP-514/m-p/93699#M19479</guid>
      <dc:creator>fletch13</dc:creator>
      <dc:date>2013-10-11T17:43:22Z</dc:date>
    </item>
    <item>
      <title>Re: Getting Splunk to work with Syslog UDP 514</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Getting-Splunk-to-work-with-Syslog-UDP-514/m-p/93700#M19480</link>
      <description>&lt;P&gt;i did have rsyslog running. i kill it and still not seeing my udp traffic in the metrics.log&lt;/P&gt;</description>
      <pubDate>Fri, 11 Oct 2013 17:51:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Getting-Splunk-to-work-with-Syslog-UDP-514/m-p/93700#M19480</guid>
      <dc:creator>fletch13</dc:creator>
      <dc:date>2013-10-11T17:51:38Z</dc:date>
    </item>
    <item>
      <title>Re: Getting Splunk to work with Syslog UDP 514</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Getting-Splunk-to-work-with-Syslog-UDP-514/m-p/93701#M19481</link>
      <description>&lt;P&gt;Did you restart Splunk after? It won't dynamically re-try the port. A restart will be needed.&lt;/P&gt;</description>
      <pubDate>Fri, 11 Oct 2013 20:25:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Getting-Splunk-to-work-with-Syslog-UDP-514/m-p/93701#M19481</guid>
      <dc:creator>twinspop</dc:creator>
      <dc:date>2013-10-11T20:25:20Z</dc:date>
    </item>
    <item>
      <title>Re: Getting Splunk to work with Syslog UDP 514</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Getting-Splunk-to-work-with-Syslog-UDP-514/m-p/93702#M19482</link>
      <description>&lt;P&gt;Not sure but it works now. Could have been just going over steps needs to make this work.&lt;BR /&gt;
thanks&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;configured iptables to take udp 514&lt;/LI&gt;
&lt;LI&gt;restarting iptables&lt;/LI&gt;
&lt;LI&gt;adding data input udp 514&lt;/LI&gt;
&lt;/OL&gt;

&lt;P&gt;BTW: i still don't see syslog "port 514" activity in the metrics.log but it works.&lt;/P&gt;</description>
      <pubDate>Fri, 11 Oct 2013 22:26:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Getting-Splunk-to-work-with-Syslog-UDP-514/m-p/93702#M19482</guid>
      <dc:creator>fletch13</dc:creator>
      <dc:date>2013-10-11T22:26:45Z</dc:date>
    </item>
    <item>
      <title>Re: Getting Splunk to work with Syslog UDP 514</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Getting-Splunk-to-work-with-Syslog-UDP-514/m-p/93703#M19483</link>
      <description>&lt;P&gt;Redirects 514 to 5514 in this example.&lt;/P&gt;

&lt;P&gt;Poke hole in iptables to allow web-configuration and the listener ports &lt;/P&gt;

&lt;P&gt;Redirect for port 515 up to 5514 which we are listening on (be sure to "service iptables save" after modifying iptables, or modify etc/sysconfig/iptables directly)&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;iptables -I INPUT -p tcp --dport 8000 -j ACCEPT&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;iptables -I INPUT -p tcp --dport 5514 -j ACCEPT&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;iptables -t nat -A PREROUTING -d MY.IP -p tcp -m tcp --dport 514 -j DNAT --to-destination MY.IP:5514&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;iptables -t nat -A PREROUTING -d MY.IP -p udp -m udp --dport 514 -j DNAT --to-destination MY.IP:5514&lt;/CODE&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 02 Jul 2014 01:02:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Getting-Splunk-to-work-with-Syslog-UDP-514/m-p/93703#M19483</guid>
      <dc:creator>mcronkrite</dc:creator>
      <dc:date>2014-07-02T01:02:10Z</dc:date>
    </item>
  </channel>
</rss>

