<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.networkworld.com/community" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>VPN</title>
 <link>http://www.networkworld.com/community/taxonomy/term/813</link>
 <description>Showing new posts in a forum view</description>
 <language>en</language>
<item>
 <title>The Trouble with IPsec VPNs, Part#3: IKE Phase 1 Success</title>
 <link>http://www.networkworld.com/community/node/34485</link>
 <description>&lt;p align=&quot;left&quot;&gt;I have surfaced again after a busy few weeks - and I can finally continue my description of IPsec VPN troubleshooting (sorry about the delay). This time I&amp;#39;ll take a closer look at IKE Phase 1 (main mode) troubleshooting.&lt;/p&gt;&lt;p align=&quot;left&quot;&gt;Before getting into an analysis of specific problems that can occur with IKE Phase 1, it&amp;#39;s a good idea to use the debug crypto isakmp command to examine an example of successful IKE Phase 1 negotiation. This negotiation takes place between two IPsec VPN gateways called Tokyo and Osaka: &lt;span class=&#039;read-more&#039;&gt;&lt;a href=&quot;http://www.networkworld.com/community/node/34485&quot;&gt;&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;Read more&lt;/strong&gt;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;</description>
 <comments>http://www.networkworld.com/community/node/34485#comments</comments>
 <category domain="http://www.networkworld.com/community/taxonomy/term/13658">3des</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/704">authentication</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/590">CCIE</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/3651">DES</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/568">encryption</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/13657">ike</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/1993">IPSec</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/58">security</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/17004">tunnel</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/813">VPN</category>
 <pubDate>Mon, 27 Oct 2008 11:37:26 -0400</pubDate>
 <dc:creator>Mark_Lewis</dc:creator>
 <guid isPermaLink="false">34485 at http://www.networkworld.com/community</guid>
</item>
<item>
 <title>Fix for Cisco VPN Error 51</title>
 <link>http://www.networkworld.com/community/node/34169</link>
 <description>&lt;p&gt;I don&amp;#39;t use Apple Macs but I do use Cisco VPN client software. However, it appears to me that Cisco VPN &lt;img style=&quot;width: 87px; height: 63px&quot; src=&quot;/graphics/community/cisco-vpn-client.jpg&quot; alt=&quot;&quot; width=&quot;87&quot; height=&quot;63&quot; align=&quot;right&quot; /&gt;and Macs sometimes have problems with each other (that much was pointed out by &lt;a href=&quot;/community/node/25383&quot;&gt;blogger Rob Slifka&lt;/a&gt; back in February). &lt;span class=&#039;read-more&#039;&gt;&lt;a href=&quot;http://www.networkworld.com/community/node/34169&quot;&gt;&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;Read more&lt;/strong&gt;&lt;/a&gt;&lt;/span&gt;</description>
 <comments>http://www.networkworld.com/community/node/34169#comments</comments>
 <category domain="http://www.networkworld.com/community/taxonomy/term/47">Cisco</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/9829">Cisco VPN client</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/16992">Cisco VPN client for Mac OS</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/58">security</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/813">VPN</category>
 <pubDate>Fri, 17 Oct 2008 18:14:15 -0400</pubDate>
 <dc:creator>Cisco Subnet</dc:creator>
 <guid isPermaLink="false">34169 at http://www.networkworld.com/community</guid>
