<?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>PacketU</title>
	<atom:link href="http://www.packetu.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.packetu.com</link>
	<description>What&#039;s on your wire[s]?</description>
	<lastBuildDate>Tue, 21 Feb 2012 12:30:14 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Getting Started with Cisco Anyconnect</title>
		<link>http://www.packetu.com/2012/02/21/getting-started-with-cisco-anyconnect/</link>
		<comments>http://www.packetu.com/2012/02/21/getting-started-with-cisco-anyconnect/#comments</comments>
		<pubDate>Tue, 21 Feb 2012 12:30:14 +0000</pubDate>
		<dc:creator>Paul Stewart, CCIE 26009 (Security)</dc:creator>
				<category><![CDATA[security]]></category>
		<category><![CDATA[firewall]]></category>

		<guid isPermaLink="false">http://www.packetu.com/?p=766</guid>
		<description><![CDATA[For the last few years, Cisco has been attempting to do away with what they call the Cisco EZVPN client. This has been the solution used by many corporate users in the mobile workforce for secure access to enterprise data. &#8230; <a href="http://www.packetu.com/2012/02/21/getting-started-with-cisco-anyconnect/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.packetu.com/2012/02/21/getting-started-with-cisco-anyconnect/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>CCIE Routing and Switching Written Exam Resources</title>
		<link>http://www.packetu.com/2012/02/14/ccie-routing-and-switching-written-exam-resources/</link>
		<comments>http://www.packetu.com/2012/02/14/ccie-routing-and-switching-written-exam-resources/#comments</comments>
		<pubDate>Tue, 14 Feb 2012 13:00:45 +0000</pubDate>
		<dc:creator>Paul Stewart, CCIE 26009 (Security)</dc:creator>
				<category><![CDATA[career]]></category>

		<guid isPermaLink="false">http://packetu.com/?p=754</guid>
		<description><![CDATA[Last week I took and passed the CCIE Routing and Switching Written exam (350-001). The first and foremost reason for taking this exam was to re-certify my current CCIE Security certification. Cisco requires any CCIE level written exam to be &#8230; <a href="http://www.packetu.com/2012/02/14/ccie-routing-and-switching-written-exam-resources/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.packetu.com/2012/02/14/ccie-routing-and-switching-written-exam-resources/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Future of the OSI Model</title>
		<link>http://www.packetu.com/2012/02/07/the-future-of-the-osi-model/</link>
		<comments>http://www.packetu.com/2012/02/07/the-future-of-the-osi-model/#comments</comments>
		<pubDate>Tue, 07 Feb 2012 10:30:19 +0000</pubDate>
		<dc:creator>Paul Stewart, CCIE 26009 (Security)</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://packetu.com/wordpress/?p=299</guid>
		<description><![CDATA[The OSI model is that thing that everyone seems to love to hate. The OSI is actually just a model that has its roots in the International Organization for Standardization. We&#8217;ve all had disagreements how certain protocols map to certain &#8230; <a href="http://www.packetu.com/2012/02/07/the-future-of-the-osi-model/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.packetu.com/2012/02/07/the-future-of-the-osi-model/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Migrating ASA NAT Exemption Configuration</title>
		<link>http://www.packetu.com/2012/01/31/migrating-asa-nat-exemption-configuration/</link>
		<comments>http://www.packetu.com/2012/01/31/migrating-asa-nat-exemption-configuration/#comments</comments>
		<pubDate>Tue, 31 Jan 2012 13:00:49 +0000</pubDate>
		<dc:creator>Paul Stewart, CCIE 26009 (Security)</dc:creator>
				<category><![CDATA[security]]></category>
		<category><![CDATA[firewall]]></category>

		<guid isPermaLink="false">http://packetu.com/?p=635</guid>
		<description><![CDATA[NAT exemptions are often required when a single ASA appliance is performing NAT and terminating VPN connections.  In ASA configurations prior to 8.3 and 8.4, NAT exemptions were configured with &#8220;nat 0 access-list &#60;acl name&#62;&#8221; and a related access-list. nat &#8230; <a href="http://www.packetu.com/2012/01/31/migrating-asa-nat-exemption-configuration/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.packetu.com/2012/01/31/migrating-asa-nat-exemption-configuration/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ASA L2L VPN Spoke to Spoke Communication</title>
		<link>http://www.packetu.com/2012/01/23/asa-l2l-vpn-spoke-to-spoke-communication/</link>
		<comments>http://www.packetu.com/2012/01/23/asa-l2l-vpn-spoke-to-spoke-communication/#comments</comments>
		<pubDate>Mon, 23 Jan 2012 15:00:53 +0000</pubDate>
		<dc:creator>Paul Stewart, CCIE 26009 (Security)</dc:creator>
				<category><![CDATA[security]]></category>
		<category><![CDATA[firewall]]></category>

		<guid isPermaLink="false">http://packetu.com/?p=678</guid>
		<description><![CDATA[It seems like some of the more challenging things to do on an ASA involve some sort of traffic being redirected out the same interface it was received on. This article addresses the requirement for spoke to hub to spoke &#8230; <a href="http://www.packetu.com/2012/01/23/asa-l2l-vpn-spoke-to-spoke-communication/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.packetu.com/2012/01/23/asa-l2l-vpn-spoke-to-spoke-communication/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>No SSH After Upgrading to 8.4</title>
		<link>http://www.packetu.com/2012/01/16/no-ssh-after-upgrading-to-8-4/</link>
		<comments>http://www.packetu.com/2012/01/16/no-ssh-after-upgrading-to-8-4/#comments</comments>
		<pubDate>Mon, 16 Jan 2012 07:00:58 +0000</pubDate>
		<dc:creator>Paul Stewart, CCIE 26009 (Security)</dc:creator>
				<category><![CDATA[security]]></category>
		<category><![CDATA[firewall]]></category>

		<guid isPermaLink="false">http://packetu.com/?p=621</guid>
		<description><![CDATA[There are several changes when an ASA is upgraded from 8.2 to 8.4(2). The most notable of these are the ones dealing with the syntax of the NAT configuration. However, there is another gotcha that you might not be expecting. SSH will &#8230; <a href="http://www.packetu.com/2012/01/16/no-ssh-after-upgrading-to-8-4/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.packetu.com/2012/01/16/no-ssh-after-upgrading-to-8-4/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Typical NAT/PAT Configuration Comparison for ASA 8.4</title>
		<link>http://www.packetu.com/2012/01/09/typical-natpat-configuration-comparison-for-asa-8-4/</link>
		<comments>http://www.packetu.com/2012/01/09/typical-natpat-configuration-comparison-for-asa-8-4/#comments</comments>
		<pubDate>Mon, 09 Jan 2012 18:00:00 +0000</pubDate>
		<dc:creator>Paul Stewart, CCIE 26009 (Security)</dc:creator>
				<category><![CDATA[security]]></category>
		<category><![CDATA[firewall]]></category>

		<guid isPermaLink="false">http://packetu.com/?p=567</guid>
		<description><![CDATA[A little while back, I posted an article that took a very simple ASA configuration and migrated it to 8.4. This article takes it a step further and focuses on NAT and PAT, as well as the related access control &#8230; <a href="http://www.packetu.com/2012/01/09/typical-natpat-configuration-comparison-for-asa-8-4/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.packetu.com/2012/01/09/typical-natpat-configuration-comparison-for-asa-8-4/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ASA VPN with Address Overlap</title>
		<link>http://www.packetu.com/2012/01/02/asa-vpn-with-address-overlap/</link>
		<comments>http://www.packetu.com/2012/01/02/asa-vpn-with-address-overlap/#comments</comments>
		<pubDate>Mon, 02 Jan 2012 21:37:41 +0000</pubDate>
		<dc:creator>Paul Stewart, CCIE 26009 (Security)</dc:creator>
				<category><![CDATA[security]]></category>
		<category><![CDATA[firewall]]></category>

		<guid isPermaLink="false">http://packetu.com/?p=647</guid>
		<description><![CDATA[More and more, the Internet is being used as a connection to business partners. Typically this requires building an IPSec Tunnel between two VPN capable endpoints. For me the device of choice is the Cisco ASA. Since we are connecting to a business &#8230; <a href="http://www.packetu.com/2012/01/02/asa-vpn-with-address-overlap/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.packetu.com/2012/01/02/asa-vpn-with-address-overlap/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
	</channel>
</rss>

<!-- Dynamic page generated in 0.537 seconds. -->
<!-- Cached page generated by WP-Super-Cache on 2012-02-22 16:51:25 -->

