<?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>Brendon Davis &#187; Comms</title>
	<atom:link href="http://brendon.davis.to/category/techstuff/comms/feed/" rel="self" type="application/rss+xml" />
	<link>http://brendon.davis.to</link>
	<description>The place where I'm in charge</description>
	<lastBuildDate>Fri, 30 Jul 2010 03:49:03 +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>CISCO QoS for Dummies</title>
		<link>http://brendon.davis.to/2010/02/05/cisco-qos-for-dummies/</link>
		<comments>http://brendon.davis.to/2010/02/05/cisco-qos-for-dummies/#comments</comments>
		<pubDate>Fri, 05 Feb 2010 07:25:28 +0000</pubDate>
		<dc:creator>brendon</dc:creator>
				<category><![CDATA[Comms]]></category>
		<category><![CDATA[TechStuff]]></category>

		<guid isPermaLink="false">http://brendon.davis.to/?p=593</guid>
		<description><![CDATA[Hey, for all those out there who have as much trouble with the CISCO QoS implementation as I do&#8230;. Here are 4 no so easy steps to configure. Step 1. Access List NOTE: You can specify IP addresses or traffic types here. ip access-list extended &#60;VOICE&#62;  permit udp any any range 16384 32767 ip access-list [...]]]></description>
			<content:encoded><![CDATA[<p>Hey, for all those out there who have as much trouble with the CISCO QoS implementation as I do&#8230;. Here are 4 <span style="text-decoration: line-through;">no so</span> easy steps to configure. <span id="more-593"></span></p>
<p><strong>Step 1. Access List</strong></p>
<p>NOTE: You can specify IP addresses or traffic types here.</p>
<pre>ip access-list extended <em>&lt;VOICE&gt;</em>
 permit udp any any range 16384 32767
ip access-list extended <em>&lt;VOICE-CONTROL&gt;</em>
 remark Match VoIP Control Traffic
 remark SIP
 permit tcp any any range 5060 5061
 permit udp any any range 5060 5061
 remark SCCP
 permit tcp any any range 2000 2002
 remark H323 Fast Start
 permit tcp any any eq 1720
 remark H323 Slow Start
 permit tcp any any range 11000 11999
 remark MGCP
 permit udp any any eq 2427</pre>
<p><strong>Step 2.  Class Map</strong></p>
<p>NOTE: The &#8216;match-all&#8217; or &#8216;match-any&#8217; commands are like using AND/ OR for the access lists specified.</p>
<pre>class-map match-all <em>&lt;VOICE-CONTROL&gt;</em>
 match access-group name <em>&lt;VOICE-CONTROL&gt;
</em>class-map match-any <em>&lt;VOICE&gt;</em>
 match access-group name <em>&lt;VOICE&gt;</em>
 match ip dscp ef
 match ip precedence 5</pre>
<p><strong>Step 3.  Policy Map</strong></p>
<p>NOTE: The &#8216;priority&#8217; command is the same as bandwidth but gives this traffic first access to bandwidth. You can only specify this command once.</p>
<pre>policy-map <em>&lt;VOICEWAN&gt;</em>
 class <em>&lt;VOICE&gt;</em>
    priority <em>&lt;number-kbit&gt;
</em> class <em>&lt;VOICE-CONTROL&gt;</em>
    bandwidth <em>&lt;number-kbit&gt;</em>
 class class-default
    fair-queue</pre>
<p><strong>Step 4. Interface Configuration</strong></p>
<pre>interface &lt;outside_interface&gt;
 bandwidth &lt;number-kbit&gt;
 bandwidth receive &lt;number-kbit&gt;
 service-policy output &lt;VOICEWAN&gt;</pre>
<p>What&#8217;s so hard about that?</p>
]]></content:encoded>
			<wfw:commentRss>http://brendon.davis.to/2010/02/05/cisco-qos-for-dummies/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>New version of ISA &#8211; FFTMG</title>
		<link>http://brendon.davis.to/2009/12/14/fftmg/</link>
		<comments>http://brendon.davis.to/2009/12/14/fftmg/#comments</comments>
		<pubDate>Mon, 14 Dec 2009 04:37:10 +0000</pubDate>
		<dc:creator>brendon</dc:creator>
				<category><![CDATA[Comms]]></category>
		<category><![CDATA[Server]]></category>
		<category><![CDATA[TechStuff]]></category>

		<guid isPermaLink="false">http://brendon.davis.to/?p=536</guid>
		<description><![CDATA[Well it has been a long time coming but Microsoft have finally released a new version of their awesome Internet Acceleration and Security (ISA) server. The last major upgrade was 2004 and since then the product has become a little long in the tooth. There are several new ways the internet is being used and [...]]]></description>
			<content:encoded><![CDATA[<p>Well it has been a long time coming but Microsoft have finally released a new version of their awesome Internet Acceleration and Security (ISA) server. The last major upgrade was 2004 and since then the product has become a little long in the tooth. There are several new ways the internet is being used and ISA 2004/2006 in my opinion just couldn&#8217;t keep up.</p>
<p>Jump over to <a href="http://www.microsoft.com/forefront/threat-management-gateway/en/us/default.aspx">http://www.microsoft.com/forefront/threat-management-gateway/en/us/default.aspx</a> and check out the details on Forfront Threat Management Gateway (FFTMG). Building on the new Windows Server 2008 network stack there are several new features that administrators (myself included) have been crying for:</p>
<ul>
<li>Support for dual/ failover internet links. (using a separate fibre service for remote access and publishing plus a DSL2 service for web access.)</li>
<li>Publishing (Static NAT) rules apply to both inbound and outbound traffic. (ISA would always NAT outbound connections on default IP address.)</li>
<li>Category based Access lists (requires additional licenses) to filter traffic for &#8220;Social Networking&#8221; or &#8220;Known Virus URL&#8217;s&#8221;.</li>
<li>Support in a Hyper-V or ESXi or XenServer virtualised environments.</li>
<li><span style="color: #ff0000;">ONLY RUNS on Windows Server 2008 x64 eddition</span>!!!</li>
</ul>
<p>The old <a href="http://blogs.technet.com/isablog/">ISA server team blog</a> has been updated to reference TMG now also; there are half a dozen articles available here that may help with deployment considerations.</p>
]]></content:encoded>
			<wfw:commentRss>http://brendon.davis.to/2009/12/14/fftmg/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Awesome new AP at home</title>
		<link>http://brendon.davis.to/2009/12/08/wndr3700/</link>
		<comments>http://brendon.davis.to/2009/12/08/wndr3700/#comments</comments>
		<pubDate>Tue, 08 Dec 2009 08:23:09 +0000</pubDate>
		<dc:creator>brendon</dc:creator>
				<category><![CDATA[Comms]]></category>
		<category><![CDATA[TechStuff]]></category>

		<guid isPermaLink="false">http://brendon.davis.to/?p=530</guid>
		<description><![CDATA[As a person that rents, I don&#8217;t have the option to use a patch panel and run CAT6 cables into each of my rooms. I am forced to live with ugly blue cables around the house or compete for spectrum with my neighbours using a wireless network. When I upgraded my MCE one of the [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.netgear.com.au/au/Product/Routers-and-Gateways/Wireless-N/WNDR3700"><img class="alignright size-full wp-image-531" title="WNDR3700" src="http://brendon.davis.to/wp-content/uploads/2009/12/wndr3700.jpg" alt="WNDR3700" width="80" height="154" border="0" /></a>As a person that rents, I don&#8217;t have the option to use a patch panel and run CAT6 cables into each of my rooms. I am forced to live with ugly blue cables around the house or compete for spectrum with my neighbours using a wireless network. When I upgraded my <a href="http://brendon.davis.to/mymce">MCE</a> one of the components I added was a <a href="http://www.netgear.com.au/au/Product/Adapters/RangeMax-Wireless-N-/WN311B">duel radio 802.11n (draft) PCI card</a> with external antenna.</p>
<p>Once 802.11n was released as a certified standard, I started looking around for a new Access Point that would be able to support the HD video content I use around the house. Reading over the forums and reviews I came upon <a href="http://www.smallnetbuilder.com">SmallNetBuilder</a> and their review of the <a href="http://www.smallnetbuilder.com/wireless/wireless-reviews/30925-start-your-buying-netgear-wndr3700-reviewed">NetGear WNDR3700 Wireless GBit router</a>.</p>
<p>The device ran duel radio&#8217;s 802.11abgn, had 4x GBit interfaces and wouldn&#8217;t break the bank. My current <a href="http://www.netcomm.com.au/products/3g/3g18wn?SQ_DESIGN_NAME=support&amp;SQ_PAINT_LAYOUT_NAME=support">NetComm 3G18Wn</a> was running 11n but only had 100Mbit ports and didn&#8217;t work properly with the iPhone. When I received the device I swapped it in place of the NetComm leaving all the wireless details the same.</p>
<ul>
<li><span style="color: #339966;">GOOD</span>: One of the funky features is when using Windows 7, WINDOWS takes you through a wizard to configure and secure the access point. Simply put in the PIN from the bottom of the device, next, next, finish and your AP is configured.</li>
<li><span style="color: #339966;">GOOD</span>: All my existing devices connected without any hassles and transfers between the WHS and PC are much faster using the built-in GBit switch.</li>
<li><span style="color: #339966;">GOOD</span>: There are buttons on the front of the AP which let you enable and disable the wireless plus unlock it for several seconds to let a new device associate.</li>
<li><span style="color: #ff0000;">BAD</span>: My only problem with the device is that it expects to be the internet gateway for your network. If your lucky enough to have a CISCO 877 (with IPv6) as your DSL modem and firewall, the WNDR3700 cannot use a LAN address as the default gateway.</li>
</ul>
<p><span style="color: #0000ff;">OPINION</span>: Well the title says it all. If you don&#8217;t have a 11n access point at the moment, go pick up one of these. It associates at 300MBit and I get at least 80-90Mbit/s throughput over the wireless around home. It can stream WTV files to the MCE plus DVDs to the NetBook at the same time.</p>
]]></content:encoded>
			<wfw:commentRss>http://brendon.davis.to/2009/12/08/wndr3700/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How not to use DHCP Superscopes</title>
		<link>http://brendon.davis.to/2009/12/08/how-not-to-use-dhcp-superscopes/</link>
		<comments>http://brendon.davis.to/2009/12/08/how-not-to-use-dhcp-superscopes/#comments</comments>
		<pubDate>Tue, 08 Dec 2009 07:17:52 +0000</pubDate>
		<dc:creator>brendon</dc:creator>
				<category><![CDATA[Comms]]></category>
		<category><![CDATA[TechStuff]]></category>

		<guid isPermaLink="false">http://brendon.davis.to/?p=515</guid>
		<description><![CDATA[Have you ever needed to run several separate subnets on the same physical network (not VLANs) to use different routers?? A good example of this is a single Wireless network where you want to run more than 243 devices but you don&#8217;t want the overhead of a Class B subnet. Simply create your Class C address [...]]]></description>
			<content:encoded><![CDATA[<p>Have you ever needed to run several separate subnets on the same physical network (not VLANs) to use different routers?? A good example of this is a single Wireless network where you want to run more than 243 devices but you don&#8217;t want the overhead of a Class B subnet.</p>
<p>Simply create your Class C address ranges, each in a separate DHCP scope. Then select all the new scopes and add them to a new superscope. Now when any clients from this network request addresses, they will be sent any address from the appropriate range. More information is in <a href="http://support.microsoft.com/kb/161571">KB161571</a>.</p>
<p>What you don&#8217;t do is use Superscopes to group several VLAN&#8217;s at a single site. That just breaks stuff. (Trust me)</p>
]]></content:encoded>
			<wfw:commentRss>http://brendon.davis.to/2009/12/08/how-not-to-use-dhcp-superscopes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>CITRIX Repeater with WCCP</title>
		<link>http://brendon.davis.to/2009/09/09/repeater-wccp/</link>
		<comments>http://brendon.davis.to/2009/09/09/repeater-wccp/#comments</comments>
		<pubDate>Wed, 09 Sep 2009 04:50:12 +0000</pubDate>
		<dc:creator>brendon</dc:creator>
				<category><![CDATA[CITRIX]]></category>
		<category><![CDATA[Comms]]></category>
		<category><![CDATA[TechStuff]]></category>

		<guid isPermaLink="false">http://brendon.davis.to/?p=350</guid>
		<description><![CDATA[When deploying a CITRIX Repeater (formally known as WANScaler) using WCCP with a cisco router we found that the configuration on the KB isn&#8217;t quite right. Read on for the configuration. The Repeater configuration we used are: The CISCO Router Configuration we used is: ip wccp 51 redirect-list wccp_redirect ip wccp version 2 ! interface [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://brendon.davis.to/wp-content/uploads/2009/08/WCCP-Repeater-Configuration.jpg"></a>When deploying a CITRIX Repeater (formally known as WANScaler) using WCCP with a cisco router we found that the configuration on the KB isn&#8217;t quite right. Read on for the configuration. <span id="more-350"></span></p>
<p>The Repeater configuration we used are:</p>
<p><a href="http://brendon.davis.to/wp-content/uploads/2009/08/WCCP-Repeater-Configuration.jpg"><img class="alignnone size-full wp-image-349" title="WCCP Repeater Configuration" src="http://brendon.davis.to/wp-content/uploads/2009/08/WCCP-Repeater-Configuration.jpg" border="0" alt="WCCP Repeater Configuration" width="534" height="310" /></a><a href="http://brendon.davis.to/wp-content/uploads/2009/08/WCCP-Repeater-Configuration.jpg"></a></p>
<p>The CISCO Router Configuration we used is:</p>
<pre>ip wccp 51 redirect-list wccp_redirect
ip wccp version 2
!
interface FastEthernet0/0
 Description ‘Internal LAN Interface’
 ip address 10.228.3.101 255.255.255.0
 ip wccp 51 redirect in
!
interface FastEthernet0/1
 Description ‘WAN Link’
 ip wccp 51 redirect in
!
ip access-list extended wccp_redirect
 permit host &lt;SourceIP1&gt; any
 permit any host &lt;SourceIP1&gt;
 permit host &lt;SourceIP2&gt; any
 permit any host &lt;SourceIP2&gt; </pre>
<p>You can use the command ‘show ip wccp 51 detail’ and ‘show ip wccp’ to check the tunnel before adding the ‘ip wccp 51 redirect in’ command on the interfaces. And believe me, you don’t want to leave a ‘debug ip wccp packet’ active on a production device that routes 30Mbit of wan traffic. Just in case the redirect list is wrong and the router tries to display all packets flowing through it&#8230;.</p>
]]></content:encoded>
			<wfw:commentRss>http://brendon.davis.to/2009/09/09/repeater-wccp/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Windows IAS for Telstra WAN</title>
		<link>http://brendon.davis.to/2009/08/31/windows-ias-for-telstra-wan/</link>
		<comments>http://brendon.davis.to/2009/08/31/windows-ias-for-telstra-wan/#comments</comments>
		<pubDate>Mon, 31 Aug 2009 04:55:42 +0000</pubDate>
		<dc:creator>brendon</dc:creator>
				<category><![CDATA[Comms]]></category>
		<category><![CDATA[TechStuff]]></category>

		<guid isPermaLink="false">http://brendon.davis.to/?p=327</guid>
		<description><![CDATA[I posted previously on information Telstra needs to configure in order for their RADIUS servers to proxy authentication attempts to a Windows IAS Server. I have been asked for the necessary configuration on the IAS server to work with Telstra. Telstra likes to provide a 10MB document outlining how RADIUS works but not how to [...]]]></description>
			<content:encoded><![CDATA[<p>I <a href="http://brendon.davis.to/2008/08/05/telstra-radius-proxy-to-ias/">posted previously</a> on information Telstra needs to configure in order for their RADIUS servers to proxy authentication attempts to a Windows IAS Server. I have been asked for the necessary configuration on the IAS server to work with Telstra.</p>
<p>Telstra likes to provide a 10MB document outlining how RADIUS works but not how to configure it. Here is a working example of IAS configuration for the Telstra RADIUS servers.</p>
<p><span id="more-327"></span></p>
<p> Step 1: Install IAS (Internet Authentication Service) from the Add/ Remove Programs &#8211; Windows Components menu.</p>
<p>Step 2: In the IAS console, under remote access policies, define a new policy to permit group members dial-in access.</p>
<p><a href="http://brendon.davis.to/wp-content/uploads/2009/08/Policy.jpg"><img class="alignnone size-full wp-image-331" title="Access Policy" src="http://brendon.davis.to/wp-content/uploads/2009/08/Policy.jpg" alt="Access Policy" width="377" height="368" /></a></p>
<p>Note that access can be granted to all users by specifying the &#8216;DOMAIN\Domain Users&#8217; group or to a select set of users by using a new group eg. &#8216;DOMAIN\NextG Dial-up&#8217;.</p>
<p>Use default configuration for all Remote Access Policy tabs, specifying the following settings:</p>
<p><span style="text-decoration: underline;">Advanced<br />
</span>Name                                                Vendor                                                 Value<br />
Ascend-Client-Primary-DNS   Ascend Communications Inc.   &lt;DNS Server IP&gt;<br />
Framed-Pool                                  RADIUS Standard                            pool_001<br />
Framed-Protocol                         RADIUS Standard                            PPP<br />
Service-Type                                 RADIUS Standard                            Framed</p>
<p><span style="text-decoration: underline;">Authentication</span><br />
No EAP Methods<br />
MS-CHAP v2 (Change Password after Expired)<br />
MS-CHAP (Change Password after Expired)<br />
CHAP</p>
<p><span style="text-decoration: underline;">Encryption<br />
</span>x Basic (MPPE 40-bit)<br />
x Strong (MPPE 56 bit)<br />
x Strongest (MPPE 128 bit)<br />
- No encryption</p>
<p>Step 3: Create the RADIUS Clients for both Telstra RADIUS proxy servers. Note that if you manage the default gateway for your site, you will need to send traffic to these IP Addresses via your Telstra WAN link. (Yes I know they are Internet IP addresses&#8230;.)</p>
<p><a href="http://brendon.davis.to/wp-content/uploads/2009/03/radiusservers.jpg"><img class="alignnone size-full wp-image-330" title="Telstra Radius Servers" src="http://brendon.davis.to/wp-content/uploads/2009/03/radiusservers.jpg" alt="Telstra Radius Servers" width="458" height="233" /></a></p>
<p><a href="http://brendon.davis.to/wp-content/uploads/2009/03/serverconfig.jpg"><img class="alignnone size-medium wp-image-329" title="Server Config" src="http://brendon.davis.to/wp-content/uploads/2009/03/serverconfig-269x300.jpg" alt="Server Config" width="188" height="210" /></a></p>
<p>Step 4: For any users that need to authenticate via Radius, you will need to enable &#8216;<a href="http://technet.microsoft.com/en-us/library/cc784581(WS.10).aspx">Store password using reversible encryption</a>&#8216; on the account and have the user change their password. This can either be done on a per-user basis or in the <a href="http://technet.microsoft.com/en-us/library/cc957013.aspx">default domain GPO</a>. <em>Note: That as reversible encrypted passwords, if a Domain Controller was ever compromised by an attacker, they can easily read the current passwords for users off the SAM.</em></p>
<p>Step 5: Test access using the &lt;Username&gt;@&lt;TelstraSpecifiedDomain&gt;. Note that access logs for IAS are stored in the System Event Log.</p>
]]></content:encoded>
			<wfw:commentRss>http://brendon.davis.to/2009/08/31/windows-ias-for-telstra-wan/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Telstra Radius Proxy to IAS</title>
		<link>http://brendon.davis.to/2008/08/05/telstra-radius-proxy-to-ias/</link>
		<comments>http://brendon.davis.to/2008/08/05/telstra-radius-proxy-to-ias/#comments</comments>
		<pubDate>Tue, 05 Aug 2008 11:43:50 +0000</pubDate>
		<dc:creator>brendon</dc:creator>
				<category><![CDATA[Comms]]></category>
		<category><![CDATA[TechStuff]]></category>

		<guid isPermaLink="false">http://brendon.davis.to/?p=314</guid>
		<description><![CDATA[For all those fortunate enough to live in Australia but unfortunate enough to deal with Telstra managed WAN&#8217;s, I have found out the configuration necessary to make the TELSTRA RADIUS proxy servers talk with a Microsoft Internet Authentication Server (IAS). I realise you will probably never need to know this but I&#8217;ll bet my bike I [...]]]></description>
			<content:encoded><![CDATA[<p>For all those fortunate enough to live in Australia but unfortunate enough to deal with Telstra managed WAN&#8217;s, I have found out the configuration necessary to make the TELSTRA RADIUS proxy servers talk with a Microsoft Internet Authentication Server (IAS).</p>
<p>I realise you will probably never need to know this but I&#8217;ll bet my bike I will run into this problem again in the future. You will need to forgive the Double-Dutch, this is the code strait from the Telstra Tech&#8217;s mouth.</p>
<ul>
<li>Under Dial-SMC</li>
<li>Operations to RAN</li>
<li>SS-Accept</li>
<li>Interfere RADIUS</li>
<li>Attribute 88</li>
<li>Framed Port = Att 88 = none (default = gen/sub)</li>
</ul>
<p>I hope this helps you as much as it did me.</p>
]]></content:encoded>
			<wfw:commentRss>http://brendon.davis.to/2008/08/05/telstra-radius-proxy-to-ias/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>ISA 2006 to CISCO L2TP/ IPSec VPN Configuration</title>
		<link>http://brendon.davis.to/2007/10/22/isa-2006-to-cisco-l2tp-ipsec-vpn-configuration/</link>
		<comments>http://brendon.davis.to/2007/10/22/isa-2006-to-cisco-l2tp-ipsec-vpn-configuration/#comments</comments>
		<pubDate>Mon, 22 Oct 2007 06:18:00 +0000</pubDate>
		<dc:creator>brendon</dc:creator>
				<category><![CDATA[Comms]]></category>
		<category><![CDATA[TechStuff]]></category>

		<guid isPermaLink="false">http://brendon.davis.to/2007/10/22/isa-2006-to-cisco-l2tp-ipsec-vpn-configuration/</guid>
		<description><![CDATA[Would you believe, not one web site (indexed by Google) has a simple configuration for ISA to CISCO Site-to-Site VPN using Pre-shared sectets over L2TP/ IPSec. So for anyone that finds this useful, the following configuration should set you right with both the ASA and Routers. :-) This diagram shows the example IP address configuration [...]]]></description>
			<content:encoded><![CDATA[<p>Would you believe, not one web site (indexed by Google) has a simple configuration for ISA to CISCO Site-to-Site VPN using Pre-shared sectets over L2TP/ IPSec. So for anyone that finds this useful, the following configuration should set you right with both the ASA and Routers. :-)</p>
<p><span id="more-221"></span></p>
<p align="center">This diagram shows the example IP address configuration for the sites.<br />
<img src="http://brendon.davis.to/wp-content/uploads/2007/10/site-layout.gif" alt="Example Site Layout" /></p>
<p>Using the ISA Site-to-Site VPN Wizard, create a site using the default values. When prompted for the VPN tunnel endpoint, be sure to enter the Outside address of the Router.</p>
<p><strong>The ISA Server configuration should be</strong>:</p>
<p>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;<br />
Local Tunnel Endpoint: 1.1.1.1<br />
Remote Tunnel Endpoint: 2.2.2.2</p>
<p>IKE Phase I Parameters:<br />
    Mode: Main mode<br />
    Encryption: 3DES<br />
    Integrity: SHA1<br />
    Diffie-Hellman group: Group 2 (1024 bit)<br />
    Authentication method: Pre-shared secret (demosecret)<br />
    Security Association lifetime: 28800 seconds</p>
<p>IKE Phase II Parameters:<br />
    Mode: ESP tunnel mode<br />
    Encryption: 3DES<br />
    Integrity: SHA1<br />
    Perfect Forward Secrecy: ON<br />
    Diffie-Hellman group: Group 2 (1024 bit)<br />
    Time rekeying: ON<br />
    Security Association lifetime: 3600 seconds<br />
    Kbyte rekeying: OFF</p>
<p>Remote Network &#8216;LSE_VPN&#8217; IP Subnets:<br />
    Subnet: 192.168.0.0/255.255.255.0</p>
<p>Local Network &#8216;Internal&#8217; IP Subnets:<br />
    Subnet: 10.0.0.0/255.255.255.0<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;</p>
<p><strong>The necessary CISCO Router configuration should be</strong>:</p>
<p>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;<br />
crypto isakmp policy 1<br />
 encr 3des<br />
 authentication pre-share<br />
 group 2<br />
 lifetime 28800<br />
crypto isakmp key demosecret address 1.1.1.1 no-xauth<br />
!<br />
crypto ipsec transform-set ISA_2006 esp-3des esp-sha-hmac<br />
!<br />
crypto map Head_Office 10 ipsec-isakmp<br />
 set peer 1.1.1.1<br />
 set transform-set ISA_2006<br />
 set pfs group2<br />
 match address 102<br />
 reverse-route<br />
!<br />
interface (inside)<br />
ip address 192.168.0.1 255.255.255.0<br />
ip nat inside<br />
!<br />
interface (outside)<br />
ip address 2.2.2.2 255.255.255.0<br />
ip nat outside<br />
crypto map Head_Office<br />
!<br />
ip nat inside source route-map nonat interface Dialer0 overload<br />
!<br />
access-list 101 remark Permit_Outbound_NAT<br />
access-list 101 deny   ip 192.168.0.0 0.0.0.255 10.0.0.0 0.255.255.255<br />
access-list 101 permit ip 192.168.0.0 0.0.0.255 any<br />
access-list 102 remark Forward_Through_VPN<br />
access-list 102 permit ip 192.168.0.0 0.0.0.255 10.0.0.0 0.255.255.255<br />
!<br />
route-map nonat permit 10<br />
 match ip address 101<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;</p>
<p><strong>The CISCO ASA Device configuration should be</strong>:</p>
<p>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;<br />
interface Vlan1<br />
 nameif inside<br />
 security-level 100<br />
 ip address 192.168.0.1 255.255.255.0<br />
!<br />
interface Vlan2<br />
 nameif outside<br />
 security-level 0<br />
 ip address 2.2.2.2 255.255.255.0<br />
!<br />
access-list In_to_out extended permit ip 192.168.0.0 255.255.255.0 any<br />
access-list outside_20_cryptomap extended permit ip 192.168.0.0 255.255.255.0 10.0.0.0 255.255.255.0<br />
!<br />
global (outside) 1 interface<br />
access-group In_to_out in interface inside<br />
!<br />
crypto ipsec transform-set ESP-3DES-SHA esp-3des esp-sha-hmac<br />
crypto map outside_map 20 set pfs<br />
crypto map outside_map0 20 match address outside_20_cryptomap<br />
crypto map outside_map0 20 set pfs<br />
crypto map outside_map0 20 set peer 1.1.1.1<br />
crypto map outside_map0 20 set transform-set ESP-3DES-SHA<br />
crypto map outside_map0 interface outside<br />
crypto isakmp identity address<br />
crypto isakmp enable outside<br />
crypto isakmp policy 10<br />
 authentication pre-share<br />
 encryption 3des<br />
 hash sha<br />
 group 2<br />
 lifetime 86400<br />
tunnel-group 1.1.1.1 type ipsec-l2l<br />
tunnel-group 1.1.1.1 ipsec-attributes<br />
 pre-shared-key demosecret<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;</p>
<p>For more information on the PIX/ Router/ ASA VPN configurations, have a look at <a href="http://www.cisco.com/en/US/tech/tk583/tk372/technologies_configuration_example09186a008051a69a.shtml">PIX to Router</a>, <a href="http://www.cisco.com/en/US/products/hw/routers/ps221/products_configuration_example09186a008073e078.shtml">Router to Router</a> or <a href="http://www.cisco.com/en/US/products/hw/routers/ps380/prod_configuration_examples_list.html">List of Configuration Examples</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://brendon.davis.to/2007/10/22/isa-2006-to-cisco-l2tp-ipsec-vpn-configuration/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
