D-Link DFL-260 Product Manual - Page 188

Setting Up OSPF, Routing Action, Type 2, OSPF Router Process, Autonomous Area, OSPF Area

Page 188 highlights

4.5.5. Setting Up OSPF Chapter 4. Routing A Routing Action is used to manipulate and export routing changes to one or more local routing tables. Destination Offset Metric Offset Metric Type 2 Limit Metric To Static Route Override Default Route Override Specifies into which routing table the route changes to the OSPF AS should be imported. Increases the metric by this value. Increases the Type 2 router's metric by this value. Limits the metrics for these routes to a minimum and maximum value. If a route has a higher value than specified then it will be set to the specified value. Allows the override of the static routes. Allows the override of the default route. 4.5.5. Setting Up OSPF Setting up OSPF can seem complicated because of the large number of configuration possibilities that OSPF offers. However, in many cases a simple OSPF solution using a minimum of NetDefendOS objects is needed and setup can be straightforward. Let us examine again the simple scenario described earlier with just two NetDefend Firewalls. In this example we connect together the two NetDefend Firewalls with OSPF so they can share the routes in their routing tables. Both will be inside a single OSPF area which will be part of a single OSPF autonomous system (AS). If you are unfamiliar with these OSPF concepts, refer to earlier sections for an explanation. Beginning with just one of these firewalls, the NetDefendOS setup steps are as follows: 1. Create an OSPF Router object Create a NetDefendOS OSPF Router Process object. This will represent an OSPF Autonomous Area (AS) which is the highest level in the OSPF hierarchy. Give the object an appropriate name. The Router ID can be left blank since this will be assigned automatically by NetDefendOS. 2. Add an OSPF Area to the OSPF Router Within the OSPF Router Process created in the previous step, add a new OSPF Area object. Assign an appropriate name and use the value 0.0.0.0 for the Area ID. An AS can have multiple areas but in many cases only one is needed. The ID 0.0.0.0 identifies this area as the backbone area which forms the central portion of the AS. 3. Add OSPF Interfaces to the OSPF Area Within the OSPF Area created in the previous step, add a new OSPF Interface for each physical interface that will be part of the area. The OSPF Interface object needs the following parameters specified in its properties: • Interface - the physical interface which will be part of the OSPF area. • Network - the network on the interface that will be part of the area. This does not need to be specified and if it is not, the network assigned to the physical interface is used. For example if lan is the interface then lannet will be the default network. • Interface Type - this would normally be Auto so that the correct type is automatically selected. 188

  • 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
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368
  • 369
  • 370
  • 371
  • 372
  • 373
  • 374
  • 375
  • 376
  • 377
  • 378
  • 379
  • 380
  • 381
  • 382
  • 383
  • 384
  • 385
  • 386
  • 387
  • 388
  • 389
  • 390
  • 391
  • 392
  • 393
  • 394
  • 395
  • 396
  • 397
  • 398
  • 399
  • 400
  • 401
  • 402
  • 403
  • 404
  • 405
  • 406
  • 407
  • 408
  • 409
  • 410
  • 411
  • 412
  • 413
  • 414
  • 415
  • 416
  • 417
  • 418
  • 419
  • 420
  • 421
  • 422
  • 423
  • 424
  • 425
  • 426
  • 427
  • 428
  • 429
  • 430
  • 431
  • 432
  • 433
  • 434
  • 435
  • 436
  • 437
  • 438
  • 439
  • 440
  • 441
  • 442
  • 443
  • 444
  • 445
  • 446
  • 447
  • 448
  • 449
  • 450
  • 451
  • 452
  • 453
  • 454
  • 455
  • 456
  • 457
  • 458
  • 459
  • 460
  • 461
  • 462
  • 463
  • 464
  • 465
  • 466
  • 467
  • 468
  • 469
  • 470
  • 471
  • 472
  • 473
  • 474
  • 475
  • 476
  • 477
  • 478
  • 479
  • 480
  • 481
  • 482
  • 483
  • 484
  • 485
  • 486
  • 487
  • 488
  • 489
  • 490
  • 491
  • 492
  • 493
  • 494
  • 495
  • 496
  • 497
  • 498
  • 499
  • 500
  • 501
  • 502
  • 503
  • 504
  • 505
  • 506
  • 507
  • 508
  • 509
  • 510
  • 511
  • 512
  • 513
  • 514
  • 515
  • 516
  • 517
  • 518
  • 519
  • 520
  • 521
  • 522
  • 523
  • 524
  • 525
  • 526
  • 527
  • 528
  • 529
  • 530
  • 531
  • 532
  • 533
  • 534
  • 535
  • 536
  • 537
  • 538
  • 539
  • 540
  • 541
  • 542
  • 543
  • 544
  • 545

A
Routing Action
is used to manipulate and export routing changes to one or more local routing
tables.
Destination
Specifies into which routing table the route changes to the OSPF
AS should be imported.
Offset Metric
Increases the metric by this value.
Offset Metric Type 2
Increases the
Type 2
router's metric by this value.
Limit Metric To
Limits the metrics for these routes to a minimum and maximum
value. If a route has a higher value than specified then it will be
set to the specified value.
Static Route Override
Allows the override of the static routes.
Default Route Override
Allows the override of the default route.
4.5.5. Setting Up OSPF
Setting up OSPF can seem complicated because of the large number of configuration possibilities
that OSPF offers. However, in many cases a simple OSPF solution using a minimum of
NetDefendOS objects is needed and setup can be straightforward.
Let us examine again the simple scenario described earlier with just two NetDefend Firewalls.
In this example we connect together the two NetDefend Firewalls with OSPF so they can share the
routes in their routing tables. Both will be inside a single OSPF area which will be part of a single
OSPF autonomous system (AS). If you are unfamiliar with these OSPF concepts, refer to earlier
sections for an explanation.
Beginning with just one of these firewalls, the NetDefendOS setup steps are as follows:
1.
Create an OSPF Router object
Create a NetDefendOS
OSPF Router Process
object. This will represent an OSPF
Autonomous Area
(AS) which is the highest level in the OSPF hierarchy. Give the object an appropriate name. The
Router ID
can be left blank since this will be assigned automatically by NetDefendOS.
2.
Add an OSPF Area to the OSPF Router
Within the
OSPF Router Process
created in the previous step, add a new
OSPF Area
object. Assign
an appropriate name and use the value
0.0.0.0
for the
Area ID
.
An AS can have multiple areas but in many cases only one is needed. The ID
0.0.0.0
identifies this
area as the
backbone area
which forms the central portion of the AS.
3.
Add OSPF Interfaces to the OSPF Area
Within the
OSPF Area
created in the previous step, add a new
OSPF Interface
for each physical
interface that will be part of the area.
The
OSPF Interface
object needs the following parameters specified in its properties:
Interface
- the physical interface which will be part of the OSPF area.
Network
- the network on the interface that will be part of the area.
This does not need to be specified and if it is not, the network assigned to the physical interface
is used. For example if
lan
is the interface then
lannet
will be the default network.
Interface Type
- this would normally be
Auto
so that the correct type is automatically selected.
4.5.5. Setting Up OSPF
Chapter 4. Routing
188