D-Link DFL-800-AV-12 User Manual - Page 231

VPN Quickstart Guide, 9.2.1. IPsec LAN to LAN with Pre-shared Keys

Page 231 highlights

9.2. VPN Quickstart Guide Chapter 9. VPN 9.2. VPN Quickstart Guide Later sections in this chapter will explore VPN components in detail. To help put those later sections in context, this section is a quickstart summary of the key steps in VPN setup. It outlines the individual steps in setting up VPNs for the most common VPN scenarios. These are: • IPsec LAN to LAN with Pre-shared Keys • IPsec Roaming Clients with Pre-shared Keys • IPsec Roaming Clients with Certificates • L2TP Roaming Clients with Pre-Shared Keys • L2TP Roaming Clients with Certificates • PPTP Roaming Clients 9.2.1. IPsec LAN to LAN with Pre-shared Keys 1. Create a Pre-shared Key object. 2. Optionally create a new IKE Proposal List object and/or an IPsec Proposal List object if the default list settings are not satisfactory. This will depend on the capabilities of the device at the other side of the tunnel. 3. In Hosts & Networks create IP objects for: • The remote VPN gateway which is the IP address of the network device at the other end of the tunnel (let's call this object remote_gw). • The remote network which lies behind the remote VPN gateway (let's call this object remote_net). • The local network behind the D-Link Firewall which will communicate across the tunnel. Here we will assume that this is the pre-defined address lannet and this network is attached to the NetDefendOS lan interface. 4. Create an IPsec Tunnel object (let's call this object ipsec_tunnel). Specify the following tunnel parameters: • Set Local Network to lannet. • Set Remote Network to remote_net. • Set Remote Gateway to remote_gw. • Set Encapsulation mode to Tunnel. • Choose the IKE and IPsec proposal lists to be used. • For Authentication select the Pre-shared Key object defined in step (1) above. The IPsec Tunnel object can be treated exactly like any NetDefendOS Interface object in later steps. 5. Set up two IP rules in the IP rule set for the tunnel: • An Allow rule for outbound traffic that has the previously defined ipsec_tunnel object as 231

  • 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
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355

9.2. VPN Quickstart Guide
Later sections in this chapter will explore VPN components in detail. To help put those later
sections in context, this section is a quickstart summary of the key steps in VPN setup.
It outlines the individual steps in setting up VPNs for the most common VPN scenarios. These are:
IPsec LAN to LAN with Pre-shared Keys
IPsec Roaming Clients with Pre-shared Keys
IPsec Roaming Clients with Certificates
L2TP Roaming Clients with Pre-Shared Keys
L2TP Roaming Clients with Certificates
PPTP Roaming Clients
9.2.1. IPsec LAN to LAN with Pre-shared Keys
1.
Create a
Pre-shared Key
object.
2.
Optionally create a new
IKE Proposal List
object and/or an
IPsec Proposal List
object if the
default list settings are not satisfactory. This will depend on the capabilities of the device at the
other side of the tunnel.
3.
In
Hosts & Networks
create IP objects for:
The remote VPN gateway which is the IP address of the network device at the other end of
the tunnel (let's call this object
remote_gw
).
The remote network which lies behind the remote VPN gateway (let's call this object
remote_net
).
The local network behind the D-Link Firewall which will communicate across the tunnel.
Here we will assume that this is the pre-defined address
lannet
and this network is attached
to the NetDefendOS
lan
interface.
4.
Create an
IPsec Tunnel
object (let's call this object
ipsec_tunnel
). Specify the following tunnel
parameters:
Set
Local Network
to
lannet
.
Set
Remote Network
to
remote_net
.
Set
Remote Gateway
to
remote_gw
.
Set
Encapsulation mode
to
Tunnel
.
Choose the IKE and IPsec proposal lists to be used.
For
Authentication
select the
Pre-shared Key
object defined in step
(1)
above.
The
IPsec Tunnel
object can be treated exactly like any NetDefendOS
Interface
object in later
steps.
5.
Set up two IP rules in the IP rule set for the tunnel:
An
Allow
rule for outbound traffic that has the previously defined
ipsec_tunnel
object as
9.2. VPN Quickstart Guide
Chapter 9. VPN
231