.TH IPTABLES 8 "" "iptables 1.4.14" "iptables 1.4.14" .\" .\" Man page written by Herve Eychenne (May 1999) .\" It is based on ipchains page. .\" TODO: add a word for protocol helpers (FTP, IRC, SNMP-ALG) .\" .\" ipchains page by Paul ``Rusty'' Russell March 1997 .\" Based on the original ipfwadm man page by Jos Vos .\" .\" This program is free software; you can redistribute it and/or modify .\" it under the terms of the GNU General Public License as published by .\" the Free Software Foundation; either version 2 of the License, or .\" (at your option) any later version. .\" .\" This program is distributed in the hope that it will be useful, .\" but WITHOUT ANY WARRANTY; without even the implied warranty of .\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the .\" GNU General Public License for more details. .\" .\" You should have received a copy of the GNU General Public License .\" along with this program; if not, write to the Free Software .\" Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. .\" .\" .SH NAME iptables \(em administration tool for IPv4 packet filtering and NAT .SH SYNOPSIS \fBiptables\fP [\fB\-t\fP \fItable\fP] {\fB\-A\fP|\fB\-C\fP|\fB\-D\fP} \fIchain\fP \fIrule-specification\fP .PP \fBiptables\fP [\fB\-t\fP \fItable\fP] \fB\-I\fP \fIchain\fP [\fIrulenum\fP] \fIrule-specification\fP .PP \fBiptables\fP [\fB\-t\fP \fItable\fP] \fB\-R\fP \fIchain rulenum rule-specification\fP .PP \fBiptables\fP [\fB\-t\fP \fItable\fP] \fB\-D\fP \fIchain rulenum\fP .PP \fBiptables\fP [\fB\-t\fP \fItable\fP] \fB\-S\fP [\fIchain\fP [\fIrulenum\fP]] .PP \fBiptables\fP [\fB\-t\fP \fItable\fP] {\fB\-F\fP|\fB\-L\fP|\fB\-Z\fP} [\fIchain\fP [\fIrulenum\fP]] [\fIoptions...\fP] .PP \fBiptables\fP [\fB\-t\fP \fItable\fP] \fB\-N\fP \fIchain\fP .PP \fBiptables\fP [\fB\-t\fP \fItable\fP] \fB\-X\fP [\fIchain\fP] .PP \fBiptables\fP [\fB\-t\fP \fItable\fP] \fB\-P\fP \fIchain target\fP .PP \fBiptables\fP [\fB\-t\fP \fItable\fP] \fB\-E\fP \fIold-chain-name new-chain-name\fP .PP rule-specification = [\fImatches...\fP] [\fItarget\fP] .PP match = \fB\-m\fP \fImatchname\fP [\fIper-match-options\fP] .PP target = \fB\-j\fP \fItargetname\fP [\fIper\-target\-options\fP] .SH DESCRIPTION \fBIptables\fP is used to set up, maintain, and inspect the tables of IPv4 packet filter rules in the Linux kernel. Several different tables may be defined. Each table contains a number of built-in chains and may also contain user-defined chains. .PP Each chain is a list of rules which can match a set of packets. Each rule specifies what to do with a packet that matches. This is called a `target', which may be a jump to a user-defined chain in the same table. .SH TARGETS A firewall rule specifies criteria for a packet and a target. If the packet does not match, the next rule in the chain is the examined; if it does match, then the next rule is specified by the value of the target, which can be the name of a user-defined chain or one of the special values \fBACCEPT\fP, \fBDROP\fP, \fBQUEUE\fP or \fBRETURN\fP. .PP \fBACCEPT\fP means to let the packet through. \fBDROP\fP means to drop the packet on the floor. \fBQUEUE\fP means to pass the packet to userspace. (How the packet can be received by a userspace process differs by the particular queue handler. 2.4.x and 2.6.x kernels up to 2.6.13 include the \fBip_queue\fP queue handler. Kernels 2.6.14 and later additionally include the \fBnfnetlink_queue\fP queue handler. Packets with a target of QUEUE will be sent to queue number '0' in this case. Please also see the \fBNFQUEUE\fP target as described later in this man page.) \fBRETURN\fP means stop traversing this chain and resume at the next rule in the previous (calling) chain. If the end of a built-in chain is reached or a rule in a built-in chain with target \fBRETURN\fP is matched, the target specified by the chain policy determines the fate of the packet. .SH TABLES There are currently three independent tables (which tables are present at any time depends on the kernel configuration options and which modules are present). .TP \fB\-t\fP, \fB\-\-table\fP \fItable\fP This option specifies the packet matching table which the command should operate on. If the kernel is configured with automatic module loading, an attempt will be made to load the appropriate module for that table if it is not already there. The tables are as follows: .RS .TP .4i \fBfilter\fP: This is the default table (if no \-t option is passed). It contains the built-in chains \fBINPUT\fP (for packets destined to local sockets), \fBFORWARD\fP (for packets being routed through the box), and \fBOUTPUT\fP (for locally-generated packets). .TP \fBnat\fP: This table is consulted when a packet that creates a new connection is encountered. It consists of three built-ins: \fBPREROUTING\fP (for altering packets as soon as they come in), \fBOUTPUT\fP (for altering locally-generated packets before routing), and \fBPOSTROUTING\fP (for altering packets as they are about to go out). .TP \fBmangle\fP: This table is used for specialized packet alteration. Until kernel 2.4.17 it had two built-in chains: \fBPREROUTING\fP (for altering incoming packets before routing) and \fBOUTPUT\fP (for altering locally-generated packets before routing). Since kernel 2.4.18, three other built-in chains are also supported: \fBINPUT\fP (for packets coming into the box itself), \fBFORWARD\fP (for altering packets being routed through the box), and \fBPOSTROUTING\fP (for altering packets as they are about to go out). .TP \fBraw\fP: This table is used mainly for configuring exemptions from connection tracking in combination with the NOTRACK target. It registers at the netfilter hooks with higher priority and is thus called before ip_conntrack, or any other IP tables. It provides the following built-in chains: \fBPREROUTING\fP (for packets arriving via any network interface) \fBOUTPUT\fP (for packets generated by local processes) .TP \fBsecurity\fP: This table is used for Mandatory Access Control (MAC) networking rules, such as those enabled by the \fBSECMARK\fP and \fBCONNSECMARK\fP targets. Mandatory Access Control is implemented by Linux Security Modules such as SELinux. The security table is called after the filter table, allowing any Discretionary Access Control (DAC) rules in the filter table to take effect before MAC rules. This table provides the following built-in chains: \fBINPUT\fP (for packets coming into the box itself), \fBOUTPUT\fP (for altering locally-generated packets before routing), and \fBFORWARD\fP (for altering packets being routed through the box). .RE .SH OPTIONS The options that are recognized by \fBiptables\fP can be divided into several different groups. .SS COMMANDS These options specify the desired action to perform. Only one of them can be specified on the command line unless otherwise stated below. For long versions of the command and option names, you need to use only enough letters to ensure that \fBiptables\fP can differentiate it from all other options. .TP \fB\-A\fP, \fB\-\-append\fP \fIchain rule-specification\fP Append one or more rules to the end of the selected chain. When the source and/or destination names resolve to more than one address, a rule will be added for each possible address combination. .TP \fB\-C\fP, \fB\-\-check\fP \fIchain rule-specification\fP Check whether a rule matching the specification does exist in the selected chain. This command uses the same logic as \fB\-D\fP to find a matching entry, but does not alter the existing iptables configuration and uses its exit code to indicate success or failure. .TP \fB\-D\fP, \fB\-\-delete\fP \fIchain rule-specification\fP .ns .TP \fB\-D\fP, \fB\-\-delete\fP \fIchain rulenum\fP Delete one or more rules from the selected chain. There are two versions of this command: the rule can be specified as a number in the chain (starting at 1 for the first rule) or a rule to match. .TP \fB\-I\fP, \fB\-\-insert\fP \fIchain\fP [\fIrulenum\fP] \fIrule-specification\fP Insert one or more rules in the selected chain as the given rule number. So, if the rule number is 1, the rule or rules are inserted at the head of the chain. This is also the default if no rule number is specified. .TP \fB\-R\fP, \fB\-\-replace\fP \fIchain rulenum rule-specification\fP Replace a rule in the selected chain. If the source and/or destination names resolve to multiple addresses, the command will fail. Rules are numbered starting at 1. .TP \fB\-L\fP, \fB\-\-list\fP [\fIchain\fP] List all rules in the selected chain. If no chain is selected, all chains are listed. Like every other iptables command, it applies to the specified table (filter is the default), so NAT rules get listed by .nf iptables \-t nat \-n \-L .fi Please note that it is often used with the \fB\-n\fP option, in order to avoid long reverse DNS lookups. It is legal to specify the \fB\-Z\fP (zero) option as well, in which case the chain(s) will be atomically listed and zeroed. The exact output is affected by the other arguments given. The exact rules are suppressed until you use .nf iptables \-L \-v .fi .TP \fB\-S\fP, \fB\-\-list\-rules\fP [\fIchain\fP] Print all rules in the selected chain. If no chain is selected, all chains are printed like iptables-save. Like every other iptables command, it applies to the specified table (filter is the default). .TP \fB\-F\fP, \fB\-\-flush\fP [\fIchain\fP] Flush the selected chain (all the chains in the table if none is given). This is equivalent to deleting all the rules one by one. .TP \fB\-Z\fP, \fB\-\-zero\fP [\fIchain\fP [\fIrulenum\fP]] Zero the packet and byte counters in all chains, or only the given chain, or only the given rule in a chain. It is legal to specify the \fB\-L\fP, \fB\-\-list\fP (list) option as well, to see the counters immediately before they are cleared. (See above.) .TP \fB\-N\fP, \fB\-\-new\-chain\fP \fIchain\fP Create a new user-defined chain by the given name. There must be no target of that name already. .TP \fB\-X\fP, \fB\-\-delete\-chain\fP [\fIchain\fP] Delete the optional user-defined chain specified. There must be no references to the chain. If there are, you must delete or replace the referring rules before the chain can be deleted. The chain must be empty, i.e. not contain any rules. If no argument is given, it will attempt to delete every non-builtin chain in the table. .TP \fB\-P\fP, \fB\-\-policy\fP \fIchain target\fP Set the policy for the chain to the given target. See the section \fBTARGETS\fP for the legal targets. Only built-in (non-user-defined) chains can have policies, and neither built-in nor user-defined chains can be policy targets. .TP \fB\-E\fP, \fB\-\-rename\-chain\fP \fIold\-chain new\-chain\fP Rename the user specified chain to the user supplied name. This is cosmetic, and has no effect on the structure of the table. .TP \fB\-h\fP Help. Give a (currently very brief) description of the command syntax. .SS PARAMETERS The following parameters make up a rule specification (as used in the add, delete, insert, replace and append commands). .TP [\fB!\fP] \fB\-p\fP, \fB\-\-protocol\fP \fIprotocol\fP The protocol of the rule or of the packet to check. The specified protocol can be one of \fBtcp\fP, \fBudp\fP, \fBudplite\fP, \fBicmp\fP, \fBesp\fP, \fBah\fP, \fBsctp\fP or the special keyword "\fBall\fP", or it can be a numeric value, representing one of these protocols or a different one. A protocol name from /etc/protocols is also allowed. A "!" argument before the protocol inverts the test. The number zero is equivalent to \fBall\fP. "\fBall\fP" will match with all protocols and is taken as default when this option is omitted. .TP [\fB!\fP] \fB\-s\fP, \fB\-\-source\fP \fIaddress\fP[\fB/\fP\fImask\fP][\fB,\fP\fI...\fP] Source specification. \fIAddress\fP can be either a network name, a hostname, a network IP address (with \fB/\fP\fImask\fP), or a plain IP address. Hostnames will be resolved once only, before the rule is submitted to the kernel. Please note that specifying any name to be resolved with a remote query such as DNS is a really bad idea. The \fImask\fP can be either a network mask or a plain number, specifying the number of 1's at the left side of the network mask. Thus, a mask of \fI24\fP is equivalent to \fI255.255.255.0\fP. A "!" argument before the address specification inverts the sense of the address. The flag \fB\-\-src\fP is an alias for this option. Multiple addresses can be specified, but this will \fBexpand to multiple rules\fP (when adding with \-A), or will cause multiple rules to be deleted (with \-D). .TP [\fB!\fP] \fB\-d\fP, \fB\-\-destination\fP \fIaddress\fP[\fB/\fP\fImask\fP][\fB,\fP\fI...\fP] Destination specification. See the description of the \fB\-s\fP (source) flag for a detailed description of the syntax. The flag \fB\-\-dst\fP is an alias for this option. .TP \fB\-j\fP, \fB\-\-jump\fP \fItarget\fP This specifies the target of the rule; i.e., what to do if the packet matches it. The target can be a user-defined chain (other than the one this rule is in), one of the special builtin targets which decide the fate of the packet immediately, or an extension (see \fBEXTENSIONS\fP below). If this option is omitted in a rule (and \fB\-g\fP is not used), then matching the rule will have no effect on the packet's fate, but the counters on the rule will be incremented. .TP \fB\-g\fP, \fB\-\-goto\fP \fIchain\fP This specifies that the processing should continue in a user specified chain. Unlike the \-\-jump option return will not continue processing in this chain but instead in the chain that called us via \-\-jump. .TP [\fB!\fP] \fB\-i\fP, \fB\-\-in\-interface\fP \fIname\fP Name of an interface via which a packet was received (only for packets entering the \fBINPUT\fP, \fBFORWARD\fP and \fBPREROUTING\fP chains). When the "!" argument is used before the interface name, the sense is inverted. If the interface name ends in a "+", then any interface which begins with this name will match. If this option is omitted, any interface name will match. .TP [\fB!\fP] \fB\-o\fP, \fB\-\-out\-interface\fP \fIname\fP Name of an interface via which a packet is going to be sent (for packets entering the \fBFORWARD\fP, \fBOUTPUT\fP and \fBPOSTROUTING\fP chains). When the "!" argument is used before the interface name, the sense is inverted. If the interface name ends in a "+", then any interface which begins with this name will match. If this option is omitted, any interface name will match. .TP [\fB!\fP] \fB\-f\fP, \fB\-\-fragment\fP This means that the rule only refers to second and further fragments of fragmented packets. Since there is no way to tell the source or destination ports of such a packet (or ICMP type), such a packet will not match any rules which specify them. When the "!" argument precedes the "\-f" flag, the rule will only match head fragments, or unfragmented packets. .TP \fB\-c\fP, \fB\-\-set\-counters\fP \fIpackets bytes\fP This enables the administrator to initialize the packet and byte counters of a rule (during \fBINSERT\fP, \fBAPPEND\fP, \fBREPLACE\fP operations). .SS "OTHER OPTIONS" The following additional options can be specified: .TP \fB\-v\fP, \fB\-\-verbose\fP Verbose output. This option makes the list command show the interface name, the rule options (if any), and the TOS masks. The packet and byte counters are also listed, with the suffix 'K', 'M' or 'G' for 1000, 1,000,000 and 1,000,000,000 multipliers respectively (but see the \fB\-x\fP flag to change this). For appending, insertion, deletion and replacement, this causes detailed information on the rule or rules to be printed. \fB\-v\fP may be specified multiple times to possibly emit more detailed debug statements. .TP \fB\-n\fP, \fB\-\-numeric\fP Numeric output. IP addresses and port numbers will be printed in numeric format. By default, the program will try to display them as host names, network names, or services (whenever applicable). .TP \fB\-x\fP, \fB\-\-exact\fP Expand numbers. Display the exact value of the packet and byte counters, instead of only the rounded number in K's (multiples of 1000) M's (multiples of 1000K) or G's (multiples of 1000M). This option is only relevant for the \fB\-L\fP command. .TP \fB\-\-line\-numbers\fP When listing rules, add line numbers to the beginning of each rule, corresponding to that rule's position in the chain. .TP \fB\-\-modprobe=\fP\fIcommand\fP When adding or inserting rules into a chain, use \fIcommand\fP to load any necessary modules (targets, match extensions, etc). .SH MATCH EXTENSIONS .PP iptables can use extended packet matching modules with the \fB\-m\fP or \fB\-\-match\fP options, followed by the matching module name; after these, various extra command line options become available, depending on the specific module. You can specify multiple extended match modules in one line, and you can use the \fB\-h\fP or \fB\-\-help\fP options after the module has been specified to receive help specific to that module. .PP If the \fB\-p\fP or \fB\-\-protocol\fP was specified and if and only if an unknown option is encountered, iptables will try load a match module of the same name as the protocol, to try making the option available. .\" @MATCH@ .SS addrtype This module matches packets based on their .B address type. Address types are used within the kernel networking stack and categorize addresses into various groups. The exact definition of that group depends on the specific layer three protocol. .PP The following address types are possible: .TP .BI "UNSPEC" an unspecified address (i.e. 0.0.0.0) .TP .BI "UNICAST" an unicast address .TP .BI "LOCAL" a local address .TP .BI "BROADCAST" a broadcast address .TP .BI "ANYCAST" an anycast packet .TP .BI "MULTICAST" a multicast address .TP .BI "BLACKHOLE" a blackhole address .TP .BI "UNREACHABLE" an unreachable address .TP .BI "PROHIBIT" a prohibited address .TP .BI "THROW" FIXME .TP .BI "NAT" FIXME .TP .BI "XRESOLVE" .TP [\fB!\fP] \fB\-\-src\-type\fP \fItype\fP Matches if the source address is of given type .TP [\fB!\fP] \fB\-\-dst\-type\fP \fItype\fP Matches if the destination address is of given type .TP .BI "\-\-limit\-iface\-in" The address type checking can be limited to the interface the packet is coming in. This option is only valid in the .BR PREROUTING , .B INPUT and .B FORWARD chains. It cannot be specified with the \fB\-\-limit\-iface\-out\fP option. .TP \fB\-\-limit\-iface\-out\fP The address type checking can be limited to the interface the packet is going out. This option is only valid in the .BR POSTROUTING , .B OUTPUT and .B FORWARD chains. It cannot be specified with the \fB\-\-limit\-iface\-in\fP option. .SS ah This module matches the SPIs in Authentication header of IPsec packets. .TP [\fB!\fP] \fB\-\-ahspi\fP \fIspi\fP[\fB:\fP\fIspi\fP] .SS cluster Allows you to deploy gateway and back-end load-sharing clusters without the need of load-balancers. .PP This match requires that all the nodes see the same packets. Thus, the cluster match decides if this node has to handle a packet given the following options: .TP \fB\-\-cluster\-total\-nodes\fP \fInum\fP Set number of total nodes in cluster. .TP [\fB!\fP] \fB\-\-cluster\-local\-node\fP \fInum\fP Set the local node number ID. .TP [\fB!\fP] \fB\-\-cluster\-local\-nodemask\fP \fImask\fP Set the local node number ID mask. You can use this option instead of \fB\-\-cluster\-local\-node\fP. .TP \fB\-\-cluster\-hash\-seed\fP \fIvalue\fP Set seed value of the Jenkins hash. .PP Example: .IP iptables \-A PREROUTING \-t mangle \-i eth1 \-m cluster \-\-cluster\-total\-nodes 2 \-\-cluster\-local\-node 1 \-\-cluster\-hash\-seed 0xdeadbeef \-j MARK \-\-set-mark 0xffff .IP iptables \-A PREROUTING \-t mangle \-i eth2 \-m cluster \-\-cluster\-total\-nodes 2 \-\-cluster\-local\-node 1 \-\-cluster\-hash\-seed 0xdeadbeef \-j MARK -\-set\-mark 0xffff .IP iptables \-A PREROUTING \-t mangle \-i eth1 \-m mark ! \-\-mark 0xffff \-j DROP .IP iptables \-A PREROUTING \-t mangle \-i eth2 \-m mark ! \-\-mark 0xffff \-j DROP .PP And the following commands to make all nodes see the same packets: .IP ip maddr add 01:00:5e:00:01:01 dev eth1 .IP ip maddr add 01:00:5e:00:01:02 dev eth2 .IP arptables \-A OUTPUT \-o eth1 \-\-h\-length 6 \-j mangle \-\-mangle-mac-s 01:00:5e:00:01:01 .IP arptables \-A INPUT \-i eth1 \-\-h-length 6 \-\-destination-mac 01:00:5e:00:01:01 \-j mangle \-\-mangle\-mac\-d 00:zz:yy:xx:5a:27 .IP arptables \-A OUTPUT \-o eth2 \-\-h\-length 6 \-j mangle \-\-mangle\-mac\-s 01:00:5e:00:01:02 .IP arptables \-A INPUT \-i eth2 \-\-h\-length 6 \-\-destination\-mac 01:00:5e:00:01:02 \-j mangle \-\-mangle\-mac\-d 00:zz:yy:xx:5a:27 .PP In the case of TCP connections, pickup facility has to be disabled to avoid marking TCP ACK packets coming in the reply direction as valid. .IP echo 0 > /proc/sys/net/netfilter/nf_conntrack_tcp_loose .SS comment Allows you to add comments (up to 256 characters) to any rule. .TP \fB\-\-comment\fP \fIcomment\fP .TP Example: iptables \-A INPUT \-i eth1 \-m comment \-\-comment "my local LAN" .SS connbytes Match by how many bytes or packets a connection (or one of the two flows constituting the connection) has transferred so far, or by average bytes per packet. .PP The counters are 64-bit and are thus not expected to overflow ;) .PP The primary use is to detect long-lived downloads and mark them to be scheduled using a lower priority band in traffic control. .PP The transferred bytes per connection can also be viewed through `conntrack \-L` and accessed via ctnetlink. .PP NOTE that for connections which have no accounting information, the match will always return false. The "net.netfilter.nf_conntrack_acct" sysctl flag controls whether \fBnew\fP connections will be byte/packet counted. Existing connection flows will not be gaining/losing a/the accounting structure when be sysctl flag is flipped. .TP [\fB!\fP] \fB\-\-connbytes\fP \fIfrom\fP[\fB:\fP\fIto\fP] match packets from a connection whose packets/bytes/average packet size is more than FROM and less than TO bytes/packets. if TO is omitted only FROM check is done. "!" is used to match packets not falling in the range. .TP \fB\-\-connbytes\-dir\fP {\fBoriginal\fP|\fBreply\fP|\fBboth\fP} which packets to consider .TP \fB\-\-connbytes\-mode\fP {\fBpackets\fP|\fBbytes\fP|\fBavgpkt\fP} whether to check the amount of packets, number of bytes transferred or the average size (in bytes) of all packets received so far. Note that when "both" is used together with "avgpkt", and data is going (mainly) only in one direction (for example HTTP), the average packet size will be about half of the actual data packets. .TP Example: iptables .. \-m connbytes \-\-connbytes 10000:100000 \-\-connbytes\-dir both \-\-connbytes\-mode bytes ... .SS connlimit Allows you to restrict the number of parallel connections to a server per client IP address (or client address block). .TP \fB\-\-connlimit\-upto\fP \fIn\fP Match if the number of existing connections is below or equal \fIn\fP. .TP \fB\-\-connlimit\-above\fP \fIn\fP Match if the number of existing connections is above \fIn\fP. .TP \fB\-\-connlimit\-mask\fP \fIprefix_length\fP Group hosts using the prefix length. For IPv4, this must be a number between (including) 0 and 32. For IPv6, between 0 and 128. If not specified, the maximum prefix length for the applicable protocol is used. .TP \fB\-\-connlimit\-saddr\fP Apply the limit onto the source group. This is the default if \-\-connlimit\-daddr is not specified. .TP \fB\-\-connlimit\-daddr\fP Apply the limit onto the destination group. .PP Examples: .TP # allow 2 telnet connections per client host iptables \-A INPUT \-p tcp \-\-syn \-\-dport 23 \-m connlimit \-\-connlimit\-above 2 \-j REJECT .TP # you can also match the other way around: iptables \-A INPUT \-p tcp \-\-syn \-\-dport 23 \-m connlimit \-\-connlimit\-upto 2 \-j ACCEPT .TP # limit the number of parallel HTTP requests to 16 per class C sized \ source network (24 bit netmask) iptables \-p tcp \-\-syn \-\-dport 80 \-m connlimit \-\-connlimit\-above 16 \-\-connlimit\-mask 24 \-j REJECT .TP # limit the number of parallel HTTP requests to 16 for the link local network (ipv6) ip6tables \-p tcp \-\-syn \-\-dport 80 \-s fe80::/64 \-m connlimit \-\-connlimit\-above 16 \-\-connlimit\-mask 64 \-j REJECT .TP # Limit the number of connections to a particular host: ip6tables \-p tcp \-\-syn \-\-dport 49152:65535 \-d 2001:db8::1 \-m connlimit \-\-connlimit-above 100 \-j REJECT .SS connmark This module matches the netfilter mark field associated with a connection (which can be set using the \fBCONNMARK\fP target below). .TP [\fB!\fP] \fB\-\-mark\fP \fIvalue\fP[\fB/\fP\fImask\fP] Matches packets in connections with the given mark value (if a mask is specified, this is logically ANDed with the mark before the comparison). .SS conntrack This module, when combined with connection tracking, allows access to the connection tracking state for this packet/connection. .TP [\fB!\fP] \fB\-\-ctstate\fP \fIstatelist\fP \fIstatelist\fP is a comma separated list of the connection states to match. Possible states are listed below. .TP [\fB!\fP] \fB\-\-ctproto\fP \fIl4proto\fP Layer-4 protocol to match (by number or name) .TP [\fB!\fP] \fB\-\-ctorigsrc\fP \fIaddress\fP[\fB/\fP\fImask\fP] .TP [\fB!\fP] \fB\-\-ctorigdst\fP \fIaddress\fP[\fB/\fP\fImask\fP] .TP [\fB!\fP] \fB\-\-ctreplsrc\fP \fIaddress\fP[\fB/\fP\fImask\fP] .TP [\fB!\fP] \fB\-\-ctrepldst\fP \fIaddress\fP[\fB/\fP\fImask\fP] Match against original/reply source/destination address .TP [\fB!\fP] \fB\-\-ctorigsrcport\fP \fIport\fP[\fB:\fP\fIport\fP] .TP [\fB!\fP] \fB\-\-ctorigdstport\fP \fIport\fP[\fB:\fP\fIport\fP] .TP [\fB!\fP] \fB\-\-ctreplsrcport\fP \fIport\fP[\fB:\fP\fIport\fP] .TP [\fB!\fP] \fB\-\-ctrepldstport\fP \fIport\fP[\fB:\fP\fIport\fP] Match against original/reply source/destination port (TCP/UDP/etc.) or GRE key. Matching against port ranges is only supported in kernel versions above 2.6.38. .TP [\fB!\fP] \fB\-\-ctstatus\fP \fIstatelist\fP \fIstatuslist\fP is a comma separated list of the connection statuses to match. Possible statuses are listed below. .TP [\fB!\fP] \fB\-\-ctexpire\fP \fItime\fP[\fB:\fP\fItime\fP] Match remaining lifetime in seconds against given value or range of values (inclusive) .TP \fB\-\-ctdir\fP {\fBORIGINAL\fP|\fBREPLY\fP} Match packets that are flowing in the specified direction. If this flag is not specified at all, matches packets in both directions. .PP States for \fB\-\-ctstate\fP: .TP \fBINVALID\fP meaning that the packet is associated with no known connection .TP \fBNEW\fP meaning that the packet has started a new connection, or otherwise associated with a connection which has not seen packets in both directions, and .TP \fBESTABLISHED\fP meaning that the packet is associated with a connection which has seen packets in both directions, .TP \fBRELATED\fP meaning that the packet is starting a new connection, but is associated with an existing connection, such as an FTP data transfer, or an ICMP error. .TP \fBUNTRACKED\fP meaning that the packet is not tracked at all, which happens if you use the NOTRACK target in raw table. .TP \fBSNAT\fP A virtual state, matching if the original source address differs from the reply destination. .TP \fBDNAT\fP A virtual state, matching if the original destination differs from the reply source. .PP Statuses for \fB\-\-ctstatus\fP: .TP \fBNONE\fP None of the below. .TP \fBEXPECTED\fP This is an expected connection (i.e. a conntrack helper set it up) .TP \fBSEEN_REPLY\fP Conntrack has seen packets in both directions. .TP \fBASSURED\fP Conntrack entry should never be early-expired. .TP \fBCONFIRMED\fP Connection is confirmed: originating packet has left box. .SS cpu .TP [\fB!\fP] \fB\-\-cpu\fP \fInumber\fP Match cpu handling this packet. cpus are numbered from 0 to NR_CPUS-1 Can be used in combination with RPS (Remote Packet Steering) or multiqueue NICs to spread network traffic on different queues. .PP Example: .PP iptables \-t nat \-A PREROUTING \-p tcp \-\-dport 80 \-m cpu \-\-cpu 0 \-j REDIRECT \-\-to\-port 8080 .PP iptables \-t nat \-A PREROUTING \-p tcp \-\-dport 80 \-m cpu \-\-cpu 1 \-j REDIRECT \-\-to\-port 8081 .PP Available since Linux 2.6.36. .SS dccp .TP [\fB!\fP] \fB\-\-source\-port\fP,\fB\-\-sport\fP \fIport\fP[\fB:\fP\fIport\fP] .TP [\fB!\fP] \fB\-\-destination\-port\fP,\fB\-\-dport\fP \fIport\fP[\fB:\fP\fIport\fP] .TP [\fB!\fP] \fB\-\-dccp\-types\fP \fImask\fP Match when the DCCP packet type is one of 'mask'. 'mask' is a comma-separated list of packet types. Packet types are: .BR "REQUEST RESPONSE DATA ACK DATAACK CLOSEREQ CLOSE RESET SYNC SYNCACK INVALID" . .TP [\fB!\fP] \fB\-\-dccp\-option\fP \fInumber\fP Match if DCCP option set. .SS dscp This module matches the 6 bit DSCP field within the TOS field in the IP header. DSCP has superseded TOS within the IETF. .TP [\fB!\fP] \fB\-\-dscp\fP \fIvalue\fP Match against a numeric (decimal or hex) value [0-63]. .TP [\fB!\fP] \fB\-\-dscp\-class\fP \fIclass\fP Match the DiffServ class. This value may be any of the BE, EF, AFxx or CSx classes. It will then be converted into its according numeric value. .SS ecn This allows you to match the ECN bits of the IPv4/IPv6 and TCP header. ECN is the Explicit Congestion Notification mechanism as specified in RFC3168 .TP [\fB!\fP] \fB\-\-ecn\-tcp\-cwr\fP This matches if the TCP ECN CWR (Congestion Window Received) bit is set. .TP [\fB!\fP] \fB\-\-ecn\-tcp\-ece\fP This matches if the TCP ECN ECE (ECN Echo) bit is set. .TP [\fB!\fP] \fB\-\-ecn\-ip\-ect\fP \fInum\fP This matches a particular IPv4/IPv6 ECT (ECN-Capable Transport). You have to specify a number between `0' and `3'. .SS esp This module matches the SPIs in ESP header of IPsec packets. .TP [\fB!\fP] \fB\-\-espspi\fP \fIspi\fP[\fB:\fP\fIspi\fP] .SS hashlimit \fBhashlimit\fP uses hash buckets to express a rate limiting match (like the \fBlimit\fP match) for a group of connections using a \fBsingle\fP iptables rule. Grouping can be done per-hostgroup (source and/or destination address) and/or per-port. It gives you the ability to express "\fIN\fP packets per time quantum per group" (see below for some examples). .PP A hash limit option (\fB\-\-hashlimit\-upto\fP, \fB\-\-hashlimit\-above\fP) and \fB\-\-hashlimit\-name\fP are required. .TP \fB\-\-hashlimit\-upto\fP \fIamount\fP[\fB/second\fP|\fB/minute\fP|\fB/hour\fP|\fB/day\fP] Match if the rate is below or equal to \fIamount\fP/quantum. It is specified as a number, with an optional time quantum suffix; the default is 3/hour. .TP \fB\-\-hashlimit\-above\fP \fIamount\fP[\fB/second\fP|\fB/minute\fP|\fB/hour\fP|\fB/day\fP] Match if the rate is above \fIamount\fP/quantum. .TP \fB\-\-hashlimit\-burst\fP \fIamount\fP Maximum initial number of packets to match: this number gets recharged by one every time the limit specified above is not reached, up to this number; the default is 5. .TP \fB\-\-hashlimit\-mode\fP {\fBsrcip\fP|\fBsrcport\fP|\fBdstip\fP|\fBdstport\fP}\fB,\fP... A comma-separated list of objects to take into consideration. If no \-\-hashlimit\-mode option is given, hashlimit acts like limit, but at the expensive of doing the hash housekeeping. .TP \fB\-\-hashlimit\-srcmask\fP \fIprefix\fP When \-\-hashlimit\-mode srcip is used, all source addresses encountered will be grouped according to the given prefix length and the so-created subnet will be subject to hashlimit. \fIprefix\fP must be between (inclusive) 0 and 32. Note that \-\-hashlimit\-srcmask 0 is basically doing the same thing as not specifying srcip for \-\-hashlimit\-mode, but is technically more expensive. .TP \fB\-\-hashlimit\-dstmask\fP \fIprefix\fP Like \-\-hashlimit\-srcmask, but for destination addresses. .TP \fB\-\-hashlimit\-name\fP \fIfoo\fP The name for the /proc/net/ipt_hashlimit/foo entry. .TP \fB\-\-hashlimit\-htable\-size\fP \fIbuckets\fP The number of buckets of the hash table .TP \fB\-\-hashlimit\-htable\-max\fP \fIentries\fP Maximum entries in the hash. .TP \fB\-\-hashlimit\-htable\-expire\fP \fImsec\fP After how many milliseconds do hash entries expire. .TP \fB\-\-hashlimit\-htable\-gcinterval\fP \fImsec\fP How many milliseconds between garbage collection intervals. .PP Examples: .TP matching on source host "1000 packets per second for every host in 192.168.0.0/16" => \-s 192.168.0.0/16 \-\-hashlimit\-mode srcip \-\-hashlimit\-upto 1000/sec .TP matching on source port "100 packets per second for every service of 192.168.1.1" => \-s 192.168.1.1 \-\-hashlimit\-mode srcport \-\-hashlimit\-upto 100/sec .TP matching on subnet "10000 packets per minute for every /28 subnet (groups of 8 addresses) in 10.0.0.0/8" => \-s 10.0.0.8 \-\-hashlimit\-mask 28 \-\-hashlimit\-upto 10000/min .SS helper This module matches packets related to a specific conntrack-helper. .TP [\fB!\fP] \fB\-\-helper\fP \fIstring\fP Matches packets related to the specified conntrack-helper. .RS .PP string can be "ftp" for packets related to a ftp-session on default port. For other ports append \-portnr to the value, ie. "ftp\-2121". .PP Same rules apply for other conntrack-helpers. .RE .SS icmp This extension can be used if `\-\-protocol icmp' is specified. It provides the following option: .TP [\fB!\fP] \fB\-\-icmp\-type\fP {\fItype\fP[\fB/\fP\fIcode\fP]|\fItypename\fP} This allows specification of the ICMP type, which can be a numeric ICMP type, type/code pair, or one of the ICMP type names shown by the command .nf iptables \-p icmp \-h .fi .SS iprange This matches on a given arbitrary range of IP addresses. .TP [\fB!\fP] \fB\-\-src\-range\fP \fIfrom\fP[\fB\-\fP\fIto\fP] Match source IP in the specified range. .TP [\fB!\fP] \fB\-\-dst\-range\fP \fIfrom\fP[\fB\-\fP\fIto\fP] Match destination IP in the specified range. .SS ipvs Match IPVS connection properties. .TP [\fB!\fP] \fB\-\-ipvs\fP packet belongs to an IPVS connection .TP Any of the following options implies \-\-ipvs (even negated) .TP [\fB!\fP] \fB\-\-vproto\fP \fIprotocol\fP VIP protocol to match; by number or name, e.g. "tcp" .TP [\fB!\fP] \fB\-\-vaddr\fP \fIaddress\fP[\fB/\fP\fImask\fP] VIP address to match .TP [\fB!\fP] \fB\-\-vport\fP \fIport\fP VIP port to match; by number or name, e.g. "http" .TP \fB\-\-vdir\fP {\fBORIGINAL\fP|\fBREPLY\fP} flow direction of packet .TP [\fB!\fP] \fB\-\-vmethod\fP {\fBGATE\fP|\fBIPIP\fP|\fBMASQ\fP} IPVS forwarding method used .TP [\fB!\fP] \fB\-\-vportctl\fP \fIport\fP VIP port of the controlling connection to match, e.g. 21 for FTP .SS length This module matches the length of the layer-3 payload (e.g. layer-4 packet) of a packet against a specific value or range of values. .TP [\fB!\fP] \fB\-\-length\fP \fIlength\fP[\fB:\fP\fIlength\fP] .SS limit This module matches at a limited rate using a token bucket filter. A rule using this extension will match until this limit is reached. It can be used in combination with the .B LOG target to give limited logging, for example. .PP xt_limit has no negation support - you will have to use \-m hashlimit ! \-\-hashlimit \fIrate\fP in this case whilst omitting \-\-hashlimit\-mode. .TP \fB\-\-limit\fP \fIrate\fP[\fB/second\fP|\fB/minute\fP|\fB/hour\fP|\fB/day\fP] Maximum average matching rate: specified as a number, with an optional `/second', `/minute', `/hour', or `/day' suffix; the default is 3/hour. .TP \fB\-\-limit\-burst\fP \fInumber\fP Maximum initial number of packets to match: this number gets recharged by one every time the limit specified above is not reached, up to this number; the default is 5. .SS mac .TP [\fB!\fP] \fB\-\-mac\-source\fP \fIaddress\fP Match source MAC address. It must be of the form XX:XX:XX:XX:XX:XX. Note that this only makes sense for packets coming from an Ethernet device and entering the .BR PREROUTING , .B FORWARD or .B INPUT chains. .SS mark This module matches the netfilter mark field associated with a packet (which can be set using the .B MARK target below). .TP [\fB!\fP] \fB\-\-mark\fP \fIvalue\fP[\fB/\fP\fImask\fP] Matches packets with the given unsigned mark value (if a \fImask\fP is specified, this is logically ANDed with the \fImask\fP before the comparison). .SS multiport This module matches a set of source or destination ports. Up to 15 ports can be specified. A port range (port:port) counts as two ports. It can only be used in conjunction with \fB\-p tcp\fP or \fB\-p udp\fP. .TP [\fB!\fP] \fB\-\-source\-ports\fP,\fB\-\-sports\fP \fIport\fP[\fB,\fP\fIport\fP|\fB,\fP\fIport\fP\fB:\fP\fIport\fP]... Match if the source port is one of the given ports. The flag \fB\-\-sports\fP is a convenient alias for this option. Multiple ports or port ranges are separated using a comma, and a port range is specified using a colon. \fB53,1024:65535\fP would therefore match ports 53 and all from 1024 through 65535. .TP [\fB!\fP] \fB\-\-destination\-ports\fP,\fB\-\-dports\fP \fIport\fP[\fB,\fP\fIport\fP|\fB,\fP\fIport\fP\fB:\fP\fIport\fP]... Match if the destination port is one of the given ports. The flag \fB\-\-dports\fP is a convenient alias for this option. .TP [\fB!\fP] \fB\-\-ports\fP \fIport\fP[\fB,\fP\fIport\fP|\fB,\fP\fIport\fP\fB:\fP\fIport\fP]... Match if either the source or destination ports are equal to one of the given ports. .SS nfacct The nfacct match provides the extended accounting infrastructure for iptables. You have to use this match together with the standalone user-space utility .B nfacct(8) .PP The only option available for this match is the following: .TP \fB\-\-nfacct\-name\fP \fIname\fP This allows you to specify the existing object name that will be use for accounting the traffic that this rule-set is matching. .PP To use this extension, you have to create an accounting object: .IP nfacct add http\-traffic .PP Then, you have to attach it to the accounting object via iptables: .IP iptables \-I INPUT \-p tcp \-\-sport 80 \-m nfacct \-\-nfacct\-name http\-traffic .IP iptables \-I OUTPUT \-p tcp \-\-dport 80 \-m nfacct \-\-nfacct\-name http\-traffic .PP Then, you can check for the amount of traffic that the rules match: .IP nfacct get http\-traffic .IP { pkts = 00000000000000000156, bytes = 00000000000000151786 } = http-traffic; .PP You can obtain .B nfacct(8) from http://www.netfilter.org or, alternatively, from the git.netfilter.org repository. .SS osf The osf module does passive operating system fingerprinting. This modules compares some data (Window Size, MSS, options and their order, TTL, DF, and others) from packets with the SYN bit set. .TP [\fB!\fP] \fB\-\-genre\fP \fIstring\fP Match an operating system genre by using a passive fingerprinting. .TP \fB\-\-ttl\fP \fIlevel\fP Do additional TTL checks on the packet to determine the operating system. \fIlevel\fP can be one of the following values: .IP \(bu 4 0 - True IP address and fingerprint TTL comparison. This generally works for LANs. .IP \(bu 4 1 - Check if the IP header's TTL is less than the fingerprint one. Works for globally-routable addresses. .IP \(bu 4 2 - Do not compare the TTL at all. .TP \fB\-\-log\fP \fIlevel\fP Log determined genres into dmesg even if they do not match the desired one. \fIlevel\fP can be one of the following values: .IP \(bu 4 0 - Log all matched or unknown signatures .IP \(bu 4 1 - Log only the first one .IP \(bu 4 2 - Log all known matched signatures .PP You may find something like this in syslog: .PP Windows [2000:SP3:Windows XP Pro SP1, 2000 SP3]: 11.22.33.55:4024 -> 11.22.33.44:139 hops=3 Linux [2.5-2.6:] : 1.2.3.4:42624 -> 1.2.3.5:22 hops=4 .PP OS fingerprints are loadable using the \fBnfnl_osf\fP program. To load fingerprints from a file, use: .PP \fBnfnl_osf -f /usr/share/xtables/pf.os\fP .PP To remove them again, .PP \fBnfnl_osf -f /usr/share/xtables/pf.os -d\fP .PP The fingerprint database can be downlaoded from http://www.openbsd.org/cgi-bin/cvsweb/src/etc/pf.os . .SS owner This module attempts to match various characteristics of the packet creator, for locally generated packets. This match is only valid in the OUTPUT and POSTROUTING chains. Forwarded packets do not have any socket associated with them. Packets from kernel threads do have a socket, but usually no owner. .TP [\fB!\fP] \fB\-\-uid\-owner\fP \fIusername\fP .TP [\fB!\fP] \fB\-\-uid\-owner\fP \fIuserid\fP[\fB\-\fP\fIuserid\fP] Matches if the packet socket's file structure (if it has one) is owned by the given user. You may also specify a numerical UID, or an UID range. .TP [\fB!\fP] \fB\-\-gid\-owner\fP \fIgroupname\fP .TP [\fB!\fP] \fB\-\-gid\-owner\fP \fIgroupid\fP[\fB\-\fP\fIgroupid\fP] Matches if the packet socket's file structure is owned by the given group. You may also specify a numerical GID, or a GID range. .TP [\fB!\fP] \fB\-\-socket\-exists\fP Matches if the packet is associated with a socket. .SS physdev This module matches on the bridge port input and output devices enslaved to a bridge device. This module is a part of the infrastructure that enables a transparent bridging IP firewall and is only useful for kernel versions above version 2.5.44. .TP [\fB!\fP] \fB\-\-physdev\-in\fP \fIname\fP Name of a bridge port via which a packet is received (only for packets entering the .BR INPUT , .B FORWARD and .B PREROUTING chains). If the interface name ends in a "+", then any interface which begins with this name will match. If the packet didn't arrive through a bridge device, this packet won't match this option, unless '!' is used. .TP [\fB!\fP] \fB\-\-physdev\-out\fP \fIname\fP Name of a bridge port via which a packet is going to be sent (for packets entering the .BR FORWARD , .B OUTPUT and .B POSTROUTING chains). If the interface name ends in a "+", then any interface which begins with this name will match. Note that in the .BR nat " and " mangle .B OUTPUT chains one cannot match on the bridge output port, however one can in the .B "filter OUTPUT" chain. If the packet won't leave by a bridge device or if it is yet unknown what the output device will be, then the packet won't match this option, unless '!' is used. .TP [\fB!\fP] \fB\-\-physdev\-is\-in\fP Matches if the packet has entered through a bridge interface. .TP [\fB!\fP] \fB\-\-physdev\-is\-out\fP Matches if the packet will leave through a bridge interface. .TP [\fB!\fP] \fB\-\-physdev\-is\-bridged\fP Matches if the packet is being bridged and therefore is not being routed. This is only useful in the FORWARD and POSTROUTING chains. .SS pkttype This module matches the link-layer packet type. .TP [\fB!\fP] \fB\-\-pkt\-type\fP {\fBunicast\fP|\fBbroadcast\fP|\fBmulticast\fP} .SS policy This modules matches the policy used by IPsec for handling a packet. .TP \fB\-\-dir\fP {\fBin\fP|\fBout\fP} Used to select whether to match the policy used for decapsulation or the policy that will be used for encapsulation. .B in is valid in the .B PREROUTING, INPUT and FORWARD chains, .B out is valid in the .B POSTROUTING, OUTPUT and FORWARD chains. .TP \fB\-\-pol\fP {\fBnone\fP|\fBipsec\fP} Matches if the packet is subject to IPsec processing. \fB\-\-pol none\fP cannot be combined with \fB\-\-strict\fP. .TP \fB\-\-strict\fP Selects whether to match the exact policy or match if any rule of the policy matches the given policy. .PP For each policy element that is to be described, one can use one or more of the following options. When \fB\-\-strict\fP is in effect, at least one must be used per element. .TP [\fB!\fP] \fB\-\-reqid\fP \fIid\fP Matches the reqid of the policy rule. The reqid can be specified with .B setkey(8) using .B unique:id as level. .TP [\fB!\fP] \fB\-\-spi\fP \fIspi\fP Matches the SPI of the SA. .TP [\fB!\fP] \fB\-\-proto\fP {\fBah\fP|\fBesp\fP|\fBipcomp\fP} Matches the encapsulation protocol. .TP [\fB!\fP] \fB\-\-mode\fP {\fBtunnel\fP|\fBtransport\fP} Matches the encapsulation mode. .TP [\fB!\fP] \fB\-\-tunnel\-src\fP \fIaddr\fP[\fB/\fP\fImask\fP] Matches the source end-point address of a tunnel mode SA. Only valid with \fB\-\-mode tunnel\fP. .TP [\fB!\fP] \fB\-\-tunnel\-dst\fP \fIaddr\fP[\fB/\fP\fImask\fP] Matches the destination end-point address of a tunnel mode SA. Only valid with \fB\-\-mode tunnel\fP. .TP \fB\-\-next\fP Start the next element in the policy specification. Can only be used with \fB\-\-strict\fP. .SS quota Implements network quotas by decrementing a byte counter with each packet. The condition matches until the byte counter reaches zero. Behavior is reversed with negation (i.e. the condition does not match until the byte counter reaches zero). .TP [\fB!\fP] \fB\-\-quota\fP \fIbytes\fP The quota in bytes. .SS rateest The rate estimator can match on estimated rates as collected by the RATEEST target. It supports matching on absolute bps/pps values, comparing two rate estimators and matching on the difference between two rate estimators. .PP For a better understanding of the available options, these are all possible combinations: .\" * Absolute: .IP \(bu 4 \fBrateest\fP \fIoperator\fP \fBrateest-bps\fP .IP \(bu 4 \fBrateest\fP \fIoperator\fP \fBrateest-pps\fP .\" * Absolute + Delta: .IP \(bu 4 (\fBrateest\fP minus \fBrateest-bps1\fP) \fIoperator\fP \fBrateest-bps2\fP .IP \(bu 4 (\fBrateest\fP minus \fBrateest-pps1\fP) \fIoperator\fP \fBrateest-pps2\fP .\" * Relative: .IP \(bu 4 \fBrateest1\fP \fIoperator\fP \fBrateest2\fP \fBrateest-bps\fP(without rate!) .IP \(bu 4 \fBrateest1\fP \fIoperator\fP \fBrateest2\fP \fBrateest-pps\fP(without rate!) .\" * Relative + Delta: .IP \(bu 4 (\fBrateest1\fP minus \fBrateest-bps1\fP) \fIoperator\fP (\fBrateest2\fP minus \fBrateest-bps2\fP) .IP \(bu 4 (\fBrateest1\fP minus \fBrateest-pps1\fP) \fIoperator\fP (\fBrateest2\fP minus \fBrateest-pps2\fP) .TP \fB\-\-rateest\-delta\fP For each estimator (either absolute or relative mode), calculate the difference between the estimator-determined flow rate and the static value chosen with the BPS/PPS options. If the flow rate is higher than the specified BPS/PPS, 0 will be used instead of a negative value. In other words, "max(0, rateest#_rate - rateest#_bps)" is used. .TP [\fB!\fP] \fB\-\-rateest\-lt\fP Match if rate is less than given rate/estimator. .TP [\fB!\fP] \fB\-\-rateest\-gt\fP Match if rate is greater than given rate/estimator. .TP [\fB!\fP] \fB\-\-rateest\-eq\fP Match if rate is equal to given rate/estimator. .PP In the so-called "absolute mode", only one rate estimator is used and compared against a static value, while in "relative mode", two rate estimators are compared against another. .TP \fB\-\-rateest\fP \fIname\fP Name of the one rate estimator for absolute mode. .TP \fB\-\-rateest1\fP \fIname\fP .TP \fB\-\-rateest2\fP \fIname\fP The names of the two rate estimators for relative mode. .TP \fB\-\-rateest\-bps\fP [\fIvalue\fP] .TP \fB\-\-rateest\-pps\fP [\fIvalue\fP] .TP \fB\-\-rateest\-bps1\fP [\fIvalue\fP] .TP \fB\-\-rateest\-bps2\fP [\fIvalue\fP] .TP \fB\-\-rateest\-pps1\fP [\fIvalue\fP] .TP \fB\-\-rateest\-pps2\fP [\fIvalue\fP] Compare the estimator(s) by bytes or packets per second, and compare against the chosen value. See the above bullet list for which option is to be used in which case. A unit suffix may be used - available ones are: bit, [kmgt]bit, [KMGT]ibit, Bps, [KMGT]Bps, [KMGT]iBps. .PP Example: This is what can be used to route outgoing data connections from an FTP server over two lines based on the available bandwidth at the time the data connection was started: .PP # Estimate outgoing rates .PP iptables \-t mangle \-A POSTROUTING \-o eth0 \-j RATEEST \-\-rateest\-name eth0 \-\-rateest\-interval 250ms \-\-rateest\-ewma 0.5s .PP iptables \-t mangle \-A POSTROUTING \-o ppp0 \-j RATEEST \-\-rateest\-name ppp0 \-\-rateest\-interval 250ms \-\-rateest\-ewma 0.5s .PP # Mark based on available bandwidth .PP iptables \-t mangle \-A balance \-m conntrack \-\-ctstate NEW \-m helper \-\-helper ftp \-m rateest \-\-rateest\-delta \-\-rateest1 eth0 \-\-rateest\-bps1 2.5mbit \-\-rateest\-gt \-\-rateest2 ppp0 \-\-rateest\-bps2 2mbit \-j CONNMARK \-\-set\-mark 1 .PP iptables \-t mangle \-A balance \-m conntrack \-\-ctstate NEW \-m helper \-\-helper ftp \-m rateest \-\-rateest\-delta \-\-rateest1 ppp0 \-\-rateest\-bps1 2mbit \-\-rateest\-gt \-\-rateest2 eth0 \-\-rateest\-bps2 2.5mbit \-j CONNMARK \-\-set\-mark 2 .PP iptables \-t mangle \-A balance \-j CONNMARK \-\-restore\-mark .SS realm This matches the routing realm. Routing realms are used in complex routing setups involving dynamic routing protocols like BGP. .TP [\fB!\fP] \fB\-\-realm\fP \fIvalue\fP[\fB/\fP\fImask\fP] Matches a given realm number (and optionally mask). If not a number, value can be a named realm from /etc/iproute2/rt_realms (mask can not be used in that case). .SS recent Allows you to dynamically create a list of IP addresses and then match against that list in a few different ways. .PP For example, you can create a "badguy" list out of people attempting to connect to port 139 on your firewall and then DROP all future packets from them without considering them. .PP \fB\-\-set\fP, \fB\-\-rcheck\fP, \fB\-\-update\fP and \fB\-\-remove\fP are mutually exclusive. .TP \fB\-\-name\fP \fIname\fP Specify the list to use for the commands. If no name is given then \fBDEFAULT\fP will be used. .TP [\fB!\fP] \fB\-\-set\fP This will add the source address of the packet to the list. If the source address is already in the list, this will update the existing entry. This will always return success (or failure if \fB!\fP is passed in). .TP \fB\-\-rsource\fP Match/save the source address of each packet in the recent list table. This is the default. .TP \fB\-\-rdest\fP Match/save the destination address of each packet in the recent list table. .TP [\fB!\fP] \fB\-\-rcheck\fP Check if the source address of the packet is currently in the list. .TP [\fB!\fP] \fB\-\-update\fP Like \fB\-\-rcheck\fP, except it will update the "last seen" timestamp if it matches. .TP [\fB!\fP] \fB\-\-remove\fP Check if the source address of the packet is currently in the list and if so that address will be removed from the list and the rule will return true. If the address is not found, false is returned. .TP \fB\-\-seconds\fP \fIseconds\fP This option must be used in conjunction with one of \fB\-\-rcheck\fP or \fB\-\-update\fP. When used, this will narrow the match to only happen when the address is in the list and was seen within the last given number of seconds. .TP \fB\-\-reap\fP This option can only be used in conjunction with \fB\-\-seconds\fP. When used, this will cause entries older than the last given number of seconds to be purged. .TP \fB\-\-hitcount\fP \fIhits\fP This option must be used in conjunction with one of \fB\-\-rcheck\fP or \fB\-\-update\fP. When used, this will narrow the match to only happen when the address is in the list and packets had been received greater than or equal to the given value. This option may be used along with \fB\-\-seconds\fP to create an even narrower match requiring a certain number of hits within a specific time frame. The maximum value for the hitcount parameter is given by the "ip_pkt_list_tot" parameter of the xt_recent kernel module. Exceeding this value on the command line will cause the rule to be rejected. .TP \fB\-\-rttl\fP This option may only be used in conjunction with one of \fB\-\-rcheck\fP or \fB\-\-update\fP. When used, this will narrow the match to only happen when the address is in the list and the TTL of the current packet matches that of the packet which hit the \fB\-\-set\fP rule. This may be useful if you have problems with people faking their source address in order to DoS you via this module by disallowing others access to your site by sending bogus packets to you. .PP Examples: .IP iptables \-A FORWARD \-m recent \-\-name badguy \-\-rcheck \-\-seconds 60 \-j DROP .IP iptables \-A FORWARD \-p tcp \-i eth0 \-\-dport 139 \-m recent \-\-name badguy \-\-set \-j DROP .PP Steve's ipt_recent website (http://snowman.net/projects/ipt_recent/) also has some examples of usage. .PP \fB/proc/net/xt_recent/*\fP are the current lists of addresses and information about each entry of each list. .PP Each file in \fB/proc/net/xt_recent/\fP can be read from to see the current list or written two using the following commands to modify the list: .TP \fBecho +\fP\fIaddr\fP\fB >/proc/net/xt_recent/DEFAULT\fP to add \fIaddr\fP to the DEFAULT list .TP \fBecho \-\fP\fIaddr\fP\fB >/proc/net/xt_recent/DEFAULT\fP to remove \fIaddr\fP from the DEFAULT list .TP \fBecho / >/proc/net/xt_recent/DEFAULT\fP to flush the DEFAULT list (remove all entries). .PP The module itself accepts parameters, defaults shown: .TP \fBip_list_tot\fP=\fI100\fP Number of addresses remembered per table. .TP \fBip_pkt_list_tot\fP=\fI20\fP Number of packets per address remembered. .TP \fBip_list_hash_size\fP=\fI0\fP Hash table size. 0 means to calculate it based on ip_list_tot, default: 512. .TP \fBip_list_perms\fP=\fI0644\fP Permissions for /proc/net/xt_recent/* files. .TP \fBip_list_uid\fP=\fI0\fP Numerical UID for ownership of /proc/net/xt_recent/* files. .TP \fBip_list_gid\fP=\fI0\fP Numerical GID for ownership of /proc/net/xt_recent/* files. .SS rpfilter Performs a reverse path filter test on a packet. If a reply to the packet would be sent via the same interface that the packet arrived on, the packet will match. Note that, unlike the in-kernel rp_filter, packets protected by IPSec are not treated specially. Combine this match with the policy match if you want this. Also, packets arriving via the loopback interface are always permitted. This match can only be used in the PREROUTING chain of the raw or mangle table. .TP \fB\-\-loose\fP Used to specifiy that the reverse path filter test should match even if the selected output device is not the expected one. .TP \fB\-\-validmark\fP Also use the packets' nfmark value when performing the reverse path route lookup. .TP \fB\-\-accept\-local\fP This will permit packets arriving from the network with a source address that is also assigned to the local machine. \fB\-\-invert\fP This will invert the sense of the match. Instead of matching packets that passed the reverse path filter test, match those that have failed it. .PP Example to log and drop packets failing the reverse path filter test: iptables \-t raw \-N RPFILTER iptables \-t raw \-A RPFILTER \-m rpfilter \-j RETURN iptables \-t raw \-A RPFILTER \-m limit \-\-limit 10/minute \-j NFLOG \-\-nflog\-prefix "rpfilter drop" iptables \-t raw \-A RPFILTER \-j DROP iptables \-t raw \-A PREROUTING \-j RPFILTER Example to drop failed packets, without logging: iptables \-t raw \-A RPFILTER \-m rpfilter \-\-invert \-j DROP .SS sctp .TP [\fB!\fP] \fB\-\-source\-port\fP,\fB\-\-sport\fP \fIport\fP[\fB:\fP\fIport\fP] .TP [\fB!\fP] \fB\-\-destination\-port\fP,\fB\-\-dport\fP \fIport\fP[\fB:\fP\fIport\fP] .TP [\fB!\fP] \fB\-\-chunk\-types\fP {\fBall\fP|\fBany\fP|\fBonly\fP} \fIchunktype\fP[\fB:\fP\fIflags\fP] [...] The flag letter in upper case indicates that the flag is to match if set, in the lower case indicates to match if unset. Chunk types: DATA INIT INIT_ACK SACK HEARTBEAT HEARTBEAT_ACK ABORT SHUTDOWN SHUTDOWN_ACK ERROR COOKIE_ECHO COOKIE_ACK ECN_ECNE ECN_CWR SHUTDOWN_COMPLETE ASCONF ASCONF_ACK FORWARD_TSN chunk type available flags .br DATA I U B E i u b e .br ABORT T t .br SHUTDOWN_COMPLETE T t (lowercase means flag should be "off", uppercase means "on") .P Examples: iptables \-A INPUT \-p sctp \-\-dport 80 \-j DROP iptables \-A INPUT \-p sctp \-\-chunk\-types any DATA,INIT \-j DROP iptables \-A INPUT \-p sctp \-\-chunk\-types any DATA:Be \-j ACCEPT .SS set This module matches IP sets which can be defined by ipset(8). .TP [\fB!\fP] \fB\-\-match\-set\fP \fIsetname\fP \fIflag\fP[\fB,\fP\fIflag\fP]... where flags are the comma separated list of .BR "src" and/or .BR "dst" specifications and there can be no more than six of them. Hence the command .IP iptables \-A FORWARD \-m set \-\-match\-set test src,dst .IP will match packets, for which (if the set type is ipportmap) the source address and destination port pair can be found in the specified set. If the set type of the specified set is single dimension (for example ipmap), then the command will match packets for which the source address can be found in the specified set. .PP The option \fB\-\-match\-set\fP can be replaced by \fB\-\-set\fP if that does not clash with an option of other extensions. .PP Use of -m set requires that ipset kernel support is provided, which, for standard kernels, is the case since Linux 2.6.39. .SS socket This matches if an open socket can be found by doing a socket lookup on the packet. .TP \fB\-\-transparent\fP Ignore non-transparent sockets. .SS state This module, when combined with connection tracking, allows access to the connection tracking state for this packet. .TP [\fB!\fP] \fB\-\-state\fP \fIstate\fP Where state is a comma separated list of the connection states to match. Possible states are .B INVALID meaning that the packet could not be identified for some reason which includes running out of memory and ICMP errors which don't correspond to any known connection, .B ESTABLISHED meaning that the packet is associated with a connection which has seen packets in both directions, .B NEW meaning that the packet has started a new connection, or otherwise associated with a connection which has not seen packets in both directions, and .B RELATED meaning that the packet is starting a new connection, but is associated with an existing connection, such as an FTP data transfer, or an ICMP error. .B UNTRACKED meaning that the packet is not tracked at all, which happens if you use the NOTRACK target in raw table. .SS statistic This module matches packets based on some statistic condition. It supports two distinct modes settable with the \fB\-\-mode\fP option. .PP Supported options: .TP \fB\-\-mode\fP \fImode\fP Set the matching mode of the matching rule, supported modes are .B random and .B nth. .TP [\fB!\fP] \fB\-\-probability\fP \fIp\fP Set the probability for a packet to be randomly matched. It only works with the \fBrandom\fP mode. \fIp\fP must be within 0.0 and 1.0. The supported granularity is in 1/2147483648th increments. .TP [\fB!\fP] \fB\-\-every\fP \fIn\fP Match one packet every nth packet. It works only with the .B nth mode (see also the \fB\-\-packet\fP option). .TP \fB\-\-packet\fP \fIp\fP Set the initial counter value (0 <= p <= n\-1, default 0) for the .B nth mode. .SS string This modules matches a given string by using some pattern matching strategy. It requires a linux kernel >= 2.6.14. .TP \fB\-\-algo\fP {\fBbm\fP|\fBkmp\fP} Select the pattern matching strategy. (bm = Boyer-Moore, kmp = Knuth-Pratt-Morris) .TP \fB\-\-from\fP \fIoffset\fP Set the offset from which it starts looking for any matching. If not passed, default is 0. .TP \fB\-\-to\fP \fIoffset\fP Set the offset up to which should be scanned. That is, byte \fIoffset\fP-1 (counting from 0) is the last one that is scanned. If not passed, default is the packet size. .TP [\fB!\fP] \fB\-\-string\fP \fIpattern\fP Matches the given pattern. .TP [\fB!\fP] \fB\-\-hex\-string\fP \fIpattern\fP Matches the given pattern in hex notation. .SS tcp These extensions can be used if `\-\-protocol tcp' is specified. It provides the following options: .TP [\fB!\fP] \fB\-\-source\-port\fP,\fB\-\-sport\fP \fIport\fP[\fB:\fP\fIport\fP] Source port or port range specification. This can either be a service name or a port number. An inclusive range can also be specified, using the format \fIfirst\fP\fB:\fP\fIlast\fP. If the first port is omitted, "0" is assumed; if the last is omitted, "65535" is assumed. If the first port is greater than the second one they will be swapped. The flag \fB\-\-sport\fP is a convenient alias for this option. .TP [\fB!\fP] \fB\-\-destination\-port\fP,\fB\-\-dport\fP \fIport\fP[\fB:\fP\fIport\fP] Destination port or port range specification. The flag \fB\-\-dport\fP is a convenient alias for this option. .TP [\fB!\fP] \fB\-\-tcp\-flags\fP \fImask\fP \fIcomp\fP Match when the TCP flags are as specified. The first argument \fImask\fP is the flags which we should examine, written as a comma-separated list, and the second argument \fIcomp\fP is a comma-separated list of flags which must be set. Flags are: .BR "SYN ACK FIN RST URG PSH ALL NONE" . Hence the command .nf iptables \-A FORWARD \-p tcp \-\-tcp\-flags SYN,ACK,FIN,RST SYN .fi will only match packets with the SYN flag set, and the ACK, FIN and RST flags unset. .TP [\fB!\fP] \fB\-\-syn\fP Only match TCP packets with the SYN bit set and the ACK,RST and FIN bits cleared. Such packets are used to request TCP connection initiation; for example, blocking such packets coming in an interface will prevent incoming TCP connections, but outgoing TCP connections will be unaffected. It is equivalent to \fB\-\-tcp\-flags SYN,RST,ACK,FIN SYN\fP. If the "!" flag precedes the "\-\-syn", the sense of the option is inverted. .TP [\fB!\fP] \fB\-\-tcp\-option\fP \fInumber\fP Match if TCP option set. .SS tcpmss This matches the TCP MSS (maximum segment size) field of the TCP header. You can only use this on TCP SYN or SYN/ACK packets, since the MSS is only negotiated during the TCP handshake at connection startup time. .TP [\fB!\fP] \fB\-\-mss\fP \fIvalue\fP[\fB:\fP\fIvalue\fP] Match a given TCP MSS value or range. .SS time This matches if the packet arrival time/date is within a given range. All options are optional, but are ANDed when specified. All times are interpreted as UTC by default. .TP \fB\-\-datestart\fP \fIYYYY\fP[\fB\-\fP\fIMM\fP[\fB\-\fP\fIDD\fP[\fBT\fP\fIhh\fP[\fB:\fP\fImm\fP[\fB:\fP\fIss\fP]]]]] .TP \fB\-\-datestop\fP \fIYYYY\fP[\fB\-\fP\fIMM\fP[\fB\-\fP\fIDD\fP[\fBT\fP\fIhh\fP[\fB:\fP\fImm\fP[\fB:\fP\fIss\fP]]]]] Only match during the given time, which must be in ISO 8601 "T" notation. The possible time range is 1970-01-01T00:00:00 to 2038-01-19T04:17:07. .IP If \-\-datestart or \-\-datestop are not specified, it will default to 1970-01-01 and 2038-01-19, respectively. .TP \fB\-\-timestart\fP \fIhh\fP\fB:\fP\fImm\fP[\fB:\fP\fIss\fP] .TP \fB\-\-timestop\fP \fIhh\fP\fB:\fP\fImm\fP[\fB:\fP\fIss\fP] Only match during the given daytime. The possible time range is 00:00:00 to 23:59:59. Leading zeroes are allowed (e.g. "06:03") and correctly interpreted as base-10. .TP [\fB!\fP] \fB\-\-monthdays\fP \fIday\fP[\fB,\fP\fIday\fP...] Only match on the given days of the month. Possible values are \fB1\fP to \fB31\fP. Note that specifying \fB31\fP will of course not match on months which do not have a 31st day; the same goes for 28- or 29-day February. .TP [\fB!\fP] \fB\-\-weekdays\fP \fIday\fP[\fB,\fP\fIday\fP...] Only match on the given weekdays. Possible values are \fBMon\fP, \fBTue\fP, \fBWed\fP, \fBThu\fP, \fBFri\fP, \fBSat\fP, \fBSun\fP, or values from \fB1\fP to \fB7\fP, respectively. You may also use two-character variants (\fBMo\fP, \fBTu\fP, etc.). .TP \fB\-\-kerneltz\fP Use the kernel timezone instead of UTC to determine whether a packet meets the time regulations. .PP About kernel timezones: Linux keeps the system time in UTC, and always does so. On boot, system time is initialized from a referential time source. Where this time source has no timezone information, such as the x86 CMOS RTC, UTC will be assumed. If the time source is however not in UTC, userspace should provide the correct system time and timezone to the kernel once it has the information. .PP Local time is a feature on top of the (timezone independent) system time. Each process has its own idea of local time, specified via the TZ environment variable. The kernel also has its own timezone offset variable. The TZ userspace environment variable specifies how the UTC-based system time is displayed, e.g. when you run date(1), or what you see on your desktop clock. The TZ string may resolve to different offsets at different dates, which is what enables the automatic time-jumping in userspace. when DST changes. The kernel's timezone offset variable is used when it has to convert between non-UTC sources, such as FAT filesystems, to UTC (since the latter is what the rest of the system uses). .PP The caveat with the kernel timezone is that Linux distributions may ignore to set the kernel timezone, and instead only set the system time. Even if a particular distribution does set the timezone at boot, it is usually does not keep the kernel timezone offset - which is what changes on DST - up to date. ntpd will not touch the kernel timezone, so running it will not resolve the issue. As such, one may encounter a timezone that is always +0000, or one that is wrong half of the time of the year. As such, \fBusing \-\-kerneltz is highly discouraged.\fP .PP EXAMPLES. To match on weekends, use: .IP \-m time \-\-weekdays Sa,Su .PP Or, to match (once) on a national holiday block: .IP \-m time \-\-datestart 2007\-12\-24 \-\-datestop 2007\-12\-27 .PP Since the stop time is actually inclusive, you would need the following stop time to not match the first second of the new day: .IP \-m time \-\-datestart 2007\-01\-01T17:00 \-\-datestop 2007\-01\-01T23:59:59 .PP During lunch hour: .IP \-m time \-\-timestart 12:30 \-\-timestop 13:30 .PP The fourth Friday in the month: .IP \-m time \-\-weekdays Fr \-\-monthdays 22,23,24,25,26,27,28 .PP (Note that this exploits a certain mathematical property. It is not possible to say "fourth Thursday OR fourth Friday" in one rule. It is possible with multiple rules, though.) .SS tos This module matches the 8-bit Type of Service field in the IPv4 header (i.e. including the "Precedence" bits) or the (also 8-bit) Priority field in the IPv6 header. .TP [\fB!\fP] \fB\-\-tos\fP \fIvalue\fP[\fB/\fP\fImask\fP] Matches packets with the given TOS mark value. If a mask is specified, it is logically ANDed with the TOS mark before the comparison. .TP [\fB!\fP] \fB\-\-tos\fP \fIsymbol\fP You can specify a symbolic name when using the tos match for IPv4. The list of recognized TOS names can be obtained by calling iptables with \fB\-m tos \-h\fP. Note that this implies a mask of 0x3F, i.e. all but the ECN bits. .SS ttl This module matches the time to live field in the IP header. .TP [\fB!\fP] \fB\-\-ttl\-eq\fP \fIttl\fP Matches the given TTL value. .TP \fB\-\-ttl\-gt\fP \fIttl\fP Matches if TTL is greater than the given TTL value. .TP \fB\-\-ttl\-lt\fP \fIttl\fP Matches if TTL is less than the given TTL value. .SS u32 U32 tests whether quantities of up to 4 bytes extracted from a packet have specified values. The specification of what to extract is general enough to find data at given offsets from tcp headers or payloads. .TP [\fB!\fP] \fB\-\-u32\fP \fItests\fP The argument amounts to a program in a small language described below. .IP tests := location "=" value | tests "&&" location "=" value .IP value := range | value "," range .IP range := number | number ":" number .PP a single number, \fIn\fP, is interpreted the same as \fIn:n\fP. \fIn:m\fP is interpreted as the range of numbers \fB>=n\fP and \fB<=m\fP. .IP "" 4 location := number | location operator number .IP "" 4 operator := "&" | "<<" | ">>" | "@" .PP The operators \fB&\fP, \fB<<\fP, \fB>>\fP and \fB&&\fP mean the same as in C. The \fB=\fP is really a set membership operator and the value syntax describes a set. The \fB@\fP operator is what allows moving to the next header and is described further below. .PP There are currently some artificial implementation limits on the size of the tests: .IP " *" no more than 10 of "\fB=\fP" (and 9 "\fB&&\fP"s) in the u32 argument .IP " *" no more than 10 ranges (and 9 commas) per value .IP " *" no more than 10 numbers (and 9 operators) per location .PP To describe the meaning of location, imagine the following machine that interprets it. There are three registers: .IP A is of type \fBchar *\fP, initially the address of the IP header .IP B and C are unsigned 32 bit integers, initially zero .PP The instructions are: .IP number B = number; .IP C = (*(A+B)<<24) + (*(A+B+1)<<16) + (*(A+B+2)<<8) + *(A+B+3) .IP &number C = C & number .IP << number C = C << number .IP >> number C = C >> number .IP @number A = A + C; then do the instruction number .PP Any access of memory outside [skb\->data,skb\->end] causes the match to fail. Otherwise the result of the computation is the final value of C. .PP Whitespace is allowed but not required in the tests. However, the characters that do occur there are likely to require shell quoting, so it is a good idea to enclose the arguments in quotes. .PP Example: .IP match IP packets with total length >= 256 .IP The IP header contains a total length field in bytes 2-3. .IP \-\-u32 "\fB0 & 0xFFFF = 0x100:0xFFFF\fP" .IP read bytes 0-3 .IP AND that with 0xFFFF (giving bytes 2-3), and test whether that is in the range [0x100:0xFFFF] .PP Example: (more realistic, hence more complicated) .IP match ICMP packets with icmp type 0 .IP First test that it is an ICMP packet, true iff byte 9 (protocol) = 1 .IP \-\-u32 "\fB6 & 0xFF = 1 &&\fP ... .IP read bytes 6-9, use \fB&\fP to throw away bytes 6-8 and compare the result to 1. Next test that it is not a fragment. (If so, it might be part of such a packet but we cannot always tell.) N.B.: This test is generally needed if you want to match anything beyond the IP header. The last 6 bits of byte 6 and all of byte 7 are 0 iff this is a complete packet (not a fragment). Alternatively, you can allow first fragments by only testing the last 5 bits of byte 6. .IP ... \fB4 & 0x3FFF = 0 &&\fP ... .IP Last test: the first byte past the IP header (the type) is 0. This is where we have to use the @syntax. The length of the IP header (IHL) in 32 bit words is stored in the right half of byte 0 of the IP header itself. .IP ... \fB0 >> 22 & 0x3C @ 0 >> 24 = 0\fP" .IP The first 0 means read bytes 0-3, \fB>>22\fP means shift that 22 bits to the right. Shifting 24 bits would give the first byte, so only 22 bits is four times that plus a few more bits. \fB&3C\fP then eliminates the two extra bits on the right and the first four bits of the first byte. For instance, if IHL=5, then the IP header is 20 (4 x 5) bytes long. In this case, bytes 0-1 are (in binary) xxxx0101 yyzzzzzz, \fB>>22\fP gives the 10 bit value xxxx0101yy and \fB&3C\fP gives 010100. \fB@\fP means to use this number as a new offset into the packet, and read four bytes starting from there. This is the first 4 bytes of the ICMP payload, of which byte 0 is the ICMP type. Therefore, we simply shift the value 24 to the right to throw out all but the first byte and compare the result with 0. .PP Example: .IP TCP payload bytes 8-12 is any of 1, 2, 5 or 8 .IP First we test that the packet is a tcp packet (similar to ICMP). .IP \-\-u32 "\fB6 & 0xFF = 6 &&\fP ... .IP Next, test that it is not a fragment (same as above). .IP ... \fB0 >> 22 & 0x3C @ 12 >> 26 & 0x3C @ 8 = 1,2,5,8\fP" .IP \fB0>>22&3C\fP as above computes the number of bytes in the IP header. \fB@\fP makes this the new offset into the packet, which is the start of the TCP header. The length of the TCP header (again in 32 bit words) is the left half of byte 12 of the TCP header. The \fB12>>26&3C\fP computes this length in bytes (similar to the IP header before). "@" makes this the new offset, which is the start of the TCP payload. Finally, 8 reads bytes 8-12 of the payload and \fB=\fP checks whether the result is any of 1, 2, 5 or 8. .SS udp These extensions can be used if `\-\-protocol udp' is specified. It provides the following options: .TP [\fB!\fP] \fB\-\-source\-port\fP,\fB\-\-sport\fP \fIport\fP[\fB:\fP\fIport\fP] Source port or port range specification. See the description of the \fB\-\-source\-port\fP option of the TCP extension for details. .TP [\fB!\fP] \fB\-\-destination\-port\fP,\fB\-\-dport\fP \fIport\fP[\fB:\fP\fIport\fP] Destination port or port range specification. See the description of the \fB\-\-destination\-port\fP option of the TCP extension for details. .SS unclean This module takes no options, but attempts to match packets which seem malformed or unusual. This is regarded as experimental. .SH TARGET EXTENSIONS iptables can use extended target modules: the following are included in the standard distribution. .\" @TARGET@ .SS AUDIT This target allows to create audit records for packets hitting the target. It can be used to record accepted, dropped, and rejected packets. See auditd(8) for additional details. .TP \fB\-\-type\fP {\fBaccept\fP|\fBdrop\fP|\fBreject\fP} Set type of audit record. .PP Example: .IP iptables \-N AUDIT_DROP .IP iptables \-A AUDIT_DROP \-j AUDIT \-\-type drop .IP iptables \-A AUDIT_DROP \-j DROP .SS CHECKSUM This target allows to selectively work around broken/old applications. It can only be used in the mangle table. .TP \fB\-\-checksum\-fill\fP Compute and fill in the checksum in a packet that lacks a checksum. This is particularly useful, if you need to work around old applications such as dhcp clients, that do not work well with checksum offloads, but don't want to disable checksum offload in your device. .SS CLASSIFY This module allows you to set the skb\->priority value (and thus classify the packet into a specific CBQ class). .TP \fB\-\-set\-class\fP \fImajor\fP\fB:\fP\fIminor\fP Set the major and minor class value. The values are always interpreted as hexadecimal even if no 0x prefix is given. .SS CLUSTERIP This module allows you to configure a simple cluster of nodes that share a certain IP and MAC address without an explicit load balancer in front of them. Connections are statically distributed between the nodes in this cluster. .TP \fB\-\-new\fP Create a new ClusterIP. You always have to set this on the first rule for a given ClusterIP. .TP \fB\-\-hashmode\fP \fImode\fP Specify the hashing mode. Has to be one of \fBsourceip\fP, \fBsourceip\-sourceport\fP, \fBsourceip\-sourceport\-destport\fP. .TP \fB\-\-clustermac\fP \fImac\fP Specify the ClusterIP MAC address. Has to be a link\-layer multicast address .TP \fB\-\-total\-nodes\fP \fInum\fP Number of total nodes within this cluster. .TP \fB\-\-local\-node\fP \fInum\fP Local node number within this cluster. .TP \fB\-\-hash\-init\fP \fIrnd\fP Specify the random seed used for hash initialization. .SS CONNMARK This module sets the netfilter mark value associated with a connection. The mark is 32 bits wide. .TP \fB\-\-set\-xmark\fP \fIvalue\fP[\fB/\fP\fImask\fP] Zero out the bits given by \fImask\fP and XOR \fIvalue\fP into the ctmark. .TP \fB\-\-save\-mark\fP [\fB\-\-nfmask\fP \fInfmask\fP] [\fB\-\-ctmask\fP \fIctmask\fP] Copy the packet mark (nfmark) to the connection mark (ctmark) using the given masks. The new nfmark value is determined as follows: .IP ctmark = (ctmark & ~ctmask) ^ (nfmark & nfmask) .IP i.e. \fIctmask\fP defines what bits to clear and \fInfmask\fP what bits of the nfmark to XOR into the ctmark. \fIctmask\fP and \fInfmask\fP default to 0xFFFFFFFF. .TP \fB\-\-restore\-mark\fP [\fB\-\-nfmask\fP \fInfmask\fP] [\fB\-\-ctmask\fP \fIctmask\fP] Copy the connection mark (ctmark) to the packet mark (nfmark) using the given masks. The new ctmark value is determined as follows: .IP nfmark = (nfmark & ~\fInfmask\fP) ^ (ctmark & \fIctmask\fP); .IP i.e. \fInfmask\fP defines what bits to clear and \fIctmask\fP what bits of the ctmark to XOR into the nfmark. \fIctmask\fP and \fInfmask\fP default to 0xFFFFFFFF. .IP \fB\-\-restore\-mark\fP is only valid in the \fBmangle\fP table. .PP The following mnemonics are available for \fB\-\-set\-xmark\fP: .TP \fB\-\-and\-mark\fP \fIbits\fP Binary AND the ctmark with \fIbits\fP. (Mnemonic for \fB\-\-set\-xmark 0/\fP\fIinvbits\fP, where \fIinvbits\fP is the binary negation of \fIbits\fP.) .TP \fB\-\-or\-mark\fP \fIbits\fP Binary OR the ctmark with \fIbits\fP. (Mnemonic for \fB\-\-set\-xmark\fP \fIbits\fP\fB/\fP\fIbits\fP.) .TP \fB\-\-xor\-mark\fP \fIbits\fP Binary XOR the ctmark with \fIbits\fP. (Mnemonic for \fB\-\-set\-xmark\fP \fIbits\fP\fB/0\fP.) .TP \fB\-\-set\-mark\fP \fIvalue\fP[\fB/\fP\fImask\fP] Set the connection mark. If a mask is specified then only those bits set in the mask are modified. .TP \fB\-\-save\-mark\fP [\fB\-\-mask\fP \fImask\fP] Copy the nfmark to the ctmark. If a mask is specified, only those bits are copied. .TP \fB\-\-restore\-mark\fP [\fB\-\-mask\fP \fImask\fP] Copy the ctmark to the nfmark. If a mask is specified, only those bits are copied. This is only valid in the \fBmangle\fP table. .SS CONNSECMARK This module copies security markings from packets to connections (if unlabeled), and from connections back to packets (also only if unlabeled). Typically used in conjunction with SECMARK, it is valid in the .B security table (for backwards compatibility with older kernels, it is also valid in the .B mangle table). .TP \fB\-\-save\fP If the packet has a security marking, copy it to the connection if the connection is not marked. .TP \fB\-\-restore\fP If the packet does not have a security marking, and the connection does, copy the security marking from the connection to the packet. .SS CT The CT target allows to set parameters for a packet or its associated connection. The target attaches a "template" connection tracking entry to the packet, which is then used by the conntrack core when initializing a new ct entry. This target is thus only valid in the "raw" table. .TP \fB\-\-notrack\fP Disables connection tracking for this packet. .TP \fB\-\-helper\fP \fIname\fP Use the helper identified by \fIname\fP for the connection. This is more flexible than loading the conntrack helper modules with preset ports. .TP \fB\-\-ctevents\fP \fIevent\fP[\fB,\fP...] Only generate the specified conntrack events for this connection. Possible event types are: \fBnew\fP, \fBrelated\fP, \fBdestroy\fP, \fBreply\fP, \fBassured\fP, \fBprotoinfo\fP, \fBhelper\fP, \fBmark\fP (this refers to the ctmark, not nfmark), \fBnatseqinfo\fP, \fBsecmark\fP (ctsecmark). .TP \fB\-\-expevents\fP \fIevent\fP[\fB,\fP...] Only generate the specified expectation events for this connection. Possible event types are: \fBnew\fP. .TP \fB\-\-zone\fP \fIid\fP Assign this packet to zone \fIid\fP and only have lookups done in that zone. By default, packets have zone 0. .TP \fB\-\-timeout\fP \fIname\fP Use the timeout policy identified by \fIname\fP for the connection. This is provides more flexible timeout policy definition than global timeout values available at /proc/sys/net/netfilter/nf_conntrack_*_timeout_*. .SS DNAT This target is only valid in the .B nat table, in the .B PREROUTING and .B OUTPUT chains, and user-defined chains which are only called from those chains. It specifies that the destination address of the packet should be modified (and all future packets in this connection will also be mangled), and rules should cease being examined. It takes one type of option: .TP \fB\-\-to\-destination\fP [\fIipaddr\fP[\fB\-\fP\fIipaddr\fP]][\fB:\fP\fIport\fP[\fB\-\fP\fIport\fP]] which can specify a single new destination IP address, an inclusive range of IP addresses, and optionally, a port range (which is only valid if the rule also specifies \fB\-p tcp\fP or \fB\-p udp\fP). If no port range is specified, then the destination port will never be modified. If no IP address is specified then only the destination port will be modified. In Kernels up to 2.6.10 you can add several \-\-to\-destination options. For those kernels, if you specify more than one destination address, either via an address range or multiple \-\-to\-destination options, a simple round-robin (one after another in cycle) load balancing takes place between these addresses. Later Kernels (>= 2.6.11-rc1) don't have the ability to NAT to multiple ranges anymore. .TP \fB\-\-random\fP If option \fB\-\-random\fP is used then port mapping will be randomized (kernel >= 2.6.22). .TP \fB\-\-persistent\fP Gives a client the same source-/destination-address for each connection. This supersedes the SAME target. Support for persistent mappings is available from 2.6.29-rc2. .SS DSCP This target allows to alter the value of the DSCP bits within the TOS header of the IPv4 packet. As this manipulates a packet, it can only be used in the mangle table. .TP \fB\-\-set\-dscp\fP \fIvalue\fP Set the DSCP field to a numerical value (can be decimal or hex) .TP \fB\-\-set\-dscp\-class\fP \fIclass\fP Set the DSCP field to a DiffServ class. .SS ECN This target allows to selectively work around known ECN blackholes. It can only be used in the mangle table. .TP \fB\-\-ecn\-tcp\-remove\fP Remove all ECN bits from the TCP header. Of course, it can only be used in conjunction with \fB\-p tcp\fP. .SS IDLETIMER This target can be used to identify when interfaces have been idle for a certain period of time. Timers are identified by labels and are created when a rule is set with a new label. The rules also take a timeout value (in seconds) as an option. If more than one rule uses the same timer label, the timer will be restarted whenever any of the rules get a hit. One entry for each timer is created in sysfs. This attribute contains the timer remaining for the timer to expire. The attributes are located under the xt_idletimer class: .PP /sys/class/xt_idletimer/timers/