Netgear FVS318 FVS318v3 Reference Manual - Page 109

How to Check VPN Connections, Testing the Gateway A FVS318v3 LAN and the Gateway B LAN

Page 109 highlights

Reference Manual for the ProSafe VPN Firewall FVS318v3 How to Check VPN Connections You can test connectivity and view VPN status information on the FVS318v3 (see also "VPN Tunnel Control" on page 5-26). Testing the Gateway A FVS318v3 LAN and the Gateway B LAN 1. Using our example, from a PC attached to the FVS318v3 on LAN A, on a Windows PC click the Start button on the taskbar and then click Run. 2. Type ping -t 172.23.9.1, and then click OK. 3. This will cause a continuous ping to be sent to the LAN interface of Gateway B. Within two minutes, the ping response should change from timed out to reply. 4. At this point the connection is established. 5. To test connectivity between the FVS318v3 Gateway A and Gateway B WAN ports, follow these steps: a. Using our example, log in to the FVS318v3 on LAN A, go to the main menu Maintenance section and click the Diagnostics link. b. To test connectivity to the WAN port of Gateway B, enter 22.23.24.25, and then click Ping. c. This causes a ping to be sent to the WAN interface of Gateway B. Within two minutes, the ping response should change from timed out to reply. You may have to run this test several times before you get the reply message back from the target FVS318v3. d. At this point the connection is established. Note: If you want to ping the FVS318v3 as a test of network connectivity, be sure the FVS318v3 is configured to respond to a ping on the Internet WAN port by checking the check box seen in Figure 4-2 on page 4-3. However, to preserve a high degree of security, you should turn off this feature when you are finished with testing. 6. To view the FVS318v3 event log and status of Security Associations, follow these steps: a. Go to the FVS318v3 main menu VPN section and click the VPN Status link. b. The log screen displays a history of the VPN connections, and the IPSec SA and IKE SA tables will report the status and data transmission statistics of the VPN tunnels for each policy. Advanced Virtual Private Networking January 2005 6-21

  • 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
Advanced Virtual Private Networking
6-21
January 2005
How to Check VPN Connections
You can test connectivity and view VPN status information on the FVS318v3 (see also
“VPN
Tunnel Control” on page 5-26
).
Testing the Gateway A FVS318v3 LAN and the Gateway B LAN
1.
Using our example, from a PC attached to the FVS318v3 on LAN A, on a Windows PC click
the
Start
button on the taskbar and then click
Run
.
2.
Type
ping -t
172.23.9.1
, and then click
OK
.
3.
This will cause a continuous ping to be sent to the LAN interface of Gateway B. Within two
minutes, the ping response should change from timed out to reply.
4.
At this point the connection is established.
5.
To test connectivity between the FVS318v3 Gateway A and Gateway B WAN ports, follow
these steps:
a.
Using our example, log in to the FVS318v3 on LAN A, go to the main menu Maintenance
section and click the
Diagnostics
link.
b.
To test connectivity to the WAN port of Gateway B, enter
22.23.24.25
, and then click
Ping
.
c.
This causes a ping to be sent to the WAN interface of Gateway B. Within two minutes, the
ping response should change from timed out to reply. You may have to run this test several
times before you get the reply message back from the target FVS318v3.
d.
At this point the connection is established.
Note
: If you want to ping the FVS318v3 as a test of network connectivity, be sure the
FVS318v3 is configured to respond to a ping on the Internet WAN port by checking the check
box seen in
Figure 4-2
on
page 4-3
. However, to preserve a high degree of security, you should
turn off this feature when you are finished with testing.
6.
To view the FVS318v3 event log and status of Security Associations, follow these steps:
a.
Go to the FVS318v3 main menu VPN section and click the
VPN Status
link.
b.
The log screen displays a history of the VPN connections, and the IPSec SA and IKE SA
tables will report the status and data transmission statistics of the VPN tunnels for each
policy.