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

IP Pools, IP pools, IKE Config Mode

Page 132 highlights

5.5. IP Pools Chapter 5. DHCP Services 5.5. IP Pools Overview IP pools are used to offer other subsystems access to a cache of DHCP IP addresses. These addresses are gathered into a pool by internally maintaining a series of DHCP clients (one per IP). The DHCP servers used by a pool can either be external or be DHCP servers defined in NetDefendOS itself. External DHCP servers can be specified as the server on a specific interface or by a unique IP address. Multiple IP Pools can be set up with different identifying names. The primary usage of IP Pools is with IKE Config Mode which a feature used for allocating IP addresses to remote clients connecting through IPsec tunnels. For more information on this see Section 9.4.3.4, "Using Config Mode". Basic IP Pool Options The basic options available for an IP Pool are: DHCP Server behind interface Server filter Specify DHCP Server Address Client IP filter Indicates that the IP pool should use the DHCP server(s) residing on the specified interface. Optional setting used to specify which servers to use. If unspecified any DHCP server on the interface will be used. The order of the provided adddress or ranges (if multiple) will be used to indicate the preferred servers. Specify DHCP server IP(s) in preferred ascending order to be used. Using the IP loopback address 127.0.0.1 indicates that the DHCP server is NetDefendOS itself. Optional setting used to specify which offered IPs are valid to use. In most cases this will be set to the default of all-nets. Alternatively a set of IP ranges might be specified. The filter ensures that only certain IP addresses from DHCP servers are acceptable and is used in the situation where there might be a DHCP server response with an unacceptable IP address. Advanced IP Pool Options Advanced options available for IP Pool configuration are: Routing table Receive interface MAC Range Prefetched leases Maximum free Policy routing table to be used for lookups when resolving the destination interfaces for the configured DHCP servers. "Simulated" receive interface. This can be used in policy based routing rules and/or used to trigger a specific DHCP server rule if the pool is using a DHCP server in NetDefendOS and the IP address of that server has been specified as the loopback interface. A range of MAC addresses that will be use to create "fake" DHCP clients. Used when the DHCP server(s) map clients by the MAC address. An indication of the need for MAC ranges is when the DHCP server keeps giving out the same IP for each client. Specifies the number of leases to keep prefetched. Prefetching will improve performance since there won't be any wait time when a system requests an IP (while there exists prefetched IPs). The maximum number of "free" IPs to be kept. Must be equal to or 132

  • 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

5.5. IP Pools
Overview
IP pools
are used to offer other subsystems access to a cache of DHCP IP addresses. These
addresses are gathered into a pool by internally maintaining a series of DHCP clients (one per IP).
The DHCP servers used by a pool can either be external or be DHCP servers defined in
NetDefendOS itself. External DHCP servers can be specified as the server on a specific interface or
by a unique IP address. Multiple IP Pools can be set up with different identifying names.
The primary usage of IP Pools is with
IKE Config Mode
which a feature used for allocating IP
addresses to remote clients connecting through IPsec tunnels. For more information on this see
Section 9.4.3.4, “Using Config Mode”.
Basic IP Pool Options
The basic options available for an IP Pool are:
DHCP Server behind interface
Indicates that the IP pool should use the DHCP server(s)
residing on the specified interface.
Server filter
Optional setting used to specify which servers to use. If
unspecified any DHCP server on the interface will be used.
The order of the provided adddress or ranges (if multiple) will
be used to indicate the preferred servers.
Specify DHCP Server Address
Specify DHCP server IP(s) in preferred ascending order to be
used. Using the IP loopback address
127.0.0.1
indicates that
the DHCP server is NetDefendOS itself.
Client IP filter
Optional setting used to specify which offered IPs are valid to
use. In most cases this will be set to the default of
all-nets
.
Alternatively a set of IP ranges might be specified. The filter
ensures that only certain IP addresses from DHCP servers are
acceptable and is used in the situation where there might be a
DHCP server response with an unacceptable IP address.
Advanced IP Pool Options
Advanced options available for IP Pool configuration are:
Routing table
Policy
routing
table
to
be
used
for
lookups
when
resolving
the
destination interfaces for the configured DHCP servers.
Receive interface
"Simulated" receive interface. This can be used in policy based routing
rules and/or used to trigger a specific DHCP server rule if the pool is
using a DHCP server in NetDefendOS and the IP address of that server
has been specified as the loopback interface.
MAC Range
A range of MAC addresses that will be use to create "fake" DHCP
clients. Used when the DHCP server(s) map clients by the MAC
address. An indication of the need for MAC ranges is when the DHCP
server keeps giving out the same IP for each client.
Prefetched leases
Specifies the number of leases to keep prefetched. Prefetching will
improve performance since there won't be any wait time when a system
requests an IP (while there exists prefetched IPs).
Maximum free
The maximum number of "free" IPs to be kept. Must be equal to or
5.5. IP Pools
Chapter 5. DHCP Services
132