<?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>Backdrifter &#187; equinux</title>
	<atom:link href="http://www.backdrifter.com/tags/equinux/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.backdrifter.com</link>
	<description>The personal site of Jared Hanson</description>
	<lastBuildDate>Tue, 22 Jun 2010 22:16:08 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Connecting VPN Tracker to Linksys BEFVP41</title>
		<link>http://www.backdrifter.com/2009/02/18/connecting-vpn-tracker-to-linksys-befvp41/</link>
		<comments>http://www.backdrifter.com/2009/02/18/connecting-vpn-tracker-to-linksys-befvp41/#comments</comments>
		<pubDate>Thu, 19 Feb 2009 04:24:08 +0000</pubDate>
		<dc:creator>Jared Hanson</dc:creator>
				<category><![CDATA[Unknown]]></category>
		<category><![CDATA[equinux]]></category>
		<category><![CDATA[linksys]]></category>
		<category><![CDATA[vpn]]></category>
		<category><![CDATA[vpntracker]]></category>

		<guid isPermaLink="false">http://www.backdrifter.com/?p=127</guid>
		<description><![CDATA[One of my priorities when setting up my new MacBook Pro was to allow VPN access into my home network.  When I&#8217;m working in a cafe, it is occasionally handy to access files or data on a system at my apartment. 
VPNs are notoriosly difficult to configure and maintain, and I wanted something that [...]]]></description>
			<content:encoded><![CDATA[<p>One of my priorities when setting up my new <a href="http://www.apple.com/macbookpro/">MacBook Pro</a> was to allow <a href="http://en.wikipedia.org/wiki/VPN">VPN</a> access into my home network.  When I&#8217;m working in a cafe, it is occasionally handy to access files or data on a system at my apartment. </p>
<p>VPNs are notoriosly difficult to configure and maintain, and I wanted something that would eliminate most of these hassles.  As such, I decided to use <a href="http://www.equinux.com/us/products/vpntracker/index.html">VPN Tracker</a> from <a href="http://www.equinux.com/us/start/index.html">equinux</a> to connect to my <a href="http://www.linksysbycisco.com/US/en/products/BEFVP41">Linksys BEFVP41</a>.</p>
<p>It&#8217;s not how I envision the ideal scenario, and it requires some geek-cred to set up, but it does work.</p>
<p><span id="more-127"></span></p>
<p><b>Add a New Connection</b></p>
<p><a href="/assets/2009/02/18/connecting-vpn-tracker-to-linksys-befvp41/step1.jpg"><img src="/assets/2009/02/18/connecting-vpn-tracker-to-linksys-befvp41/step1-tn.jpg" alt="Step 1" width="125" height="100" class="align-left"/></a> In the initial window that is displayed when launching VPN Tracker, click the + button to add a new connection.  A device selection dialog will appear, allowing you to choose a template of common settings for the particular connection being setup.</p>
<p><a href="/assets/2009/02/18/connecting-vpn-tracker-to-linksys-befvp41/step2.jpg"><img src="/assets/2009/02/18/connecting-vpn-tracker-to-linksys-befvp41/step2-tn.jpg" alt="Step 2" width="225" height="136" class="align-right"/></a> In my case, I am connecting to a Linksys BEFVP41, so I chose the corresponding selection.  equinux provides a <a href="http://www.equinux.com/cms_components/media/vpnt/VPNT_Interop_Howtos/81/Linksys_BEFVP41-4-EN.pdf">how-to</a> for interoperability between VPN Tracker and the BEFVP41.  It&#8217;s based on the previous version of VPN Tracker, but has some good information I suggest reading.</p>
<p><b>Configure the Connection</b></p>
<p><a href="/assets/2009/02/18/connecting-vpn-tracker-to-linksys-befvp41/step3.jpg"><img src="/assets/2009/02/18/connecting-vpn-tracker-to-linksys-befvp41/step3-tn.jpg" alt="Step 3" width="400" height="261" class="center"/></a></p>
<p>There are a lot of toggles to fiddle with under the Basic and Advanced configuration tabs.  To be honest, even I can&#8217;t describe what each is used for.</p>
<p>The first critical setting is <b>VPN Gateway</b>.  This can be either an IP address or host name.  I&#8217;ve chosen to use <a href="http://www.dyndns.com/">DynDNS.com</a> to point a DNS entry to my IP address, which is dynamically assigned by <a href="http://www.att.com/">AT&#038;T</a>.  I recommend this method, as dynamic IP addresses can and will periodically change, potentially leaving you stranded from your network if you are unable to determine the new address.</p>
<p><b>Remote Networks</b> need to be configured as well, so the address range of the internal network is known.  Typical home networks will use 192.168.1.0 / 255.255.255.0.  I&#8217;ve modified my address range just to be different.</p>
<p>Finally, set the <b>Identifiers</b> to Local Endpoint IP Address and Remote Endpoint IP Address.</p>
<p>With those settings, flip the connection switch to on and hope the connection establishes correctly.  If it works, you should be able to issue a ping command to the broadcast address and see responses from the systems on your network.</p>
<p><code>$ ping 192.168.1.255</code></p>
<p>As I previously noted, there are many permutations of settings, both in VPN Tracker and on the Linksys BEFVP41 itself.  As I recall, my Linksys BEFVP41 should be using the factory settings, which I&#8217;ve left alone.  If you encounter trouble, break out the documentation, sharpen your Google search skills, and get ready to learn a whole lot of esoteric network configuration knowledge.  Good luck!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.backdrifter.com/2009/02/18/connecting-vpn-tracker-to-linksys-befvp41/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
