summaryrefslogtreecommitdiffstats
path: root/network/arno-iptables-firewall/README
diff options
context:
space:
mode:
author Philip Lacroix2015-04-29 16:33:27 +0200
committer Willy Sudiarto Raharjo2015-04-29 16:33:27 +0200
commit1b6e3e199819f8db59da7a168cf0f2560df8a0ae (patch)
tree4528021c1106cc2dc5edfa72b27ffe76e3807f95 /network/arno-iptables-firewall/README
parent0af17d28124558254094dffcf037056379db6e05 (diff)
downloadslackbuilds-1b6e3e199819f8db59da7a168cf0f2560df8a0ae.tar.gz
network/arno-iptables-firewall: Fix source naming.
Signed-off-by: Willy Sudiarto Raharjo <willysr@slackbuilds.org>
Diffstat (limited to 'network/arno-iptables-firewall/README')
-rw-r--r--network/arno-iptables-firewall/README47
1 files changed, 22 insertions, 25 deletions
diff --git a/network/arno-iptables-firewall/README b/network/arno-iptables-firewall/README
index c90b74baf3..57dc9d2018 100644
--- a/network/arno-iptables-firewall/README
+++ b/network/arno-iptables-firewall/README
@@ -1,25 +1,23 @@
-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.
+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 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:
+NOTE - The setup script will *not* run automatically after your package was
+installed. In order to run the script you 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):
+To enable the startup of the firewall at boot-time you need to create a symlink
+as follows (in order to disable it, either remove the symlink or "chmod -x" the
+startup script):
# 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:
+You can also start the firewall manually with one of the following commands:
# /etc/rc.d/rc.arno-iptables-firewall start
@@ -27,16 +25,15 @@ of the following commands:
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).
+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.
+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.
+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 OPEN_TCP (e.g.) accordingly.