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

The Format of DHCP Message

Page 207 highlights

identifier and the IP address offered by the server. Based on the server's identifier, servers are informed whose offer the client has accepted. 4) DHCP acknowledgement: The server selected in the DHCP-REQUEST message commits the binding for the client to persistent storage and responds with a DHCP-ACK message containing the configuration parameters for the requesting client. If the selected server is unable to satisfy the DHCP-REQUEST message (e.g., the requested IP address has been allocated), the server should respond with a DHCP-NAK message. 5) In Dynamic assignment policy, the DHCP client is assigned an IP address with a lease time (e.g. 2 hours) from the DHCP server. This IP address will be reclaimed by the DHCP server when its lease time expires. If the client wants to use the IP address continually, it should unicast a DHCP-REQUEST message to the server to extend its lease. After obtaining parameters via DHCP, a host should be able to exchange packets with any other host in the networks.  The Format of DHCP Message Figure 10-12 The Process of DHCPgives the process of DHCP and Figure 10-13 describes each field in the DHCP message. The numbers in parentheses indicate the size of each field in octets. The names for the fields given in the figure will be used throughout this document to refer to the fields in DHCP messages. Figure 10-13 The Format of DHCP Message 1) op:Message type, '1' = BOOT-REQUEST, '2' = BOOT-REPLY. 2) htype:Hardware address type, '1' for ethernet. 3) hlen:Hardware address length, '6' for ethernet. 4) hops:Clients set this field to zero and broadcast the DHCP-REQUEST message , optionally used by relay-agents when booting via a relay-agent. 5) xid:Transaction ID, a random number chosen by the client, used by the client and server to associate messages. 6) secs:Filled in by client, seconds elapsed since client started trying to boot. 7) flags:A client that cannot receive unicast IP datagrams until its protocol software has been configured with an IP address should set the first bit in the 'flags' field to 1 in any DHCP-DISCOVER or DHCP-REQUEST message that client sends. A client that can receive 196

  • 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

identifier and the IP address offered by the server. Based on the server’s identifier, servers
are informed whose offer the client has accepted.
4)
DHCP acknowledgement: The server selected in the DHCP-REQUEST message commits the
binding for the client to persistent storage and responds with a DHCP-ACK message
containing the configuration parameters for the requesting client. If the selected server is
unable to satisfy the DHCP-REQUEST message (e.g., the requested IP address has been
allocated), the server should respond with a DHCP-NAK message.
5)
In Dynamic assignment policy, the DHCP client is assigned an IP address with a lease time
(e.g. 2 hours) from the DHCP server. This IP address will be reclaimed by the DHCP server
when its lease time expires. If the client wants to use the IP address continually, it should
unicast a DHCP-REQUEST message to the server to extend its lease.
After obtaining parameters via DHCP, a host should be able to exchange packets with any other
host in the networks.
The Format of DHCP Message
F
igure 10-12 The Process of DHCPgives the process of DHCP and Figure 10-13 describes each
field in the DHCP message. The numbers in parentheses indicate the size of each field in octets.
The names for the fields given in the figure will be used throughout this document to refer to the
fields in DHCP messages.
Figure 10-13 The Format of DHCP Message
1)
op
Message type, ‘1’ = BOOT-REQUEST, ‘2’ = BOOT-REPLY.
2)
htype
Hardware address type, '1' for ethernet.
3)
hlen
Hardware address length, '6' for ethernet.
4)
hops
Clients set this field to zero and broadcast the DHCP-REQUEST message , optionally
used by relay-agents when booting via a relay-agent.
5)
xid
Transaction ID, a random number chosen by the client, used by the client and server to
associate messages.
6)
secs
Filled in by client, seconds elapsed since client started trying to boot.
7)
flags
A client that cannot receive unicast IP datagrams until its protocol software has been
configured with an IP address should set the first bit in the 'flags' field to 1 in any
DHCP-DISCOVER or DHCP-REQUEST message that client sends. A client that can receive
196