Refer
e
nc
e
Man
ual
for
the
Pr
oSafe
8
02.11
g
Wire
less
VPN F
irewa
ll FVG31
8
VPN Co
nfigur
ation
of NETGEAR
FVS318
v3
B-2
7
BETA
The FVG318-to-VPN Client Case
Client-to-Gateway VPN T
u
nnel Overview
The
ope
rational dif
fere
nce
s be
tween ga
te
way-to-g
atew
ay and
cl
ie
nt-to-gate
way VPN tunnels
a
re
summa
rized as follows:
Ta
ble B-4
.
Policy Summar
y
VPN
C
onsortium Scenari
o:
S
cena
rio 1
Ty
pe
of
VPN
PC/Clie
nt-to-Gateway
Security
Sch
eme:
IKE with Presha
re
d Secret/Key
Date T
ested:
Nove
mb
er
2
004
Model
/F
irmware T
ested:
NETGEAR-Ga
te
w
ay A
F
VS3
18v3 with firmw
are version
v3.0_
14
NETGEAR-Clie
nt B
N
ETGEAR
Pr
o
S
afe
VPN Cl
ient v10.3.5
IP Addre
ssi
ng:
NETGEAR-Ga
te
w
ay A
S
ta
tic IP ad
dress
NETGEAR-Clie
nt B
D
yna
m
ic
IP a
ddress
Ta
ble B-5
.
Diff
ere
n
ce
s bet
w
ee
n VPN t
unne
l t
y
pes
Op
era
tio
n
G
a
tewa
y-to-Gateway VPN T
u
n
n
els
C
lie
n
t-to
-Ga
te
wa
y VPN
T
u
n
n
el
s
Exch
ang
e Mo
de
Main Mode
—The
IP
addre
sse
s o
f both
gatew
ays a
re
kn
own
(espe
ci
ally
whe
n
FQDN is used), so
e
ach gatewa
y
can
use the In
te
rnet
so
urce
of
the traf
fic
for
vali
dation
p
urposes.
A
g
g
res
siv
e Mo
de
—The
IP addre
ss of
the
clien
t is n
ot kn
own i
n adva
nce, so the
g
ateway is progra
m
me
d
to accep
t vali
d
traf
fic sourced from
a
ny
Intern
et lo
cati
on
(i.e., less secure).
Direction
/T
ype
Bo
th
D
ir
ection
s
—Either e
nd
of the
VPN
tu
nne
l ma
y
in
itiate tra
ffic (usua
lly).
R
emo
te
A
cces
s
—Th
e cl
ien
t end
o
f the
VPN tunn
el must in
iti
ate traf
fic beca
use
its IP ad
dress
is
n
ot kno
w
in
advan
ce,
w
hich preve
nt
s the gatew
ay
e
nd of
the
VPN tunn
el fro
m
in
iti
ating traf
fic.
