<?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"
	>
<channel>
	<title>Comments for Practical Tactics</title>
	<atom:link href="http://practical.wordpress.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://practical.wordpress.com</link>
	<description>technology experiences and insights</description>
	<pubDate>Wed, 23 Jul 2008 18:53:04 +0000</pubDate>
	<generator>http://wordpress.org/?v=MU</generator>
		<item>
		<title>Comment on IRS Exempt from Security? by R Jones</title>
		<link>http://practical.wordpress.com/2008/04/08/irs-exempt-from-security/#comment-188</link>
		<dc:creator>R Jones</dc:creator>
		<pubDate>Fri, 27 Jun 2008 13:45:59 +0000</pubDate>
		<guid isPermaLink="false">http://practical.wordpress.com/?p=42#comment-188</guid>
		<description>There are more than 300 possible computer notices the IRS can send out to a taxpayer. The IRS computer system is ridiculously vast. It can generate notices on a taxpayer for a simple math or clerical error to a full on audit that determines you owe additional taxes. If you challenge one of these notices ALWAYS send your response with CONFIRMED delivery.</description>
		<content:encoded><![CDATA[<p>There are more than 300 possible computer notices the IRS can send out to a taxpayer. The IRS computer system is ridiculously vast. It can generate notices on a taxpayer for a simple math or clerical error to a full on audit that determines you owe additional taxes. If you challenge one of these notices ALWAYS send your response with CONFIRMED delivery.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Tweaking PLA: Using rsyslog by Rick</title>
		<link>http://practical.wordpress.com/2008/03/11/tweaking-pla-using-rsyslog/#comment-187</link>
		<dc:creator>Rick</dc:creator>
		<pubDate>Thu, 22 May 2008 21:51:00 +0000</pubDate>
		<guid isPermaLink="false">http://practical.wordpress.com/?p=39#comment-187</guid>
		<description>Chris,

The following is what my logs look like now:
     
2008 05 22 11:36:35 192.168.0.1 05 22 2008 11:36:35 %PIX-6-305012:     Teardown dynamic TCP translation from inside:192.168.0.48/2457 to outside:1.1.1.1/57097 duration 0:00:31

The following is from my pla_parsed script:

$regex_log_begin = "(.*) (.*) (.*) (.*) (.*) (.*)";
#$regex_lob_begin = "(.*):(.*) (.*) (.*) (.*) ((.*):(.*):(.*)) (.*)";
$var_pixhost=2;
$var_pixmonth=3;
$var_pixdate=4;
$var_pixyear=5;
$var_pixtime=6;

I am getting nothing in my DB at all and am not sure if my regex_lob_begin is correct. 

Thanks.</description>
		<content:encoded><![CDATA[<p>Chris,</p>
<p>The following is what my logs look like now:</p>
<p>2008 05 22 11:36:35 192.168.0.1 05 22 2008 11:36:35 %PIX-6-305012:     Teardown dynamic TCP translation from inside:192.168.0.48/2457 to outside:1.1.1.1/57097 duration 0:00:31</p>
<p>The following is from my pla_parsed script:</p>
<p>$regex_log_begin = &#8220;(.*) (.*) (.*) (.*) (.*) (.*)&#8221;;<br />
#$regex_lob_begin = &#8220;(.*):(.*) (.*) (.*) (.*) ((.*):(.*):(.*)) (.*)&#8221;;<br />
$var_pixhost=2;<br />
$var_pixmonth=3;<br />
$var_pixdate=4;<br />
$var_pixyear=5;<br />
$var_pixtime=6;</p>
<p>I am getting nothing in my DB at all and am not sure if my regex_lob_begin is correct. </p>
<p>Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on IRS Exempt from Security? by Sue Massey</title>
		<link>http://practical.wordpress.com/2008/04/08/irs-exempt-from-security/#comment-176</link>
		<dc:creator>Sue Massey</dc:creator>
		<pubDate>Wed, 09 Apr 2008 05:23:44 +0000</pubDate>
		<guid isPermaLink="false">http://practical.wordpress.com/?p=42#comment-176</guid>
		<description>I like your writing style. Looking forward to reading more from you.

- Sue.</description>
		<content:encoded><![CDATA[<p>I like your writing style. Looking forward to reading more from you.</p>
<p>- Sue.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Tweaking PLA: Using rsyslog by bmestep</title>
		<link>http://practical.wordpress.com/2008/03/11/tweaking-pla-using-rsyslog/#comment-172</link>
		<dc:creator>bmestep</dc:creator>
		<pubDate>Thu, 20 Mar 2008 18:22:33 +0000</pubDate>
		<guid isPermaLink="false">http://practical.wordpress.com/?p=39#comment-172</guid>
		<description>Chris,

I made a quick perl hack to find the solution and I'll throw together a post on it shortly, in the meantime...

Stick a ; at the end of your regex you pasted above and you should be set.
Change your variables to this:

$var_pixhost=2;
$var_pixmonth=3;
$var_pixdate=4;
$var_pixyear=5;
$var_pixtime=6;

The original regex should have worked, based on testing the message you provided and the &lt;em&gt;$regex_log_begin = "(.*):(.*) (.*) (.*) (.*) (.*) ((.*):(.*):(.*))"; &lt;/em&gt; will definitely work.</description>
		<content:encoded><![CDATA[<p>Chris,</p>
<p>I made a quick perl hack to find the solution and I&#8217;ll throw together a post on it shortly, in the meantime&#8230;</p>
<p>Stick a ; at the end of your regex you pasted above and you should be set.<br />
Change your variables to this:</p>
<p>$var_pixhost=2;<br />
$var_pixmonth=3;<br />
$var_pixdate=4;<br />
$var_pixyear=5;<br />
$var_pixtime=6;</p>
<p>The original regex should have worked, based on testing the message you provided and the <em>$regex_log_begin = &#8220;(.*):(.*) (.*) (.*) (.*) (.*) ((.*):(.*):(.*))&#8221;; </em> will definitely work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Tweaking PLA: Using rsyslog by bmestep</title>
		<link>http://practical.wordpress.com/2008/03/11/tweaking-pla-using-rsyslog/#comment-171</link>
		<dc:creator>bmestep</dc:creator>
		<pubDate>Thu, 20 Mar 2008 17:41:32 +0000</pubDate>
		<guid isPermaLink="false">http://practical.wordpress.com/?p=39#comment-171</guid>
		<description>It would be more reliable to start with the original regex "(.*):(.*)..." and then map the variables as follows:

$var_pixhost=3;
$var_pixmonth=4;
$var_pixdate=5;
$var_pixyear=6;
$var_pixtime=7;

I suspect the initial timestamp is throwing the regex off.
You can get regex to better match your log format by replacing the 7th (.*) with the format I used in the rsyslog example above: ((.*):(.*):(.*))

Drop me an email, if that doesn't work or if you need help translating that into the pla_parsed file. bmestep (is_at) gmail (dot) com</description>
		<content:encoded><![CDATA[<p>It would be more reliable to start with the original regex &#8220;(.*):(.*)&#8230;&#8221; and then map the variables as follows:</p>
<p>$var_pixhost=3;<br />
$var_pixmonth=4;<br />
$var_pixdate=5;<br />
$var_pixyear=6;<br />
$var_pixtime=7;</p>
<p>I suspect the initial timestamp is throwing the regex off.<br />
You can get regex to better match your log format by replacing the 7th (.*) with the format I used in the rsyslog example above: ((.*):(.*):(.*))</p>
<p>Drop me an email, if that doesn&#8217;t work or if you need help translating that into the pla_parsed file. bmestep (is_at) gmail (dot) com</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Tweaking PLA: Using rsyslog by Chris</title>
		<link>http://practical.wordpress.com/2008/03/11/tweaking-pla-using-rsyslog/#comment-170</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Thu, 20 Mar 2008 05:35:03 +0000</pubDate>
		<guid isPermaLink="false">http://practical.wordpress.com/?p=39#comment-170</guid>
		<description>using  syslog-ng, I get the following format for pix log entries:

2008-03-19T22:32:46-07:00 1.1.1.5 Mar 19 2008 21:32:46: %PIX-4-106023: Deny tcp src outside:58.224.81.118/3603 dst pridmz:server01/25 by access-group "outside"

would the following be a suitable regex for this?

$regex_log_begin = "(.*) (.*) (.*) (.*) (.*) (.*)" 
$var_pixhost=2;
$var_pixmonth=3;
$var_pixdate=4;
$var_pixyear=5;
$var_pixtime=6;

please let me know, thx!!</description>
		<content:encoded><![CDATA[<p>using  syslog-ng, I get the following format for pix log entries:</p>
<p>2008-03-19T22:32:46-07:00 1.1.1.5 Mar 19 2008 21:32:46: %PIX-4-106023: Deny tcp src outside:58.224.81.118/3603 dst pridmz:server01/25 by access-group &#8220;outside&#8221;</p>
<p>would the following be a suitable regex for this?</p>
<p>$regex_log_begin = &#8220;(.*) (.*) (.*) (.*) (.*) (.*)&#8221;<br />
$var_pixhost=2;<br />
$var_pixmonth=3;<br />
$var_pixdate=4;<br />
$var_pixyear=5;<br />
$var_pixtime=6;</p>
<p>please let me know, thx!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on PIX Parsing (Usable Logs!) by Kris Philipsen</title>
		<link>http://practical.wordpress.com/2007/10/22/pix-parsing-usable-logs/#comment-169</link>
		<dc:creator>Kris Philipsen</dc:creator>
		<pubDate>Wed, 19 Mar 2008 06:59:07 +0000</pubDate>
		<guid isPermaLink="false">http://practical.wordpress.com/2007/10/22/pix-parsing-usable-logs/#comment-169</guid>
		<description>Patrux, Bmestep,

Thanks for the updates. If you want you can contact me via email on kris [at] logging [dash] architecture [dot] net. A traffic_log db of 148 Million records is not bad, how's that fairing up for you so far? Are you using many display / parse filters? With regards to the speed of the MySQL queries, because of the display filtering being enabled and perfoming a JOIN, it makes the query a little slower. I'll have to look around to see whether there's a more effective way of handling these queries.

Bmestep, I like your write up on using rsyslogd with PLA, do you mind if I put a link to your write up on the PLA website?

Kris</description>
		<content:encoded><![CDATA[<p>Patrux, Bmestep,</p>
<p>Thanks for the updates. If you want you can contact me via email on kris [at] logging [dash] architecture [dot] net. A traffic_log db of 148 Million records is not bad, how&#8217;s that fairing up for you so far? Are you using many display / parse filters? With regards to the speed of the MySQL queries, because of the display filtering being enabled and perfoming a JOIN, it makes the query a little slower. I&#8217;ll have to look around to see whether there&#8217;s a more effective way of handling these queries.</p>
<p>Bmestep, I like your write up on using rsyslogd with PLA, do you mind if I put a link to your write up on the PLA website?</p>
<p>Kris</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on PIX Parsing (Usable Logs!) by bmestep</title>
		<link>http://practical.wordpress.com/2007/10/22/pix-parsing-usable-logs/#comment-168</link>
		<dc:creator>bmestep</dc:creator>
		<pubDate>Wed, 19 Mar 2008 01:44:25 +0000</pubDate>
		<guid isPermaLink="false">http://practical.wordpress.com/2007/10/22/pix-parsing-usable-logs/#comment-168</guid>
		<description>I have a traffic_log database with over 148Million records, I can run some tests on the queries to see which ones perform faster, in the case of the one you mentioned above.

Look for a new post to capture ideas on enhancing speed / performance of PLA.</description>
		<content:encoded><![CDATA[<p>I have a traffic_log database with over 148Million records, I can run some tests on the queries to see which ones perform faster, in the case of the one you mentioned above.</p>
<p>Look for a new post to capture ideas on enhancing speed / performance of PLA.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on PIX Parsing (Usable Logs!) by patux</title>
		<link>http://practical.wordpress.com/2007/10/22/pix-parsing-usable-logs/#comment-167</link>
		<dc:creator>patux</dc:creator>
		<pubDate>Tue, 18 Mar 2008 20:47:04 +0000</pubDate>
		<guid isPermaLink="false">http://practical.wordpress.com/2007/10/22/pix-parsing-usable-logs/#comment-167</guid>
		<description>hey!
that's cool.

I've spent some time trying to speedup PLA without good results.
I think that the problem (in my case) is that we're running "syslog server" and the database on the same system.
About the database changes, i've made changes to storage type on MySQL, adding partitioning and fixes (i hope) to some querys.
I changed expression:
  log_time&#62;'expr' and log_time&#60;'expr'
for 
  log_time between 'time1' and 'time2'
while i'm using partitions by "range" (to_days) this sentences uses only partitions that contains records in this interval of time. The original sentences uses all partitions.

Now i'm working to move the database and the front-end to another system.

I hope that we're having news about PLA!.</description>
		<content:encoded><![CDATA[<p>hey!<br />
that&#8217;s cool.</p>
<p>I&#8217;ve spent some time trying to speedup PLA without good results.<br />
I think that the problem (in my case) is that we&#8217;re running &#8220;syslog server&#8221; and the database on the same system.<br />
About the database changes, i&#8217;ve made changes to storage type on MySQL, adding partitioning and fixes (i hope) to some querys.<br />
I changed expression:<br />
  log_time&gt;&#8217;expr&#8217; and log_time&lt;&#8217;expr&#8217;<br />
for<br />
  log_time between &#8216;time1&#8242; and &#8216;time2&#8242;<br />
while i&#8217;m using partitions by &#8220;range&#8221; (to_days) this sentences uses only partitions that contains records in this interval of time. The original sentences uses all partitions.</p>
<p>Now i&#8217;m working to move the database and the front-end to another system.</p>
<p>I hope that we&#8217;re having news about PLA!.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Tweaking PLA: Using rsyslog by PIX Logging Architecture is Back Online &#171; Practical Tactics</title>
		<link>http://practical.wordpress.com/2008/03/11/tweaking-pla-using-rsyslog/#comment-166</link>
		<dc:creator>PIX Logging Architecture is Back Online &#171; Practical Tactics</dc:creator>
		<pubDate>Tue, 18 Mar 2008 17:48:41 +0000</pubDate>
		<guid isPermaLink="false">http://practical.wordpress.com/?p=39#comment-166</guid>
		<description>[...] Tweaking PLA: Using&#160;rsyslog [...]</description>
		<content:encoded><![CDATA[<p>[...] Tweaking PLA: Using&nbsp;rsyslog [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