</item>
<item>
 <title>DMVPN: How this Cisco IOS technology can help cut 70% off your corporate phone bill, Part 1</title>
 <link>http://www.networkworld.com/community/node/33369</link>
 <description>&lt;p&gt;&lt;em&gt;If you work with Cisco IOS you need to know about &lt;/em&gt;&lt;a href=&quot;http://www.cisco.com/en/US/docs/ios/12_2t/12_2t13/feature/guide/ftgreips.html#wp1039425&quot;&gt;&lt;em&gt;DMVPN&lt;/em&gt;&lt;/a&gt;&lt;em&gt; - the Dynamic Multipoint Virtual Private Network, which could help to cut up to 70% off your company&amp;#39;s telephone bill. George Morton, dual CCIE 18532, &lt;img style=&quot;width: 63px; height: 71px&quot; src=&quot;/graphics/community/george-morton2.jpg&quot; alt=&quot;&quot; width=&quot;63&quot; height=&quot;71&quot; align=&quot;right&quot; /&gt;Router/Switch &amp;amp; Security of IT consultancy &lt;/em&gt;&lt;a href=&quot;http://www.madisonsolutions.net&quot;&gt;&lt;em&gt;Madison Solutions&lt;/em&gt;&lt;/a&gt;&lt;em&gt;, has written a whitepaper about this Cisco technology, which we will post over two parts. Part 1 begins today (Update: &lt;a href=&quot;/community/node/33545&quot;&gt;Part 2 is here&lt;/a&gt;.)&lt;/em&gt;  &lt;/p&gt;&lt;p&gt;Dynamic Multipoint Virtual Private Network, (DMVPN) is an idea whose time has come.  Now the telephone companies don’t want you to read about DMVPN.  So if you love your telephone company and don’t want to save up to 70% off your current telephone bill stop reading now. &lt;/p&gt;&lt;p&gt;With up to 70% savings over your current MPLS and Frame Relay networks you are going to have understand DMVPN.  So even if not today, DMVPN is in your future, so let’s start today. &lt;/p&gt;&lt;p&gt;Part 1 of this series will introduce DMVPN and Part 2 will discuss configurations. Later on, we’ll also publish articles that will discuss DMVPN in various applications that support business-to-business, supplier, customer, employee and stakeholders.  &lt;span class=&#039;read-more&#039;&gt;&lt;a href=&quot;http://www.networkworld.com/community/node/33369&quot;&gt;&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;Read more&lt;/strong&gt;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;</description>
 <comments>http://www.networkworld.com/community/node/33369#comments</comments>
 <category domain="http://www.networkworld.com/community/taxonomy/term/47">Cisco</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/3626">Cisco VPN</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/16453">DMVPN</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/16454">Dynamic Multipoint Virtual Private Network</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/16455">George Morton</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/16456">Madison Solutions</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/813">VPN</category>
 <pubDate>Mon, 29 Sep 2008 17:59:25 -0400</pubDate>
 <dc:creator>Cisco Subnet</dc:creator>
 <guid isPermaLink="false">33369 at http://www.networkworld.com/community</guid>
</item>
<item>
 <title>The Trouble with IPsec VPNs, Part#2: Methodology</title>
 <link>http://www.networkworld.com/community/node/32338</link>
 <description>  &lt;p&gt;A while back, I started blogging on the subject of &lt;a href=&quot;/community/node/29893&quot;&gt;IPsec troubleshooting&lt;/a&gt;. In that blog post, I mentioned that in order to successfully troubleshoot IPsec in a fast and efficient manner it is necessary to have a good knowledge of how IPsec works and to follow a good troubleshooting methodology.&lt;/p&gt;&lt;p align=&quot;left&quot;&gt;So, in this blog post, I am going to describe a simple and efficient troubleshooting methodology. This methodology is shown in the following figure:&lt;/p&gt;&lt;p align=&quot;left&quot;&gt;Figure 1: IPsec Troubleshooting Methodology&lt;/p&gt;&lt;p align=&quot;left&quot;&gt;&lt;img src=&quot;/graphics/community/0902-ml.jpg&quot; alt=&quot;&quot; width=&quot;453&quot; height=&quot;572&quot; /&gt; &lt;span class=&#039;read-more&#039;&gt;&lt;a href=&quot;http://www.networkworld.com/community/node/32338&quot;&gt;&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;Read more&lt;/strong&gt;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;</description>
 <comments>http://www.networkworld.com/community/node/32338#comments</comments>
 <category domain="http://www.networkworld.com/community/taxonomy/term/13658">3des</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/3650">AES</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/2746">Cisco</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/3651">DES</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/13657">ike</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/1993">IPSec</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/58">security</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/813">VPN</category>
 <pubDate>Fri, 05 Sep 2008 17:26:02 -0400</pubDate>
 <dc:creator>Mark_Lewis</dc:creator>
 <guid isPermaLink="false">32338 at http://www.networkworld.com/community</guid>
</item>
<item>
 <title>Securing the Line Part 5 - Media Encryption</title>
 <link>http://www.networkworld.com/community/node/32163</link>
 <description>As discussed earlier, VLANs, ACLs, and firewall policies are extremely important components to any converged network security architecture.  However, what these methods &lt;em&gt;do not&lt;/em&gt; secure is the content &lt;em&gt;within&lt;/em&gt; each call or conversation.

