D-Link DWS-3160-24TC DWS-3160 Series Web UI Reference Guide - Page 504

Certificate Generation on the Access Point

Page 504 highlights

DWS-3160 Series Gigabit Ethernet Unified Switch Web UI Reference Guide Each wireless device has a copy of a certificate of the device with which it needs to communicate. During TLS connection establishment the Wireless devices compare the certificate received on the connection setup with all available loaded certificates for other wireless devices. If a matching certificate is found then the certificate verification succeeds. The verification function does not attempt to correlate the IP address of the device with the certificate and it does not check the certificate expiration date. The TLS connections are configured to validate the certificates only on the initial connection setup. The connection reauthentications don't trigger new certificate validation attempts. Certificate Generation on the Access Point: The AP auto-generates an X.509 certificate when it boots. At boot time the AP checks whether the key file and the certificate file already exists. If the files exist then the AP uses them, otherwise the AP generates the files. The /etc/uwskey.pem file contains the 1024 bit private key. The /etc/uwscert.pem file contains the X.509 certificate. In order to regenerate the AP certificates the administrator may issue a "factory-reset" command on the AP or delete the two files from the file system and reboot the AP. Certificate Generation on the Switch: The Switch auto-generates an X.509 certificate and other key files when it boots. At boot time the Switch checks whether the certificate and key files exist, and if they don't then the Switch generates the files. The administrator can re-generate the X.509 certificates used by the Wireless component. Note that Diffie-Hellman keys are not regenerated. The wireless feature should be disabled while the keys are being regenerated. If mutual authentication is enabled then the Switch must be re-provisioned before it can join the cluster. IP Address Assignment The Wireless Switches are assigned IP addresses by the administrator. The routing package is included into the product and the routing is enabled by default. Besides the existing System interface, the administrator may create a routing interface optionally. The wireless software automatically selects the IP Address of the lowest interface index. The System interface is always the interface with the lowest index "1". If the System interface is deleted then the software automatically selects the IP address of a lowest index routing interface. If no interfaces are defined then the wireless function is disabled. Disabling the interface or changing the IP address of the interface disables the wireless function. If another interface exists then the wireless function starts using it automatically. Once an interface is selected the wireless function continues to use that interface until the interface goes down. Changing the IP address of the network interface automatically disables and re-enables the wireless function. The administrator has the option to disable automatic IP address assignment for the Wireless function and enter a static IPv4 address. The IP address must be the same as an address of an active routing interface in order for the Wireless function to work. If the interface with the specified address doesn't exist or is not active then the Wireless function is disabled and the WLAN Switch Disable Reason is set to "No Active Interface for Statically Configured IP Address". If the static IP address is configured when the Wireless feature is already enabled then if the configured static IP address is different from the current IP address used by the Wireless feature then the Wireless feature is automatically disabled and re-enabled with the new IP address. If the configured static IP address is already being used by the Wireless feature then the Wireless feature is not disabled and service to the wireless clients is not interrupted. IP Tunnel versus MBA and IMPB When Wireless Switches enables IP tunneling for wireless clients, the MAC of the wireless tunnel client has the highest priority. MBA and IMPB will not work to limit the wireless tunnel client MAC. In addition, when a wireless tunnel client is added by Wireless Switch, the Wireless Switch will notify the MBA module to remove the client MAC if it added the MAC. 499

  • 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

DWS-3160 Series Gigabit Ethernet Unified Switch Web UI Reference Guide
499
Each wireless device has a copy of a certificate of the device with which it needs to communicate. During TLS
connection establishment the Wireless devices compare the certificate received on the connection setup with all
available loaded certificates for other wireless devices. If a matching certificate is found then the certificate
verification succeeds. The verification function does not attempt to correlate the IP address of the device with the
certificate and it does not check the certificate expiration date.
The TLS connections are configured to validate the certificates only on the initial connection setup. The connection
reauthentications don't trigger new certificate validation attempts.
Certificate Generation on the Access Point:
The AP auto-generates an X.509 certificate when it boots. At boot time the AP checks whether the key file and the
certificate file already exists. If the files exist then the AP uses them, otherwise the AP generates the files. The
/etc/uwskey.pem file contains the 1024 bit private key. The /etc/uwscert.pem file contains the X.509 certificate.
In order to regenerate the AP certificates the administrator may issue a "factory-reset" command on the AP or
delete the two files from the file system and reboot the AP.
Certificate Generation on the Switch:
The Switch auto-generates an X.509 certificate and other key files when it boots. At boot time the Switch checks
whether the certificate and key files exist, and if they don't then the Switch generates the files.
The administrator can re-generate the X.509 certificates used by the Wireless component. Note that Diffie-Hellman
keys are not regenerated. The wireless feature should be disabled while the keys are being regenerated. If mutual
authentication is enabled then the Switch must be re-provisioned before it can join the cluster.
The Wireless Switches are assigned IP addresses by the administrator. The routing package is included into the
product and the routing is enabled by default. Besides the existing System interface, the administrator may create a
routing interface optionally. The wireless software automatically selects the IP Address of the lowest interface index.
The System interface is always the interface with the lowest index “1”. If the System interface is deleted then the
software automatically selects the IP address of a lowest index routing interface. If no interfaces are defined then
the wireless function is disabled.
IP Address Assignment
Disabling the interface or changing the IP address of the interface disables the wireless function. If another
interface exists then the wireless function starts using it automatically.
Once an interface is selected the wireless function continues to use that interface until the interface goes down.
Changing the IP address of the network interface automatically disables and re-enables the wireless function.
The administrator has the option to disable automatic IP address assignment for the Wireless function and enter a
static IPv4 address. The IP address must be the same as an address of an active routing interface in order for the
Wireless function to work. If the interface with the specified address doesn’t exist or is not active then the Wireless
function is disabled and the WLAN Switch Disable Reason is set to “No Active Interface for Statically Configured IP
Address”.
If the static IP address is configured when the Wireless feature is already enabled then if the configured static IP
address is different from the current IP address used by the Wireless feature then the Wireless feature is
automatically disabled and re-enabled with the new IP address. If the configured static IP address is already being
used by the Wireless feature then the Wireless feature is not disabled and service to the wireless clients is not
interrupted.
When Wireless Switches enables IP tunneling for wireless clients, the MAC of the wireless tunnel client has the
highest priority. MBA and IMPB will not work to limit the wireless tunnel client MAC.
IP Tunnel versus MBA and IMPB
In addition, when a wireless tunnel client is added by Wireless Switch, the Wireless Switch will notify the MBA
module to remove the client MAC if it added the MAC.