<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Unflappings &#187; pfSense</title>
	<atom:link href="http://blog.unflap.com/category/howtos/pfsense/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.unflap.com</link>
	<description>Network and Systems Documentation</description>
	<lastBuildDate>Wed, 11 Aug 2010 18:13:16 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Pfsense 1.2.3 vs Vyatta CE 5 benchmark</title>
		<link>http://blog.unflap.com/2010/03/25/pfsense-1-2-3-vs-vyatta-ce-5-benchmark/</link>
		<comments>http://blog.unflap.com/2010/03/25/pfsense-1-2-3-vs-vyatta-ce-5-benchmark/#comments</comments>
		<pubDate>Thu, 25 Mar 2010 15:21:34 +0000</pubDate>
		<dc:creator>Andrew</dc:creator>
				<category><![CDATA[Benchmarks]]></category>
		<category><![CDATA[FreeBSD]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Vyatta]]></category>
		<category><![CDATA[pfSense]]></category>
		<category><![CDATA[benchmark]]></category>
		<category><![CDATA[intel]]></category>
		<category><![CDATA[iperf]]></category>
		<category><![CDATA[jetway]]></category>
		<category><![CDATA[realtek]]></category>

		<guid isPermaLink="false">http://blog.unflap.com/?p=164</guid>
		<description><![CDATA[Background While I have been a pfSense user for about 2 years, I decided to see how the FreeBSD base OS would stack up against Vyatta, a Linux base free router software package. Without going into too much detail, main differences currently is a more CLI centric interface (close to JunOS &#8220;set&#8221; syntax) for Vyatta [...]]]></description>
		<wfw:commentRss>http://blog.unflap.com/2010/03/25/pfsense-1-2-3-vs-vyatta-ce-5-benchmark/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Configuring CARP on pfSense</title>
		<link>http://blog.unflap.com/2009/12/30/configuring-carp-on-pfsense/</link>
		<comments>http://blog.unflap.com/2009/12/30/configuring-carp-on-pfsense/#comments</comments>
		<pubDate>Wed, 30 Dec 2009 16:01:51 +0000</pubDate>
		<dc:creator>Andrew</dc:creator>
				<category><![CDATA[FreeBSD]]></category>
		<category><![CDATA[HowTos]]></category>
		<category><![CDATA[pfSense]]></category>
		<category><![CDATA[carp]]></category>
		<category><![CDATA[failover]]></category>
		<category><![CDATA[networking]]></category>

		<guid isPermaLink="false">http://blog.unflap.com/?p=146</guid>
		<description><![CDATA[Purpose With any firewall and gateway, the issue of a single point of failure is always present. In order to mitigate this Common Address Redundancy Protocol was invented for the BSD world. For those of you coming from a Cisco or other network gear manufacturer, this functions at a high level the same as VRRP [...]]]></description>
		<wfw:commentRss>http://blog.unflap.com/2009/12/30/configuring-carp-on-pfsense/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Dual Boot pfSense for Testing New Versions</title>
		<link>http://blog.unflap.com/2009/12/28/dual-boot-pfsense-for-testing-new-versions/</link>
		<comments>http://blog.unflap.com/2009/12/28/dual-boot-pfsense-for-testing-new-versions/#comments</comments>
		<pubDate>Mon, 28 Dec 2009 21:38:59 +0000</pubDate>
		<dc:creator>Andrew</dc:creator>
				<category><![CDATA[FreeBSD]]></category>
		<category><![CDATA[HowTos]]></category>
		<category><![CDATA[Operating Systems]]></category>
		<category><![CDATA[pfSense]]></category>
		<category><![CDATA[boot]]></category>
		<category><![CDATA[bootloader]]></category>
		<category><![CDATA[dual boot]]></category>

		<guid isPermaLink="false">http://blog.unflap.com/?p=128</guid>
		<description><![CDATA[Recently pfSense 2.0 was released into beta stages, and as an avid 1.2.x line user, I was eager to check it out. I did still want the ability to rollback to a previous version if things were too unstable, so I configured dual booting the stable 1.2.x line with the experimental 2.0 build. Note this [...]]]></description>
		<wfw:commentRss>http://blog.unflap.com/2009/12/28/dual-boot-pfsense-for-testing-new-versions/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Fixing VLAN Recognition on pfSense 1.2 and Realtek RTL8110SC NIC</title>
		<link>http://blog.unflap.com/2009/12/28/fixing-vlan-recognition-on-pfsense-1-2-and-realtek-rtl8110sc-nic/</link>
		<comments>http://blog.unflap.com/2009/12/28/fixing-vlan-recognition-on-pfsense-1-2-and-realtek-rtl8110sc-nic/#comments</comments>
		<pubDate>Mon, 28 Dec 2009 18:51:43 +0000</pubDate>
		<dc:creator>Andrew</dc:creator>
				<category><![CDATA[FreeBSD]]></category>
		<category><![CDATA[Quick Fixes]]></category>
		<category><![CDATA[pfSense]]></category>
		<category><![CDATA[fix]]></category>
		<category><![CDATA[hardware]]></category>
		<category><![CDATA[networking]]></category>
		<category><![CDATA[realtek]]></category>

		<guid isPermaLink="false">http://blog.unflap.com/?p=125</guid>
		<description><![CDATA[If you are using pfSense (and possibly FreeBSD for that matter) you may have run into the problem of VLAN interfaces not responding after a reboot or interface creation. This leads to serious problems when this is your main router platform, as independent network segments are unable to communication. Symptoms of this include: Systems can [...]]]></description>
		<wfw:commentRss>http://blog.unflap.com/2009/12/28/fixing-vlan-recognition-on-pfsense-1-2-and-realtek-rtl8110sc-nic/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->