shorewall6-actions5Configuration Filesactionsshorewall6 action declaration file/etc/shorewall6/actionsDescriptionThis file allows you to define new ACTIONS for use in rules (see
shorewall6-rules(5)). You
define the ip6tables rules to be performed in an ACTION in
/etc/shorewall6/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.OPTIONSAdded in Shorewall 4.5.10. Available options are:builtinAdded in Shorewall 4.5.16. Defines the action as a rule
target that is supported by your ip6tables but is not directly
supported by Shorewall. The action may be used as the rule
target in an INLINE rule in shorewall6-rules(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.inlineCauses 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
option.Some of the Shorewall standard actions cannot be used
in-line and will generate a warning and the compiler will
ignore if you try to use them that
way:BroadcastDropSmurfsInvalid (Prior to Shorewall 4.5.13)NotSyn (Prior to Shorewall 4.5.13)RST (Prior to Shorewall 4.5.13)TCPFlagsnoinlineCauses any later option for the
same action to be ignored with a warning.nologAdded 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.FILES/etc/shorewall6/actionsSee ALSOhttp://www.shorewall.net/Actions.htmlshorewall6(8), shorewall6-accounting(5), shorewall6-blacklist(5),
shorewall6-hosts(5), shorewall6-interfaces(5), shorewall6-maclist(5),
shorewall6-netmap(5),shorewall6-params(5), shorewall6-policy(5),
shorewall6-providers(5), shorewall6-rtrules(5),
shorewall6-routestopped(5), shorewall6-rules(5), shorewall6.conf(5),
shorewall6-secmarks(5), shorewall6-tcclasses(5), shorewall6-tcdevices(5),
shorewall6-mangle(5), shorewall6-tos(5), shorewall6-tunnels(5),
shorewall-zones(5)