SHOREWALL-ACTIONS(5) | Configuration Files | SHOREWALL-ACTIONS(5) |
NAME¶
actions - Shorewall action declaration fileSYNOPSIS¶
/etc/shorewall/actions
DESCRIPTION¶
This file allows you to define new ACTIONS for use in rules (see shorewall-rules(5)[1]). You define the iptables rules to be performed in an ACTION in /etc/shorewall/action. action-name. Columns are: NAMEThe name of the action. ACTION names should begin with an
upper-case letter to distinguish them from Shorewall-generated chain names and
be composed of letters, digits or numbers. If you intend to log from the
action then the name must be no longer than 11 characters in length if you use
the standard LOGFORMAT.
OPTIONS
Added in Shorewall 4.5.10. Available options are:
builtin
Added in Shorewall 4.5.16. Defines the action as a rule
target that is supported by your iptables but is not directly supported by
Shorewall. The action may be used as the rule target in an INLINE rule in
shorewall-rules[1](5).
Beginning with Shorewall 4.6.0, the Netfilter table(s) in which the
builtin can be used may be specified: filter, nat,
mangle and raw. If no table name(s) are given, then
filter is assumed. The table names follow builtin and are
separated by commas; for example, "FOOBAR builtin,filter,mangle"
would specify FOOBAR as a builtin target that can be used in the filter and
mangle tables.
Beginning with Shorewall 4.6.4, you may specify the terminating option
with builtin to indicate to the Shorewall optimizer that the action is
terminating (the current packet will not be passed to the next rule in the
chain).
inline
Causes the action body (defined in
action.action-name) to be expanded in-line like a macro rather than in
its own chain. You can list Shorewall Standard Actions in this file to specify
the inline option.
Caution
Some of the Shorewall standard actions cannot be used in-line and will generate
a warning and the compiler will ignore inline if you try to use them
that way:
noinline
Broadcast
DropSmurfs
Invalid (Prior to Shorewall 4.5.13)
NotSyn (Prior to Shorewall 4.5.13)
RST (Prior to Shorewall 4.5.13)
TCPFlags
Causes any later inline option for the same action
to be ignored with a warning.
nolog
Added in Shorewall 4.5.11. When this option is specified,
the compiler does not automatically apply the log level and/or tag from the
invocation of the action to all rules inside of the action. Rather, it simply
sets the $_loglevel and $_logtag shell variables which can be used within the
action body to apply those logging options only to a subset of the
rules.
terminating
Added in Shorewall 4.6.4. When used with builtin,
indicates that the built-in action is termiating (i.e., if the action is
jumped to, the next rule in the chain is not evaluated).
FILES¶
/etc/shorewall/actionsSEE ALSO¶
http://www.shorewall.net/Actions.html[2] shorewall(8), shorewall-accounting(5), shorewall-blacklist(5), shorewall-hosts(5), shorewall_interfaces(5), shorewall-ipsets(5), shorewall-maclist(5), shorewall-masq(5), shorewall-nat(5), shorewall-netmap(5), shorewall-params(5), shorewall-policy(5), shorewall-providers(5), shorewall-proxyarp(5), shorewall-rtrules(5), shorewall-routestopped(5), shorewall-rules(5), shorewall.conf(5), shorewall-secmarks(5), shorewall-tcclasses(5), shorewall-tcdevices(5), shorewall-mangle(5), shorewall-tos(5), shorewall-tunnels(5), shorewall-zones(5)NOTES¶
10/19/2014 | Configuration Files |