Configuring a WatchGuard SOHO to SOHO IPSec Tunnel

More documents

Recommendations

Info

From the Management Station of the SOHO1 With your Web browser, go to the SOHO Configuration Settings page using thePrivate IP address of the SOHO.The default IP address is: 192.168.111.1.2 Click Virtual Private Networking.The Virtual Private Networking screen appears.3 Select Manual SOHO VPN from the drop list. Click Configure.The Manual Configuration page appears.4 Check the box labelled Enable IPSEC Network.5 Complete the following fields:Secure Gateway AddressThe external interface of the remote SOHO. In our example, this would be208.152.24.104 for Site A and 108.200.23.101 for Site B.Remote WINS ServerThe WINS server behind the remote SOHO. This is found on an address in the localnetwork address range behind the other site. In our example, we stored the WINSserver on a computer on Site B with the IP address 10.10.10.254. (This field is optional.)Remote DNS ServerThe DNS server behind the remote SOHO. This is found on an address in the localnetwork address range behind the other site. In our example, we stored the DNS4 WatchGuard SOHO with VPN Manager 2.1
Verifying the Tunnelserver on a computer on Site B with the IP address 10.10.10.253. Note that this can bethe same computer that houses the WINS server. (This field is optional.)Remote DomainThe remote domain behind the remote device (Site B). This is not applicable for aSOHO to SOHO IPSec VPN tunnel. Leave blank. (This field is optional.)Shared KeySimilar to a password, the phrase is used to authenticate both ends of the tunnel toeach other; the shared key must be identical on both sites. In our example,Gu4c4mo!3.Remote Network AddressThe address of the network on the trusted side of the remote SOHO. In our example,we entered the local network address for Site B, 10.10.10.0.Subnet MaskThe mask of the network on the trusted side of the remote SOHO. In our example,255.255.255.0Encryption MethodYou can use either DES or the more secure 3DES. Whichever you select, it must matchthe encryption level set for the remote SOHO.Authentication MethodThe algorithm type (such as MD-5 or SHA-1). It must match the authenticationmethod set for the remote SOHO.Additional Networks Reachable Through TunnelThis is not applicable for a SOHO to SOHO IPSec VPN Tunnel. Leave blank.6 Review the configuration information you have entered. Click Submit at thebottom of the page.7 A page will appear prompting you to reboot the SOHO. Confirm your settings;click Reboot.8 Repeat steps 1 through 7 for the Site B SOHO, using the IP address numbersappropriate to that installation. Make sure that the encryption, authenticationmethod, and shared secret for Site B are exactly the same as for Site A.Verifying the TunnelThe following methods allow you to verify that the tunnel created between the twoSOHO devices is functional and passing communication packets back and forth.• Browse to the remote SOHO: Open a Web browser, such as Internet Explorer orNetscape Navigator. Browse to the private IP address of the remote SOHO. If thebrowser finds the site and opens the page, the tunnel is operational.• Ping the remote SOHO: From a machine behind one SOHO, open a command lineinterface such as MS-DOS Command Prompt (Windows machines). Enter the followingcommand:ping [Remote SOHO Local Network Address]In our example, we could start from a machine behind the Site A SOHO and enter:ping 10.10.10.20This would send a ping command to the Site B local network address. If a reply isreceived from Site B (as opposed to a “request timed out”) the tunnel is operational.IPSec Tunnel Configuration 5
Page 1 and 2: Configuring a WatchGuard SOHO toSOH
Page 3: Configuring the WatchGuard SOHO for
Page 7: Glossary of TermsVPN - Virtual Priv

Configuring a WatchGuard SOHO to SOHO IPSec Tunnel

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?