Basic Virtual Private Networking 5-1
January 2005

Chapter 5

Basic Virtual Private Networking

This chapter describes how to use the virtual private networking (VPN) features of the FVS318v3
VPN Firewall. VPN communications paths are called tunnels. VPN tunnels provide secure,
encrypted communications between your local network and a remote network or computer.
The VPN information is organized as follows:
“Overview of VPN Configuration” on page 5-2 provides an overview of the two most
common VPN configurations: client-to-gateway and gateway-to-gateway.
“Planning a VPN” on page 5-3 provides the VPN Committee (VPNC) recommended default
parameters set by the VPN Wizard.
“VPN Tunnel Configuration” on page 5-5 summarizes the two ways to configure a VPN
tunnel: VPN Wizard (recommended for most situations) and Advanced (see Chapter 6,
“Advanced Virtual Private Networking).
“How to Set Up a Client-to-Gateway VPN Co nfiguration” on page 5-5 provides the steps
needed to configure a VPN tunnel b etween a remote PC and a network gateway using the VPN
Wizard and the NETGEAR ProSafe VPN Client.
“How to Set Up a Gateway-to-Gateway VPN Configuration” on page 5-20 provides the steps
needed to configure a VPN tunnel between two network gateways using the VPN Wizard.
“VPN Tunnel Control” on page 5-26 provides the step-by-step procedures for activating,
verifying, deactivating, and deleting a VPN tun nel once the VPN tunnel has been configu red .
Chapter 6, “Advanced Virtual Private Networking” provides the steps needed to configure
VPN tunnels when there are special circumstances and the VPNC recommended defaults of
the VPN Wizard are inappropriate.
Appendix C, “Virtual Private Networking” discusses Virtual Private Networking (VPN)
Internet Protocol security (IPSec). IPSec is one of the most complete , secure, and
commercially available, standards-based protocols developed for transporting data.
Appendix E, “VPN Configuration of NET GEAR FVS318 v3” presents a case study on how to
configure a secure IPSec VPN tunnel from a NETGEAR FVS318v3 to a FVL328. This case
study follows the VPN Consortium interoperability profile guidelines (found at
http://www.vpnc.org/InteropProfiles/Interop-01.html).