The industry is moving towards securing each media path used for voice, video, and data communication.  Even internally, there are many threats that may potentially compromise the &lt;em&gt;content&lt;/em&gt; within the packets transmitted over an IP network.
 &lt;span class=&#039;read-more&#039;&gt;&lt;a href=&quot;http://www.networkworld.com/community/node/32163&quot;&gt;&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;Read more&lt;/strong&gt;&lt;/a&gt;&lt;/span&gt;</description>
 <comments>http://www.networkworld.com/community/node/32163#comments</comments>
 <category domain="http://www.networkworld.com/community/taxonomy/term/317">Asterisk</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/1110">Avaya</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/2746">Cisco</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/8929">Digium</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/568">encryption</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/1993">IPSec</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/1098">Nortel</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/15631">SRTP</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/15632">TLS</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/220">VoIP</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/813">VPN</category>
 <pubDate>Tue, 02 Sep 2008 17:12:31 -0400</pubDate>
 <dc:creator>Matthew Nickasch</dc:creator>
 <guid isPermaLink="false">32163 at http://www.networkworld.com/community</guid>
</item>
<item>
 <title>Securing the Line Part 3 - Access Control</title>
 <link>http://www.networkworld.com/community/node/31684</link>
 <description>Yesterday we discussed the use of Virtual LANs (VLANs) to segment and separate voice and data networks.  This level of separation significantly increases security across both the data and voice networks, and also provides yet another of complication for any would-be hacker.

While Voice VLANs sound like a good idea (and they are), they&#039;re practically useless without the proper inter-VLAN routing configuration and safeguards.  LAN segmentation means virtually nothing without access control lists, firewalls, and policies to route and protect data on both VLANs. 
 &lt;span class=&#039;read-more&#039;&gt;&lt;a href=&quot;http://www.networkworld.com/community/node/31684&quot;&gt;&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;Read more&lt;/strong&gt;&lt;/a&gt;&lt;/span&gt;</description>
 <comments>http://www.networkworld.com/community/node/31684#comments</comments>
 <category domain="http://www.networkworld.com/community/taxonomy/term/47">Cisco</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/29">Data Center</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/33">E-commerce</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/1035">General discussions</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/22">LANs / WANs</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/21">Network Management</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/84">Outsourcing</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/16">Security</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/30">SMB</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/17">Software</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/26">VoIP / Convergence</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/715">firewall</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/11150">IP-PBX</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/1253">management</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/14059">phone system</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/58">security</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/2525">VLAN</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/220">VoIP</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/813">VPN</category>
 <pubDate>Tue, 26 Aug 2008 13:51:16 -0400</pubDate>
 <dc:creator>Matthew Nickasch</dc:creator>
 <guid isPermaLink="false">31684 at http://www.networkworld.com/community</guid>
</item>
<item>
 <title> For downtown Denver businesses, DNC conference sparks mass roll out of work from home solutions</title>
 <link>http://www.networkworld.com/community/node/31481</link>
 <description>&lt;p&gt;The Democratic National Convention is in my home state this year. Many of my downtown Denver customers and friends have worked diligently over the past couple months to setup a remote access teleworker solution for their businesses. Projects and timetables were linked to the coming of the DNC, surprise, surprise. Downtown Denver businesses are worried that their employees might not be able to commute in for work everyday. Things like increase in traffic, closings of streets due to motorcades, and the possibility of a perimeter lockdown of the City due to security incidents or threats are all top of mind. This has caused many businesses to look to teleworker solutions as a way to have employees work from home during the DNC and beyond.  &lt;span class=&#039;read-more&#039;&gt;&lt;a href=&quot;http://www.networkworld.com/community/node/31481&quot;&gt;&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;Read more&lt;/strong&gt;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;</description>
 <comments>http://www.networkworld.com/community/node/31481#comments</comments>
 <category domain="http://www.networkworld.com/community/taxonomy/term/47">Cisco</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/1035">General discussions</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/16">Security</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/45">Wireless / Mobile</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/2746">Cisco</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/14952">democratic national convention security</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/14954">denver</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/14951">dnc</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/4620">Heary</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/4641">Jamey Heary</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/14955">jeremy sing</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/58">security</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/14953">teleworker</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/813">VPN</category>
 <pubDate>Mon, 25 Aug 2008 20:47:25 -0400</pubDate>
 <dc:creator>jheary</dc:creator>
 <guid isPermaLink="false">31481 at http://www.networkworld.com/community</guid>
