File: README.Debian

package info (click to toggle)
ferm 2.1-5
  • links: PTS
  • area: main
  • in suites: wheezy
  • size: 620 kB
  • sloc: perl: 2,252; sh: 147; makefile: 129
file content (33 lines) | stat: -rw-r--r-- 1,412 bytes parent folder | download | duplicates (5)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
The ferm debian package
=======================

By default, ferm's configuration file is /etc/ferm/ferm.conf.  The
directory /etc/ferm is reserved for includes you might want to write.

The init script itself is configured with /etc/default/ferm, which
contains several variables.  Most important for now is "ENABLED=yes"
if you want ferm to be run automatically on boot.

Setting "FAST=yes" is, well, faster - but you shouldn't enable it on
Debian Sarge because it ships iptables 1.2, which is know to be too
bugged for ferm's fast mode.

If you want to use ferm on sarge you have use iptables 1.3 or remove the 1.3
dependency and set FAST=no in /etc/default/ferm (the latter is done for the
packages on backports.org). 

The cache ("CACHE=yes", enabled by default) speeds things up, too,
because ferm will only be run when you modify its configuration, but
this also means that ferm's rollback-on-error isn't assisting you.
Also note that the init script doesn't notice when you change an
include file.  To work around that, touch /etc/ferm/ferm.conf.

I recommend you use ferm's so-called "interactive mode" while you
develop firewall rules on remote machines.  In this mode, ferm applies
the new firewall rules and asks you for confirmation.  If you don't
confirm within 30 seconds, ferm reverts to the previous rule set.
Run:

  ferm --interactive /etc/ferm/ferm.conf

 -- Max Kellermann <max@duempel.org>