Filter
Top Products
Page 36 | AlliedWare™ OS How To Note: VPNs for Corporate Networks
How to test your VPN solution
If the following tests show that your tunnel is not working, see the How To Note How To
Troubleshoot A Virtual Private Network (VPN).
Check the
LANs are
reachable
The simplest way to test a tunnel is to ping from one LAN to the other.
From a PC attached to one peer, ping a PC attached to the other peer. For example, you can
test the VPN between branch office
1
and headquarters by pinging any PC in the branch
office
1
LAN from any PC in the headquarters LAN. If a PC in the branch office
1
LAN has an
address of
1
92.
1
68.
1
4
1
.
1
, that means using the following command at the command prompt
on a PC at headquarters:
ping 192.168.141.1
If a Microsoft Windows PC’s IP address was assigned dynamically, you can find out what it is
by using the following command at the command prompt:
ipconfig
Check traffic
goes through
the VPN
To tell if traffic passes through the tunnel, perform a traceroute from one LAN to the
other—so from a PC attached to one peer, perform a traceroute to a PC attached to the
other peer. For example, if a PC in the branch office
1
LAN has an address of
1
92.
1
68.
1
4
1
.
1
,
that means using the following command at the command prompt on a (Windows) PC at
headquarters:
tracert 192.168.141.1
If traffic goes through the tunnel, the traceroute may display IP addresses from one or both
peers’ private networks and public interfaces. If it shows other public IP addresses, then
traffic is not passing through the tunnel.