</item>
<item>
 <title>The Trouble with IPsec VPNs, Part#1</title>
 <link>http://www.networkworld.com/community/node/29893</link>
 <description>  &lt;p align=&quot;left&quot;&gt;Depending on their size and configuration, IPsec VPNs can be relatively easy to design and deploy, even if you are not all that knowledgeable about how IPsec actually works. But, if you don&amp;#39;t understand how IPsec works and you don&amp;#39;t apply a good troubleshooting methodology, then when your IPsec VPN breaks or doesn&amp;#39;t work in the first place, you&amp;#39;ll probably have to resort to what I call ‘stab-in-the-dark&amp;#39; (SITD) troubleshooting. &lt;span class=&#039;read-more&#039;&gt;&lt;a href=&quot;http://www.networkworld.com/community/node/29893&quot;&gt;&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;Read more&lt;/strong&gt;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;</description>
 <comments>http://www.networkworld.com/community/node/29893#comments</comments>
 <category domain="http://www.networkworld.com/community/taxonomy/term/13658">3des</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/3650">AES</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/3651">DES</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/1492">ESP</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/13657">ike</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/1993">IPSec</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/58">security</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/813">VPN</category>
 <pubDate>Mon, 14 Jul 2008 13:26:12 -0400</pubDate>
 <dc:creator>Mark_Lewis</dc:creator>
 <guid isPermaLink="false">29893 at http://www.networkworld.com/community</guid>
</item>
<item>
 <title>iPhone to include Cisco VPN</title>
 <link>http://www.networkworld.com/community/node/28628</link>
 <description>&lt;p&gt;As expected, Apple revealed the new iPhone 2.0 Monday. &lt;em&gt;Windows into Silicon Valley &lt;/em&gt;blogger &lt;a href=&quot;http://www.networkworld.com/community/node/28540&quot;&gt;Alex Lewis reports &lt;/a&gt;that it will ship with the Cisco VPN as well as the new 2.0 software including Exchange ActiveSync, and A-GPS. Also see: &lt;em&gt;&lt;a href=&quot;http://www.networkworld.com/news/2008/060908-iphone-20-release-slated-for.html&quot;&gt;iPhone 2.0 release slated for early July&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;&lt;strong&gt;Go to &lt;a href=&quot;http://www.networkworld.com/subnets/cisco/&quot;&gt;Cisco Subnet &lt;/a&gt; for more Cisco news, blogs, discussion forums, security alerts, book giveaways, and more.&lt;/strong&gt;&lt;/blockquote&gt;
</description>
 <comments>http://www.networkworld.com/community/node/28628#comments</comments>
 <category domain="http://www.networkworld.com/community/taxonomy/term/47">Cisco</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/3626">Cisco VPN</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/1188">iPhone</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/813">VPN</category>
 <pubDate>Tue, 10 Jun 2008 00:12:30 -0400</pubDate>
 <dc:creator>Cisco Subnet</dc:creator>
 <guid isPermaLink="false">28628 at http://www.networkworld.com/community</guid>
</item>
<item>
 <title>Security concerns arise for home workers allowed to VPN into company networks, Cisco 800 Series was the perfect fit.</title>
 <link>http://www.networkworld.com/community/node/27947</link>
 <description>  &lt;p&gt;Security concerns arise for home workers allowed to VPN into company networks&lt;/p&gt;&lt;p&gt;I was recently brought in by a company who had a security breach due to a home user who was allowed to create a VPN tunnel back to the home office. This was done by creating an end point to end point connection from the users home wlan router which has a vpn option on it to the home office vpn router. Normally this would not be an issue but the user set up different ssid&amp;#39;s  for home and work, the only ssid that had any type of WEP on it was the one used for the company laptop. The other ssid&amp;#39;s created for home users and children did not have a WEP settings created.  &lt;span class=&#039;read-more&#039;&gt;&lt;a href=&quot;http://www.networkworld.com/community/node/27947&quot;&gt;&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;Read more&lt;/strong&gt;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;</description>
 <comments>http://www.networkworld.com/community/node/27947#comments</comments>
 <category domain="http://www.networkworld.com/community/taxonomy/term/2746">Cisco</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/12180">cisco smb router</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/2562">expert</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/12181">home office</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/8814">Larry Chaffin</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/58">security</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/813">VPN</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/52">wireless</category>
 <pubDate>Mon, 19 May 2008 19:57:46 -0400</pubDate>
 <dc:creator>Larry Chaffin</dc:creator>
 <guid isPermaLink="false">27947 at http://www.networkworld.com/community</guid>
