Netgear FVS336G-100NAS Reference Manual - Page 105

VPN Tunnel Connection Status, Creating a VPN Client Connection: VPN Client to FVS336G

Page 105 highlights

ProSafe Dual WAN Gigabit Firewall with SSL & IPsec VPN FVS336G Reference Manual VPN Tunnel Connection Status Recent VPN tunnel activity is shown on the IPsec Connection Status screen (accessed by selecting VPN from the main menu and Connection Status from the submenu).You can set a Poll Interval (in seconds) to check the connection status of all active IKE Policies to obtain the latest VPN tunnel activity. The Active IPsec (SA)s table also lists current data for each active IPsec SA (Security Association): • Policy Name. The name of the VPN policy associated with this SA. • Endpoint. The IP address on the remote VPN Endpoint. • Tx (KBytes). The amount of data transmitted over this SA. • Tx (Packets). The number of packets transmitted over this SA. • State. The current state of the SA. Phase 1 is "Authentication phase" and Phase 2 is "Key Exchange phase". • Action. Allows you to terminate or build the SA (connection), if required. Creating a VPN Client Connection: VPN Client to FVS336G This section describes how to configure a VPN connection between a Windows PC and the FVS336G VPN firewall. Using the FVS336G's VPN Wizard, we will create a single set of VPN client policies (IKE and VPN) that will allow up to 200 remote PCs to connect from locations in which their IP addresses are unknown in advance. The PCs may be directly connected to the Internet or may be behind NAT routers. If more PCs are to be connected, an additional policy or policies must be created. Each PC will use Netgear's ProSafe VPN Client software. Since the PC's IP address is assumed to be unknown, the PC must always be the initiator of the connection. This procedure was developed and tested using: • Netgear FVS336G ProSafe Dual WAN Gigabit Firewall with SSL & IPsec VPN • Netgear ProSafe VPN Client • NAT router: Netgear FR114P Configuring the FVS336G 1. Start/open the VPN Wizard. Virtual Private Networking Using IPsec v1.0, October 2007 5-17

  • 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

ProSafe Dual WAN Gigabit Firewall with SSL & IPsec VPN FVS336G Reference Manual
Virtual Private Networking Using IPsec
5-17
v1.0, October 2007
VPN Tunnel Connection Status
Recent VPN tunnel activity is shown on the
IPsec Connection Status
screen (accessed by
selecting
VPN
from the main menu and
Connection Status
from the submenu).You can set a Poll
Interval (in seconds) to check the connection status of all active IKE Policies to obtain the latest
VPN tunnel activity. The Active IPsec (SA)s table also lists current data for each active IPsec SA
(Security Association):
Policy Name
. The name of the VPN policy associated with this SA.
Endpoint
. The IP address on the remote VPN Endpoint.
Tx (KBytes)
. The amount of data transmitted over this SA.
Tx (Packets)
. The number of packets transmitted over this SA.
State
. The current state of the SA. Phase 1 is “Authentication phase” and Phase 2 is “Key
Exchange phase”.
Action
. Allows you to terminate or build the SA (connection), if required.
Creating a VPN Client Connection: VPN Client to FVS336G
This section describes how to configure a VPN connection between a Windows PC and the
FVS336G VPN firewall.
Using the FVS336G's VPN Wizard, we will create a single set of VPN client policies (IKE and
VPN) that will allow up to 200 remote PCs to connect from locations in which their IP addresses
are unknown in advance. The PCs may be directly connected to the Internet or may be behind NAT
routers. If more PCs are to be connected, an additional policy or policies must be created.
Each PC will use Netgear's ProSafe VPN Client software. Since the PC's IP address is assumed to
be unknown, the PC must always be the initiator of the connection.
This procedure was developed and tested using:
Netgear FVS336G ProSafe Dual WAN Gigabit Firewall with SSL & IPsec VPN
Netgear ProSafe VPN Client
NAT router: Netgear FR114P
Configuring the FVS336G
1.
Start/open the VPN Wizard.