<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Log iptables Messages to a Separate File with rsyslog</title>
	<atom:link href="http://blog.shadypixel.com/log-iptables-messages-to-a-separate-file-with-rsyslog/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.shadypixel.com/log-iptables-messages-to-a-separate-file-with-rsyslog/</link>
	<description>tech, politics, etc.</description>
	<lastBuildDate>Thu, 22 Jul 2010 17:48:20 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: btmorex</title>
		<link>http://blog.shadypixel.com/log-iptables-messages-to-a-separate-file-with-rsyslog/#comment-3443</link>
		<dc:creator>btmorex</dc:creator>
		<pubDate>Sun, 08 Nov 2009 21:14:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.shadypixel.com/?p=269#comment-3443</guid>
		<description>The advantage of rsyslog is that you&#039;re probably already using it and you can&#039;t really run a linux system with out some sort of syslog daemon. ulogd might make sense on a dedicated firewall, but it&#039;s sort of ridiculous to have to run a completely separate daemon just to log iptables on a workstation.</description>
		<content:encoded><![CDATA[<p>The advantage of rsyslog is that you&#8217;re probably already using it and you can&#8217;t really run a linux system with out some sort of syslog daemon. ulogd might make sense on a dedicated firewall, but it&#8217;s sort of ridiculous to have to run a completely separate daemon just to log iptables on a workstation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://blog.shadypixel.com/log-iptables-messages-to-a-separate-file-with-rsyslog/#comment-3441</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Sun, 08 Nov 2009 17:42:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.shadypixel.com/?p=269#comment-3441</guid>
		<description>Or you could skip rsyslog all together, and use ULOGD and the ULOG target.  More flexibility this way - send the logs to a file, or a database.  No issues with filtering, and you can use as many prefixes as you want without having to reconfigure rsyslog.</description>
		<content:encoded><![CDATA[<p>Or you could skip rsyslog all together, and use ULOGD and the ULOG target.  More flexibility this way &#8211; send the logs to a file, or a database.  No issues with filtering, and you can use as many prefixes as you want without having to reconfigure rsyslog.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://blog.shadypixel.com/log-iptables-messages-to-a-separate-file-with-rsyslog/#comment-3036</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Sat, 24 Oct 2009 12:53:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.shadypixel.com/?p=269#comment-3036</guid>
		<description>This help file is for rsyslog not sysctl</description>
		<content:encoded><![CDATA[<p>This help file is for rsyslog not sysctl</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Eisentraut</title>
		<link>http://blog.shadypixel.com/log-iptables-messages-to-a-separate-file-with-rsyslog/#comment-1182</link>
		<dc:creator>Peter Eisentraut</dc:creator>
		<pubDate>Wed, 01 Jul 2009 07:39:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.shadypixel.com/?p=269#comment-1182</guid>
		<description>Thanks for the tip, but I couldn&#039;t actually get it to work verbatim. The log messages for me look like this:

Jul  1 10:34:57 somehost kernel: [40863.468270] &#039;firehol: &#039;IN-world&#039;:...

The timestamp in brackets is part of the message and needs to be matched as well.

I got it to work using &quot;contains&quot; instead of &quot;startswith&quot;.

Another useful tip is to add

kernel.printk = 4 4 1 7

to /etc/sysctl.conf to stop the iptables messages from going to the console.

Perhaps this will be helpful for some readers.</description>
		<content:encoded><![CDATA[<p>Thanks for the tip, but I couldn&#8217;t actually get it to work verbatim. The log messages for me look like this:</p>
<p>Jul  1 10:34:57 somehost kernel: [40863.468270] &#8216;firehol: &#8216;IN-world&#8217;:&#8230;</p>
<p>The timestamp in brackets is part of the message and needs to be matched as well.</p>
<p>I got it to work using &#8220;contains&#8221; instead of &#8220;startswith&#8221;.</p>
<p>Another useful tip is to add</p>
<p>kernel.printk = 4 4 1 7</p>
<p>to /etc/sysctl.conf to stop the iptables messages from going to the console.</p>
<p>Perhaps this will be helpful for some readers.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic page generated in 0.240 seconds. -->
<!-- Cached page generated by WP-Super-Cache on 2010-07-23 14:45:01 -->
<!-- Compression = gzip -->