D-Link DFL-260-IPS-12 Product Manual - Page 94
Note: A gateway IP cannot be deleted with DHCP enabled, DHCP Hostname, Enable Transparent Mode
View all D-Link DFL-260-IPS-12 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 94 highlights
3.3.2. Ethernet Interfaces Chapter 3. Fundamentals allocated to NetDefendOS address objects with the names _dns1 and _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 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.7, "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 interface and any corresponding non-switch routes are automatically removed. • Hardware Settings In some circumstances it may be necessary to change hardware settings for an interface. The available options are: i. The speed of the link can be set. Usually this is best left as Auto. ii. The MAC address can be set if it needs to be different to the MAC address inbuilt into the hardware. Some ISP connections might require this. • Virtual Routing To implement virtual routing where the routes related to different interfaces are kept in separate routing table, there are a number of options: i. Make the interface a member of all routing tables. This option is enabled by default and means that traffic arriving on the interface will be routed according to the main routing table. Routes for the interface IP will be inserted into all routing tables. ii. The alternative to the above is to insert the route for this interface into only a specific routing table. The specified routing table will be used for all route lookups unless overridden by a routing rule. • Automatic Route Creation 94