Configure an Interface as a DHCP Client
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
Configure an Interface as a DHCP Client
Configure a firewall interface as a DHCP client.
Before configuring a firewall interface as
a DHCP client, make sure you have configured a Layer 3 interface
(Ethernet, Ethernet subinterface, VLAN, VLAN subinterface, aggregate,
or aggregate subinterface) and the interface is assigned to a virtual
router and a zone. Configure an interface as a DHCP client if you
need to use DHCP to request an IPv4 address for the interface.
You
can also Configure
the Management Interface as a DHCP Client.
- Configure an interface as a DHCP client.
- Select.NetworkInterfaces
- On theEthernettab or theVLANtab,Adda Layer 3 interface or select a configured Layer 3 interface that you want to be a DHCP client.
- Select theIPv4tab and, forType, selectDHCP Client.
- SelectEnable.
- (Optional) Enable the option toAutomatically create default route pointing to default gateway provided by serverenabled by default). Enabling this option causes the firewall to create a static route to the default gateway, which is useful when clients try to access many destinations that do not need to have routes maintained in a route table on the firewall.
- (Optional) Enable the option toSend Hostnameto assign a hostname to the DHCP client interface and send that hostname (Option 12) to a DHCP server, which can then register the hostname with the DNS server. The DNS server can then automatically manage hostname-to-dynamic IP address resolutions. External hosts can identify the interface by its hostname. The default value indicatessystem-hostname, which is the firewall hostname that you set in. Alternatively, enter a hostname for the interface, which can be a maximum of 64 characters, including uppercase and lowercase letters, numbers, period (.), hyphen (-), and underscore (_).DeviceSetupManagementGeneral Settings
- (Optional) Enter aDefault Route Metric(priority level) for the route between the firewall and the DHCP server (range is 1 to 65,535; default is 10). A route with a lower number has higher priority during route selection. For example, a route with a metric of 10 is used before a route with a metric of 100.TheDefault Route Metricfor the route between the firewall and the DHCP server is 10 by default. If the static default route 0.0.0.0/0 uses the DHCP interface as its egress interface, that route’s defaultMetricis also 10. Therefore, there are two routes with a metric of 10 and the firewall can randomly choose one of the routes one time and the other route another time.Suppose you enable the option toAutomatically create default route pointing to default gateway provided by server, select a virtual router, add a static route for a Layer 3 interface, change theMetric(which defaults to 10) to a value greater than 10 (for this example, 100) and Commit your changes. In the route table, the route’s metric will not indicate 100. Instead, it will indicate the default value of 10, as expected, because 10 takes precedence over the configured value of 100. However, if you change the static route’sMetricto a value less than 10 (such as 6), the route in the route table is updated to indicate the configured metric of 6.
- (Optional) Enable the option toShow DHCP Client Runtime Infoto see all of the settings the client inherited from its DHCP server.
- Commit your changes.ClickOKandCommit.The Ethernet interface should now indicateDynamic-DHCP Clientas itsIP Addresson theEthernettab.
- (Optional) See which interfaces on the firewall are configured as DHCP clients.
- Selectand check theNetworkInterfacesEthernetIP Addressto see which interfaces indicate DHCP Client.
- Selectand check theNetworkInterfacesVLANIP Addressto see which interfaces indicate DHCP Client.