•
Source Network: all-nets
•
Destination Interface: core
•
Destination Network: wan_ip
4.
Under the SAT tab, make sure that the Destination IP Address option is selected
5.
In the New IP Address textbox, enter 10.10.10.5
6.
Click OK
Then create a corresponding Allow rule:
1.
Go to Rules > IP Rules > Add > IPRule
2.
Specify a suitable name for the rule, for example Allow_HTTP_To_DMZ
3.
Now enter:
•
Action: Allow
•
Service: http
•
Source Interface: any
•
Source Network: all-nets
•
Destination Interface: core
•
Destination Network: wan_ip
4.
Under the Service tab, select http in the Pre-defined list
5.
Click OK
The example results in the following two rules in the rule set:
#
Action
Src Iface
Src Net
Dest Iface
Dest Net
Parameters
1
SAT
any
all-nets
core
wan_ip
http SETDEST
10.10.10.5 80
2
Allow
any
all-nets
core
wan_ip
http
These two rules allow us to access the web server via the D-Link Firewall's external IP address. Rule 1 states that
address translation can take place if the connection has been permitted, and rule 2 permits the connection.
Of course, we also need a rule that allows internal machines to be dynamically address translated to the Internet.
In this example, we use a rule that permits everything from the internal network to access the Internet via NAT
hide:
#
Action
Src Iface
Src Net
Dest Iface
Dest Net
Parameters
3
NAT
lan
lannet
any
all-nets
All
Now, what is wrong with this rule set?
If we assume that we want to implement address translation for reasons of security as well as functionality, we
discover that this rule set makes our internal addresses visible to machines in the DMZ. When internal machines
connect to wan_ip port 80, they will be allowed to proceed by rule 2 as it matches that communication. From an
internal perspective, all machines in the DMZ should be regarded as any other Internet-connected servers; we do
not trust them, which is the reason for locating them in a DMZ in the first place.
There are two possible solutions:
1.
You can change rule 2 so that it only applies to external traffic.
2.
You can swap rules 2 and 3 so that the NAT rule is carried out for internal traffic before the Allow rule
matches.
Which of these two options is the best? For this configuration, it makes no difference. Both solutions work just as
well.
7.3.1. Translation of a Single IP
Address (1:1)
Chapter 7. Address Translation
292
Summary of Contents for 800 - DFL 800 - Security Appliance
Page 24: ...1 3 NetDefendOS State Engine Packet Flow Chapter 1 NetDefendOS Overview 24 ...
Page 69: ...2 6 4 Restore to Factory Defaults Chapter 2 Management and Maintenance 69 ...
Page 121: ...3 9 DNS Chapter 3 Fundamentals 121 ...
Page 181: ...4 7 5 Advanced Settings for Transparent Mode Chapter 4 Routing 181 ...
Page 192: ...5 5 IP Pools Chapter 5 DHCP Services 192 ...
Page 282: ...6 7 Blacklisting Hosts and Networks Chapter 6 Security Mechanisms 282 ...
Page 300: ...mechanism 7 3 7 SAT and FwdFast Rules Chapter 7 Address Translation 300 ...
Page 301: ...7 3 7 SAT and FwdFast Rules Chapter 7 Address Translation 301 ...
Page 318: ...8 3 Customizing HTML Pages Chapter 8 User Authentication 318 ...
Page 322: ...ALG 9 1 5 The TLS Alternative for VPN Chapter 9 VPN 322 ...
Page 377: ...Management Interface Failure with VPN Chapter 9 VPN 377 ...
Page 408: ...10 4 6 SLB_SAT Rules Chapter 10 Traffic Management 408 ...
Page 419: ...11 5 HA Advanced Settings Chapter 11 High Availability 419 ...
Page 426: ...12 3 5 Limitations Chapter 12 ZoneDefense 426 ...
Page 449: ...13 9 Miscellaneous Settings Chapter 13 Advanced Settings 449 ...