Provided by: shorewall_4.4.26.1-1_all bug

NAME

       notrack - shorewall notrack file

SYNOPSIS

       /etc/shorewall/notrack

DESCRIPTION

       The notrack file is used to exempt certain traffic from Netfilter connection tracking.
       Traffic matching entries in this file will not be tracked.

       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).

       SOURCE – {zone[:interface][:address-list]|COMMENT}
           where zone is the name of a zone, interface is an interface to that zone, and
           address-list is a comma-separated list of addresses (may contain exclusion - see
           shorewall-exclusion[1] (5)).

           Comments may be attached to Netfilter rules generated from entries in this file
           through the use of COMMENT lines. These lines begin with the word 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.

       DEST – [interface|address-list]
           where interface is the name of a network interface and address-list is a
           comma-separated list of addresses (may contain exclusion - see shorewall-exclusion[1]
           (5)). If an interface is given:

           ·   It must be up and configured with an IPv4 address when Shorewall is started or
               restarted.

           ·   All routes out of the interface must be configured when Shorewall is started or
               restarted.

           ·   Default routes out of the interface will result in a warning message and will be
               ignored.

           These restrictions are because Netfilter doesn't support NOTRACK rules that specify a
           destination interface (these rules are applied before packets are routed and hence the
           destination interface is unknown). Shorewall uses the routes out of the interface to
           replace the interface with an address list corresponding to the networks routed out of
           the named interface.

       PROTO – protocol-name-or-number
           A protocol name from /etc/protocols or a protocol number.

       DEST PORT(S) (dport) - port-number/service-name-list
           A comma-separated list of port numbers and/or service names from /etc/services. May
           also include port ranges of the form low-port:high-port if your kernel and iptables
           include port range support.

       SOURCE PORT(S) (sport) - port-number/service-name-list
           A comma-separated list of port numbers and/or service names from /etc/services. May
           also include port ranges of the form low-port:high-port if your kernel and iptables
           include port range support.

       USER/GROUP (user) – [user][:group]
           May only be specified if the SOURCE zone is $FW. Specifies the effective user id and
           or group id of the process sending the traffic.

FILES

       /etc/shorewall/notrack

SEE ALSO

       http://shorewall.net/configuration_file_basics.htm#Pairs

       shorewall(8), shorewall-accounting(5), shorewall-actions(5), shorewall-blacklist(5),
       shorewall-hosts(5), shorewall_interfaces(5), shorewall-ipsets(5), shorewall-masq(5),
       shorewall-nat(5), shorewall-netmap(5), shorewall-params(5), shorewall-policy(5),
       shorewall-providers(5), shorewall-proxyarp(5), shorewall-route_rules(5),
       shorewall-routestopped(5), shorewall-rules(5), shorewall.conf(5), shorewall-secmarks(5),
       shorewall-tcclasses(5), shorewall-tcdevices(5), shorewall-tcrules(5), shorewall-tos(5),
       shorewall-tunnels(5), shorewall-zones(5)

NOTES

        1. shorewall-exclusion
           http://www.shorewall.net/manpages/shorewall-exclusion.html

[FIXME: source]                             12/13/2011                      SHOREWALL6-NOTRACK(5)