</item>
<item>
 <title>MPLS: How does it work?</title>
 <link>http://www.networkworld.com/community/node/26669</link>
 <description>It is in some ways similar to an internet based VPN (Virtual Private Network) in the setup... but very different as well.&lt;/p&gt;
&lt;p&gt;MPLS in its root is a signal formatting that allows traffic to be tagged and prioritized. Ultimately, carriers either run MPLS over their IP network cloud or some maintain a separate network cloud for MPLS only. Either way, you connect into the cloud via whatever you need. Could be a &lt;a href=&quot;http://www.bandwidtht1.com&quot;&gt;T1&lt;/a&gt; or bonded T1s for one location, full or fractional DS3 for others, etc. &lt;span class=&#039;read-more&#039;&gt;&lt;a href=&quot;http://www.networkworld.com/community/node/26669&quot;&gt;&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;Read more&lt;/strong&gt;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;</description>
 <comments>http://www.networkworld.com/community/node/26669#comments</comments>
 <category domain="http://www.networkworld.com/community/taxonomy/term/21">Network Management</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/9778">DS3</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/739">MPLS</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/9780">T1 LINE</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/813">VPN</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/31">Wide Area Networks</category>
 <pubDate>Sun, 06 Apr 2008 02:09:34 -0400</pubDate>
 <dc:creator>andrenym00</dc:creator>
 <guid isPermaLink="false">26669 at http://www.networkworld.com/community</guid>
</item>
<item>
 <title>Configuring an L2TPv3 Ethernet Pseudowire</title>
 <link>http://www.networkworld.com/community/node/26272</link>
 <description>  &lt;p&gt;As I mentioned last time, L2TPv3 has a plethora of capabilities, including the capability to be used for remote access VPNs, the capability to transport a number of Layer-2 protocols in a pseudowire configuration, the capability to transport MPLS Layer-3 VPN traffic, and the capability to transport IPv6 over an IPv4 backbone network.&lt;/p&gt;&lt;p&gt;In this blog post, I am going to focus on the most popular application for L2TPv3 - pseudowires.&lt;/p&gt;&lt;p&gt;The first question to answer in regard to L2TPv3 pseudowire configuration is, ‘What is a pseudowire?&amp;#39;. As I mentioned briefly last time, a pseudowire is simply an emulated circuit. By using L2TPv3, it is possible to extend a number of layer-2 circuit types over an IP backbone network. &lt;span class=&#039;read-more&#039;&gt;&lt;a href=&quot;http://www.networkworld.com/community/node/26272&quot;&gt;&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;Read more&lt;/strong&gt;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;</description>
 <comments>http://www.networkworld.com/community/node/26272#comments</comments>
 <category domain="http://www.networkworld.com/community/taxonomy/term/22">LANs / WANs</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/1062">Ethernet</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/8216">l2tp</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/10601">l2tpv3</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/10602">pseudowire</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/813">VPN</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/452">VPNs</category>
 <pubDate>Mon, 24 Mar 2008 18:18:04 -0400</pubDate>
 <dc:creator>Mark_Lewis</dc:creator>
 <guid isPermaLink="false">26272 at http://www.networkworld.com/community</guid>
</item>
<item>
 <title>Apple integrates Cisco’s VPN Client into the iPhone</title>
 <link>http://www.networkworld.com/community/node/25780</link>
 <description>Today Apple announced the details of the iPhone 2.0 software beta.  Many new features are coming to the coolest gadget on the planet.  Of particular interest to me is the integration of Cisco’s VPN client software into the iPhone.  This will be a full blown IPSEC client that will even support the use of certificates or password based multi-factor authentication.   Very nice!  The iPhone VPN client will be able to connect to Cisco VPN gateway devices, like the Cisco ASA and older Cisco PIX.  

