The Fvg318-To-Vpn Client Case; Client-To-Gateway Vpn Tunnel Overview - NETGEAR ProSafe FVG318 Reference Manual

Reference Manual for the ProSafe Wireless 802.11g VPN Firewall Model FVG318

The FVG318-to-VPN Client Case

Table B-1. Policy Summary
VPN Consortium Scenario:
Type of VPN
Security Scheme:
Date Tested:
Model/Firmware Tested:
NETGEAR-Gateway A
NETGEAR-Client B
IP Addressing:
NETGEAR-Gateway A
NETGEAR-Client B

Client-to-Gateway VPN Tunnel Overview

The operational differences between gateway-to-gateway and client-to-gateway VPN tunnels are
summarized as follows:
Table B-2. Differences between VPN tunnel types
Operation
Exchange Mode
Direction/Type
VPN Configuration of NETGEAR FVG318
Scenario 1
PC/Client-to-Gateway
IKE with Preshared Secret/Key
FVG318 with firmware version v1.0
NETGEAR ProSafe VPN Client v10.3.5
Static IP address
Dynamic IP address
Gateway-to-Gateway VPN Tunnels
Main Mode—The IP addresses of both
gateways are known (especially when
FQDN is used), so each gateway can
use the Internet source of the traffic for
validation purposes.
Both Directions—Either end of the VPN
tunnel may initiate traffic (usually).
v1.0, October 2005
Client-to-Gateway VPN Tunnels
Aggressive Mode—The IP address of
the client is not known in advance, so the
gateway is programmed to accept valid
traffic sourced from any Internet location
(i.e., less secure).
Remote Access—The client end of the
VPN tunnel must initiate traffic because
its IP address is not know in advance,
which prevents the gateway end of the
VPN tunnel from initiating traffic.
C-15