| Age | Commit message (Collapse) | Author |
|---|
|
> The specified protocol can be one of tcp, udp, udplite, icmp, icmpv6,esp,
> ah, sctp, mh or the special keyword "all", or it can be a numeric value,
> representing one of these protocols or a different one.
source: https://ipset.netfilter.org/iptables.man.html
Also see [0] for Assigned Internet Protocol Numbers.
--
[0] https://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml
|
|
|
|
- implement validations for port ranges
- add test cases for these scenarios
|
|
This enables defining ferm::rule with multiple protocols at once,
because using 'all' for $proto does not allow using $dport/$sport.
|
|
Previously it was neither possible to properly define custom chains nor
to define rules in tables other than the default filter table.
For various legitimate reasons it can be required to define rules in the
raw, nat or mangle tables, e.g. to use NOTRACK or to configure
DNAT/SNAT/MASQUERADE.
Additionally it might come in handy to define custom chains to group
certain rules and allow a more efficient evaluation for incoming packets
by not cramming all rules into the filter/INPUT chain so that
(worst-case) all packets need to traverse and evaluate all rules.
I have tried to maintain backwards compatibility and to not change
default filenames/paths so that it won't result in leftover obsolete unmaged
files from previous versions of this module.
In order to improve the naming schema the rule $policy has been renamed
to $action, however both parameters are available and optional now, with
some sanity checks that require at most one of them and issueing a
warning() for users of the now deprecated $policy parameter.
All previous tests have been adapted to the changes, a long with an
additional set of tests for the new feature.
Fixes #61
|
|
|
|
|
|
|
|
|
|
|
