In this section, we will attempt to explain the usage of new netfilter matches.
The patches will appear in alphabetical order. Additionally, we will not explain
patches that break other patches. But this might come later.
Generally speaking, for matches, you can get the help hints from a particular
module by typing :
# iptables -m the_match_you_want --help
This would display the normal iptables help message, plus the specific
``the_match_you_want'' match help message at the end.
This patch by Yon Uriarte <yon@astaro.de> adds 2 new matches :
``ah'' : lets you match an AH packet based on its Security Parameter Index (SPI).
``esp'' : lets you match an ESP packet based on its SPI.
This patch can be quite useful for people using IPSEC who are willing
to discriminate connections based on their SPI.
For example, we will drop all the AH packets that have a SPI equal to
500 :
# iptables -A INPUT -p 51 -m ah --ahspi 500 -j DROP
# iptables --list
Chain INPUT (policy ACCEPT)
target prot opt source destination
DROP ipv6-auth-- anywhere anywhere ah spi:500
Supported options for the ah match are :
--ahspi [!] spi[:spi]
-> match spi (range)
The esp match works exactly the same :
# iptables -A INPUT -p 50 -m esp --espspi 500 -j DROP
# iptables --list
Chain INPUT (policy ACCEPT)
target prot opt source destination
DROP ipv6-crypt-- anywhere anywhere esp spi:500
Supported options for the esp match are :
--espspi [!] spi[:spi]
-> match spi (range)
Do not forget to specify the proper protocol through ``-p 50'' or ``-p 51'' (for esp & ah respectively)
when you use the ah or esp matches, or else the rule insertion will simply abort
for obvious reasons.
This patch by Marc Boucher <marc+nf@mbsi.ca> adds a new general conntrack match module
(a superset of the state match) that allows you to match on additional conntrack information.
For example, if you want to allow all the RELATED connections for TCP protocols only,
then you can proceed as follows :
# iptables -A FORWARD -m conntrack --ctstate RELATED --ctproto tcp -j ACCEPT
# iptables --list
Chain FORWARD (policy ACCEPT)
target prot opt source destination
ACCEPT all -- anywhere anywhere ctstate RELATED
-> State(s) to match. The "new" `SNAT' and `DNAT' states are virtual ones, matching if the original
source address differs from the reply destination, or if the original destination differs from the reply source.
[!] --ctproto proto
-> Protocol to match; by number or name, eg. `tcp'.
This patch by Gerd Knorr <kraxel@bytesex.org> adds a new match that
will allow you to restrict the number of parallel TCP connections
from a particular host or network.
For example, let's limit the number of parallel HTTP connections made by a single
IP address to 4 :
This patch by Andreas Ferber <af@devcon.net> adds a new match that allows
you to specify ports with a mix of port-ranges and single ports for UDP and TCP protocols.
For example, if you want to block ftp, ssh, telnet and http in one line, you can :
This patch by Fabrice MARIE <fabrice@celestix.com> adds a new match that allows
you to match a particular Nth packet received by the rule.
For example, if you want to drop every 2 ping packets, you can do as follows :
# iptables -A INPUT -p icmp --icmp-type echo-request -m nth --every 2 -j DROP
# iptables --list
Chain INPUT (policy ACCEPT)
target prot opt source destination
DROP icmp -- anywhere anywhere icmp echo-request every 2th
Extensions by Richard Wagner <rwagner@cloudnet.com> allows
you to create an easy and quick method to produce load-balancing for both inbound and outbound
connections.
For example, if you want to balance the load to the 3 addresses 10.0.0.5, 10.0.0.6 and 10.0.0.7,
then you can do as follows :
-> Initialize the counter at the number `num' instead of 0. Must be between 0 and (Nth-1).
[--packet] num
-> Match on the `num' packet. Must be between 0 and Nth-1.
If `--packet' is used for a counter, then there must be Nth number of --packet rules, covering all values between 0 and
(Nth-1) inclusively.
Patch by Patrick Schaaf <bof@bof.de>. Joakim Axelsson and Patrick are in the process
of re-writing it, therefore they will replace this section with the actual
explanations once its written.
This patch by Sampsa Ranta <sampsa@netsonic.fi> adds a new match that allows you
to use realm key from routing as match criteria similar to the one found in the packet
classifier.
For example, to log all the outgoing packet with a realm of 10, you can do the following :
This patch by Stephen Frost <sfrost@snowman.net> adds a new match that allows you
to dynamically create a list of IP addresses and then match against that list in a few
different ways.
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.
# iptables -A FORWARD -m recent --name badguy --rcheck --seconds 60 -j DROP
# iptables -A FORWARD -p tcp -i eth0 --dport 139 -m recent --name badguy --set -j DROP
# iptables --list
Chain FORWARD (policy ACCEPT)
target prot opt source destination
DROP all -- anywhere anywhere recent: CHECK seconds: 60
DROP tcp -- anywhere anywhere tcp dpt:netbios-ssn recent: SET
Supported options for the recent match are :
--name name
-> Specify the list to use for the commands. If no name is given
then 'DEFAULT' will be used.
[!] --set
-> 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 `!' is passed in.
[!] --rcheck
-> This will check if the source address of the packet is currently
in the list and return true if it is, and false otherwise. Opposite is returned if `!' is passed in.
[!] --update
-> This will check if the source address of the packet is currently
in the list. If it is then that entry will be updated and the rule will return true. If the source
address is not in the list then the rule will return false. Opposite is returned if `!' is passed in.
[!] --remove
-> This will 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. Opposite is returned if `!' is passed in.
[!] --seconds seconds
-> This option must be used in conjunction with one of `rcheck' or
`update'. 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. Opposite is returned if `!' is passed in.
[!] --hitcount hits
-> This option must be used in conjunction with one of `rcheck' or
`update'. 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 `seconds'
to create an even narrower match requiring a certain number of hits within a specific time frame.
Opposite returned if `!' passed in.
--rttl
-> This option must be used in conjunction with one of `rcheck' or `update'.
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 --set 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.
This patch by Marcelo Barbosa Lima <marcelo.lima@dcc.unicamp.br> adds a new match that allows
you to match if the source of the packet has requested that port through the portmapper before,
or it is a new GET request to the portmapper, allowing effective RPC filtering.
To match RPC connection tracking information, simply do the following :
This patch by Emmanuel Roger <winfield@freegates.be> adds a new match that allows
you to match a string anywhere in the packet.
For example, to match packets containing the string ``cmd.exe'' anywhere
in the packet and queue them to a userland IDS, you could use :
# iptables -A INPUT -m string --string 'cmd.exe' -j QUEUE
# iptables --list
Chain INPUT (policy ACCEPT)
target prot opt source destination
QUEUE all -- anywhere anywhere STRING match cmd.exe
Please do use this match with caution. A lot of people want to use
this match to stop worms, along with the DROP target. This is a major mistake.
It would be defeated by any IDS evasion method.
In a similar fashion, a lot of people have been using this match as a mean
to stop particular functions in HTTP like POST or GET by dropping
any HTTP packet containing the string POST. Please understand that this job
is better done by a filtering proxy. Additionally, any HTML content with
the word POST would get dropped with the former method.
This match has been designed to be able to queue to userland interesting packets
for better analysis, that's all. Dropping packet based on this would be defeated
by any IDS evasion method.
This patch by Fabrice MARIE <fabrice@celestix.com> adds a new match that allows
you to match a packet based on its arrival or departure (for locally generated packets) timestamp.
for example, to accept packets that have an arrival time from 8:00H to 18:00H from Monday
to Friday you can do as follows :
# iptables -A INPUT -m time --timestart 8:00 --timestop 18:00 --days Mon,Tue,Wed,Thu,Fri -j ACCEPT
# iptables --list
Chain INPUT (policy ACCEPT)
target prot opt source destination
ACCEPT all -- anywhere anywhere TIME from 8:0 to 18:0 on Mon,Tue,Wed,Thu,Fri