Apple also announced support for WPA enterprise with 802.1x authentication coming in the 2.0 code.  This will enable more enterprises to allow the iPhone to connect securely to their wireless infrastructure.  
 &lt;span class=&#039;read-more&#039;&gt;&lt;a href=&quot;http://www.networkworld.com/community/node/25780&quot;&gt;&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;Read more&lt;/strong&gt;&lt;/a&gt;&lt;/span&gt;</description>
 <comments>http://www.networkworld.com/community/node/25780#comments</comments>
 <category domain="http://www.networkworld.com/community/taxonomy/term/47">Cisco</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/1035">General discussions</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/22">LANs / WANs</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/16">Security</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/45">Wireless / Mobile</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/1228">Apple iPhone</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/6461">CIsco ASA</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/3626">Cisco VPN</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/4620">Heary</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/1188">iPhone</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/4641">Jamey Heary</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/813">VPN</category>
 <pubDate>Thu, 06 Mar 2008 23:18:26 -0500</pubDate>
 <dc:creator>jheary</dc:creator>
 <guid isPermaLink="false">25780 at http://www.networkworld.com/community</guid>
</item>
<item>
 <title>Cyber Warfare:  Frontline combat power gets a boost with the new Cisco ASR 1000 Router Series</title>
 <link>http://www.networkworld.com/community/node/25715</link>
 <description>Yesterday, Cisco officially announced its next generation, frontline, cyber superiority Battlestar, known as the Cisco ASR 1000 series routers.   This new edge router series offers a 10 fold+ increase in routing, IPSEC, and Firewall performance versus previous midrange aggregation routers with these services enabled. Much has already been reported on it, but I wanted to focus on &lt;b&gt;security&lt;/b&gt;.  Is the new Cisco ASR 1000 Series unmatched in the raw combat power it is capable of unleashing on its enemies in cyberspace?  Let’s dig into the performance characteristics and combat power of this next-gen edge router to see.   And keeping in mind that raw combat power per se cannot guarantee cyber combat success, we’ll also look into the technological advances that it offers.  
 &lt;span class=&#039;read-more&#039;&gt;&lt;a href=&quot;http://www.networkworld.com/community/node/25715&quot;&gt;&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;Read more&lt;/strong&gt;&lt;/a&gt;&lt;/span&gt;</description>
 <comments>http://www.networkworld.com/community/node/25715#comments</comments>
 <category domain="http://www.networkworld.com/community/taxonomy/term/47">Cisco</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/29">Data Center</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/22">LANs / WANs</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/16">Security</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/2746">Cisco</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/10010">Cisco ASR 1000</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/715">firewall</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/4620">Heary</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/4641">Jamey Heary</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/10119">nbar</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/1074">routers</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/58">security</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/813">VPN</category>
 <pubDate>Wed, 05 Mar 2008 15:51:12 -0500</pubDate>
 <dc:creator>jheary</dc:creator>
 <guid isPermaLink="false">25715 at http://www.networkworld.com/community</guid>
</item>
<item>
 <title>What is MPLS?</title>
 <link>http://www.networkworld.com/community/node/25527</link>
 <description>&lt;p&gt;&lt;/p&gt;&lt;p&gt;It is in some ways similar to an internet based VPN (Virtual Private Network) in the setup... but very different as well.&lt;/p&gt;
&lt;p&gt;MPLS in its root is a signal formatting that allows traffic to be tagged and prioritized. Ultimately, carriers either run MPLS over their IP network cloud or some maintain a separate network cloud for MPLS only. Either way, you connect into the cloud via whatever you need. Could be a &lt;a href=&quot;http://www.bandwidtht1.com&quot;&gt;T1&lt;/a&gt; or bonded T1s for one location, full or fractional DS3 for others, etc. &lt;span class=&#039;read-more&#039;&gt;&lt;a href=&quot;http://www.networkworld.com/community/node/25527&quot;&gt;&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;Read more&lt;/strong&gt;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;
</description>
 <comments>http://www.networkworld.com/community/node/25527#comments</comments>
 <category domain="http://www.networkworld.com/community/taxonomy/term/1035">General discussions</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/9778">DS3</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/739">MPLS</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/9780">T1 LINE</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/813">VPN</category>
 <pubDate>Fri, 29 Feb 2008 02:08:44 -0500</pubDate>
 <dc:creator>andrenym00</dc:creator>
 <guid isPermaLink="false">25527 at http://www.networkworld.com/community</guid>
