All addresses received from the DHCP server are assigned to corresponding IP4Address
objects. In this way, dynamically assigned addresses can be used throughout the
configuration in the same way as static addresses. By default, the objects in use are the same
ones as defined in Section 3.1.5, “Auto-Generated Address Objects”.
By default, DHCP is disabled on Ethernet interfaces. If the interface is being used for
connection to the public Internet via an ISP using fixed IP addresses then DHCP shouldn't be
used. In addition, DHCPv6 for IPv6 addresses is available as a separate property of the
interface configuration object and this is also disabled by default (see Section 5.6.1, “DHCPv6
Client”).
Important: DHCP clients are not supported in HA clusters
Both IPv4 DHCP clients and DHCPv6 clients are not supported in a high availability
cluster. If either property is enabled for an interface then this will produce the error
Shared HA IP address not set when trying to commit the configuration.
DNS server addresses received through DHCP on an interface which is named
<interface-name> will be allocated to NetDefendOS address objects with the names
<interface-name>_dns1 and <interface-name>_dns2.
Note: A gateway IP cannot be deleted with DHCP enabled
If DHCP is enabled for a given Ethernet interface then any gateway IP address (for
example, the address of an ISP) that is defined for that interface cannot be deleted.
To remove the gateway address, the DHCP option must be first disabled.
If DHCP is enabled then there is a set of interface specific advanced settings:
i. A preferred IP address can be requested.
ii. A preferred lease time can be requested.
iii. Static routes can be sent from the DHCP server.
iv. Do not allow IP address collisions with static routes.
v. Do not allow network collisions with static routes.
vi. Specify an allowed IP address for the DHCP lease.
vii. Specify an address range for DHCP servers from which leases will be accepted.
• DHCP Hostname
In some, infrequent cases a DHCP server may require a hostname to be sent by the DHCP
client.
• Enable Transparent Mode
The recommended way to enable Transparent Mode is to add switch routes, as described in
Section 4.8, “Transparent Mode”. An alternative method is to enable transparent mode directly
on an interface with this option.
When enabled, default switch routes are automatically added to the routing table for the
Chapter 3: Fundamentals
183
To Next Page
Loading...
