value[:{C|F|P|T|CF|CP|CT}]

]A mark value is an integer, expressed either in decimal or in hex.

Normally will set the mark value. If preceded by a vertical bar ("|"), the mark value will be logically ORed with the current mark value to produce a new mark value. If preceded by an ampersand ("&"), will be logically ANDed with the current mark value to produce a new mark value.

Both "|" and "&" require Extended MARK Target support in your kernel and ip6tables; neither may be used with connection marks (see below).

May optionally be followed by :P, :F or :T where :P indicates that marking should occur in the PREROUTING chain, :F indicates that marking should occur in the FORWARD chain and :T indicates that marking should occur in the POSTROUTING chain. If neither :P, :F nor :T follow the mark value then the chain is determined as follows:

- If the SOURCE is $FW[:address-or-range[,address-or-range]...], then the rule is inserted into the OUTPUT chain. When HIGH_ROUTE_MARKS=Yes (PROVIDER_OFFSET> 0 in 4.5.0 and later), only provider mark values may be assigned there. Packet marking rules for traffic shaping of packets originating on the firewall must be coded in the POSTROUTING chain (see below).

- Otherwise, the chain is determined by the setting of MARK_IN_FORWARD_CHAIN in shorewall6.conf(5).

If your kernel and ip6tables include CONNMARK support then you can also mark the connection rather than the packet.

The mark value may be optionally followed by "/" and a mask value (used to determine those bits of the connection mark to actually be set). The mark and optional mask are then followed by one of:

When marking in the prerouting chain, the value must fall within the proper range for provider marks. See PROVIDER_OFFSET and PROVIDER_BITS in shorewall.conf(5).

major:minor

A classification Id (classid) takes the form major:minor where major and minor are integers. Corresponds to the 'class' specification in these traffic shaping modules:

       atm
       cbq
       dsmark
       pfifo_fast
       htb
       prio

Classification occurs in the POSTROUTING chain except when the SOURCE is $FW[:address] in which case classification occurs in the OUTPUT chain.

When using Shorewall6's built-in traffic shaping tool, the major class is the device number (the first device in shorewall6-tcdevices(5) is major class 1, the second device is major class 2, and so on) and the minor class is the class's MARK value in shorewall6-tcclasses(5) preceded by the number 1 (MARK 1 corresponds to minor class 11, MARK 5 corresponds to minor class 15, MARK 22 corresponds to minor class 122, etc.).

RESTORE[/mask][:{P|F|T}]

Restore the packet's mark from the connection's mark using the supplied mask if any. Your kernel and ip6tables must include CONNMARK support.

As in 1) above, may be followed by :P, :F or :T.

SAVE[/mask][:{P|F|T}]

Save the packet's mark to the connection's mark using the supplied mask if any. Your kernel and ip6tables must include CONNMARK support.

As in 1) above, may be followed by :P, :F or :T.

CONTINUE[:{P|F|T}]

Don't process any more marking rules in the table.

As in 1) above, may be followed by :P, :F, or :T. Currently, CONTINUE may not be used with exclusion (see the SOURCE and DEST columns below); that restriction will be removed when ip6tables/Netfilter provides the necessary support.

SAME

Some websites run applications that require multiple connections from a client browser. Where multiple 'balanced' providers are configured, this can lead to problems when some of the connections are routed through one provider and some through another. The SAME target allows you to work around that problem. SAME may be used in the PREROUTING and OUTPUT chains. When used in PREROUTING, it causes matching connections from an individual local system to all use the same provider. For example:

#MARK/            SOURCE                 DEST         PROTO      DEST
#CLASSIFY                                                        PORT(S)
SAME:P            2002:ce7c:92b4::1/64   ::           tcp        80,443

If a host in 192.168.1.0/24 attempts a connection on TCP port 80 or 443 and it has sent a packet on either of those ports in the last five minutes then the new connection will use the same provider as the connection over which that last packet was sent.

When used in the OUTPUT chain, it causes all matching connections to an individual remote system to all use the same provider. For example:

#MARK/            SOURCE         DEST         PROTO      DEST
#CLASSIFY                                                PORT(S)
SAME              $FW            ::           tcp        80,443

If the firewall attempts a connection on TCP port 80 or 443 and it has sent a packet on either of those ports in the last five minutes to the same remote system then the new connection will use the same provider as the connection over which that last packet was sent.

COMMENT

The rest of the line will be attached as a comment to the Netfilter rule(s) generated by the following entries. The comment will appear delimited by "/* ... */" in the output of shorewall6 show mangle

To stop the comment from being attached to further rules, simply include COMMENT on a line by itself.

TPROXY(mark[/mask][,[port][,[address]]])

Transparently redirects a packet without altering the IP header. Requires a local provider to be defined in shorewall6-providers(5).

There are three parameters to TPROXY - only the first (mark) is required:

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 chain qualifier.

A comma-separated list of host or network IP addresses or MAC addresses. This form will not match traffic that originates on the firewall itself unless either <major><minor> or the :T chain qualifier is used in the MARK column.

An interface name followed by a colon (":") followed by a comma-separated list of host or network IP addresses or MAC addresses (e.g., eth1:<2002:ce7c:92b4::/48>). May not be used in classify rules or in rules using the :T chain qualifier.

$FW optionally followed by a colon (":") and a comma-separated list of host or network IP addresses. Matches packets originating on the firewall. May not be used with a chain qualifier (:P, :F, etc.) in the MARK column.

An interface name. May not be used in the PREROUTING chain (:P in the mark column or no chain qualifier and MARK_IN_FORWARD_CHAIN=No in shorewall.conf (5)). The interface name may be optionally followed by a colon (":") and an IP address list.

A comma-separated list of host or network IP addresses. The list may include ip address ranges if your kernel and ip6tables include iprange support.