Howto Linksys - Revision history

Admin: /* Additional Considerations */

2013-01-09T05:22:03Z

Additional Considerations

2012-09-03T21:01:04Z

Gateway Configuration - GroupVPN

2012-09-03T20:55:47Z

Local Identity sub-tab

2012-09-03T20:55:28Z

Remote Identity sub-tab

2012-09-03T20:55:07Z

Phase 2 Tab

2012-09-03T20:54:40Z

Phase 1 Tab

2012-09-03T20:54:04Z

Policy Tab

2012-09-03T20:53:36Z

Policy Tab

2012-09-03T20:52:50Z

Additional Considerations

2012-09-03T20:52:39Z

Additional Considerations

@@ Line 168: / Line 168: @@
 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) <br/>
 Remote Procedure Call (RPC) Locator

@@ Line 17: / Line 17: @@
 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)]]
+[[File:Lynksys-img1.png]]
 ==== Add new group VPN ====
@@ Line 27: / Line 27: @@
 *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)]]
+[[File:Lynksys-img2.png]]
 ==== Local Group Setup ====
@@ Line 35: / Line 35: @@
 *Subnet mask should autopopulate with the mask of the LAN.<br>
-[[Image(http://www.shrew.net/static/howto/Linksys/3_local-group.png)]]
+[[File:Lynksys-img3.png]]
 ==== Remote Client Setup ====
@@ Line 43: / Line 43: @@
 {This value will be needed when configuring the client}<br>
-[[Image(http://www.shrew.net/static/howto/Linksys/4_remote-client.png)]]
+[[File:Lynksys-img4.png]]
 ==== IPSec Setup ====
@@ Line 63: / Line 63: @@
 *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)]]
+[[File:Lynksys-img5.png]]
 Select the 'Advanced' button for further options<br><br>
@@ Line 75: / Line 75: @@
 . NAT Traversal<br><br>
-[[Image(http://www.shrew.net/static/howto/Linksys/6_advanced.png)]]
+[[File:Lynksys-img6.png]]
 == Client Configuration ==

@@ Line 113: / Line 113: @@
 ==== 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>
+Idntification Type was configured into the router, see section titled Remote Client Setup above for these values.
-Identification Type 'Fully Qualified Domain Name'<br>
+This guide uses:
-FQDN String 'shrew.net'<br><br>
+* Identification Type 'Fully Qualified Domain Name'<br>
 ==== Remote Identity sub-tab ====

@@ Line 119: / Line 119: @@
 ==== Remote Identity sub-tab ====
-Idntification Type was configured into the router, see section titled Local Group Setup above.  This guide uses;<br>
+Idntification Type was configured into the router, see section titled Local Group Setup above.
-Identification Type 'IP Address'<br>
+This guide uses:
-Enable 'Use a discovered remote host address'<br><br>
+* Identification Type 'IP Address'<br>
 ==== Credentials sub-tab ====

@@ Line 143: / Line 143: @@
 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 Algorithm 'esp-aes'<br>
-Transform Key Length '256' Bits<br>
+* Transform Key Length '256' Bits<br>
-HMAC Algorithm 'sha1'<br>
+* HMAC Algorithm 'sha1'<br>
-PFS Exchange 'group 2'<br>
+* PFS Exchange 'group 2'<br>
-Compress Algorithm 'disabled'<br>
+* Compress Algorithm 'disabled'<br>
-Key Life Time limit '3600' Secs (default)<br>
+* Key Life Time limit '3600' Secs (default)<br>
-Key Life Data limit '0' Kbytes (default)<br><br>
+* Key Life Data limit '0' Kbytes (default)<br><br>
 === Policy Tab ===

@@ Line 131: / Line 131: @@
 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>
+* Exchange Type 'aggresive'<br>
-DH Exchange 'group 2'<br>
+* DH Exchange 'group 2'<br>
-Cipher Algorithm 'aes'<br>
+* Cipher Algorithm 'aes'<br>
-Cipher Key Length '256' Bits<br>
+* Cipher Key Length '256' Bits<br>
-Hash Algorithm 'sha1'<br>
+* Hash Algorithm 'sha1'<br>
-Key Life Time Limit '28800' (default)<br>
+* Key Life Time Limit '28800' (default)<br>
-Key Life Data limit '0' (default)<br><br>
+* Key Life Data limit '0' (default)<br><br>
 === Phase 2 Tab ===

@@ Line 156: / Line 156: @@
 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'
+* Select 'Add'
-In the new window Set Type 'Include' (default)
+** In the new window Set Type 'Include' (default)
-Address of the remote LAN.  (Our example remote LAN is 192.168.0.0)
+** 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)
+** Netmask of the remote LAN (Our example remote LAN netmask is 255.255.255.0)
+* Select 'Save'
 == Additional Considerations ==

@@ Line 167: / Line 167: @@
 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.<br>
-Remote Procedure Call (RPC)<br>
+Remote Procedure Call (RPC)
-Remote Procedure Call (RPC) Locator<br><br>
+Remote Procedure Call (RPC) Locator
 == Credits ==