Stateless NAT Pools
The Stateless option means that no state table is maintained and the external IP address chosen for
each new connection is the one that has the least connections already allocated to it. This means two
connections between one internal host to the same external host may use two different external IP
addresses.
The advantage of a Stateless NAT Pool is that there is good spreading of new connections between
external IP addresses with no requirement for memory allocated to a state table and there is less
processing time involved in setting up each new connection. The disadvantage is that it is not
suitable for communication that requires a constant external IP address.
Fixed NAT Pools
The Fixed option means that each internal client or host is allocated one of the external IP addresses
through a hashing algorithm. Although the administrator has no control over which of the external
connections will be used, this scheme ensures that a particular internal client or host will always
communicate through the same external IP address.
The Fixed option has the advantage of not requiring memory for a state table and providing very fast
processing for new connection establishment. Although explicit load balancing is not part of this
option, there should be spreading of the load across the external connections due to the random
nature of the allocating algorithm.
IP Pool Usage
When allocating external IP addresses to a NAT Pool it is not necessary to explicitly state these.
Instead a NetDefendOS IP Pool object can be selected. IP Pools gather collections of IP addresses
automatically through DHCP and can therefore supply external IP addresses automatically to a NAT
Pool. See Section 5.5, “IP Pools” for more details on this topic.
Proxy ARP Usage
Where an external router sends ARP queries to the D-Link Firewall to resolve external IP addresses
included in a NAT Pool, NetDefendOS will need to send the correct ARP replies for this resolution
to take place through its Proxy ARP mechanism so the external router can correctly build its routing
table.
By default, the administrator must specify in NAT Pool setup which interfaces will be used by NAT
pools. The option exists however to enable Proxy ARP for a NAT Pool on all interfaces but this can
cause problems sometimes by possibly creating routes to interfaces on which packets should not
arrive. It is therefore recommended that the interface(s) to be used for the NAT Pool Proxy ARP
mechanism are explicitly specified.
Using NAT Pools
NAT Pools are used in conjunction with a normal NAT IP rule. When defining a NAT rule, the
dialog includes the option to select a NAT Pool to use with the rule. This association brings the
NAT Pool into use.
Example 7.2. Using NAT Pools
This example creates a NAT pool which will be applied the external IP address range 10.6.13.10 to 10.16.13.15
and then uses it in a NAT IP rule for HTTP traffic on the Wan interface.
7.2. NAT Pools
Chapter 7. Address Translation
289
Содержание 800 - DFL 800 - Security Appliance
Страница 24: ...1 3 NetDefendOS State Engine Packet Flow Chapter 1 NetDefendOS Overview 24 ...
Страница 69: ...2 6 4 Restore to Factory Defaults Chapter 2 Management and Maintenance 69 ...
Страница 121: ...3 9 DNS Chapter 3 Fundamentals 121 ...
Страница 166: ...interfaces without an overriding IGMP Setting Default 1 000 4 6 4 Advanced IGMP Settings Chapter 4 Routing 166 ...
Страница 181: ...4 7 5 Advanced Settings for Transparent Mode Chapter 4 Routing 181 ...
Страница 192: ...5 5 IP Pools Chapter 5 DHCP Services 192 ...
Страница 282: ...6 7 Blacklisting Hosts and Networks Chapter 6 Security Mechanisms 282 ...
Страница 300: ...mechanism 7 3 7 SAT and FwdFast Rules Chapter 7 Address Translation 300 ...
Страница 301: ...7 3 7 SAT and FwdFast Rules Chapter 7 Address Translation 301 ...
Страница 303: ... Changed on a regular basis such as every three months 8 1 Overview Chapter 8 User Authentication 303 ...
Страница 318: ...8 3 Customizing HTML Pages Chapter 8 User Authentication 318 ...
Страница 322: ...ALG 9 1 5 The TLS Alternative for VPN Chapter 9 VPN 322 ...
Страница 377: ...Management Interface Failure with VPN Chapter 9 VPN 377 ...
Страница 408: ...10 4 6 SLB_SAT Rules Chapter 10 Traffic Management 408 ...
Страница 419: ...11 5 HA Advanced Settings Chapter 11 High Availability 419 ...
Страница 426: ...12 3 5 Limitations Chapter 12 ZoneDefense 426 ...
Страница 449: ...13 9 Miscellaneous Settings Chapter 13 Advanced Settings 449 ...