DHCP option 82（国外英文资料）.docVIP

DHCP option 82 When the DHCP server and client are not in the same subnet, if the client wants to assign the IP address from the DHCP server, it must be forwarded by the DHCP relay agent (DHCP Relay Agent) to forward the DHCP request packet. Before the DHCP relay agent will transmit DHCP packets of the client to the DHCP server, you can insert some options for information, so that the DHCP server can accurately know the clients information, which can be more flexible according to the corresponding strategy to assign IP addresses and other parameters. This option is called: DHCP, relay, agent, information, option (relay agent information options), option number 82, it is also known as option 82, the relevant standard document for RFC3046. Option 82 is an extended application of the DHCP option. Option 82 is just an extension of the application, and whether to carry options 82 does not affect the original application of DHCP. Also depends on whether the DHCP server supports option 82. Option 82 does not support the DHCP server receives the message into option 82, option 82 or support DHCP server receives the message without insertion of option 82, these two kinds of circumstances will not affect the original basic DHCP services. To support the extended application of option 82, the DHCP server itself must support option 82 and the received DHCP message must be inserted into option 82 information. A DHCP request message is received from a non trusted port, regardless of whether the DHCP server and client are on the same subnet, and the Cisco switch that opens the DHCP listening function can choose whether to insert option 82 information. By default, the switch inserts option 82 information about the DHCP request message received from the untrusted port. When a converged switch that opens the DHCP listener and a boundary switch (access switch) that inserts the 82 information of the option, is connected: If the switch is connected to the port boundary trust aggregation s