View source for Howto Linksys

== Introduction ==

This guide provides information that can be used to configure a Linksys RV-042 or RV-082 router to support IPsec GroupVPN client connectivity. This guide will also provide configuration information when using a Windows XPSP3 client.  The current Linksys firmware version at the time of this writing is Version: 1.3.98-tm  We are using Shrew version 2.1.4.<br><br>

== Overview ==

The Shrew client running on Windows XP will need to know the specifics of the remote WAN/LAN since this Linksys router does not support modcfg (ike push/pull) functionality.<br><br>

== Gateway Configuration ==

This guide assumes familiarity with configuring the Linksys router using its web UI.  This Linksys router allows for multiple WAN links.  This guide assumes WAN1 is the preferred link to use for the remote VPN connectivity.<br><br>

It is suggested to use the routers DDNS feature if the router is assigned a non-static IP address by the ISP.  The Linksys will self register any IP address changes it receives by the ISP with the selected DDNS service.  If the router is in the Americas, it is suggested to create a free account at DynDNS.org and set those values in the routers DDNS configuration area, Setup->More...->DDNS

=== Gateway Configuration - GroupVPN ===

Using the Linksys web UI, navigate to the VPN => Client to Gateway configuration area.

[[Image(http://www.shrew.net/static/howto/Linksys/1_client-2-gateway.png)]]

==== Add new group VPN ====

*Select the Group VPN radio button.<br>
*Group No. is not editable and will auto increment from 1 to 2.  A maximum of 2 GroupVPNs are allowable.<br>
*Group Name: is a unique string used to identify the Group.<br>
*Interface: Default value is WAN1.  This is the interface that remote clients will connect through.<br>
*Enable: Is greyed out.  This option will become available after these changes are "Saved".<br>

[[Image(http://www.shrew.net/static/howto/Linksys/2_new-group-vpn.png)]]

==== Local Group Setup ====

*Local Security Group Type: Choose 'subnet' from the dropdown.  This will allow all systems on the LAN to access the tunnel.<br>
*IP Address should autopopulate with the network IP block of the LAN.<br>
*Subnet mask should autopopulate with the mask of the LAN.<br>

[[Image(http://www.shrew.net/static/howto/Linksys/3_local-group.png)]]

==== Remote Client Setup ====

*Remote Client: Either Domain Name(FQDN) or E-mail Address(USER FQDN) can be selected from the drop down list.  We have selected Domain Name(FQDN) in this guide.<br>
*Domain name: shrew.net<br>
{This value will be needed when configuring the client}<br>

[[Image(http://www.shrew.net/static/howto/Linksys/4_remote-client.png)]]

==== IPSec Setup ====

{Most of the following values will be needed when configuring the Shrew client.<br><br>
*Keying Mode: IKE with Preshared key is auto selected when using GroupVPN<br>
*Phase1 DH Group: We have selected Group 2<br>
{Select Group 1 for network speed or Group 5 for greatest security}<br>
*Phase1 Encryption: We have selected AES-256<br>
{Select DES for lesser but greater speed or up to AES-256 for greatest security}<br>
*Phase1 Authentication: We have selected SHA1<br>
{SHA is recommended because it is more secure}<br>
*Phase1 SA Lifetime: 28800 (default value)<br>
*Perfect Forward Security: enable<br><br>
*Phase2 DH Group: We have selected Group 2<br>
*Phase2 Encryption: We have selected AES-256<br>
*Phase2 Authentication: SHA1<br>
*Phase2 SA Lifetime: 3600 (default)<br>
*Preshared Key: Use up to a 30 digit character or hexadecimal string that is difficult to brute force<br><br>

[[Image(http://www.shrew.net/static/howto/Linksys/5_ipsec-setup.png)]]

Select the 'Advanced' button for further options<br><br>

==== Advanced ====

Aggressive Mode is enabled when using GroupVPN.  This cannot be changed.<br><br>
Enable the following 3 advanced options leaving the rest of the options disabled.
#Keep-Alive
2. NetBIOS Broadcast (If browsing network shares is required)
3. NAT Traversal<br><br>

[[Image(http://www.shrew.net/static/howto/Linksys/6_advanced.png)]]

== Client Configuration ==

As stated earlier, the Linksys router does not support modecfg, so Shrew client will need to be configured with specific information about the connection.  Also, it is suggested to run WINS from the LAN side of the Linksys if network share browsing is required.

Open the Access Manager application and create a new site configuration. Configure the settings listed below in the following tabs.

=== General Tab ===

The Remote Host section must be configured. The Host Name or IP Address is defined as either the static IP address assigned to the WAN interface of the router or it's DDNS hostname.
The Auto Configuration mode should be set to 'disabled'.<br><br>

Set the Address Method to "Use a Virtual Adaptor and assigned address", then choose and address which is NOT in the current range of the Windows XP (client) network (local LAN) AND not in the current range of the LAN side of the Linksys (remote LAN).  For example, <br>
The client used in this guide is on a local LAN of 10.1.1.0 with a subnet of 255.255.255.0.  The LAN side of the Linksys is on a remote LAN of 192.168.0.0 with a subnet of 255.255.255.0.  For this Shrew client configuration, we will choose an address of 192.168.30.0 with a subnet of 255.255.255.0

Set MTU to '1380' (default)<br><br>

=== Client Tab ===

Set NAT Traversal to 'enable'<br>
Nat Traversal Port to '4500' (default)<br>
Keep alive packet rate '15' secs (default)<br>
IKE Fragmentation 'disable'<br><br>

=== Name Resolution Tab ===

Enable WINS and key in the IP address of the WINS server of the remote LAN.<br>
Enable DNS and key in the IP address of the DNS server of the remote LAN.  In most cases, the IP address of the LAN interface of the router will be successful.  The LAN side of the router used in this example is 192.168.0.1<br>
Key in a domain suffix if the remote LAN is set to use such value<br>
DO Not enable 'SPlit DNS', this is not supported by the Linksys<br><br>

=== Authentication Tab ===

Set Authentication Method to 'Mutual PSK' in the drop down menu<br><br>

==== Local Identity sub-tab ====

Idntification Type was configured into the router, see section titled Remote Client Setup above for these values.  This guide uses;<br>
Identification Type 'Fully Qualified Domain Name'<br>
FQDN String 'shrew.net'<br><br>

==== Remote Identity sub-tab ====

Idntification Type was configured into the router, see section titled Local Group Setup above.  This guide uses;<br>
Identification Type 'IP Address'<br>
Enable 'Use a discovered remote host address'<br><br>

==== Credentials sub-tab ====

Key in the Pre-Shared Key, a non-dictionary word that was configured into the router.  See section IPSec Setup above.<br><br>

=== Phase 1 Tab ===

See section IPSec Setup above.  The values that are set in this tab area must match those used in the router configuration.<br><br>

* Exchange Type 'aggresive'<br>
* DH Exchange 'group 2'<br>
* Cipher Algorithm 'aes'<br>
* Cipher Key Length '256' Bits<br>
* Hash Algorithm 'sha1'<br>
* Key Life Time Limit '28800' (default)<br>
* Key Life Data limit '0' (default)<br><br>

=== Phase 2 Tab ===

See section IPSec Setup above.  The values that are set in this tab area must match those used in the router configuration.<br><br>

Transform Algorithm 'esp-aes'<br>
Transform Key Length '256' Bits<br>
HMAC Algorithm 'sha1'<br>
PFS Exchange 'group 2'<br>
Compress Algorithm 'disabled'<br>
Key Life Time limit '3600' Secs (default)<br>
Key Life Data limit '0' Kbytes (default)<br><br>

=== Policy Tab ===

Here we must give access to the Remote LAN network resources.[[BR]
DO Not enable either of the two options under IPSec Policy Configuration, however, select the 'Add' button to include a mapping to the remote LAN.

* Select 'Add'
** In the new window Set Type 'Include' (default)
** Address of the remote LAN.  (Our example remote LAN is 192.168.0.0)
** Netmask of the remote LAN (Our example remote LAN netmask is 255.255.255.0)
* Select 'Save'

== Additional Considerations ==

If browsing directory shares is a requirement and the WINS server is running on the remote LAN and the Shrew client is configured to find WINS, then browsing should be successful using Network Neighborhood.  We have found that starting the following 2 services on the XP client enable the success.

Remote Procedure Call (RPC)
Remote Procedure Call (RPC) Locator

== Credits ==

This guide was submitted by Drew Flickema.  Happy Tunneling <><   <br>
Thanks Shrew!