 VPN
Router Tutorial - Getting it to work with an IPSec Client Part 4: Routing Traffic
across the VPN
We are ALOMST finished
with the configuration process. The last thing we need to do
is tell the client computer to route the correct traffic through the
VPN Connection.
SSH Sentinel 'should' handle the routing
without having to do anything else. Give the next section
(testing the connection) a try before typing in any routing
commands.
IP Schema Review
Home WAN IP: 24.60.60.100 (from your ISP)
Home LAN Router IP: 192.168.100.1
Home LAN IP Network: 192.168.100.0: Subnet
255.255.255.0
Computer on Home LAN: 192.168.100.2
Remote (friends) computer on the Internet:
24.60.60.200
Lets Get To it
Version 1.3 users will
need to activate the VPN connection by right clicking the SSH
Sentinel taskbar icon, selecting Select VPN and then selecting the
VPN connection you created. 1.3 users will get an error
message if the connection fails.
Version 1.2 users will
activate the VPN network with a PING once we set up the
routing.
Routing
From a command prompt (dos
shell) type (with a home LAN computer IP address)
PING 192.168.100.2
You should see
'Destination unreachable' message
This is because the
REMOTE computer does not know how to get to the private
network: 192.168.100.0. Type ROUTE PRINT to see
the current routing table.
To add the home network to
the routing table type in the following
route add
192.168.100.0 mask 255.255.255.0 24.60.60.100
The first number is the
home lan network IP schema, the second is the network mask, and the
third number is the Internet WAN IP address of the VPN router.
This route will go away after the computer is rebooted and will need
to be typed in again.
Under Windows 2000 and XP,
a parameter can be added that will make the route permanent.
route -p add
192.168.100.0 mask 255.255.255.0 24.60.60.100
I suggest putting this
command in a BATCH file so it is easily accessible.
Testing the
connection
From a command prompt (dos
shell) type (with a home LAN computer IP address)
PING 192.168.100.2
For version 1.2 users, it
might take a couple of tries to get this command to work. When
this PING is first run, the VPN connection is established.
This can take up to 60 seconds or so.
If you get a
response, your VPN works!!!
Mounting a network Drive
across the VPN
Our next set is to mount a
shared network drive across the VPN. From the remote computer's file
explorer, select "mount network drive' from the menu.
Next type in the home LAN
computer address and the name of the share this way. In this case,
the computer I want to reach is at 192.168.10.2 and the share name I
set up was 'c'
Your VPN is now
running!
Article TOC |
|
|
If you enjoyed this tutorial, please LINK to it! |
| 
Routing Traffic
Menu:
