Ethernet Interface Parameters
The following are the various parameters that can be set for an Ethernet interface:
•
Interface Name
The names of the Ethernet interfaces are predefined by the system, and are mapped to the names
of the physical interfaces.
The names of the Ethernet interfaces can be changed to better reflect their usage. For example, if
an interface named dmz is connected to a wireless LAN, it might be convenient to change the
interface name to radio. For maintenance and troubleshooting, it is recommended to tag the
corresponding physical interface with the new name.
Note: Interface enumeration
The startup process will enumerate all available Ethernet interfaces. Each
interface will be given a name of the form lanN, wanN and dmz, where N
represents the number of the interface if the NetDefend Firewall has more than one
of these interfaces. In most of the examples in this guide lan is used for LAN traffic
and wan is used for WAN traffic. If the NetDefend Firewall does not have these
interface names, please substitute the references with the actual names of the
interfaces.
•
IP Address
Each Ethernet interface is required to have an Interface IP Address, which can be either a static
address or an address provided by DHCP. The interface IP address is used as the primary
address for communicating with the system through the specific Ethernet interface.
NetDefendOS IP4 Address objects are usually used to define the IPv4 addresses of Ethernet
interfaces. Those objects are normally auto-generated by the system. For more information,
please see Section 3.1.5, “Auto-Generated Address Objects”.
Tip: Specifying multiple IP addresses on an interface
Multiple IP addresses can be specified for an Ethernet interface by using the ARP
Publish feature. (For more information, see Section 3.5, “ARP”).
•
Network
In addition to the interface IP address, a Network address is also specified for an Ethernet
interface. The Network address provides information to NetDefendOS about what IP addresses
are directly reachable through the interface. In other words, those residing on the same LAN
segment as the interface itself. In the routing table associated with the interface, NetDefendOS
will automatically create a direct route to the specified network over the actual interface.
•
Default Gateway
A Default Gateway address can optionally be specified for an Ethernet interface. This is
normally the address of a router and very often the router which acts as the gateway to the
Internet.
Normally, only one default all-nets route to the default gateway needs to exist in the routing
table.
3.4.2. Ethernet Interfaces
Chapter 3. Fundamentals
111
Summary of Contents for NetDefend DFL-1660
Page 28: ...1 3 NetDefendOS State Engine Packet Flow Chapter 1 NetDefendOS Overview 28 ...
Page 88: ...2 6 3 Restore to Factory Defaults Chapter 2 Management and Maintenance 88 ...
Page 166: ...3 10 DNS Chapter 3 Fundamentals 166 ...
Page 254: ...4 7 5 Advanced Settings for Transparent Mode Chapter 4 Routing 254 ...
Page 268: ...5 4 IP Pools Chapter 5 DHCP Services 268 ...
Page 368: ...6 7 Blacklisting Hosts and Networks Chapter 6 Security Mechanisms 368 ...
Page 390: ...7 4 7 SAT and FwdFast Rules Chapter 7 Address Translation 390 ...
Page 414: ...8 3 Customizing Authentication HTML Pages Chapter 8 User Authentication 414 ...
Page 490: ...9 8 6 Specific Symptoms Chapter 9 VPN 490 ...
Page 528: ...10 4 6 Setting Up SLB_SAT Rules Chapter 10 Traffic Management 528 ...
Page 544: ...11 7 HA Advanced Settings Chapter 11 High Availability 544 ...
Page 551: ...12 3 5 Limitations Chapter 12 ZoneDefense 551 ...
Page 574: ...Default 512 13 9 Miscellaneous Settings Chapter 13 Advanced Settings 574 ...
Page 575: ...13 9 Miscellaneous Settings Chapter 13 Advanced Settings 575 ...