15.4.2 Configuring Manually
The following paragraphs provide step-by-step instructions for a successful configura-
tion. Each configuration item is marked as to whether it is relevant to firewalling or
masquerading. Use port range (for example,
500:510
) whenever appropriate. Aspects
related to the DMZ (demilitarized zone) as mentioned in the configuration file are not
covered here. They are applicable only to a more complex network infrastructure found
in larger organizations (corporate networks), which require extensive configuration and
in-depth knowledge about the subject.
First, use the YaST module System Services (Runlevel) to enable SuSEfirewall2 in
your runlevel (3 or 5 most likely). It sets the symlinks for the SuSEfirewall2_* scripts
in the
/etc/init.d/rc?.d/
directories.
FW_DEV_EXT
(firewall, masquerading)
The device linked to the Internet. For a modem connection, enter
ppp0
. For an
ISDN link, use
ippp0
. DSL connections use
dsl0
. Specify
auto
to use the in-
terface that corresponds to the default route.
FW_DEV_INT
(firewall, masquerading)
The device linked to the internal, private network (such as
eth0
). Leave this blank
if there is no internal network and the firewall protects only the host on which it
runs.
FW_ROUTE
(firewall, masquerading)
If you need the masquerading function, set this to
yes
. Your internal hosts will
not be visible to the outside, because their private network addresses (e.g.,
192.168.x.x
) are ignored by Internet routers.
For a firewall without masquerading, only set this to
yes
if you want to allow access
to the internal network. Your internal hosts need to use officially registered IP ad-
dresses in this case. Normally, however, you should not allow access to your internal
network from the outside.
FW_MASQUERADE
(masquerading)
Set this to
yes
if you need the masquerading function. This provides a virtually
direct connection to the Internet for the internal hosts. It is more secure to have a
proxy server between the hosts of the internal network and the Internet. Masquerad-
ing is not needed for services a proxy server provides.
Masquerading and Firewalls
177
Summary of Contents for LINUX ENTERPRISE DESKTOP 11
Page 1: ...SUSE Linux Enterprise Server www novell com 11 March 17 2009 Security Guide...
Page 9: ...32 7 Managing Audit Event Records Using Keys 433 33 Useful Resources 435...
Page 10: ......
Page 29: ...Part I Authentication...
Page 30: ......
Page 55: ...Figure 4 2 YaST LDAP Server Configuration LDAP A Directory Service 41...
Page 126: ......
Page 127: ...Part II Local Security...
Page 128: ......
Page 158: ......
Page 173: ...Part III Network Security...
Page 174: ......
Page 194: ......
Page 197: ...Figure 16 2 Scenario 2 Figure 16 3 Scenario 3 Configuring VPN Server 183...
Page 210: ......
Page 228: ......
Page 229: ...Part IV Confining Privileges with Novell AppArmor...
Page 230: ......
Page 274: ......
Page 300: ......
Page 328: ......
Page 340: ......
Page 342: ......
Page 386: ......
Page 387: ...Part V The Linux Audit Framework...
Page 388: ......