</item>
<item>
 <title>L2TPv3 Pseudowhat?</title>
 <link>http://www.networkworld.com/community/node/25381</link>
 <description>  &lt;p&gt;L2TPv3 has been around for a while now, but it seems to be one of those things that not too many people know about.&lt;/p&gt;&lt;p&gt;Typically, when I raise the subject of L2TPv3, I get one of the following reactions:&lt;/p&gt;&lt;p&gt;‘L2TPv3 pseudowhat?&amp;#39;&lt;/p&gt;&lt;p&gt;‘Nobody uses that anymore - it&amp;#39;s obsolete, isn&amp;#39;t it?&amp;#39;&lt;/p&gt;&lt;p&gt;‘That&amp;#39;s a good solution for tunnelling PPP, but we&amp;#39;re talking about Ethernet.&amp;#39;&lt;/p&gt;&lt;p&gt;So, for those who aren&amp;#39;t really aware of L2TPv3 or what it can do, I thought I&amp;#39;d blog a little on the subject.&lt;/p&gt;&lt;p&gt;The first thing to say about L2TPv3 is that it is not L2TPv2, but it is based on L2TPv2. And the first thing to say about L2TPv2 is that it is neither L2F nor PPTP, but it is based on both of those protocols. &lt;span class=&#039;read-more&#039;&gt;&lt;a href=&quot;http://www.networkworld.com/community/node/25381&quot;&gt;&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;Read more&lt;/strong&gt;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;</description>
 <comments>http://www.networkworld.com/community/node/25381#comments</comments>
 <category domain="http://www.networkworld.com/community/taxonomy/term/8216">l2tp</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/739">MPLS</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/813">VPN</category>
 <pubDate>Mon, 25 Feb 2008 17:48:32 -0500</pubDate>
 <dc:creator>Mark_Lewis</dc:creator>
 <guid isPermaLink="false">25381 at http://www.networkworld.com/community</guid>
</item>
<item>
 <title>10 wishes for router security</title>
 <link>http://www.networkworld.com/community/node/24969</link>
 <description>&lt;p&gt;&lt;br /&gt;Reader Shaun wrote in with 10 points he&amp;#39;d like to see in router security (our responses are below):&lt;/p&gt;&lt;p&gt;1. Stand-alone Router secured&lt;/p&gt;&lt;p&gt;2. Stand-alone switch secured. Including Port Security features.&lt;/p&gt;&lt;p&gt;3. Stand-alone Router supporting a single secured incoming VPN connection &lt;/p&gt;&lt;p&gt;4. Stand-alone Router supporting maximum secured Wireless&lt;/p&gt;&lt;p&gt;5. Stand-alone Router supporting a VPN across a maximum secured Wireless&lt;/p&gt;&lt;p&gt;6. RIP2/OSPF/EIGRP routing between 2 or more routers done securely with full explanation on how key chains works and what are the relevent/significant parts of configuring key chains.&lt;/p&gt;&lt;p&gt;7. Securing Multiple switches, VLAN&amp;#39;s and VTP Domains.&lt;/p&gt;&lt;p&gt;8. Setting up secure in band Managment Networks &lt;span class=&#039;read-more&#039;&gt;&lt;a href=&quot;http://www.networkworld.com/community/node/24969&quot;&gt;&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;Read more&lt;/strong&gt;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;</description>
 <comments>http://www.networkworld.com/community/node/24969#comments</comments>
 <category domain="http://www.networkworld.com/community/taxonomy/term/47">Cisco</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/9462">packet sniffing</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/5178">port security</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/6491">router security</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/1113">VLANs</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/813">VPN</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/9461">VTP Domains</category>
 <pubDate>Tue, 12 Feb 2008 11:43:58 -0500</pubDate>
 <dc:creator>Gregg_and_Dave</dc:creator>
 <guid isPermaLink="false">24969 at http://www.networkworld.com/community</guid>
