slackbuilds_ponce/network/arno-iptables-firewall
Philip Lacroix 7dbadc7a54 network/arno-iptables-firewall: Update Build Script.
Signed-off-by: Willy Sudiarto Raharjo <willysr@slackbuilds.org>
2014-04-07 14:43:37 +07:00
..
files network/arno-iptables-firewall: Update Build Script. 2014-04-07 14:43:37 +07:00
arno-iptables-firewall.info network/arno-iptables-firewall: Update Build Script. 2014-04-07 14:43:37 +07:00
arno-iptables-firewall.SlackBuild network/arno-iptables-firewall: Update Build Script. 2014-04-07 14:43:37 +07:00
CHANGELOG network/arno-iptables-firewall: Update Build Script. 2014-04-07 14:43:37 +07:00
doinst.sh network/arno-iptables-firewall: Added (a front-end for iptables). 2014-03-12 12:42:52 -05:00
README network/arno-iptables-firewall: Update Build Script. 2014-04-07 14:43:37 +07:00
slack-desc network/arno-iptables-firewall: Update Build Script. 2014-04-07 14:43:37 +07:00

arno-iptables-firewall is a front-end for iptables. Its configuration
script will set up a secure and restrictive firewall by just asking a
few questions. This includes configuring internal networks for Internet
access via NAT and potential network services like http or ssh. Moreover,
it provides many advanced additional features that can be enabled in the
well documented configuration file.

PLEASE NOTE - The setup script is NOT going to be run automatically
after your package is installed. In order to do that you'll have to
issue the following command:

# arno-iptables-firewall-configure

To enable firewall startup at boot-time you'll need to create a symlink
as follows (remove the link to disable automatic firewall startup, or
"chmod -x" the startup script for the same result):

# ln -sv /etc/rc.d/rc.arno-iptables-firewall /etc/rc.d/rc.firewall
# chmod +x /etc/rc.d/rc.arno-iptables-firewall

When everything is ready you can start the firewall manually with one
of the following commands:

# /etc/rc.d/rc.arno-iptables-firewall start

# arno-iptables-firewall start

IMPORTANT - A few security notes from the upstream author:

1) If possible, make sure that the firewall is started before the (ADSL)
Internet connection is enabled. For a ppp-interface that doesn't exist
yet you can use the wildcard device called "ppp+" (but you can only use
ppp+ if there aren't any other ppp interfaces).

2) Don't change any (security) settings ('EXPERT SETTINGS') if you don't
really understand what they mean. Changing them anyway could have a big
impact on the security of your machine.

3) A lot of people complain that their server stopped working after
installing the firewall. This is the CORRECT behaviour for a firewall:
blocking ALL incoming traffic by default. Configure your e.g. OPEN_TCP
accordingly.