TP-Link T2600G-28MPS T2600G-28MPSUN V1 User Guide - Page 206

The Process of DHCP

Page 206 highlights

Figure 10-11 DHCP model To meet the different requirements of DHCP clients, DHCP server is always designed to supply hosts with the configuration parameters in three policies. 1) Manual Assignment: For the specific DHCP clients (e.g., web server), the configuration parameters are manually specified by the administrator and are assigned to these clients via a DHCP server. 2) Automatic Assignment: The DHCP server must supplies the configuration parameters to DHCP client with the lease time continued for ever. 3) Dynamic Assignment: A network administrator assigns a range of IP addresses to DHCP server, and each client computer on the LAN is configured to request an IP address from the DHCP server with a fixed period of time (e.g., 2 hours), allowing the DHCP server to reclaim (and then reallocate) IP addresses that are not renewed.  The Process of DHCP DHCP uses UDP as its transport protocol. DHCP messages from a client to a server are sent to the 'DHCP server' port (67), and DHCP messages from a server to a client are sent to the 'DHCP client' port (68). DHCP clients and servers both construct DHCP messages by filling in fields in the fixed format section of the message and appending tagged data items in the variable length option area. The process is shown as follows. Figure 10-12 The Process of DHCP 1) DHCP discover: the client broadcasts messages on the physical subnet to discover available DHCP servers in the LAN. Network administrators can configure a local router (e.g. a relay agent) to forward DHCP-DISCOVER messages to a DHCP server in a different subnet. 2) DHCP offer: Each server who received the DHCP-DISCOVER message may respond a DHCP-OFFER message that includes configuration parameters (in the example below, IP address) to the client. The server unicast the DHCP-OFFER message to the client (using the DHCP/BOOTP relay agent if necessary) if possible, or may broadcast the message to a broadcast address on the client's subnet. 3) DHCP request: A client can receive DHCP offers from multiple servers, but it will accept only one DHCP-OFFER and broadcast a DHCP-REQUEST message which includes the server's 195

  • 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

Figure 10-11 DHCP model
To meet the different requirements of DHCP clients, DHCP server is always designed to supply
hosts with the configuration parameters in three policies.
1)
Manual Assignment: For the specific DHCP clients (e.g., web server), the configuration
parameters are manually specified by the administrator and are assigned to these clients via
a DHCP server.
2)
Automatic Assignment: The DHCP server must supplies the configuration parameters to
DHCP client with the lease time continued for ever.
3)
Dynamic Assignment: A network administrator assigns a range of IP addresses to DHCP
server, and each client computer on the LAN is configured to request an IP address from the
DHCP server with a fixed period of time (e.g., 2 hours), allowing the DHCP server to reclaim
(and then reallocate) IP addresses that are not renewed.
The Process of DHCP
DHCP uses UDP as its transport protocol. DHCP messages from a client to a server are sent to
the 'DHCP server' port (67), and DHCP messages from a server to a client are sent to the 'DHCP
client' port (68). DHCP clients and servers both construct DHCP messages by filling in fields in the
fixed format section of the message and appending tagged data items in the variable length option
area. The process is shown as follows.
F
igure 10-12 The Process of DHCP
1)
DHCP discover: the client broadcasts messages on the physical subnet to discover available
DHCP servers in the LAN. Network administrators can configure a local router (e.g. a relay
agent) to forward DHCP-DISCOVER messages to a DHCP server in a different subnet.
2)
DHCP offer: Each server who received the DHCP-DISCOVER message may respond a
DHCP-OFFER message that includes configuration parameters (in the example below, IP
address) to the client. The server unicast the DHCP-OFFER message to the client (using the
DHCP/BOOTP relay agent if necessary) if possible, or may broadcast the message to a
broadcast address on the client's subnet.
3)
DHCP request: A client can receive DHCP offers from multiple servers, but it will accept only
one DHCP-OFFER and broadcast a DHCP-REQUEST message which includes the server’s
195