Netgear FVS318 FVS318 Reference Manual - Page 183

Enter a Remote IPSec Identifier name for the remote Cisco IOS Gateway B. This name

Get Netgear FVS318 - ProSafe VPN Firewall Router PDF manuals and user guides
UPC - 606449023381
View all Netgear FVS318 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 183 highlights

Reference Manual for the Model FVS318 Broadband ProSafe VPN Firewall Figure F-2: NETGEAR FVS318 vA1.4 VPN Settings (part 1) - Main Mode - In the Connection Name box, enter in a unique name for the VPN tunnel to be configured between the NETGEAR devices. For this example we have used "toCiscoIOS". - Enter a Local IPSec Identifier name for the NETGEAR FVS318 Gateway A. This name must be entered in the other endpoint as Remote IPSec Identifier. In this example we used 22.23.24.25 as the local identifier. - Enter a Remote IPSec Identifier name for the remote Cisco IOS Gateway B. This name must be entered in the other endpoint as Local IPSec Identifier. In this example we used 14.15.16.17 as the remote identifier. - Choose "a subnet of local addresses" from the "Tunnel can be accessed from" pull-down menu. - Type the starting LAN IP Address of Gateway A (172.23.9.1 in our example) in the Local IP Local LAN start IP Address field. - Type the LAN Subnet Mask of Gateway A (255.255.255.0 in our example) in the Local LAN IP Subnetmask field. - Choose "a subnet of remote addresses" from the "Tunnel can access" pull-down menu. NETGEAR VPN Configuration FVS318 or FVM318 to Cisco IOS F-3 M-10146-01

  • 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
Reference Manual for the Model FVS318 Broadband
ProSafe VPN Firewall
NETGEAR VPN Configuration FVS318 or FVM318 to Cisco IOS
F-3
M-10146-01
Figure F-2:
NETGEAR FVS318 vA1.4 VPN Settings (part 1) – Main Mode
–
In the Connection Name box, enter in a unique name for the VPN tunnel to be configured
between the NETGEAR devices. For this example we have used “
toCiscoIOS
”.
–
Enter a Local IPSec Identifier name for the NETGEAR FVS318 Gateway A. This name
must be entered in the other endpoint as Remote IPSec Identifier. In this example we used
22.23.24.25
as the local identifier.
–
Enter a Remote IPSec Identifier name for the remote Cisco IOS Gateway B. This name
must be entered in the other endpoint as Local IPSec Identifier. In this example we used
14.15.16.17
as the remote identifier.
–
Choose “a subnet of local addresses” from the “Tunnel can be accessed from” pull-down
menu.
–
Type the starting LAN IP Address of Gateway A (
172.23.9.1
in our example) in the Local
IP Local LAN start IP Address field.
–
Type the LAN Subnet Mask of Gateway A (
255.255.255.0
in our example) in the Local
LAN IP Subnetmask field.
–
Choose “a subnet of remote addresses” from the “Tunnel can access” pull-down menu.