Provided by: shorewall6_4.5.21.6-1_all 
NAME
secmarks - Shorewall6 file
SYNOPSIS
/etc/shorewall6/secmarks
DESCRIPTION
Important
Unlike rules in the shorewall6-rules[1](5) file, evaluation of rules in this file will
continue after a match. So the final secmark for each packet will be the one assigned
by the LAST rule that matches.
The secmarks file is used to associate an SELinux context with packets. It was added in
Shorewall6 version 4.4.13.
The columns in the file are as follows (where the column name is followed by a different
name in parentheses, the different name is used in the alternate specification syntax).
SECMARK - {SAVE|RESTORE|context|[?]COMMENT comment}
SAVE
If an SELinux context is associated with the packet, the context is saved in the
connection. Normally, the remaining columns should be left blank.
RESTORE
If an SELinux context is not currently associated with the packet, then the saved
context (if any) is associated with the packet. Normally, the remaining columns
should be left blank.
context
An SELinux context.
[?]COMMENT
The remainder of the line is treated as a comment which is attached to subsequent
rules until another COMMENT line is found or until the end of the file is reached.
To stop adding comments to rules, use a line with only the word COMMENT.
Note
Beginning with Shorewall 4.5.11, ?COMMENT is a synonym for COMMENT and is
preferred.
CHAIN:STATE (chain) - {P|I|F|O|T}[:{N|I|U|IU|NI|NU|NIU|NUI:E|ER}]
This column determines the CHAIN where the SELinux context is to be applied:
P - PREROUTING
I - INPUT
F - FORWARD
O - OUTPUT
T - POSTROUTING
It may be optionally followed by a colon and an indication of the Netfilter connection
state(s) at which the context is to be applied:
:N - NEW connection
:I - INVALID connection
:NI - NEW or INVALID connection
:E - ESTABLISHED connection
:ER - ESTABLISHED or RELATED connection
Beginning with Shorewall 4.5.10, the following additional options are available
:U - UNTRACKED connection
:IU - INVALID or UNTRACKED connection
:NU - NEW or UNTRACKED connection
:NIU - NEW, INVALID or UNTRACKED connection.
SOURCE - {-interface|[interface:]address-or-range[,address-or-range]...}[exclusion]
May be:
1. An interface name - matches traffic entering the firewall on the specified
interface. May not be used in classify rules or in rules using the T in the CHAIN
column.
2. A comma-separated list of host or network IP addresses or MAC addresses.
3. An interface name followed by a colon (":") followed by a comma-separated list of
host or network IP addresses or MAC addresses.
MAC addresses must be prefixed with "~" and use "-" as a separator.
Example: ~00-A0-C9-15-39-78
You may exclude certain hosts from the set already defined through use of an exclusion
(see shorewall6-exclusion[2](5)).
DEST - {-|{interface|[interface:]address-or-range[,address-or-range]...}[exclusion]
May be:
1. An interface name. May not be used in the PREROUTING or INPUT chains. The
interface name may be optionally followed by a colon (":") and an IP address list.
2. A comma-separated list of host or network IP addresses. The list may include ip
address ranges if your kernel and iptables include iprange support.
You may exclude certain hosts from the set already defined through use of an exclusion
(see shorewall6-exclusion[3](5)).
PROTO - {-|tcp:syn|ipp2p|ipp2p:udp|ipp2p:all|protocol-number|protocol-name|all}
Protocol - ipp2p requires ipp2p match support in your kernel and iptables.
Beginning with Shorewall 4.5.12, this column can accept a comma-separated list of
protocols.
PORT(S) (dport) - [-|port-name-number-or-range[,port-name-number-or-range]...]
Optional destination Ports. A comma-separated list of Port names (from services(5)),
port numbers or port ranges; if the protocol is icmp, this column is interpreted as
the destination icmp-type(s). ICMP types may be specified as a numeric type, a numeric
type and code separated by a slash (e.g., 3/4), or a typename. See
http://www.shorewall.net/configuration_file_basics.htm#ICMP.
If the protocol is ipp2p, this column is interpreted as an ipp2p option without the
leading "--" (example bit for bit-torrent). If no PORT is given, ipp2p is assumed.
This column is ignored if PROTOCOL = all but must be entered if any of the following
field is supplied. In that case, it is suggested that this field contain "-"
SOURCE PORT(S) (sport) - [-|port-name-number-or-range[,port-name-number-or-range]...]
Optional source port(s). If omitted, any source port is acceptable. Specified as a
comma-separated list of port names, port numbers or port ranges.
Beginning with Shorewall 4.5.15, you may place '=' in this column, provided that the
DEST PORT(S) column is non-empty. This causes the rule to match when either the source
port or the destination port in a packet matches one of the ports specified in DEST
PORTS(S). Use of '=' requires multi-port match in your iptables and kernel.
USER - [!][user-name-or-number][:group-name-or-number]
This optional column may only be non-empty if the SOURCE is the firewall itself.
When this column is non-empty, the rule applies only if the program generating the
output is running under the effective user and/or group specified (or is NOT running
under that id if "!" is given).
Examples:
joe
program must be run by joe
:kids
program must be run by a member of the 'kids' group
!:kids
program must not be run by a member of the 'kids' group
MARK - [!]value[/mask][:C]
Defines a test on the existing packet or connection mark. The rule will match only if
the test returns true.
If you don't want to define a test but need to specify anything in the following
columns, place a "-" in this field.
!
Inverts the test (not equal)
value
Value of the packet or connection mark.
mask
A mask to be applied to the mark before testing.
:C
Designates a connection mark. If omitted, the packet mark's value is tested.
EXAMPLE
Mark the first incoming packet of a connection on the loopback interface and destined for
address ::1 and tcp port 3306 with context system_u:object_r:mysqld_t:s0 and save that
context in the conntrack table. On subsequent input packets in the connection, set the
context from the conntrack table.
/etc/shorewall6/interfaces:
#ZONE INTERFACE BROADCAST OPTIONS
- lo - ignore
/etc/shorewall6/secmarks:
#SECMARK CHAIN: SOURCE DEST PROTO DEST SOURCE USER/ MARK
# STATE PORT(S) PORT(S) GROUP
system_u:object_r:mysqld_packet_t:s0 I:N lo ::1 tcp 3306
SAVE I:N
RESTORE I:ER
FILES
/etc/shorewall6/secmarks
SEE ALSO
http://james-morris.livejournal.com/11010.html
http://shorewall.net/configuration_file_basics.htm#Pairs
shorewall6(8), shorewall6-actions(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-tcclasses(5), shorewall6-tcdevices(5),
shorewall6-tcrules(5), shorewall6-tos(5), shorewall6-tunnels(5), shorewall6-zones(5)
NOTES
1. shorewall6-rules
http://www.shorewall.netshorewall6-rules.html
2. shorewall6-exclusion
http://www.shorewall.netshorewall6-exclusion.html
3. shorewall6-exclusion
http://www.shorewall.netshorewall-exclusion.html
[FIXME: source] 01/30/2014 SHOREWALL6-SECMARKS(5)