</item>
<item>
 <title>Understanding MPLS VPNs, Part I</title>
 <link>http://www.networkworld.com/community/node/24781</link>
 <description>&lt;!--StartFragment--&gt;  &lt;p class=&quot;MsoNormal&quot;&gt;&lt;!--StartFragment--&gt;  &lt;/p&gt;&lt;p class=&quot;MsoNormal&quot;&gt;One of the most compelling drivers for MPLS in service provider networks is its support for Virtual Private Networks (VPNs), in which the provider’s customers can connect geographically diverse sites across the provider’s network. &lt;/p&gt;  &lt;p class=&quot;MsoNormal&quot;&gt;There are three kinds of MPLS-based VPN: &lt;span class=&#039;read-more&#039;&gt;&lt;a href=&quot;http://www.networkworld.com/community/node/24781&quot;&gt;&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;Read more&lt;/strong&gt;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;</description>
 <comments>http://www.networkworld.com/community/node/24781#comments</comments>
 <category domain="http://www.networkworld.com/community/taxonomy/term/739">MPLS</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/813">VPN</category>
 <pubDate>Wed, 06 Feb 2008 21:57:49 -0500</pubDate>
 <dc:creator>jdoyle</dc:creator>
 <guid isPermaLink="false">24781 at http://www.networkworld.com/community</guid>
</item>
<item>
 <title>Choosing the Right Remote Access VPN: 9 Important Questions</title>
 <link>http://www.networkworld.com/community/node/23362</link>
 <description>&lt;p&gt;&lt;font face=&quot;arial,helvetica,sans-serif&quot; size=&quot;2&quot;&gt;&lt;span style=&quot;color: #292526; font-family: Arial&quot;&gt;&lt;font size=&quot;3&quot;&gt;Last time I looked at some important questions to ask when selecting a site-to-site VPN protocol or technology. This time I will discuss some the important questions to ask when choosing a remote access VPN.&lt;/font&gt;&lt;/span&gt;&lt;span style=&quot;color: #292526; font-family: Arial&quot;&gt;&lt;font size=&quot;3&quot;&gt; &lt;/font&gt;&lt;/span&gt;&lt;/font&gt; &lt;span class=&#039;read-more&#039;&gt;&lt;a href=&quot;http://www.networkworld.com/community/node/23362&quot;&gt;&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;Read more&lt;/strong&gt;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;</description>
 <comments>http://www.networkworld.com/community/node/23362#comments</comments>
 <category domain="http://www.networkworld.com/community/taxonomy/term/1993">IPSec</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/8216">l2tp</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/8260">pptp</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/2671">remote access</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/451">SSL</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/813">VPN</category>
 <pubDate>Thu, 27 Dec 2007 16:10:29 -0500</pubDate>
 <dc:creator>Mark_Lewis</dc:creator>
 <guid isPermaLink="false">23362 at http://www.networkworld.com/community</guid>
</item>
<item>
 <title>Which Site-to-Site VPN: 10 Important Questions</title>
 <link>http://www.networkworld.com/community/node/23294</link>
 <description>&lt;p&gt;&lt;span style=&quot;color: #444444&quot;&gt;One of the most common questions that I am asked is what type of VPN an organization should deploy. So, in the hope that it will save some people some time, I thought I’d just go through some of the most basic considerations when choosing a VPN protocol.&lt;/span&gt;&lt;span style=&quot;color: #444444&quot;&gt; &lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style=&quot;color: #444444&quot;&gt;Let’s suppose you’ve decided to deploy a VPN to connect your organization’s/customers’ sites (a site-to-site VPN). But you are not sure which VPN technology and type you should deploy – should it be IPsec, MPLS layer-3, MPLS layer-2, L2TPv3-based, or another technology?&lt;/span&gt;&lt;span style=&quot;color: #444444&quot;&gt; &lt;/span&gt; &lt;span class=&#039;read-more&#039;&gt;&lt;a href=&quot;http://www.networkworld.com/community/node/23294&quot;&gt;&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;Read more&lt;/strong&gt;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;</description>
 <comments>http://www.networkworld.com/community/node/23294#comments</comments>
 <category domain="http://www.networkworld.com/community/taxonomy/term/1993">IPSec</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/8216">l2tp</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/739">MPLS</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/7072">VPLS</category>
 <category domain="http://www.networkworld.com/community/taxonomy/term/813">VPN</category>
 <pubDate>Sat, 22 Dec 2007 21:56:21 -0500</pubDate>
 <dc:creator>Mark_Lewis</dc:creator>
 <guid isPermaLink="false">23294 at http://www.networkworld.com/community</guid>
</item>
</channel>
</rss>
