<?xml version="1.0" encoding="UTF-8"?><!-- generator="WordPress/2.9.1" -->
<rss version="0.92">
<channel>
	<title>tech notes</title>
	<link>http://bsd.dischaos.com</link>
	<description>just some random notes on BSDs, linux and web development</description>
	<lastBuildDate>Sun, 31 Jan 2010 00:30:50 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	
	<item>
		<title>Munin plugin for Ironport</title>
		<description><![CDATA[A simple munin plugin for graphing Ironport statistics.  All it graphs is CPU, memory, disk IO and queue utilisation. It requires SNMP to be enabled on the Ironport (and assumes you&#8217;re using SNMP v3) and snmpwalk to be installed on the munin server. The plugin supports the following environment variables:
* snmp_community &#8211; by default [...]]]></description>
		<link>http://bsd.dischaos.com/2010/01/31/munin-plugin-for-ironport/</link>
			</item>
	<item>
		<title>Portauditing jails</title>
		<description><![CDATA[I run most of the services in separate jails (that&#8217;s all easy to set up and maintain with ezjail) and quite often end up having 10+ jails even on simple mail/web server installations. 
Installing portaudit, updating its database and running it every day in each jail seems to be a waste of space and resources. [...]]]></description>
		<link>http://bsd.dischaos.com/2010/01/07/portauditing-jails/</link>
			</item>
	<item>
		<title>Fixing corrupted Ironport Queue</title>
		<description><![CDATA[Looks like there&#8217;s a hidden command you can use to fix queue problems similar to these:

Critical: Queue: Your queue has been corrupted; UNABLE TO REPAIR: unable to
mount queue: &#8216;(\&#8217;qstore/gcq.py get_time_sorted_gens&#124;919\&#8217;, &#8220;&#8220;, &#8220;[Errno 2] No such file or directory:
        \&#8217;/var/db/godspeed/gen/gen063.chk\&#8217;&#8221;, \&#8217;[qstore/gcq.py mount&#124;1387]
        [...]]]></description>
		<link>http://bsd.dischaos.com/2010/01/05/fixing-corrupted-ironport-queue/</link>
			</item>
	<item>
		<title>how to create a new kvm image for eucalyptus UEC</title>
		<description><![CDATA[Eucalyptus is a new cloud management software available with the latest version of ubuntu (karmic koala). It&#8217;s compatible with Amazon&#8217;s EC2 (in terms of images and CLI tools) and it&#8217;s opensource so anyone can build a EC2 like service. That is&#8230; when it becomes a little bit more stable&#8230;  
Eucalyptus comes with 2 images [...]]]></description>
		<link>http://bsd.dischaos.com/2009/11/15/how-to-create-a-new-kvm-image-for-eucalyptus-uec/</link>
			</item>
	<item>
		<title>ssh port knocking with pf</title>
		<description><![CDATA[The idea of port knocking is simple &#8211; a service, normally firewalled accepts connections from a given source IP if that IP address has connected to certain ports in some special sequence. This is a simplified implementation of this idea using pf to protect the ssh service.
In pf.conf file:
&#8230;
### pf tables
table &#60;ssh_accept&#62; persist
&#8230;
### pf rules
block [...]]]></description>
		<link>http://bsd.dischaos.com/2009/10/24/ssh-port-knocking-with-pf/</link>
			</item>
	<item>
		<title>RPM build environment on CentOS</title>
		<description><![CDATA[Just a quick note on how to build RPMs
 setting up build environment 
RPMs should be built from a &#8221;&#8217;standard user&#8221;&#8217; account, &#8221;&#8217;not root&#8221;&#8217;. This saves a lot of trouble when something goes wrong during package preparation/installation and keeps the build environment clean.
Here&#8217;s how to setup build environment in your home directory:
mkdir -p ~/build/{BUILD,RPMS,S{OURCES,PECS,RPMS}}
These directories [...]]]></description>
		<link>http://bsd.dischaos.com/2009/09/02/rpm-build-environment-on-centos/</link>
			</item>
	<item>
		<title>Graphing Alteon configuration</title>
		<description><![CDATA[If you happen to use Nortel&#8217;s Alteon load balancers and need something to help you visualise your configuration here&#8217;s a script that produces graphs of connections and dependencies between groups, virtual IPs, real IPs and services in the Alteon configuration. It&#8217;s not very useful, the code is ugly, but the graphs are cool to look [...]]]></description>
		<link>http://bsd.dischaos.com/2009/08/31/graphing-alteon-configuration/</link>
			</item>
	<item>
		<title>Getting all prefixes advertised by an AS</title>
		<description><![CDATA[This simple script displays all prefixes advertised by an AS. It uses RIPE&#8217;s looking glass to get their local BGP table and parses it for the given AS number.
For example, to get all the other networks advertised by the AS dischaos.com is in, first I need to get Layered tech&#8217;s AS number:
whois -h www.ris.ripe.net 216.32.74.94

% [...]]]></description>
		<link>http://bsd.dischaos.com/2009/07/22/getting-all-prefixes-advertised-by-an-as/</link>
			</item>
	<item>
		<title>DNS traceroute</title>
		<description><![CDATA[This helps tracking down bottlenecks in DNS response from recursive queries.
First you need a DNS query payload (contents of a valid udp DNS A type query).
$hostname = &#8220;www.google.com&#8221;;
$header = pack(&#8220;n C2 n4&#8243;, 6666, 1, 0, 1, 0, 0, 0);
for (split(/\./,$hostname)) {
      $lformat .= &#8220;C a* &#8220;;
     [...]]]></description>
		<link>http://bsd.dischaos.com/2009/07/22/109/</link>
			</item>
	<item>
		<title>Nagios plugin template in python</title>
		<description><![CDATA[A template for nagios plugins I use:

#!/usr/bin/env python
import sys, getopt
nagios_codes = &#123;&#8216;OK&#8217;: 0, 
&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#8216;WARNING&#8217;: 1, 
&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#8216;CRITICAL&#8217;: 2,
&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#8216;UNKNOWN&#8217;: 3,
&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#8216;DEPENDENT&#8217;: 4&#125;
def usage&#40;&#41;:
&#160; &#160; &#34;&#34;&#34; returns [...]]]></description>
		<link>http://bsd.dischaos.com/2009/04/29/nagios-plugin-template-in-python/</link>
			</item>
</channel>
</rss>
