Netgear FVS318 FVS318v3 Reference Manual - Page 221

The FVS318v3-to-VPN Client Case, Client-to-Gateway VPN Tunnel Overview

Page 221 highlights

Reference Manual for the ProSafe VPN Firewall FVS318v3 The FVS318v3-to-VPN Client Case Table E-4. 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 Scenario 1 PC/Client-to-Gateway IKE with Preshared Secret/Key November 2004 FVS318v3 with firmware version v3.0_14 NETGEAR ProSafe VPN Client v10.3.5 Static IP address Dynamic IP address Client-to-Gateway VPN Tunnel Overview The operational differences between gateway-to-gateway and client-to-gateway VPN tunnels are summarized as follows: Table E-5. Differences between VPN tunnel types Operation Exchange Mode Direction/Type Gateway-to-Gateway VPN Tunnels Client-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. 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). Both Directions-Either end of the VPN tunnel may initiate traffic (usually). 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. VPN Configuration of NETGEAR FVS318v3 January 2005 E-27

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242

Reference Manual for the ProSafe VPN Firewall FVS318v3
VPN Configuration of NETGEAR FVS318v3
E-27
January 2005
The FVS318v3-to-VPN Client Case
Client-to-Gateway VPN Tunnel Overview
The operational differences between gateway-to-gateway and client-to-gateway VPN tunnels are
summarized as follows:
Table E-4.
Policy Summary
VPN Consortium Scenario:
Scenario 1
Type of VPN
PC/Client-to-Gateway
Security Scheme:
IKE with Preshared Secret/Key
Date Tested:
November 2004
Model/Firmware Tested:
NETGEAR-Gateway A
FVS318v3 with firmware version v3.0_14
NETGEAR-Client B
NETGEAR ProSafe VPN Client v10.3.5
IP Addressing:
NETGEAR-Gateway A
Static IP address
NETGEAR-Client B
Dynamic IP address
Table E-5.
Differences between VPN tunnel types
Operation
Gateway-to-Gateway VPN Tunnels
Client-to-Gateway VPN Tunnels
Exchange Mode
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.
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).
Direction/Type
Both Directions
—Either end of the VPN
tunnel may initiate traffic (usually).
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.