DHCP Options 43, 55, and 60 and Other Customized Options
Table of Contents
10.1
Expand all | Collapse all
-
- Tap Interfaces
-
- Layer 2 and Layer 3 Packets over a Virtual Wire
- Port Speeds of Virtual Wire Interfaces
- LLDP over a Virtual Wire
- Aggregated Interfaces for a Virtual Wire
- Virtual Wire Support of High Availability
- Zone Protection for a Virtual Wire Interface
- VLAN-Tagged Traffic
- Virtual Wire Subinterfaces
- Configure Virtual Wires
- Configure an Aggregate Interface Group
- Configure Bonjour Reflector for Network Segmentation
- Use Interface Management Profiles to Restrict Access
-
- DNS Overview
- DNS Proxy Object
- DNS Server Profile
- Multi-Tenant DNS Deployments
- Configure a DNS Proxy Object
- Configure a DNS Server Profile
- Use Case 1: Firewall Requires DNS Resolution
- Use Case 2: ISP Tenant Uses DNS Proxy to Handle DNS Resolution for Security Policies, Reporting, and Services within its Virtual System
- Use Case 3: Firewall Acts as DNS Proxy Between Client and Server
- DNS Proxy Rule and FQDN Matching
-
- NAT Rule Capacities
- Dynamic IP and Port NAT Oversubscription
- Dataplane NAT Memory Statistics
-
- Translate Internal Client IP Addresses to Your Public IP Address (Source DIPP NAT)
- Enable Clients on the Internal Network to Access your Public Servers (Destination U-Turn NAT)
- Enable Bi-Directional Address Translation for Your Public-Facing Servers (Static Source NAT)
- Configure Destination NAT with DNS Rewrite
- Configure Destination NAT Using Dynamic IP Addresses
- Modify the Oversubscription Rate for DIPP NAT
- Reserve Dynamic IP NAT Addresses
- Disable NAT for a Specific Host or Interface
-
- Network Packet Broker Overview
- How Network Packet Broker Works
- Prepare to Deploy Network Packet Broker
- Configure Transparent Bridge Security Chains
- Configure Routed Layer 3 Security Chains
- Network Packet Broker HA Support
- User Interface Changes for Network Packet Broker
- Limitations of Network Packet Broker
- Troubleshoot Network Packet Broker
DHCP
Options 43, 55, and 60 and Other Customized Options
The following table describes the option behavior for
several options described in RFC 2132.
Option Code | Option Name | Option Description/Behavior |
|---|---|---|
43 | Vendor Specific Information | Sent from server to client. Vendor-specific
information that the DHCP server has been configured to offer to
the client. The information is sent to the client only if the server
has a Vendor Class Identifier (VCI) in its table that matches the
VCI in the client’s DHCPREQUEST. An Option 43 packet can contain
multiple vendor-specific pieces of information. It can also include
encapsulated, vendor-specific extensions of data. |
55 | Parameter Request List | Sent from client to server. List of configuration
parameters (option codes) that a DHCP client is requesting, possibly
in order of the client’s preference. The server tries to respond with
options in the same order. |
60 | Vendor Class Identifier (VCI) | Sent from client to server. Vendor type
and configuration of a DHCP client. The DHCP client sends option
code 60 in a DHCPREQUEST to the DHCP server. When the server receives option 60,
it sees the VCI, finds the matching VCI in its own table, and then
it returns option 43 with the value (that corresponds to the VCI),
thereby relaying vendor-specific information to the correct client.
Both the client and server have knowledge of the VCI. |
You can send custom, vendor-specific option codes that are not
defined in RFC 2132. The option codes can be in the range 1-254
and of fixed or variable length.
Custom DHCP options are not validated by the DHCP Server;
you must ensure that you enter correct values for the options you
create.
For ASCII and hexadecimal DHCP option types, the option value
can be a maximum of 255 octets.