NetDefendOS May Also Need Internet Access
The NetDefend Firewall also needs to find the public Internet if it is to perform NetDefendOS
functions such as DNS lookup, Web Content Filtering or Anti-Virus and IDP updating. To allow
this, individual "normal" non-switch routes need to be set up in the routing table for each IP address
specifying the interface which leads to the ISP and the ISPs gateway IP address.
If the IP addresses that need to be reached by NetDefendOS are 85.12.184.39 and 194.142.215.15
then the complete routing table for the above example would be:
Route type
Interface
Destination
Gateway
Switch
if1
all-nets
Switch
if2
all-nets
Non-switch
if1
85.12.184.39
gw-ip
Non-switch
if1
194.142.215.15
gw-ip
The appropriate IP rules will also need to be added to the IP rule set to allow Internet access through
the NetDefend Firewall.
Grouping IP Addresses
It can be quicker when dealing with many IP addresses to group all the addresses into a single group
IP object and then use that object in a single defined route. In the above example, 85.12.184.39 and
194.142.215.15 could be grouped into a single object in this way.
Using NAT
NAT should not be enabled for NetDefendOS in Transparent Mode since, as explained previously,
the NetDefend Firewall is acting like a level 2 switch and address translation is done at the higher IP
OSI layer.
The other consequence of not using NAT is that IP addresses of users accessing the Internet usually
need to be public IP addresses.
If NATing needs to be performed in the example above to hide individual addresses from the
Internet, it would have to be done by a device (possibly another NetDefend Firewall) between the
192.168.10.0/24 network and the public Internet. In this case, internal IP addresses could be used by
the users on Ethernet network pn2.
4.7.3. Transparent Mode Scenarios
Scenario 1
The firewall in Transparent Mode is placed between an Internet access router and the internal
network. The router is used to share the Internet connection with a single public IP address. The
internal NATed network behind the firewall is in the 10.0.0.0/24 address space. Clients on the
internal network are allowed to access the Internet via the HTTP protocol.
4.7.3. Transparent Mode Scenarios
Chapter 4. Routing
218
Содержание NetDefend DFL-260E
Страница 27: ...1 3 NetDefendOS State Engine Packet Flow Chapter 1 NetDefendOS Overview 27...
Страница 79: ...2 7 3 Restore to Factory Defaults Chapter 2 Management and Maintenance 79...
Страница 146: ...3 9 DNS Chapter 3 Fundamentals 146...
Страница 227: ...4 7 5 Advanced Settings for Transparent Mode Chapter 4 Routing 227...
Страница 241: ...5 4 IP Pools Chapter 5 DHCP Services 241...
Страница 339: ...6 7 Blacklisting Hosts and Networks Chapter 6 Security Mechanisms 339...
Страница 360: ...7 4 7 SAT and FwdFast Rules Chapter 7 Address Translation 360...
Страница 382: ...8 3 Customizing HTML Pages Chapter 8 User Authentication 382...
Страница 386: ...The TLS ALG 9 1 5 The TLS Alternative for VPN Chapter 9 VPN 386...
Страница 439: ...Figure 9 3 PPTP Client Usage 9 5 4 PPTP L2TP Clients Chapter 9 VPN 439...
Страница 450: ...9 7 6 Specific Symptoms Chapter 9 VPN 450...
Страница 488: ...10 4 6 Setting Up SLB_SAT Rules Chapter 10 Traffic Management 488...
Страница 503: ...11 6 HA Advanced Settings Chapter 11 High Availability 503...
Страница 510: ...12 3 5 Limitations Chapter 12 ZoneDefense 510...
Страница 533: ...13 9 Miscellaneous Settings Chapter 13 Advanced Settings 533...