shorewall6-conntrack 5 conntrack shorewall conntrack file /etc/shorewall/conntrack The original intent of the notrack file was to exempt certain traffic from Netfilter connection tracking. Traffic matching entries in the file were not to be tracked. The role of the file was expanded in Shorewall 4.4.27 to include all rules that can be added in the Netfilter raw table. In 4.5.7, the file's name was changed to conntrack. The file supports two different column layouts: FORMAT 1 and FORMAT 2, FORMAT 1 being the default. The two differ in that FORMAT 2 has an additional leading ACTION column. When an entry in the file of this form is encountered, the format of the following entries are assumed to be of the specified format. FORMAT format where format is either 1 or 2. 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. 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). ACTION - {NOTRACK|CT:helper:name[(arg=val[,...])|CT:notrack} This column is only present when FORMAT = 2. Values other than NOTRACK or DROP require CT Target support in your iptables and kernel. NOTRACK or CT:notrack Disables connection tracking for this packet. DROP Added in Shorewall 4.5.10. Silently discard the packet. helper:name Attach the helper identified by the name to this connection. This is more flexible than loading the conntrack helper with preset ports. At this writing, the available helpers are: amanda Requires that the amanda netfilter helper is present. ftp Requires that the FTP netfilter helper is present. irc Requires that the IRC netfilter helper is present. netbios-ns Requires that the netbios_ns (sic) helper is present. RAS and Q.931 These require that the H323 netfilter helper is present. pptp Requires that the pptp netfilter helper is present. sane Requires that the SANE netfilter helper is present. sip Requires that the SIP netfilter helper is present. snmp Requires that the SNMP netfilter helper is present. tftp Requires that the TFTP netfilter helper is present. May be followed by an option list of arg=val pairs in parentheses: ctevents=event[,...] Only generate the specified conntrack events for this connection. Possible event types are: new, related, destroy, reply, assured, protoinfo, helper, mark (this is connection mark, not packet mark), natseqinfo, and secmark. If more than one event is listed, the event list must be enclosed in parentheses (e.g., ctevents=(new,related)). expevents=new Only generate a new expectation events for this connection. When FORMAT = 1, this column is not present and the rule is processed as if NOTRACK had been entered in this column. 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 (5)). Beginning with Shorewall 4.5.7, all can be used as the zone name to mean all zones. 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 (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. #ACTION SOURCE DEST PROTO DEST SOURCE USER/GROUP # PORT(S) PORT(S) CT:helper:ftp(expevents=new) fw - tcp 21 /etc/shorewall/notrack 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-rtrules(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)