[NETFILTER]: Add nf_conntrack subsystem.
The existing connection tracking subsystem in netfilter can only
handle ipv4. There were basically two choices present to add
connection tracking support for ipv6. We could either duplicate all
of the ipv4 connection tracking code into an ipv6 counterpart, or (the
choice taken by these patches) we could design a generic layer that
could handle both ipv4 and ipv6 and thus requiring only one sub-protocol
(TCP, UDP, etc.) connection tracking helper module to be written.
In fact nf_conntrack is capable of working with any layer 3
protocol.
The existing ipv4 specific conntrack code could also not deal
with the pecularities of doing connection tracking on ipv6,
which is also cured here. For example, these issues include:
1) ICMPv6 handling, which is used for neighbour discovery in
ipv6 thus some messages such as these should not participate
in connection tracking since effectively they are like ARP
messages
2) fragmentation must be handled differently in ipv6, because
the simplistic "defrag, connection track and NAT, refrag"
(which the existing ipv4 connection tracking does) approach simply
isn't feasible in ipv6
3) ipv6 extension header parsing must occur at the correct spots
before and after connection tracking decisions, and there were
no provisions for this in the existing connection tracking
design
4) ipv6 has no need for stateful NAT
The ipv4 specific conntrack layer is kept around, until all of
the ipv4 specific conntrack helpers are ported over to nf_conntrack
and it is feature complete. Once that occurs, the old conntrack
stuff will get placed into the feature-removal-schedule and we will
fully kill it off 6 months later.
Signed-off-by: Yasuyuki Kozakai <yasuyuki.kozakai@toshiba.co.jp>
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: Arnaldo Carvalho de Melo <acme@mandriva.com>
2005-11-10 08:38:16 +08:00
|
|
|
menu "Core Netfilter Configuration"
|
2006-12-12 16:27:46 +08:00
|
|
|
depends on NET && INET && NETFILTER
|
[NETFILTER]: Add nf_conntrack subsystem.
The existing connection tracking subsystem in netfilter can only
handle ipv4. There were basically two choices present to add
connection tracking support for ipv6. We could either duplicate all
of the ipv4 connection tracking code into an ipv6 counterpart, or (the
choice taken by these patches) we could design a generic layer that
could handle both ipv4 and ipv6 and thus requiring only one sub-protocol
(TCP, UDP, etc.) connection tracking helper module to be written.
In fact nf_conntrack is capable of working with any layer 3
protocol.
The existing ipv4 specific conntrack code could also not deal
with the pecularities of doing connection tracking on ipv6,
which is also cured here. For example, these issues include:
1) ICMPv6 handling, which is used for neighbour discovery in
ipv6 thus some messages such as these should not participate
in connection tracking since effectively they are like ARP
messages
2) fragmentation must be handled differently in ipv6, because
the simplistic "defrag, connection track and NAT, refrag"
(which the existing ipv4 connection tracking does) approach simply
isn't feasible in ipv6
3) ipv6 extension header parsing must occur at the correct spots
before and after connection tracking decisions, and there were
no provisions for this in the existing connection tracking
design
4) ipv6 has no need for stateful NAT
The ipv4 specific conntrack layer is kept around, until all of
the ipv4 specific conntrack helpers are ported over to nf_conntrack
and it is feature complete. Once that occurs, the old conntrack
stuff will get placed into the feature-removal-schedule and we will
fully kill it off 6 months later.
Signed-off-by: Yasuyuki Kozakai <yasuyuki.kozakai@toshiba.co.jp>
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: Arnaldo Carvalho de Melo <acme@mandriva.com>
2005-11-10 08:38:16 +08:00
|
|
|
|
2005-08-10 10:30:24 +08:00
|
|
|
config NETFILTER_NETLINK
|
2007-12-05 17:31:52 +08:00
|
|
|
tristate
|
2005-08-10 10:44:15 +08:00
|
|
|
|
netfilter: add extended accounting infrastructure over nfnetlink
We currently have two ways to account traffic in netfilter:
- iptables chain and rule counters:
# iptables -L -n -v
Chain INPUT (policy DROP 3 packets, 867 bytes)
pkts bytes target prot opt in out source destination
8 1104 ACCEPT all -- lo * 0.0.0.0/0 0.0.0.0/0
- use flow-based accounting provided by ctnetlink:
# conntrack -L
tcp 6 431999 ESTABLISHED src=192.168.1.130 dst=212.106.219.168 sport=58152 dport=80 packets=47 bytes=7654 src=212.106.219.168 dst=192.168.1.130 sport=80 dport=58152 packets=49 bytes=66340 [ASSURED] mark=0 use=1
While trying to display real-time accounting statistics, we require
to pool the kernel periodically to obtain this information. This is
OK if the number of flows is relatively low. However, in case that
the number of flows is huge, we can spend a considerable amount of
cycles to iterate over the list of flows that have been obtained.
Moreover, if we want to obtain the sum of the flow accounting results
that match some criteria, we have to iterate over the whole list of
existing flows, look for matchings and update the counters.
This patch adds the extended accounting infrastructure for
nfnetlink which aims to allow displaying real-time traffic accounting
without the need of complicated and resource-consuming implementation
in user-space. Basically, this new infrastructure allows you to create
accounting objects. One accounting object is composed of packet and
byte counters.
In order to manipulate create accounting objects, you require the
new libnetfilter_acct library. It contains several examples of use:
libnetfilter_acct/examples# ./nfacct-add http-traffic
libnetfilter_acct/examples# ./nfacct-get
http-traffic = { pkts = 000000000000, bytes = 000000000000 };
Then, you can use one of this accounting objects in several iptables
rules using the new nfacct match (which comes in a follow-up patch):
# iptables -I INPUT -p tcp --sport 80 -m nfacct --nfacct-name http-traffic
# iptables -I OUTPUT -p tcp --dport 80 -m nfacct --nfacct-name http-traffic
The idea is simple: if one packet matches the rule, the nfacct match
updates the counters.
Thanks to Patrick McHardy, Eric Dumazet, Changli Gao for reviewing and
providing feedback for this contribution.
Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
2011-12-23 21:19:50 +08:00
|
|
|
config NETFILTER_NETLINK_ACCT
|
|
|
|
|
tristate "Netfilter NFACCT over NFNETLINK interface"
|
|
|
|
|
depends on NETFILTER_ADVANCED
|
|
|
|
|
select NETFILTER_NETLINK
|
|
|
|
|
help
|
|
|
|
|
If this option is enabled, the kernel will include support
|
|
|
|
|
for extended accounting via NFNETLINK.
|
|
|
|
|
|
2005-08-10 10:44:15 +08:00
|
|
|
config NETFILTER_NETLINK_QUEUE
|
|
|
|
|
tristate "Netfilter NFQUEUE over NFNETLINK interface"
|
2007-12-18 14:47:05 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
2007-12-05 17:31:52 +08:00
|
|
|
select NETFILTER_NETLINK
|
2005-08-10 10:44:15 +08:00
|
|
|
help
|
2006-03-23 05:53:48 +08:00
|
|
|
If this option is enabled, the kernel will include support
|
2005-08-10 10:44:15 +08:00
|
|
|
for queueing packets via NFNETLINK.
|
|
|
|
|
|
2005-08-10 10:58:39 +08:00
|
|
|
config NETFILTER_NETLINK_LOG
|
|
|
|
|
tristate "Netfilter LOG over NFNETLINK interface"
|
2007-12-18 14:47:05 +08:00
|
|
|
default m if NETFILTER_ADVANCED=n
|
2007-12-05 17:31:52 +08:00
|
|
|
select NETFILTER_NETLINK
|
2005-08-10 10:58:39 +08:00
|
|
|
help
|
|
|
|
|
If this option is enabled, the kernel will include support
|
|
|
|
|
for logging packets via NFNETLINK.
|
|
|
|
|
|
|
|
|
|
This obsoletes the existing ipt_ULOG and ebg_ulog mechanisms,
|
|
|
|
|
and is also scheduled to replace the old syslog-based ipt_LOG
|
|
|
|
|
and ip6t_LOG modules.
|
|
|
|
|
|
2007-12-05 17:31:37 +08:00
|
|
|
config NF_CONNTRACK
|
2006-12-03 14:05:46 +08:00
|
|
|
tristate "Netfilter connection tracking support"
|
2007-12-18 14:47:05 +08:00
|
|
|
default m if NETFILTER_ADVANCED=n
|
2006-12-03 14:05:46 +08:00
|
|
|
help
|
[NETFILTER]: Add nf_conntrack subsystem.
The existing connection tracking subsystem in netfilter can only
handle ipv4. There were basically two choices present to add
connection tracking support for ipv6. We could either duplicate all
of the ipv4 connection tracking code into an ipv6 counterpart, or (the
choice taken by these patches) we could design a generic layer that
could handle both ipv4 and ipv6 and thus requiring only one sub-protocol
(TCP, UDP, etc.) connection tracking helper module to be written.
In fact nf_conntrack is capable of working with any layer 3
protocol.
The existing ipv4 specific conntrack code could also not deal
with the pecularities of doing connection tracking on ipv6,
which is also cured here. For example, these issues include:
1) ICMPv6 handling, which is used for neighbour discovery in
ipv6 thus some messages such as these should not participate
in connection tracking since effectively they are like ARP
messages
2) fragmentation must be handled differently in ipv6, because
the simplistic "defrag, connection track and NAT, refrag"
(which the existing ipv4 connection tracking does) approach simply
isn't feasible in ipv6
3) ipv6 extension header parsing must occur at the correct spots
before and after connection tracking decisions, and there were
no provisions for this in the existing connection tracking
design
4) ipv6 has no need for stateful NAT
The ipv4 specific conntrack layer is kept around, until all of
the ipv4 specific conntrack helpers are ported over to nf_conntrack
and it is feature complete. Once that occurs, the old conntrack
stuff will get placed into the feature-removal-schedule and we will
fully kill it off 6 months later.
Signed-off-by: Yasuyuki Kozakai <yasuyuki.kozakai@toshiba.co.jp>
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: Arnaldo Carvalho de Melo <acme@mandriva.com>
2005-11-10 08:38:16 +08:00
|
|
|
Connection tracking keeps a record of what packets have passed
|
|
|
|
|
through your machine, in order to figure out how they are related
|
|
|
|
|
into connections.
|
|
|
|
|
|
2006-12-03 14:05:46 +08:00
|
|
|
This is required to do Masquerading or other kinds of Network
|
2008-07-08 17:35:27 +08:00
|
|
|
Address Translation. It can also be used to enhance packet
|
|
|
|
|
filtering (see `Connection state match support' below).
|
2006-12-03 14:05:46 +08:00
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
2008-10-08 17:35:18 +08:00
|
|
|
if NF_CONNTRACK
|
|
|
|
|
|
[NETFILTER]: Add nf_conntrack subsystem.
The existing connection tracking subsystem in netfilter can only
handle ipv4. There were basically two choices present to add
connection tracking support for ipv6. We could either duplicate all
of the ipv4 connection tracking code into an ipv6 counterpart, or (the
choice taken by these patches) we could design a generic layer that
could handle both ipv4 and ipv6 and thus requiring only one sub-protocol
(TCP, UDP, etc.) connection tracking helper module to be written.
In fact nf_conntrack is capable of working with any layer 3
protocol.
The existing ipv4 specific conntrack code could also not deal
with the pecularities of doing connection tracking on ipv6,
which is also cured here. For example, these issues include:
1) ICMPv6 handling, which is used for neighbour discovery in
ipv6 thus some messages such as these should not participate
in connection tracking since effectively they are like ARP
messages
2) fragmentation must be handled differently in ipv6, because
the simplistic "defrag, connection track and NAT, refrag"
(which the existing ipv4 connection tracking does) approach simply
isn't feasible in ipv6
3) ipv6 extension header parsing must occur at the correct spots
before and after connection tracking decisions, and there were
no provisions for this in the existing connection tracking
design
4) ipv6 has no need for stateful NAT
The ipv4 specific conntrack layer is kept around, until all of
the ipv4 specific conntrack helpers are ported over to nf_conntrack
and it is feature complete. Once that occurs, the old conntrack
stuff will get placed into the feature-removal-schedule and we will
fully kill it off 6 months later.
Signed-off-by: Yasuyuki Kozakai <yasuyuki.kozakai@toshiba.co.jp>
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: Arnaldo Carvalho de Melo <acme@mandriva.com>
2005-11-10 08:38:16 +08:00
|
|
|
config NF_CONNTRACK_MARK
|
|
|
|
|
bool 'Connection mark tracking support'
|
2007-12-18 14:47:05 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
[NETFILTER]: Add nf_conntrack subsystem.
The existing connection tracking subsystem in netfilter can only
handle ipv4. There were basically two choices present to add
connection tracking support for ipv6. We could either duplicate all
of the ipv4 connection tracking code into an ipv6 counterpart, or (the
choice taken by these patches) we could design a generic layer that
could handle both ipv4 and ipv6 and thus requiring only one sub-protocol
(TCP, UDP, etc.) connection tracking helper module to be written.
In fact nf_conntrack is capable of working with any layer 3
protocol.
The existing ipv4 specific conntrack code could also not deal
with the pecularities of doing connection tracking on ipv6,
which is also cured here. For example, these issues include:
1) ICMPv6 handling, which is used for neighbour discovery in
ipv6 thus some messages such as these should not participate
in connection tracking since effectively they are like ARP
messages
2) fragmentation must be handled differently in ipv6, because
the simplistic "defrag, connection track and NAT, refrag"
(which the existing ipv4 connection tracking does) approach simply
isn't feasible in ipv6
3) ipv6 extension header parsing must occur at the correct spots
before and after connection tracking decisions, and there were
no provisions for this in the existing connection tracking
design
4) ipv6 has no need for stateful NAT
The ipv4 specific conntrack layer is kept around, until all of
the ipv4 specific conntrack helpers are ported over to nf_conntrack
and it is feature complete. Once that occurs, the old conntrack
stuff will get placed into the feature-removal-schedule and we will
fully kill it off 6 months later.
Signed-off-by: Yasuyuki Kozakai <yasuyuki.kozakai@toshiba.co.jp>
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: Arnaldo Carvalho de Melo <acme@mandriva.com>
2005-11-10 08:38:16 +08:00
|
|
|
help
|
|
|
|
|
This option enables support for connection marks, used by the
|
|
|
|
|
`CONNMARK' target and `connmark' match. Similar to the mark value
|
|
|
|
|
of packets, but this mark value is kept in the conntrack session
|
|
|
|
|
instead of the individual packets.
|
|
|
|
|
|
2006-06-09 15:31:46 +08:00
|
|
|
config NF_CONNTRACK_SECMARK
|
|
|
|
|
bool 'Connection tracking security mark support'
|
2008-10-08 17:35:18 +08:00
|
|
|
depends on NETWORK_SECMARK
|
2007-12-18 14:47:05 +08:00
|
|
|
default m if NETFILTER_ADVANCED=n
|
2006-06-09 15:31:46 +08:00
|
|
|
help
|
|
|
|
|
This option enables security markings to be applied to
|
|
|
|
|
connections. Typically they are copied to connections from
|
|
|
|
|
packets using the CONNSECMARK target and copied back from
|
|
|
|
|
connections to packets with the same target, with the packets
|
|
|
|
|
being originally labeled via SECMARK.
|
|
|
|
|
|
|
|
|
|
If unsure, say 'N'.
|
|
|
|
|
|
2010-02-16 01:13:33 +08:00
|
|
|
config NF_CONNTRACK_ZONES
|
|
|
|
|
bool 'Connection tracking zones'
|
|
|
|
|
depends on NETFILTER_ADVANCED
|
|
|
|
|
depends on NETFILTER_XT_TARGET_CT
|
|
|
|
|
help
|
|
|
|
|
This option enables support for connection tracking zones.
|
|
|
|
|
Normally, each connection needs to have a unique system wide
|
|
|
|
|
identity. Connection tracking zones allow to have multiple
|
|
|
|
|
connections using the same identity, as long as they are
|
|
|
|
|
contained in different zones.
|
|
|
|
|
|
|
|
|
|
If unsure, say `N'.
|
|
|
|
|
|
2011-04-21 15:32:45 +08:00
|
|
|
config NF_CONNTRACK_PROCFS
|
|
|
|
|
bool "Supply CT list in procfs (OBSOLETE)"
|
|
|
|
|
default y
|
|
|
|
|
depends on PROC_FS
|
|
|
|
|
---help---
|
|
|
|
|
This option enables for the list of known conntrack entries
|
|
|
|
|
to be shown in procfs under net/netfilter/nf_conntrack. This
|
|
|
|
|
is considered obsolete in favor of using the conntrack(8)
|
|
|
|
|
tool which uses Netlink.
|
|
|
|
|
|
[NETFILTER]: Add nf_conntrack subsystem.
The existing connection tracking subsystem in netfilter can only
handle ipv4. There were basically two choices present to add
connection tracking support for ipv6. We could either duplicate all
of the ipv4 connection tracking code into an ipv6 counterpart, or (the
choice taken by these patches) we could design a generic layer that
could handle both ipv4 and ipv6 and thus requiring only one sub-protocol
(TCP, UDP, etc.) connection tracking helper module to be written.
In fact nf_conntrack is capable of working with any layer 3
protocol.
The existing ipv4 specific conntrack code could also not deal
with the pecularities of doing connection tracking on ipv6,
which is also cured here. For example, these issues include:
1) ICMPv6 handling, which is used for neighbour discovery in
ipv6 thus some messages such as these should not participate
in connection tracking since effectively they are like ARP
messages
2) fragmentation must be handled differently in ipv6, because
the simplistic "defrag, connection track and NAT, refrag"
(which the existing ipv4 connection tracking does) approach simply
isn't feasible in ipv6
3) ipv6 extension header parsing must occur at the correct spots
before and after connection tracking decisions, and there were
no provisions for this in the existing connection tracking
design
4) ipv6 has no need for stateful NAT
The ipv4 specific conntrack layer is kept around, until all of
the ipv4 specific conntrack helpers are ported over to nf_conntrack
and it is feature complete. Once that occurs, the old conntrack
stuff will get placed into the feature-removal-schedule and we will
fully kill it off 6 months later.
Signed-off-by: Yasuyuki Kozakai <yasuyuki.kozakai@toshiba.co.jp>
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: Arnaldo Carvalho de Melo <acme@mandriva.com>
2005-11-10 08:38:16 +08:00
|
|
|
config NF_CONNTRACK_EVENTS
|
2008-01-15 15:31:36 +08:00
|
|
|
bool "Connection tracking events"
|
2007-12-18 14:47:05 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
[NETFILTER]: Add nf_conntrack subsystem.
The existing connection tracking subsystem in netfilter can only
handle ipv4. There were basically two choices present to add
connection tracking support for ipv6. We could either duplicate all
of the ipv4 connection tracking code into an ipv6 counterpart, or (the
choice taken by these patches) we could design a generic layer that
could handle both ipv4 and ipv6 and thus requiring only one sub-protocol
(TCP, UDP, etc.) connection tracking helper module to be written.
In fact nf_conntrack is capable of working with any layer 3
protocol.
The existing ipv4 specific conntrack code could also not deal
with the pecularities of doing connection tracking on ipv6,
which is also cured here. For example, these issues include:
1) ICMPv6 handling, which is used for neighbour discovery in
ipv6 thus some messages such as these should not participate
in connection tracking since effectively they are like ARP
messages
2) fragmentation must be handled differently in ipv6, because
the simplistic "defrag, connection track and NAT, refrag"
(which the existing ipv4 connection tracking does) approach simply
isn't feasible in ipv6
3) ipv6 extension header parsing must occur at the correct spots
before and after connection tracking decisions, and there were
no provisions for this in the existing connection tracking
design
4) ipv6 has no need for stateful NAT
The ipv4 specific conntrack layer is kept around, until all of
the ipv4 specific conntrack helpers are ported over to nf_conntrack
and it is feature complete. Once that occurs, the old conntrack
stuff will get placed into the feature-removal-schedule and we will
fully kill it off 6 months later.
Signed-off-by: Yasuyuki Kozakai <yasuyuki.kozakai@toshiba.co.jp>
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: Arnaldo Carvalho de Melo <acme@mandriva.com>
2005-11-10 08:38:16 +08:00
|
|
|
help
|
|
|
|
|
If this option is enabled, the connection tracking code will
|
|
|
|
|
provide a notifier chain that can be used by other kernel code
|
2006-03-23 05:53:48 +08:00
|
|
|
to get notified about changes in the connection tracking state.
|
[NETFILTER]: Add nf_conntrack subsystem.
The existing connection tracking subsystem in netfilter can only
handle ipv4. There were basically two choices present to add
connection tracking support for ipv6. We could either duplicate all
of the ipv4 connection tracking code into an ipv6 counterpart, or (the
choice taken by these patches) we could design a generic layer that
could handle both ipv4 and ipv6 and thus requiring only one sub-protocol
(TCP, UDP, etc.) connection tracking helper module to be written.
In fact nf_conntrack is capable of working with any layer 3
protocol.
The existing ipv4 specific conntrack code could also not deal
with the pecularities of doing connection tracking on ipv6,
which is also cured here. For example, these issues include:
1) ICMPv6 handling, which is used for neighbour discovery in
ipv6 thus some messages such as these should not participate
in connection tracking since effectively they are like ARP
messages
2) fragmentation must be handled differently in ipv6, because
the simplistic "defrag, connection track and NAT, refrag"
(which the existing ipv4 connection tracking does) approach simply
isn't feasible in ipv6
3) ipv6 extension header parsing must occur at the correct spots
before and after connection tracking decisions, and there were
no provisions for this in the existing connection tracking
design
4) ipv6 has no need for stateful NAT
The ipv4 specific conntrack layer is kept around, until all of
the ipv4 specific conntrack helpers are ported over to nf_conntrack
and it is feature complete. Once that occurs, the old conntrack
stuff will get placed into the feature-removal-schedule and we will
fully kill it off 6 months later.
Signed-off-by: Yasuyuki Kozakai <yasuyuki.kozakai@toshiba.co.jp>
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: Arnaldo Carvalho de Melo <acme@mandriva.com>
2005-11-10 08:38:16 +08:00
|
|
|
|
|
|
|
|
If unsure, say `N'.
|
|
|
|
|
|
2012-02-29 06:36:48 +08:00
|
|
|
config NF_CONNTRACK_TIMEOUT
|
|
|
|
|
bool 'Connection tracking timeout'
|
|
|
|
|
depends on NETFILTER_ADVANCED
|
|
|
|
|
help
|
|
|
|
|
This option enables support for connection tracking timeout
|
|
|
|
|
extension. This allows you to attach timeout policies to flow
|
|
|
|
|
via the CT target.
|
|
|
|
|
|
|
|
|
|
If unsure, say `N'.
|
|
|
|
|
|
2011-01-19 23:00:07 +08:00
|
|
|
config NF_CONNTRACK_TIMESTAMP
|
|
|
|
|
bool 'Connection tracking timestamping'
|
|
|
|
|
depends on NETFILTER_ADVANCED
|
|
|
|
|
help
|
|
|
|
|
This option enables support for connection tracking timestamping.
|
|
|
|
|
This allows you to store the flow start-time and to obtain
|
|
|
|
|
the flow-stop time (once it has been destroyed) via Connection
|
|
|
|
|
tracking events.
|
|
|
|
|
|
|
|
|
|
If unsure, say `N'.
|
|
|
|
|
|
2008-03-20 22:15:55 +08:00
|
|
|
config NF_CT_PROTO_DCCP
|
|
|
|
|
tristate 'DCCP protocol connection tracking support (EXPERIMENTAL)'
|
2008-10-08 17:35:18 +08:00
|
|
|
depends on EXPERIMENTAL
|
2008-03-20 22:15:55 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
2008-05-08 16:16:04 +08:00
|
|
|
default IP_DCCP
|
2008-03-20 22:15:55 +08:00
|
|
|
help
|
|
|
|
|
With this option enabled, the layer 3 independent connection
|
|
|
|
|
tracking code will be able to do state tracking on DCCP connections.
|
|
|
|
|
|
|
|
|
|
If unsure, say 'N'.
|
|
|
|
|
|
2006-12-03 14:09:41 +08:00
|
|
|
config NF_CT_PROTO_GRE
|
|
|
|
|
tristate
|
|
|
|
|
|
[NETFILTER]: Add nf_conntrack subsystem.
The existing connection tracking subsystem in netfilter can only
handle ipv4. There were basically two choices present to add
connection tracking support for ipv6. We could either duplicate all
of the ipv4 connection tracking code into an ipv6 counterpart, or (the
choice taken by these patches) we could design a generic layer that
could handle both ipv4 and ipv6 and thus requiring only one sub-protocol
(TCP, UDP, etc.) connection tracking helper module to be written.
In fact nf_conntrack is capable of working with any layer 3
protocol.
The existing ipv4 specific conntrack code could also not deal
with the pecularities of doing connection tracking on ipv6,
which is also cured here. For example, these issues include:
1) ICMPv6 handling, which is used for neighbour discovery in
ipv6 thus some messages such as these should not participate
in connection tracking since effectively they are like ARP
messages
2) fragmentation must be handled differently in ipv6, because
the simplistic "defrag, connection track and NAT, refrag"
(which the existing ipv4 connection tracking does) approach simply
isn't feasible in ipv6
3) ipv6 extension header parsing must occur at the correct spots
before and after connection tracking decisions, and there were
no provisions for this in the existing connection tracking
design
4) ipv6 has no need for stateful NAT
The ipv4 specific conntrack layer is kept around, until all of
the ipv4 specific conntrack helpers are ported over to nf_conntrack
and it is feature complete. Once that occurs, the old conntrack
stuff will get placed into the feature-removal-schedule and we will
fully kill it off 6 months later.
Signed-off-by: Yasuyuki Kozakai <yasuyuki.kozakai@toshiba.co.jp>
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: Arnaldo Carvalho de Melo <acme@mandriva.com>
2005-11-10 08:38:16 +08:00
|
|
|
config NF_CT_PROTO_SCTP
|
2006-12-03 14:11:01 +08:00
|
|
|
tristate 'SCTP protocol connection tracking support (EXPERIMENTAL)'
|
2008-10-08 17:35:18 +08:00
|
|
|
depends on EXPERIMENTAL
|
2007-12-18 14:47:05 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
2008-05-08 16:16:04 +08:00
|
|
|
default IP_SCTP
|
[NETFILTER]: Add nf_conntrack subsystem.
The existing connection tracking subsystem in netfilter can only
handle ipv4. There were basically two choices present to add
connection tracking support for ipv6. We could either duplicate all
of the ipv4 connection tracking code into an ipv6 counterpart, or (the
choice taken by these patches) we could design a generic layer that
could handle both ipv4 and ipv6 and thus requiring only one sub-protocol
(TCP, UDP, etc.) connection tracking helper module to be written.
In fact nf_conntrack is capable of working with any layer 3
protocol.
The existing ipv4 specific conntrack code could also not deal
with the pecularities of doing connection tracking on ipv6,
which is also cured here. For example, these issues include:
1) ICMPv6 handling, which is used for neighbour discovery in
ipv6 thus some messages such as these should not participate
in connection tracking since effectively they are like ARP
messages
2) fragmentation must be handled differently in ipv6, because
the simplistic "defrag, connection track and NAT, refrag"
(which the existing ipv4 connection tracking does) approach simply
isn't feasible in ipv6
3) ipv6 extension header parsing must occur at the correct spots
before and after connection tracking decisions, and there were
no provisions for this in the existing connection tracking
design
4) ipv6 has no need for stateful NAT
The ipv4 specific conntrack layer is kept around, until all of
the ipv4 specific conntrack helpers are ported over to nf_conntrack
and it is feature complete. Once that occurs, the old conntrack
stuff will get placed into the feature-removal-schedule and we will
fully kill it off 6 months later.
Signed-off-by: Yasuyuki Kozakai <yasuyuki.kozakai@toshiba.co.jp>
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: Arnaldo Carvalho de Melo <acme@mandriva.com>
2005-11-10 08:38:16 +08:00
|
|
|
help
|
|
|
|
|
With this option enabled, the layer 3 independent connection
|
|
|
|
|
tracking code will be able to do state tracking on SCTP connections.
|
|
|
|
|
|
|
|
|
|
If you want to compile it as a module, say M here and read
|
2007-03-16 21:28:43 +08:00
|
|
|
<file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
|
[NETFILTER]: Add nf_conntrack subsystem.
The existing connection tracking subsystem in netfilter can only
handle ipv4. There were basically two choices present to add
connection tracking support for ipv6. We could either duplicate all
of the ipv4 connection tracking code into an ipv6 counterpart, or (the
choice taken by these patches) we could design a generic layer that
could handle both ipv4 and ipv6 and thus requiring only one sub-protocol
(TCP, UDP, etc.) connection tracking helper module to be written.
In fact nf_conntrack is capable of working with any layer 3
protocol.
The existing ipv4 specific conntrack code could also not deal
with the pecularities of doing connection tracking on ipv6,
which is also cured here. For example, these issues include:
1) ICMPv6 handling, which is used for neighbour discovery in
ipv6 thus some messages such as these should not participate
in connection tracking since effectively they are like ARP
messages
2) fragmentation must be handled differently in ipv6, because
the simplistic "defrag, connection track and NAT, refrag"
(which the existing ipv4 connection tracking does) approach simply
isn't feasible in ipv6
3) ipv6 extension header parsing must occur at the correct spots
before and after connection tracking decisions, and there were
no provisions for this in the existing connection tracking
design
4) ipv6 has no need for stateful NAT
The ipv4 specific conntrack layer is kept around, until all of
the ipv4 specific conntrack helpers are ported over to nf_conntrack
and it is feature complete. Once that occurs, the old conntrack
stuff will get placed into the feature-removal-schedule and we will
fully kill it off 6 months later.
Signed-off-by: Yasuyuki Kozakai <yasuyuki.kozakai@toshiba.co.jp>
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: Arnaldo Carvalho de Melo <acme@mandriva.com>
2005-11-10 08:38:16 +08:00
|
|
|
|
2007-07-15 11:48:44 +08:00
|
|
|
config NF_CT_PROTO_UDPLITE
|
2008-01-15 15:31:36 +08:00
|
|
|
tristate 'UDP-Lite protocol connection tracking support'
|
2007-12-18 14:47:05 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
2007-07-15 11:48:44 +08:00
|
|
|
help
|
|
|
|
|
With this option enabled, the layer 3 independent connection
|
|
|
|
|
tracking code will be able to do state tracking on UDP-Lite
|
|
|
|
|
connections.
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
2006-12-03 14:08:26 +08:00
|
|
|
config NF_CONNTRACK_AMANDA
|
2007-01-05 04:16:06 +08:00
|
|
|
tristate "Amanda backup protocol support"
|
2007-12-18 14:47:05 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
2006-12-03 14:08:26 +08:00
|
|
|
select TEXTSEARCH
|
|
|
|
|
select TEXTSEARCH_KMP
|
|
|
|
|
help
|
|
|
|
|
If you are running the Amanda backup package <http://www.amanda.org/>
|
|
|
|
|
on this machine or machines that will be MASQUERADED through this
|
|
|
|
|
machine, then you may want to enable this feature. This allows the
|
|
|
|
|
connection tracking and natting code to allow the sub-channels that
|
|
|
|
|
Amanda requires for communication of the backup data, messages and
|
|
|
|
|
index.
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
[NETFILTER]: Add nf_conntrack subsystem.
The existing connection tracking subsystem in netfilter can only
handle ipv4. There were basically two choices present to add
connection tracking support for ipv6. We could either duplicate all
of the ipv4 connection tracking code into an ipv6 counterpart, or (the
choice taken by these patches) we could design a generic layer that
could handle both ipv4 and ipv6 and thus requiring only one sub-protocol
(TCP, UDP, etc.) connection tracking helper module to be written.
In fact nf_conntrack is capable of working with any layer 3
protocol.
The existing ipv4 specific conntrack code could also not deal
with the pecularities of doing connection tracking on ipv6,
which is also cured here. For example, these issues include:
1) ICMPv6 handling, which is used for neighbour discovery in
ipv6 thus some messages such as these should not participate
in connection tracking since effectively they are like ARP
messages
2) fragmentation must be handled differently in ipv6, because
the simplistic "defrag, connection track and NAT, refrag"
(which the existing ipv4 connection tracking does) approach simply
isn't feasible in ipv6
3) ipv6 extension header parsing must occur at the correct spots
before and after connection tracking decisions, and there were
no provisions for this in the existing connection tracking
design
4) ipv6 has no need for stateful NAT
The ipv4 specific conntrack layer is kept around, until all of
the ipv4 specific conntrack helpers are ported over to nf_conntrack
and it is feature complete. Once that occurs, the old conntrack
stuff will get placed into the feature-removal-schedule and we will
fully kill it off 6 months later.
Signed-off-by: Yasuyuki Kozakai <yasuyuki.kozakai@toshiba.co.jp>
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: Arnaldo Carvalho de Melo <acme@mandriva.com>
2005-11-10 08:38:16 +08:00
|
|
|
config NF_CONNTRACK_FTP
|
2007-01-05 04:16:06 +08:00
|
|
|
tristate "FTP protocol support"
|
2007-12-18 14:47:05 +08:00
|
|
|
default m if NETFILTER_ADVANCED=n
|
[NETFILTER]: Add nf_conntrack subsystem.
The existing connection tracking subsystem in netfilter can only
handle ipv4. There were basically two choices present to add
connection tracking support for ipv6. We could either duplicate all
of the ipv4 connection tracking code into an ipv6 counterpart, or (the
choice taken by these patches) we could design a generic layer that
could handle both ipv4 and ipv6 and thus requiring only one sub-protocol
(TCP, UDP, etc.) connection tracking helper module to be written.
In fact nf_conntrack is capable of working with any layer 3
protocol.
The existing ipv4 specific conntrack code could also not deal
with the pecularities of doing connection tracking on ipv6,
which is also cured here. For example, these issues include:
1) ICMPv6 handling, which is used for neighbour discovery in
ipv6 thus some messages such as these should not participate
in connection tracking since effectively they are like ARP
messages
2) fragmentation must be handled differently in ipv6, because
the simplistic "defrag, connection track and NAT, refrag"
(which the existing ipv4 connection tracking does) approach simply
isn't feasible in ipv6
3) ipv6 extension header parsing must occur at the correct spots
before and after connection tracking decisions, and there were
no provisions for this in the existing connection tracking
design
4) ipv6 has no need for stateful NAT
The ipv4 specific conntrack layer is kept around, until all of
the ipv4 specific conntrack helpers are ported over to nf_conntrack
and it is feature complete. Once that occurs, the old conntrack
stuff will get placed into the feature-removal-schedule and we will
fully kill it off 6 months later.
Signed-off-by: Yasuyuki Kozakai <yasuyuki.kozakai@toshiba.co.jp>
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: Arnaldo Carvalho de Melo <acme@mandriva.com>
2005-11-10 08:38:16 +08:00
|
|
|
help
|
|
|
|
|
Tracking FTP connections is problematic: special helpers are
|
|
|
|
|
required for tracking them, and doing masquerading and other forms
|
|
|
|
|
of Network Address Translation on them.
|
|
|
|
|
|
|
|
|
|
This is FTP support on Layer 3 independent connection tracking.
|
|
|
|
|
Layer 3 independent connection tracking is experimental scheme
|
|
|
|
|
which generalize ip_conntrack to support other layer 3 protocols.
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
2006-12-03 14:08:46 +08:00
|
|
|
config NF_CONNTRACK_H323
|
2008-01-15 15:31:36 +08:00
|
|
|
tristate "H.323 protocol support"
|
2008-10-08 17:35:18 +08:00
|
|
|
depends on (IPV6 || IPV6=n)
|
2007-12-18 14:47:05 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
2006-12-03 14:08:46 +08:00
|
|
|
help
|
|
|
|
|
H.323 is a VoIP signalling protocol from ITU-T. As one of the most
|
|
|
|
|
important VoIP protocols, it is widely used by voice hardware and
|
|
|
|
|
software including voice gateways, IP phones, Netmeeting, OpenPhone,
|
|
|
|
|
Gnomemeeting, etc.
|
|
|
|
|
|
|
|
|
|
With this module you can support H.323 on a connection tracking/NAT
|
|
|
|
|
firewall.
|
|
|
|
|
|
|
|
|
|
This module supports RAS, Fast Start, H.245 Tunnelling, Call
|
|
|
|
|
Forwarding, RTP/RTCP and T.120 based audio, video, fax, chat,
|
|
|
|
|
whiteboard, file transfer, etc. For more information, please
|
|
|
|
|
visit http://nath323.sourceforge.net/.
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
2006-12-03 14:09:06 +08:00
|
|
|
config NF_CONNTRACK_IRC
|
2007-01-05 04:16:06 +08:00
|
|
|
tristate "IRC protocol support"
|
2007-12-18 14:47:05 +08:00
|
|
|
default m if NETFILTER_ADVANCED=n
|
2006-12-03 14:09:06 +08:00
|
|
|
help
|
|
|
|
|
There is a commonly-used extension to IRC called
|
|
|
|
|
Direct Client-to-Client Protocol (DCC). This enables users to send
|
|
|
|
|
files to each other, and also chat to each other without the need
|
|
|
|
|
of a server. DCC Sending is used anywhere you send files over IRC,
|
|
|
|
|
and DCC Chat is most commonly used by Eggdrop bots. If you are
|
|
|
|
|
using NAT, this extension will enable you to send files and initiate
|
|
|
|
|
chats. Note that you do NOT need this extension to get files or
|
|
|
|
|
have others initiate chats, or everything else in IRC.
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
2011-01-19 01:12:24 +08:00
|
|
|
config NF_CONNTRACK_BROADCAST
|
|
|
|
|
tristate
|
|
|
|
|
|
2006-12-03 14:09:24 +08:00
|
|
|
config NF_CONNTRACK_NETBIOS_NS
|
2008-01-15 15:31:36 +08:00
|
|
|
tristate "NetBIOS name service protocol support"
|
2011-01-19 01:12:24 +08:00
|
|
|
select NF_CONNTRACK_BROADCAST
|
2006-12-03 14:09:24 +08:00
|
|
|
help
|
|
|
|
|
NetBIOS name service requests are sent as broadcast messages from an
|
|
|
|
|
unprivileged port and responded to with unicast messages to the
|
|
|
|
|
same port. This make them hard to firewall properly because connection
|
|
|
|
|
tracking doesn't deal with broadcasts. This helper tracks locally
|
|
|
|
|
originating NetBIOS name service requests and the corresponding
|
|
|
|
|
responses. It relies on correct IP address configuration, specifically
|
|
|
|
|
netmask and broadcast address. When properly configured, the output
|
|
|
|
|
of "ip address show" should look similar to this:
|
|
|
|
|
|
|
|
|
|
$ ip -4 address show eth0
|
|
|
|
|
4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
|
|
|
|
|
inet 172.16.2.252/24 brd 172.16.2.255 scope global eth0
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
2011-01-19 01:12:24 +08:00
|
|
|
config NF_CONNTRACK_SNMP
|
|
|
|
|
tristate "SNMP service protocol support"
|
|
|
|
|
depends on NETFILTER_ADVANCED
|
|
|
|
|
select NF_CONNTRACK_BROADCAST
|
|
|
|
|
help
|
|
|
|
|
SNMP service requests are sent as broadcast messages from an
|
|
|
|
|
unprivileged port and responded to with unicast messages to the
|
|
|
|
|
same port. This make them hard to firewall properly because connection
|
|
|
|
|
tracking doesn't deal with broadcasts. This helper tracks locally
|
|
|
|
|
originating SNMP service requests and the corresponding
|
|
|
|
|
responses. It relies on correct IP address configuration, specifically
|
|
|
|
|
netmask and broadcast address.
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
2006-12-03 14:09:41 +08:00
|
|
|
config NF_CONNTRACK_PPTP
|
2007-01-05 04:16:06 +08:00
|
|
|
tristate "PPtP protocol support"
|
2007-12-18 14:47:05 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
2006-12-03 14:09:41 +08:00
|
|
|
select NF_CT_PROTO_GRE
|
|
|
|
|
help
|
|
|
|
|
This module adds support for PPTP (Point to Point Tunnelling
|
|
|
|
|
Protocol, RFC2637) connection tracking and NAT.
|
|
|
|
|
|
|
|
|
|
If you are running PPTP sessions over a stateful firewall or NAT
|
|
|
|
|
box, you may want to enable this feature.
|
|
|
|
|
|
|
|
|
|
Please note that not all PPTP modes of operation are supported yet.
|
|
|
|
|
Specifically these limitations exist:
|
2007-05-09 13:12:20 +08:00
|
|
|
- Blindly assumes that control connections are always established
|
2006-12-03 14:09:41 +08:00
|
|
|
in PNS->PAC direction. This is a violation of RFC2637.
|
|
|
|
|
- Only supports a single call within each session
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
2007-02-08 07:05:12 +08:00
|
|
|
config NF_CONNTRACK_SANE
|
|
|
|
|
tristate "SANE protocol support (EXPERIMENTAL)"
|
2008-10-08 17:35:18 +08:00
|
|
|
depends on EXPERIMENTAL
|
2007-12-18 14:47:05 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
2007-02-08 07:05:12 +08:00
|
|
|
help
|
|
|
|
|
SANE is a protocol for remote access to scanners as implemented
|
|
|
|
|
by the 'saned' daemon. Like FTP, it uses separate control and
|
|
|
|
|
data connections.
|
|
|
|
|
|
|
|
|
|
With this module you can support SANE on a connection tracking
|
|
|
|
|
firewall.
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
2006-12-03 14:09:57 +08:00
|
|
|
config NF_CONNTRACK_SIP
|
2008-01-15 15:31:36 +08:00
|
|
|
tristate "SIP protocol support"
|
2007-12-18 14:47:05 +08:00
|
|
|
default m if NETFILTER_ADVANCED=n
|
2006-12-03 14:09:57 +08:00
|
|
|
help
|
|
|
|
|
SIP is an application-layer control protocol that can establish,
|
|
|
|
|
modify, and terminate multimedia sessions (conferences) such as
|
|
|
|
|
Internet telephony calls. With the ip_conntrack_sip and
|
|
|
|
|
the nf_nat_sip modules you can support the protocol on a connection
|
|
|
|
|
tracking/NATing firewall.
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
2006-12-03 14:10:18 +08:00
|
|
|
config NF_CONNTRACK_TFTP
|
2007-01-05 04:16:06 +08:00
|
|
|
tristate "TFTP protocol support"
|
2007-12-18 14:47:05 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
2006-12-03 14:10:18 +08:00
|
|
|
help
|
|
|
|
|
TFTP connection tracking helper, this is required depending
|
|
|
|
|
on how restrictive your ruleset is.
|
|
|
|
|
If you are using a tftp client behind -j SNAT or -j MASQUERADING
|
|
|
|
|
you will need this.
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
2006-01-06 04:19:05 +08:00
|
|
|
config NF_CT_NETLINK
|
2008-01-15 15:31:36 +08:00
|
|
|
tristate 'Connection tracking netlink interface'
|
2007-12-05 17:31:52 +08:00
|
|
|
select NETFILTER_NETLINK
|
2007-12-18 14:47:05 +08:00
|
|
|
default m if NETFILTER_ADVANCED=n
|
2006-01-06 04:19:05 +08:00
|
|
|
help
|
|
|
|
|
This option enables support for a netlink-based userspace interface
|
|
|
|
|
|
2012-02-29 02:13:48 +08:00
|
|
|
config NF_CT_NETLINK_TIMEOUT
|
|
|
|
|
tristate 'Connection tracking timeout tuning via Netlink'
|
|
|
|
|
select NETFILTER_NETLINK
|
|
|
|
|
depends on NETFILTER_ADVANCED
|
|
|
|
|
help
|
|
|
|
|
This option enables support for connection tracking timeout
|
|
|
|
|
fine-grain tuning. This allows you to attach specific timeout
|
|
|
|
|
policies to flows, instead of using the global timeout policy.
|
|
|
|
|
|
|
|
|
|
If unsure, say `N'.
|
|
|
|
|
|
2012-06-19 03:14:30 +08:00
|
|
|
config NF_CT_NETLINK_HELPER
|
|
|
|
|
tristate 'Connection tracking helpers in user-space via Netlink'
|
|
|
|
|
select NETFILTER_NETLINK
|
|
|
|
|
depends on NF_CT_NETLINK
|
|
|
|
|
depends on NETFILTER_NETLINK_QUEUE
|
2012-06-19 08:10:57 +08:00
|
|
|
depends on NETFILTER_NETLINK_QUEUE_CT
|
2012-06-19 03:14:30 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
|
|
|
|
help
|
|
|
|
|
This option enables the user-space connection tracking helpers
|
|
|
|
|
infrastructure.
|
|
|
|
|
|
|
|
|
|
If unsure, say `N'.
|
|
|
|
|
|
2012-06-19 08:10:57 +08:00
|
|
|
config NETFILTER_NETLINK_QUEUE_CT
|
|
|
|
|
bool "NFQUEUE integration with Connection Tracking"
|
|
|
|
|
default n
|
|
|
|
|
depends on NETFILTER_NETLINK_QUEUE
|
|
|
|
|
help
|
|
|
|
|
If this option is enabled, NFQUEUE can include Connection Tracking
|
|
|
|
|
information together with the packet is the enqueued via NFNETLINK.
|
|
|
|
|
|
2012-08-27 01:14:06 +08:00
|
|
|
config NF_NAT
|
|
|
|
|
tristate
|
|
|
|
|
|
|
|
|
|
config NF_NAT_NEEDED
|
|
|
|
|
bool
|
|
|
|
|
depends on NF_NAT
|
|
|
|
|
default y
|
|
|
|
|
|
|
|
|
|
config NF_NAT_PROTO_DCCP
|
|
|
|
|
tristate
|
|
|
|
|
depends on NF_NAT && NF_CT_PROTO_DCCP
|
|
|
|
|
default NF_NAT && NF_CT_PROTO_DCCP
|
|
|
|
|
|
|
|
|
|
config NF_NAT_PROTO_UDPLITE
|
|
|
|
|
tristate
|
|
|
|
|
depends on NF_NAT && NF_CT_PROTO_UDPLITE
|
|
|
|
|
default NF_NAT && NF_CT_PROTO_UDPLITE
|
|
|
|
|
|
|
|
|
|
config NF_NAT_PROTO_SCTP
|
|
|
|
|
tristate
|
|
|
|
|
default NF_NAT && NF_CT_PROTO_SCTP
|
|
|
|
|
depends on NF_NAT && NF_CT_PROTO_SCTP
|
|
|
|
|
select LIBCRC32C
|
|
|
|
|
|
2012-08-27 01:14:22 +08:00
|
|
|
config NF_NAT_AMANDA
|
|
|
|
|
tristate
|
|
|
|
|
depends on NF_CONNTRACK && NF_NAT
|
|
|
|
|
default NF_NAT && NF_CONNTRACK_AMANDA
|
|
|
|
|
|
2012-08-27 01:14:20 +08:00
|
|
|
config NF_NAT_FTP
|
|
|
|
|
tristate
|
|
|
|
|
depends on NF_CONNTRACK && NF_NAT
|
|
|
|
|
default NF_NAT && NF_CONNTRACK_FTP
|
|
|
|
|
|
2012-08-27 01:14:27 +08:00
|
|
|
config NF_NAT_IRC
|
|
|
|
|
tristate
|
|
|
|
|
depends on NF_CONNTRACK && NF_NAT
|
|
|
|
|
default NF_NAT && NF_CONNTRACK_IRC
|
|
|
|
|
|
2012-08-27 01:14:25 +08:00
|
|
|
config NF_NAT_SIP
|
|
|
|
|
tristate
|
|
|
|
|
depends on NF_CONNTRACK && NF_NAT
|
|
|
|
|
default NF_NAT && NF_CONNTRACK_SIP
|
|
|
|
|
|
2012-08-27 01:14:29 +08:00
|
|
|
config NF_NAT_TFTP
|
|
|
|
|
tristate
|
|
|
|
|
depends on NF_CONNTRACK && NF_NAT
|
|
|
|
|
default NF_NAT && NF_CONNTRACK_TFTP
|
|
|
|
|
|
2009-04-24 22:55:25 +08:00
|
|
|
endif # NF_CONNTRACK
|
|
|
|
|
|
2008-10-08 17:35:12 +08:00
|
|
|
# transparent proxy support
|
|
|
|
|
config NETFILTER_TPROXY
|
|
|
|
|
tristate "Transparent proxying support (EXPERIMENTAL)"
|
|
|
|
|
depends on EXPERIMENTAL
|
|
|
|
|
depends on IP_NF_MANGLE
|
|
|
|
|
depends on NETFILTER_ADVANCED
|
|
|
|
|
help
|
|
|
|
|
This option enables transparent proxying support, that is,
|
|
|
|
|
support for handling non-locally bound IPv4 TCP and UDP sockets.
|
|
|
|
|
For it to work you will have to configure certain iptables rules
|
|
|
|
|
and use policy routing. For more information on how to set it up
|
|
|
|
|
see Documentation/networking/tproxy.txt.
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
[NETFILTER] x_tables: Abstraction layer for {ip,ip6,arp}_tables
This monster-patch tries to do the best job for unifying the data
structures and backend interfaces for the three evil clones ip_tables,
ip6_tables and arp_tables. In an ideal world we would never have
allowed this kind of copy+paste programming... but well, our world
isn't (yet?) ideal.
o introduce a new x_tables module
o {ip,arp,ip6}_tables depend on this x_tables module
o registration functions for tables, matches and targets are only
wrappers around x_tables provided functions
o all matches/targets that are used from ip_tables and ip6_tables
are now implemented as xt_FOOBAR.c files and provide module aliases
to ipt_FOOBAR and ip6t_FOOBAR
o header files for xt_matches are in include/linux/netfilter/,
include/linux/netfilter_{ipv4,ipv6} contains compatibility wrappers
around the xt_FOOBAR.h headers
Based on this patchset we're going to further unify the code,
gradually getting rid of all the layer 3 specific assumptions.
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-01-13 05:30:04 +08:00
|
|
|
config NETFILTER_XTABLES
|
|
|
|
|
tristate "Netfilter Xtables support (required for ip_tables)"
|
2007-12-18 14:47:05 +08:00
|
|
|
default m if NETFILTER_ADVANCED=n
|
[NETFILTER] x_tables: Abstraction layer for {ip,ip6,arp}_tables
This monster-patch tries to do the best job for unifying the data
structures and backend interfaces for the three evil clones ip_tables,
ip6_tables and arp_tables. In an ideal world we would never have
allowed this kind of copy+paste programming... but well, our world
isn't (yet?) ideal.
o introduce a new x_tables module
o {ip,arp,ip6}_tables depend on this x_tables module
o registration functions for tables, matches and targets are only
wrappers around x_tables provided functions
o all matches/targets that are used from ip_tables and ip6_tables
are now implemented as xt_FOOBAR.c files and provide module aliases
to ipt_FOOBAR and ip6t_FOOBAR
o header files for xt_matches are in include/linux/netfilter/,
include/linux/netfilter_{ipv4,ipv6} contains compatibility wrappers
around the xt_FOOBAR.h headers
Based on this patchset we're going to further unify the code,
gradually getting rid of all the layer 3 specific assumptions.
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-01-13 05:30:04 +08:00
|
|
|
help
|
|
|
|
|
This is required if you intend to use any of ip_tables,
|
|
|
|
|
ip6_tables or arp_tables.
|
|
|
|
|
|
2008-10-08 17:35:18 +08:00
|
|
|
if NETFILTER_XTABLES
|
|
|
|
|
|
2009-02-28 10:23:57 +08:00
|
|
|
comment "Xtables combined modules"
|
|
|
|
|
|
|
|
|
|
config NETFILTER_XT_MARK
|
|
|
|
|
tristate 'nfmark target and match support'
|
|
|
|
|
default m if NETFILTER_ADVANCED=n
|
|
|
|
|
---help---
|
|
|
|
|
This option adds the "MARK" target and "mark" match.
|
|
|
|
|
|
|
|
|
|
Netfilter mark matching allows you to match packets based on the
|
|
|
|
|
"nfmark" value in the packet.
|
|
|
|
|
The target allows you to create rules in the "mangle" table which alter
|
|
|
|
|
the netfilter mark (nfmark) field associated with the packet.
|
|
|
|
|
|
|
|
|
|
Prior to routing, the nfmark can influence the routing method (see
|
|
|
|
|
"Use netfilter MARK value as routing key") and can also be used by
|
|
|
|
|
other subsystems to change their behavior.
|
|
|
|
|
|
2010-02-26 21:20:32 +08:00
|
|
|
config NETFILTER_XT_CONNMARK
|
|
|
|
|
tristate 'ctmark target and match support'
|
|
|
|
|
depends on NF_CONNTRACK
|
|
|
|
|
depends on NETFILTER_ADVANCED
|
|
|
|
|
select NF_CONNTRACK_MARK
|
|
|
|
|
---help---
|
|
|
|
|
This option adds the "CONNMARK" target and "connmark" match.
|
|
|
|
|
|
|
|
|
|
Netfilter allows you to store a mark value per connection (a.k.a.
|
|
|
|
|
ctmark), similarly to the packet mark (nfmark). Using this
|
|
|
|
|
target and match, you can set and match on this mark.
|
|
|
|
|
|
2011-02-01 22:56:00 +08:00
|
|
|
config NETFILTER_XT_SET
|
|
|
|
|
tristate 'set target and match support'
|
|
|
|
|
depends on IP_SET
|
|
|
|
|
depends on NETFILTER_ADVANCED
|
|
|
|
|
help
|
|
|
|
|
This option adds the "SET" target and "set" match.
|
|
|
|
|
|
|
|
|
|
Using this target and match, you can add/delete and match
|
|
|
|
|
elements in the sets created by ipset(8).
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
[NETFILTER] x_tables: Abstraction layer for {ip,ip6,arp}_tables
This monster-patch tries to do the best job for unifying the data
structures and backend interfaces for the three evil clones ip_tables,
ip6_tables and arp_tables. In an ideal world we would never have
allowed this kind of copy+paste programming... but well, our world
isn't (yet?) ideal.
o introduce a new x_tables module
o {ip,arp,ip6}_tables depend on this x_tables module
o registration functions for tables, matches and targets are only
wrappers around x_tables provided functions
o all matches/targets that are used from ip_tables and ip6_tables
are now implemented as xt_FOOBAR.c files and provide module aliases
to ipt_FOOBAR and ip6t_FOOBAR
o header files for xt_matches are in include/linux/netfilter/,
include/linux/netfilter_{ipv4,ipv6} contains compatibility wrappers
around the xt_FOOBAR.h headers
Based on this patchset we're going to further unify the code,
gradually getting rid of all the layer 3 specific assumptions.
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-01-13 05:30:04 +08:00
|
|
|
# alphabetically ordered list of targets
|
|
|
|
|
|
2010-02-26 21:14:22 +08:00
|
|
|
comment "Xtables targets"
|
|
|
|
|
|
2011-01-17 01:10:28 +08:00
|
|
|
config NETFILTER_XT_TARGET_AUDIT
|
|
|
|
|
tristate "AUDIT target support"
|
|
|
|
|
depends on AUDIT
|
|
|
|
|
depends on NETFILTER_ADVANCED
|
|
|
|
|
---help---
|
|
|
|
|
This option adds a 'AUDIT' target, which can be used to create
|
|
|
|
|
audit records for packets dropped/accepted.
|
|
|
|
|
|
|
|
|
|
To compileit as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
2010-07-15 23:20:46 +08:00
|
|
|
config NETFILTER_XT_TARGET_CHECKSUM
|
|
|
|
|
tristate "CHECKSUM target support"
|
|
|
|
|
depends on IP_NF_MANGLE || IP6_NF_MANGLE
|
|
|
|
|
depends on NETFILTER_ADVANCED
|
|
|
|
|
---help---
|
|
|
|
|
This option adds a `CHECKSUM' target, which can be used in the iptables mangle
|
|
|
|
|
table.
|
|
|
|
|
|
|
|
|
|
You can use this target to 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.
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
[NETFILTER] x_tables: Abstraction layer for {ip,ip6,arp}_tables
This monster-patch tries to do the best job for unifying the data
structures and backend interfaces for the three evil clones ip_tables,
ip6_tables and arp_tables. In an ideal world we would never have
allowed this kind of copy+paste programming... but well, our world
isn't (yet?) ideal.
o introduce a new x_tables module
o {ip,arp,ip6}_tables depend on this x_tables module
o registration functions for tables, matches and targets are only
wrappers around x_tables provided functions
o all matches/targets that are used from ip_tables and ip6_tables
are now implemented as xt_FOOBAR.c files and provide module aliases
to ipt_FOOBAR and ip6t_FOOBAR
o header files for xt_matches are in include/linux/netfilter/,
include/linux/netfilter_{ipv4,ipv6} contains compatibility wrappers
around the xt_FOOBAR.h headers
Based on this patchset we're going to further unify the code,
gradually getting rid of all the layer 3 specific assumptions.
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-01-13 05:30:04 +08:00
|
|
|
config NETFILTER_XT_TARGET_CLASSIFY
|
|
|
|
|
tristate '"CLASSIFY" target support'
|
2007-12-18 14:47:05 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
[NETFILTER] x_tables: Abstraction layer for {ip,ip6,arp}_tables
This monster-patch tries to do the best job for unifying the data
structures and backend interfaces for the three evil clones ip_tables,
ip6_tables and arp_tables. In an ideal world we would never have
allowed this kind of copy+paste programming... but well, our world
isn't (yet?) ideal.
o introduce a new x_tables module
o {ip,arp,ip6}_tables depend on this x_tables module
o registration functions for tables, matches and targets are only
wrappers around x_tables provided functions
o all matches/targets that are used from ip_tables and ip6_tables
are now implemented as xt_FOOBAR.c files and provide module aliases
to ipt_FOOBAR and ip6t_FOOBAR
o header files for xt_matches are in include/linux/netfilter/,
include/linux/netfilter_{ipv4,ipv6} contains compatibility wrappers
around the xt_FOOBAR.h headers
Based on this patchset we're going to further unify the code,
gradually getting rid of all the layer 3 specific assumptions.
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-01-13 05:30:04 +08:00
|
|
|
help
|
|
|
|
|
This option adds a `CLASSIFY' target, which enables the user to set
|
|
|
|
|
the priority of a packet. Some qdiscs can use this value for
|
|
|
|
|
classification, among these are:
|
|
|
|
|
|
|
|
|
|
atm, cbq, dsmark, pfifo_fast, htb, prio
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
|
|
|
|
config NETFILTER_XT_TARGET_CONNMARK
|
|
|
|
|
tristate '"CONNMARK" target support'
|
2007-03-15 07:37:25 +08:00
|
|
|
depends on NF_CONNTRACK
|
2007-12-18 14:47:05 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
2010-02-26 21:20:32 +08:00
|
|
|
select NETFILTER_XT_CONNMARK
|
|
|
|
|
---help---
|
|
|
|
|
This is a backwards-compat option for the user's convenience
|
|
|
|
|
(e.g. when running oldconfig). It selects
|
|
|
|
|
CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
|
[NETFILTER] x_tables: Abstraction layer for {ip,ip6,arp}_tables
This monster-patch tries to do the best job for unifying the data
structures and backend interfaces for the three evil clones ip_tables,
ip6_tables and arp_tables. In an ideal world we would never have
allowed this kind of copy+paste programming... but well, our world
isn't (yet?) ideal.
o introduce a new x_tables module
o {ip,arp,ip6}_tables depend on this x_tables module
o registration functions for tables, matches and targets are only
wrappers around x_tables provided functions
o all matches/targets that are used from ip_tables and ip6_tables
are now implemented as xt_FOOBAR.c files and provide module aliases
to ipt_FOOBAR and ip6t_FOOBAR
o header files for xt_matches are in include/linux/netfilter/,
include/linux/netfilter_{ipv4,ipv6} contains compatibility wrappers
around the xt_FOOBAR.h headers
Based on this patchset we're going to further unify the code,
gradually getting rid of all the layer 3 specific assumptions.
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-01-13 05:30:04 +08:00
|
|
|
|
2008-10-08 17:35:17 +08:00
|
|
|
config NETFILTER_XT_TARGET_CONNSECMARK
|
|
|
|
|
tristate '"CONNSECMARK" target support'
|
2008-10-08 17:35:18 +08:00
|
|
|
depends on NF_CONNTRACK && NF_CONNTRACK_SECMARK
|
2008-10-08 17:35:17 +08:00
|
|
|
default m if NETFILTER_ADVANCED=n
|
|
|
|
|
help
|
|
|
|
|
The CONNSECMARK target copies security markings from packets
|
|
|
|
|
to connections, and restores security markings from connections
|
|
|
|
|
to packets (if the packets are not already marked). This would
|
|
|
|
|
normally be used in conjunction with the SECMARK target.
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
2010-02-04 00:17:06 +08:00
|
|
|
config NETFILTER_XT_TARGET_CT
|
|
|
|
|
tristate '"CT" target support'
|
|
|
|
|
depends on NF_CONNTRACK
|
|
|
|
|
depends on IP_NF_RAW || IP6_NF_RAW
|
|
|
|
|
depends on NETFILTER_ADVANCED
|
|
|
|
|
help
|
|
|
|
|
This options adds a `CT' target, which allows to specify initial
|
|
|
|
|
connection tracking parameters like events to be delivered and
|
|
|
|
|
the helper to be used.
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
2006-08-22 15:30:26 +08:00
|
|
|
config NETFILTER_XT_TARGET_DSCP
|
2007-12-05 15:38:13 +08:00
|
|
|
tristate '"DSCP" and "TOS" target support'
|
2006-08-22 15:30:26 +08:00
|
|
|
depends on IP_NF_MANGLE || IP6_NF_MANGLE
|
2007-12-18 14:47:05 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
2006-08-22 15:30:26 +08:00
|
|
|
help
|
|
|
|
|
This option adds a `DSCP' target, which allows you to manipulate
|
|
|
|
|
the IPv4/IPv6 header DSCP field (differentiated services codepoint).
|
|
|
|
|
|
|
|
|
|
The DSCP field can have any value between 0x0 and 0x3f inclusive.
|
|
|
|
|
|
2007-12-05 15:38:13 +08:00
|
|
|
It also adds the "TOS" target, which allows you to create rules in
|
|
|
|
|
the "mangle" table which alter the Type Of Service field of an IPv4
|
2007-12-05 15:39:09 +08:00
|
|
|
or the Priority field of an IPv6 packet, prior to routing.
|
2007-12-05 15:38:13 +08:00
|
|
|
|
2006-08-22 15:30:26 +08:00
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
2009-02-19 01:38:40 +08:00
|
|
|
config NETFILTER_XT_TARGET_HL
|
|
|
|
|
tristate '"HL" hoplimit target support'
|
|
|
|
|
depends on IP_NF_MANGLE || IP6_NF_MANGLE
|
|
|
|
|
depends on NETFILTER_ADVANCED
|
|
|
|
|
---help---
|
|
|
|
|
This option adds the "HL" (for IPv6) and "TTL" (for IPv4)
|
|
|
|
|
targets, which enable the user to change the
|
|
|
|
|
hoplimit/time-to-live value of the IP header.
|
|
|
|
|
|
|
|
|
|
While it is safe to decrement the hoplimit/TTL value, the
|
|
|
|
|
modules also allow to increment and set the hoplimit value of
|
|
|
|
|
the header to arbitrary values. This is EXTREMELY DANGEROUS
|
|
|
|
|
since you can easily create immortal packets that loop
|
|
|
|
|
forever on the network.
|
|
|
|
|
|
2012-05-02 15:49:47 +08:00
|
|
|
config NETFILTER_XT_TARGET_HMARK
|
|
|
|
|
tristate '"HMARK" target support'
|
|
|
|
|
depends on (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
|
|
|
|
|
depends on NETFILTER_ADVANCED
|
|
|
|
|
---help---
|
|
|
|
|
This option adds the "HMARK" target.
|
|
|
|
|
|
|
|
|
|
The target allows you to create rules in the "raw" and "mangle" tables
|
|
|
|
|
which set the skbuff mark by means of hash calculation within a given
|
|
|
|
|
range. The nfmark can influence the routing method (see "Use netfilter
|
|
|
|
|
MARK value as routing key") and can also be used by other subsystems to
|
|
|
|
|
change their behaviour.
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
2010-06-15 21:04:00 +08:00
|
|
|
config NETFILTER_XT_TARGET_IDLETIMER
|
|
|
|
|
tristate "IDLETIMER target support"
|
|
|
|
|
depends on NETFILTER_ADVANCED
|
|
|
|
|
help
|
|
|
|
|
|
|
|
|
|
This option adds the `IDLETIMER' target. Each matching packet
|
|
|
|
|
resets the timer associated with label specified when the rule is
|
|
|
|
|
added. When the timer expires, it triggers a sysfs notification.
|
|
|
|
|
The remaining time for expiration can be read via sysfs.
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
2009-02-20 17:55:14 +08:00
|
|
|
config NETFILTER_XT_TARGET_LED
|
|
|
|
|
tristate '"LED" target support'
|
2009-04-06 23:09:43 +08:00
|
|
|
depends on LEDS_CLASS && LEDS_TRIGGERS
|
2009-02-20 17:55:14 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
|
|
|
|
help
|
|
|
|
|
This option adds a `LED' target, which allows you to blink LEDs in
|
|
|
|
|
response to particular packets passing through your machine.
|
|
|
|
|
|
|
|
|
|
This can be used to turn a spare LED into a network activity LED,
|
|
|
|
|
which only flashes in response to FTP transfers, for example. Or
|
|
|
|
|
you could have an LED which lights up for a minute or two every time
|
|
|
|
|
somebody connects to your machine via SSH.
|
|
|
|
|
|
|
|
|
|
You will need support for the "led" class to make this work.
|
|
|
|
|
|
|
|
|
|
To create an LED trigger for incoming SSH traffic:
|
|
|
|
|
iptables -A INPUT -p tcp --dport 22 -j LED --led-trigger-id ssh --led-delay 1000
|
|
|
|
|
|
|
|
|
|
Then attach the new trigger to an LED on your system:
|
|
|
|
|
echo netfilter-ssh > /sys/class/leds/<ledname>/trigger
|
|
|
|
|
|
|
|
|
|
For more information on the LEDs available on your system, see
|
2011-08-15 08:02:26 +08:00
|
|
|
Documentation/leds/leds-class.txt
|
2009-02-20 17:55:14 +08:00
|
|
|
|
2012-02-11 06:10:52 +08:00
|
|
|
config NETFILTER_XT_TARGET_LOG
|
|
|
|
|
tristate "LOG target support"
|
|
|
|
|
default m if NETFILTER_ADVANCED=n
|
|
|
|
|
help
|
|
|
|
|
This option adds a `LOG' target, which allows you to create rules in
|
|
|
|
|
any iptables table which records the packet header to the syslog.
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
[NETFILTER] x_tables: Abstraction layer for {ip,ip6,arp}_tables
This monster-patch tries to do the best job for unifying the data
structures and backend interfaces for the three evil clones ip_tables,
ip6_tables and arp_tables. In an ideal world we would never have
allowed this kind of copy+paste programming... but well, our world
isn't (yet?) ideal.
o introduce a new x_tables module
o {ip,arp,ip6}_tables depend on this x_tables module
o registration functions for tables, matches and targets are only
wrappers around x_tables provided functions
o all matches/targets that are used from ip_tables and ip6_tables
are now implemented as xt_FOOBAR.c files and provide module aliases
to ipt_FOOBAR and ip6t_FOOBAR
o header files for xt_matches are in include/linux/netfilter/,
include/linux/netfilter_{ipv4,ipv6} contains compatibility wrappers
around the xt_FOOBAR.h headers
Based on this patchset we're going to further unify the code,
gradually getting rid of all the layer 3 specific assumptions.
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-01-13 05:30:04 +08:00
|
|
|
config NETFILTER_XT_TARGET_MARK
|
|
|
|
|
tristate '"MARK" target support'
|
2009-02-28 10:23:57 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
|
|
|
|
select NETFILTER_XT_MARK
|
|
|
|
|
---help---
|
|
|
|
|
This is a backwards-compat option for the user's convenience
|
|
|
|
|
(e.g. when running oldconfig). It selects
|
|
|
|
|
CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
|
[NETFILTER] x_tables: Abstraction layer for {ip,ip6,arp}_tables
This monster-patch tries to do the best job for unifying the data
structures and backend interfaces for the three evil clones ip_tables,
ip6_tables and arp_tables. In an ideal world we would never have
allowed this kind of copy+paste programming... but well, our world
isn't (yet?) ideal.
o introduce a new x_tables module
o {ip,arp,ip6}_tables depend on this x_tables module
o registration functions for tables, matches and targets are only
wrappers around x_tables provided functions
o all matches/targets that are used from ip_tables and ip6_tables
are now implemented as xt_FOOBAR.c files and provide module aliases
to ipt_FOOBAR and ip6t_FOOBAR
o header files for xt_matches are in include/linux/netfilter/,
include/linux/netfilter_{ipv4,ipv6} contains compatibility wrappers
around the xt_FOOBAR.h headers
Based on this patchset we're going to further unify the code,
gradually getting rid of all the layer 3 specific assumptions.
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-01-13 05:30:04 +08:00
|
|
|
|
2012-09-21 17:37:59 +08:00
|
|
|
config NETFILTER_XT_TARGET_NETMAP
|
|
|
|
|
tristate '"NETMAP" target support'
|
|
|
|
|
depends on NF_NAT
|
|
|
|
|
---help---
|
|
|
|
|
NETMAP is an implementation of static 1:1 NAT mapping of network
|
|
|
|
|
addresses. It maps the network address part, while keeping the host
|
|
|
|
|
address part intact.
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
2006-11-29 09:35:38 +08:00
|
|
|
config NETFILTER_XT_TARGET_NFLOG
|
|
|
|
|
tristate '"NFLOG" target support'
|
2007-12-18 14:47:05 +08:00
|
|
|
default m if NETFILTER_ADVANCED=n
|
2008-12-11 09:24:33 +08:00
|
|
|
select NETFILTER_NETLINK_LOG
|
2006-11-29 09:35:38 +08:00
|
|
|
help
|
|
|
|
|
This option enables the NFLOG target, which allows to LOG
|
2008-12-11 09:24:33 +08:00
|
|
|
messages through nfnetlink_log.
|
2006-11-29 09:35:38 +08:00
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
2008-10-08 17:35:17 +08:00
|
|
|
config NETFILTER_XT_TARGET_NFQUEUE
|
|
|
|
|
tristate '"NFQUEUE" target Support'
|
|
|
|
|
depends on NETFILTER_ADVANCED
|
2011-01-18 22:18:08 +08:00
|
|
|
select NETFILTER_NETLINK_QUEUE
|
2008-10-08 17:35:17 +08:00
|
|
|
help
|
|
|
|
|
This target replaced the old obsolete QUEUE target.
|
|
|
|
|
|
|
|
|
|
As opposed to QUEUE, it supports 65535 different queues,
|
|
|
|
|
not just one.
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
2007-12-05 15:40:05 +08:00
|
|
|
config NETFILTER_XT_TARGET_RATEEST
|
|
|
|
|
tristate '"RATEEST" target support'
|
2008-01-15 15:30:56 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
2007-12-05 15:40:05 +08:00
|
|
|
help
|
|
|
|
|
This option adds a `RATEEST' target, which allows to measure
|
|
|
|
|
rates similar to TC estimators. The `rateest' match can be
|
|
|
|
|
used to match on the measured rates.
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
2012-09-21 17:41:34 +08:00
|
|
|
config NETFILTER_XT_TARGET_REDIRECT
|
|
|
|
|
tristate "REDIRECT target support"
|
|
|
|
|
depends on NF_NAT
|
|
|
|
|
---help---
|
|
|
|
|
REDIRECT is a special case of NAT: all incoming connections are
|
|
|
|
|
mapped onto the incoming interface's address, causing the packets to
|
|
|
|
|
come to the local machine instead of passing through. This is
|
|
|
|
|
useful for transparent proxies.
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
2010-04-19 20:17:47 +08:00
|
|
|
config NETFILTER_XT_TARGET_TEE
|
2010-06-22 14:22:21 +08:00
|
|
|
tristate '"TEE" - packet cloning to alternate destination'
|
2010-04-19 20:17:47 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
2010-05-12 18:11:35 +08:00
|
|
|
depends on (IPV6 || IPV6=n)
|
2010-05-15 04:52:30 +08:00
|
|
|
depends on !NF_CONNTRACK || NF_CONNTRACK
|
2010-04-19 20:17:47 +08:00
|
|
|
---help---
|
|
|
|
|
This option adds a "TEE" target with which a packet can be cloned and
|
|
|
|
|
this clone be rerouted to another nexthop.
|
|
|
|
|
|
2008-10-08 17:35:12 +08:00
|
|
|
config NETFILTER_XT_TARGET_TPROXY
|
|
|
|
|
tristate '"TPROXY" target support (EXPERIMENTAL)'
|
|
|
|
|
depends on EXPERIMENTAL
|
|
|
|
|
depends on NETFILTER_TPROXY
|
|
|
|
|
depends on NETFILTER_XTABLES
|
|
|
|
|
depends on NETFILTER_ADVANCED
|
|
|
|
|
select NF_DEFRAG_IPV4
|
2010-10-25 07:38:32 +08:00
|
|
|
select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES
|
2008-10-08 17:35:12 +08:00
|
|
|
help
|
|
|
|
|
This option adds a `TPROXY' target, which is somewhat similar to
|
|
|
|
|
REDIRECT. It can only be used in the mangle table and is useful
|
|
|
|
|
to redirect traffic to a transparent proxy. It does _not_ depend
|
|
|
|
|
on Netfilter connection tracking and NAT, unlike REDIRECT.
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
2007-07-08 13:21:23 +08:00
|
|
|
config NETFILTER_XT_TARGET_TRACE
|
|
|
|
|
tristate '"TRACE" target support'
|
|
|
|
|
depends on IP_NF_RAW || IP6_NF_RAW
|
2007-12-18 14:47:05 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
2007-07-08 13:21:23 +08:00
|
|
|
help
|
|
|
|
|
The TRACE target allows you to mark packets so that the kernel
|
|
|
|
|
will log every rule which match the packets as those traverse
|
|
|
|
|
the tables, chains, rules.
|
|
|
|
|
|
|
|
|
|
If you want to compile it as a module, say M here and read
|
2007-10-31 04:37:19 +08:00
|
|
|
<file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
|
2007-07-08 13:21:23 +08:00
|
|
|
|
2006-06-09 15:30:57 +08:00
|
|
|
config NETFILTER_XT_TARGET_SECMARK
|
|
|
|
|
tristate '"SECMARK" target support'
|
2008-10-08 17:35:18 +08:00
|
|
|
depends on NETWORK_SECMARK
|
2007-12-18 14:47:05 +08:00
|
|
|
default m if NETFILTER_ADVANCED=n
|
2006-06-09 15:30:57 +08:00
|
|
|
help
|
|
|
|
|
The SECMARK target allows security marking of network
|
|
|
|
|
packets, for use with security subsystems.
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
2007-02-08 07:09:46 +08:00
|
|
|
config NETFILTER_XT_TARGET_TCPMSS
|
|
|
|
|
tristate '"TCPMSS" target support'
|
2008-10-08 17:35:18 +08:00
|
|
|
depends on (IPV6 || IPV6=n)
|
2007-12-18 14:47:05 +08:00
|
|
|
default m if NETFILTER_ADVANCED=n
|
2007-02-08 07:09:46 +08:00
|
|
|
---help---
|
|
|
|
|
This option adds a `TCPMSS' target, which allows you to alter the
|
|
|
|
|
MSS value of TCP SYN packets, to control the maximum size for that
|
|
|
|
|
connection (usually limiting it to your outgoing interface's MTU
|
|
|
|
|
minus 40).
|
|
|
|
|
|
|
|
|
|
This is used to overcome criminally braindead ISPs or servers which
|
|
|
|
|
block ICMP Fragmentation Needed packets. The symptoms of this
|
|
|
|
|
problem are that everything works fine from your Linux
|
|
|
|
|
firewall/router, but machines behind it can never exchange large
|
|
|
|
|
packets:
|
|
|
|
|
1) Web browsers connect, then hang with no data received.
|
|
|
|
|
2) Small mail works fine, but large emails hang.
|
|
|
|
|
3) ssh works fine, but scp hangs after initial handshaking.
|
|
|
|
|
|
|
|
|
|
Workaround: activate this option and add a rule to your firewall
|
|
|
|
|
configuration like:
|
|
|
|
|
|
|
|
|
|
iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN \
|
|
|
|
|
-j TCPMSS --clamp-mss-to-pmtu
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
2007-12-05 15:21:50 +08:00
|
|
|
config NETFILTER_XT_TARGET_TCPOPTSTRIP
|
|
|
|
|
tristate '"TCPOPTSTRIP" target support (EXPERIMENTAL)'
|
2008-10-08 17:35:18 +08:00
|
|
|
depends on EXPERIMENTAL
|
2007-12-05 15:21:50 +08:00
|
|
|
depends on IP_NF_MANGLE || IP6_NF_MANGLE
|
2007-12-18 14:47:05 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
2007-12-05 15:21:50 +08:00
|
|
|
help
|
|
|
|
|
This option adds a "TCPOPTSTRIP" target, which allows you to strip
|
|
|
|
|
TCP options from TCP packets.
|
|
|
|
|
|
2010-02-26 21:14:22 +08:00
|
|
|
# alphabetically ordered list of matches
|
|
|
|
|
|
|
|
|
|
comment "Xtables matches"
|
|
|
|
|
|
2011-03-16 03:16:20 +08:00
|
|
|
config NETFILTER_XT_MATCH_ADDRTYPE
|
|
|
|
|
tristate '"addrtype" address type match support'
|
|
|
|
|
depends on NETFILTER_ADVANCED
|
|
|
|
|
---help---
|
|
|
|
|
This option allows you to match what routing thinks of an address,
|
|
|
|
|
eg. UNICAST, LOCAL, BROADCAST, ...
|
|
|
|
|
|
|
|
|
|
If you want to compile it as a module, say M here and read
|
|
|
|
|
<file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
|
|
|
|
|
|
2009-03-17 00:10:36 +08:00
|
|
|
config NETFILTER_XT_MATCH_CLUSTER
|
|
|
|
|
tristate '"cluster" match support'
|
|
|
|
|
depends on NF_CONNTRACK
|
|
|
|
|
depends on NETFILTER_ADVANCED
|
|
|
|
|
---help---
|
|
|
|
|
This option allows you to build work-load-sharing clusters of
|
|
|
|
|
network servers/stateful firewalls without having a dedicated
|
|
|
|
|
load-balancing router/server/switch. Basically, this match returns
|
|
|
|
|
true when the packet must be handled by this cluster node. Thus,
|
|
|
|
|
all nodes see all packets and this match decides which node handles
|
|
|
|
|
what packets. The work-load sharing algorithm is based on source
|
|
|
|
|
address hashing.
|
|
|
|
|
|
|
|
|
|
If you say Y or M here, try `iptables -m cluster --help` for
|
|
|
|
|
more information.
|
|
|
|
|
|
[NETFILTER] x_tables: Abstraction layer for {ip,ip6,arp}_tables
This monster-patch tries to do the best job for unifying the data
structures and backend interfaces for the three evil clones ip_tables,
ip6_tables and arp_tables. In an ideal world we would never have
allowed this kind of copy+paste programming... but well, our world
isn't (yet?) ideal.
o introduce a new x_tables module
o {ip,arp,ip6}_tables depend on this x_tables module
o registration functions for tables, matches and targets are only
wrappers around x_tables provided functions
o all matches/targets that are used from ip_tables and ip6_tables
are now implemented as xt_FOOBAR.c files and provide module aliases
to ipt_FOOBAR and ip6t_FOOBAR
o header files for xt_matches are in include/linux/netfilter/,
include/linux/netfilter_{ipv4,ipv6} contains compatibility wrappers
around the xt_FOOBAR.h headers
Based on this patchset we're going to further unify the code,
gradually getting rid of all the layer 3 specific assumptions.
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-01-13 05:30:04 +08:00
|
|
|
config NETFILTER_XT_MATCH_COMMENT
|
|
|
|
|
tristate '"comment" match support'
|
2007-12-18 14:47:05 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
[NETFILTER] x_tables: Abstraction layer for {ip,ip6,arp}_tables
This monster-patch tries to do the best job for unifying the data
structures and backend interfaces for the three evil clones ip_tables,
ip6_tables and arp_tables. In an ideal world we would never have
allowed this kind of copy+paste programming... but well, our world
isn't (yet?) ideal.
o introduce a new x_tables module
o {ip,arp,ip6}_tables depend on this x_tables module
o registration functions for tables, matches and targets are only
wrappers around x_tables provided functions
o all matches/targets that are used from ip_tables and ip6_tables
are now implemented as xt_FOOBAR.c files and provide module aliases
to ipt_FOOBAR and ip6t_FOOBAR
o header files for xt_matches are in include/linux/netfilter/,
include/linux/netfilter_{ipv4,ipv6} contains compatibility wrappers
around the xt_FOOBAR.h headers
Based on this patchset we're going to further unify the code,
gradually getting rid of all the layer 3 specific assumptions.
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-01-13 05:30:04 +08:00
|
|
|
help
|
|
|
|
|
This option adds a `comment' dummy-match, which allows you to put
|
|
|
|
|
comments in your iptables ruleset.
|
|
|
|
|
|
|
|
|
|
If you want to compile it as a module, say M here and read
|
2007-03-16 21:28:43 +08:00
|
|
|
<file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
|
[NETFILTER] x_tables: Abstraction layer for {ip,ip6,arp}_tables
This monster-patch tries to do the best job for unifying the data
structures and backend interfaces for the three evil clones ip_tables,
ip6_tables and arp_tables. In an ideal world we would never have
allowed this kind of copy+paste programming... but well, our world
isn't (yet?) ideal.
o introduce a new x_tables module
o {ip,arp,ip6}_tables depend on this x_tables module
o registration functions for tables, matches and targets are only
wrappers around x_tables provided functions
o all matches/targets that are used from ip_tables and ip6_tables
are now implemented as xt_FOOBAR.c files and provide module aliases
to ipt_FOOBAR and ip6t_FOOBAR
o header files for xt_matches are in include/linux/netfilter/,
include/linux/netfilter_{ipv4,ipv6} contains compatibility wrappers
around the xt_FOOBAR.h headers
Based on this patchset we're going to further unify the code,
gradually getting rid of all the layer 3 specific assumptions.
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-01-13 05:30:04 +08:00
|
|
|
|
|
|
|
|
config NETFILTER_XT_MATCH_CONNBYTES
|
|
|
|
|
tristate '"connbytes" per-connection counter match support'
|
2007-03-15 07:37:25 +08:00
|
|
|
depends on NF_CONNTRACK
|
2007-12-18 14:47:05 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
[NETFILTER] x_tables: Abstraction layer for {ip,ip6,arp}_tables
This monster-patch tries to do the best job for unifying the data
structures and backend interfaces for the three evil clones ip_tables,
ip6_tables and arp_tables. In an ideal world we would never have
allowed this kind of copy+paste programming... but well, our world
isn't (yet?) ideal.
o introduce a new x_tables module
o {ip,arp,ip6}_tables depend on this x_tables module
o registration functions for tables, matches and targets are only
wrappers around x_tables provided functions
o all matches/targets that are used from ip_tables and ip6_tables
are now implemented as xt_FOOBAR.c files and provide module aliases
to ipt_FOOBAR and ip6t_FOOBAR
o header files for xt_matches are in include/linux/netfilter/,
include/linux/netfilter_{ipv4,ipv6} contains compatibility wrappers
around the xt_FOOBAR.h headers
Based on this patchset we're going to further unify the code,
gradually getting rid of all the layer 3 specific assumptions.
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-01-13 05:30:04 +08:00
|
|
|
help
|
|
|
|
|
This option adds a `connbytes' match, which allows you to match the
|
|
|
|
|
number of bytes and/or packets for each direction within a connection.
|
|
|
|
|
|
|
|
|
|
If you want to compile it as a module, say M here and read
|
2007-03-16 21:28:43 +08:00
|
|
|
<file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
|
[NETFILTER] x_tables: Abstraction layer for {ip,ip6,arp}_tables
This monster-patch tries to do the best job for unifying the data
structures and backend interfaces for the three evil clones ip_tables,
ip6_tables and arp_tables. In an ideal world we would never have
allowed this kind of copy+paste programming... but well, our world
isn't (yet?) ideal.
o introduce a new x_tables module
o {ip,arp,ip6}_tables depend on this x_tables module
o registration functions for tables, matches and targets are only
wrappers around x_tables provided functions
o all matches/targets that are used from ip_tables and ip6_tables
are now implemented as xt_FOOBAR.c files and provide module aliases
to ipt_FOOBAR and ip6t_FOOBAR
o header files for xt_matches are in include/linux/netfilter/,
include/linux/netfilter_{ipv4,ipv6} contains compatibility wrappers
around the xt_FOOBAR.h headers
Based on this patchset we're going to further unify the code,
gradually getting rid of all the layer 3 specific assumptions.
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-01-13 05:30:04 +08:00
|
|
|
|
2007-07-15 11:47:26 +08:00
|
|
|
config NETFILTER_XT_MATCH_CONNLIMIT
|
|
|
|
|
tristate '"connlimit" match support"'
|
2007-07-18 17:38:32 +08:00
|
|
|
depends on NF_CONNTRACK
|
2007-12-18 14:47:05 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
2007-07-15 11:47:26 +08:00
|
|
|
---help---
|
|
|
|
|
This match allows you to match against the number of parallel
|
|
|
|
|
connections to a server per client IP address (or address block).
|
|
|
|
|
|
[NETFILTER] x_tables: Abstraction layer for {ip,ip6,arp}_tables
This monster-patch tries to do the best job for unifying the data
structures and backend interfaces for the three evil clones ip_tables,
ip6_tables and arp_tables. In an ideal world we would never have
allowed this kind of copy+paste programming... but well, our world
isn't (yet?) ideal.
o introduce a new x_tables module
o {ip,arp,ip6}_tables depend on this x_tables module
o registration functions for tables, matches and targets are only
wrappers around x_tables provided functions
o all matches/targets that are used from ip_tables and ip6_tables
are now implemented as xt_FOOBAR.c files and provide module aliases
to ipt_FOOBAR and ip6t_FOOBAR
o header files for xt_matches are in include/linux/netfilter/,
include/linux/netfilter_{ipv4,ipv6} contains compatibility wrappers
around the xt_FOOBAR.h headers
Based on this patchset we're going to further unify the code,
gradually getting rid of all the layer 3 specific assumptions.
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-01-13 05:30:04 +08:00
|
|
|
config NETFILTER_XT_MATCH_CONNMARK
|
|
|
|
|
tristate '"connmark" connection mark match support'
|
2007-03-15 07:37:25 +08:00
|
|
|
depends on NF_CONNTRACK
|
2007-12-18 14:47:05 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
2010-02-26 21:20:32 +08:00
|
|
|
select NETFILTER_XT_CONNMARK
|
|
|
|
|
---help---
|
|
|
|
|
This is a backwards-compat option for the user's convenience
|
|
|
|
|
(e.g. when running oldconfig). It selects
|
|
|
|
|
CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
|
[NETFILTER] x_tables: Abstraction layer for {ip,ip6,arp}_tables
This monster-patch tries to do the best job for unifying the data
structures and backend interfaces for the three evil clones ip_tables,
ip6_tables and arp_tables. In an ideal world we would never have
allowed this kind of copy+paste programming... but well, our world
isn't (yet?) ideal.
o introduce a new x_tables module
o {ip,arp,ip6}_tables depend on this x_tables module
o registration functions for tables, matches and targets are only
wrappers around x_tables provided functions
o all matches/targets that are used from ip_tables and ip6_tables
are now implemented as xt_FOOBAR.c files and provide module aliases
to ipt_FOOBAR and ip6t_FOOBAR
o header files for xt_matches are in include/linux/netfilter/,
include/linux/netfilter_{ipv4,ipv6} contains compatibility wrappers
around the xt_FOOBAR.h headers
Based on this patchset we're going to further unify the code,
gradually getting rid of all the layer 3 specific assumptions.
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-01-13 05:30:04 +08:00
|
|
|
|
|
|
|
|
config NETFILTER_XT_MATCH_CONNTRACK
|
|
|
|
|
tristate '"conntrack" connection tracking match support'
|
2007-03-15 07:37:25 +08:00
|
|
|
depends on NF_CONNTRACK
|
2007-12-18 14:47:05 +08:00
|
|
|
default m if NETFILTER_ADVANCED=n
|
[NETFILTER] x_tables: Abstraction layer for {ip,ip6,arp}_tables
This monster-patch tries to do the best job for unifying the data
structures and backend interfaces for the three evil clones ip_tables,
ip6_tables and arp_tables. In an ideal world we would never have
allowed this kind of copy+paste programming... but well, our world
isn't (yet?) ideal.
o introduce a new x_tables module
o {ip,arp,ip6}_tables depend on this x_tables module
o registration functions for tables, matches and targets are only
wrappers around x_tables provided functions
o all matches/targets that are used from ip_tables and ip6_tables
are now implemented as xt_FOOBAR.c files and provide module aliases
to ipt_FOOBAR and ip6t_FOOBAR
o header files for xt_matches are in include/linux/netfilter/,
include/linux/netfilter_{ipv4,ipv6} contains compatibility wrappers
around the xt_FOOBAR.h headers
Based on this patchset we're going to further unify the code,
gradually getting rid of all the layer 3 specific assumptions.
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-01-13 05:30:04 +08:00
|
|
|
help
|
|
|
|
|
This is a general conntrack match module, a superset of the state match.
|
|
|
|
|
|
|
|
|
|
It allows matching on additional conntrack information, which is
|
|
|
|
|
useful in complex configurations, such as NAT gateways with multiple
|
|
|
|
|
internet links or tunnels.
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
2010-07-23 18:59:36 +08:00
|
|
|
|
|
|
|
|
config NETFILTER_XT_MATCH_CPU
|
|
|
|
|
tristate '"cpu" match support'
|
|
|
|
|
depends on NETFILTER_ADVANCED
|
|
|
|
|
help
|
|
|
|
|
CPU matching allows you to match packets based on the CPU
|
|
|
|
|
currently handling the packet.
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
[NETFILTER] x_tables: Abstraction layer for {ip,ip6,arp}_tables
This monster-patch tries to do the best job for unifying the data
structures and backend interfaces for the three evil clones ip_tables,
ip6_tables and arp_tables. In an ideal world we would never have
allowed this kind of copy+paste programming... but well, our world
isn't (yet?) ideal.
o introduce a new x_tables module
o {ip,arp,ip6}_tables depend on this x_tables module
o registration functions for tables, matches and targets are only
wrappers around x_tables provided functions
o all matches/targets that are used from ip_tables and ip6_tables
are now implemented as xt_FOOBAR.c files and provide module aliases
to ipt_FOOBAR and ip6t_FOOBAR
o header files for xt_matches are in include/linux/netfilter/,
include/linux/netfilter_{ipv4,ipv6} contains compatibility wrappers
around the xt_FOOBAR.h headers
Based on this patchset we're going to further unify the code,
gradually getting rid of all the layer 3 specific assumptions.
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-01-13 05:30:04 +08:00
|
|
|
|
|
|
|
|
config NETFILTER_XT_MATCH_DCCP
|
2007-12-05 15:31:59 +08:00
|
|
|
tristate '"dccp" protocol match support'
|
2007-12-18 14:47:05 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
2008-05-08 16:16:04 +08:00
|
|
|
default IP_DCCP
|
[NETFILTER] x_tables: Abstraction layer for {ip,ip6,arp}_tables
This monster-patch tries to do the best job for unifying the data
structures and backend interfaces for the three evil clones ip_tables,
ip6_tables and arp_tables. In an ideal world we would never have
allowed this kind of copy+paste programming... but well, our world
isn't (yet?) ideal.
o introduce a new x_tables module
o {ip,arp,ip6}_tables depend on this x_tables module
o registration functions for tables, matches and targets are only
wrappers around x_tables provided functions
o all matches/targets that are used from ip_tables and ip6_tables
are now implemented as xt_FOOBAR.c files and provide module aliases
to ipt_FOOBAR and ip6t_FOOBAR
o header files for xt_matches are in include/linux/netfilter/,
include/linux/netfilter_{ipv4,ipv6} contains compatibility wrappers
around the xt_FOOBAR.h headers
Based on this patchset we're going to further unify the code,
gradually getting rid of all the layer 3 specific assumptions.
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-01-13 05:30:04 +08:00
|
|
|
help
|
|
|
|
|
With this option enabled, you will be able to use the iptables
|
|
|
|
|
`dccp' match in order to match on DCCP source/destination ports
|
|
|
|
|
and DCCP flags.
|
|
|
|
|
|
|
|
|
|
If you want to compile it as a module, say M here and read
|
2007-03-16 21:28:43 +08:00
|
|
|
<file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
|
[NETFILTER] x_tables: Abstraction layer for {ip,ip6,arp}_tables
This monster-patch tries to do the best job for unifying the data
structures and backend interfaces for the three evil clones ip_tables,
ip6_tables and arp_tables. In an ideal world we would never have
allowed this kind of copy+paste programming... but well, our world
isn't (yet?) ideal.
o introduce a new x_tables module
o {ip,arp,ip6}_tables depend on this x_tables module
o registration functions for tables, matches and targets are only
wrappers around x_tables provided functions
o all matches/targets that are used from ip_tables and ip6_tables
are now implemented as xt_FOOBAR.c files and provide module aliases
to ipt_FOOBAR and ip6t_FOOBAR
o header files for xt_matches are in include/linux/netfilter/,
include/linux/netfilter_{ipv4,ipv6} contains compatibility wrappers
around the xt_FOOBAR.h headers
Based on this patchset we're going to further unify the code,
gradually getting rid of all the layer 3 specific assumptions.
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-01-13 05:30:04 +08:00
|
|
|
|
2011-02-03 07:05:43 +08:00
|
|
|
config NETFILTER_XT_MATCH_DEVGROUP
|
|
|
|
|
tristate '"devgroup" match support'
|
|
|
|
|
depends on NETFILTER_ADVANCED
|
|
|
|
|
help
|
|
|
|
|
This options adds a `devgroup' match, which allows to match on the
|
|
|
|
|
device group a network device is assigned to.
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
2006-08-22 15:29:37 +08:00
|
|
|
config NETFILTER_XT_MATCH_DSCP
|
2007-12-05 15:37:54 +08:00
|
|
|
tristate '"dscp" and "tos" match support'
|
2007-12-18 14:47:05 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
2006-08-22 15:29:37 +08:00
|
|
|
help
|
|
|
|
|
This option adds a `DSCP' match, which allows you to match against
|
|
|
|
|
the IPv4/IPv6 header DSCP field (differentiated services codepoint).
|
|
|
|
|
|
|
|
|
|
The DSCP field can have any value between 0x0 and 0x3f inclusive.
|
|
|
|
|
|
2007-12-05 15:37:54 +08:00
|
|
|
It will also add a "tos" match, which allows you to match packets
|
|
|
|
|
based on the Type Of Service fields of the IPv4 packet (which share
|
|
|
|
|
the same bits as DSCP).
|
|
|
|
|
|
2006-08-22 15:29:37 +08:00
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
2011-06-10 03:03:07 +08:00
|
|
|
config NETFILTER_XT_MATCH_ECN
|
|
|
|
|
tristate '"ecn" match support'
|
|
|
|
|
depends on NETFILTER_ADVANCED
|
|
|
|
|
---help---
|
|
|
|
|
This option adds an "ECN" match, which allows you to match against
|
|
|
|
|
the IPv4 and TCP header ECN fields.
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
2006-04-01 18:22:30 +08:00
|
|
|
config NETFILTER_XT_MATCH_ESP
|
2007-12-05 15:31:59 +08:00
|
|
|
tristate '"esp" match support'
|
2007-12-18 14:47:05 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
2006-04-01 18:22:30 +08:00
|
|
|
help
|
|
|
|
|
This match extension allows you to match a range of SPIs
|
|
|
|
|
inside ESP header of IPSec packets.
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
2008-10-08 17:35:17 +08:00
|
|
|
config NETFILTER_XT_MATCH_HASHLIMIT
|
|
|
|
|
tristate '"hashlimit" match support'
|
2008-10-08 17:35:18 +08:00
|
|
|
depends on (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
|
2008-10-08 17:35:17 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
|
|
|
|
help
|
|
|
|
|
This option adds a `hashlimit' match.
|
|
|
|
|
|
|
|
|
|
As opposed to `limit', this match dynamically creates a hash table
|
|
|
|
|
of limit buckets, based on your selection of source/destination
|
|
|
|
|
addresses and/or ports.
|
|
|
|
|
|
|
|
|
|
It enables you to express policies like `10kpps for any given
|
|
|
|
|
destination address' or `500pps from any given source address'
|
|
|
|
|
with a single rule.
|
|
|
|
|
|
[NETFILTER] x_tables: Abstraction layer for {ip,ip6,arp}_tables
This monster-patch tries to do the best job for unifying the data
structures and backend interfaces for the three evil clones ip_tables,
ip6_tables and arp_tables. In an ideal world we would never have
allowed this kind of copy+paste programming... but well, our world
isn't (yet?) ideal.
o introduce a new x_tables module
o {ip,arp,ip6}_tables depend on this x_tables module
o registration functions for tables, matches and targets are only
wrappers around x_tables provided functions
o all matches/targets that are used from ip_tables and ip6_tables
are now implemented as xt_FOOBAR.c files and provide module aliases
to ipt_FOOBAR and ip6t_FOOBAR
o header files for xt_matches are in include/linux/netfilter/,
include/linux/netfilter_{ipv4,ipv6} contains compatibility wrappers
around the xt_FOOBAR.h headers
Based on this patchset we're going to further unify the code,
gradually getting rid of all the layer 3 specific assumptions.
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-01-13 05:30:04 +08:00
|
|
|
config NETFILTER_XT_MATCH_HELPER
|
|
|
|
|
tristate '"helper" match support'
|
2007-03-15 07:37:25 +08:00
|
|
|
depends on NF_CONNTRACK
|
2007-12-18 14:47:05 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
[NETFILTER] x_tables: Abstraction layer for {ip,ip6,arp}_tables
This monster-patch tries to do the best job for unifying the data
structures and backend interfaces for the three evil clones ip_tables,
ip6_tables and arp_tables. In an ideal world we would never have
allowed this kind of copy+paste programming... but well, our world
isn't (yet?) ideal.
o introduce a new x_tables module
o {ip,arp,ip6}_tables depend on this x_tables module
o registration functions for tables, matches and targets are only
wrappers around x_tables provided functions
o all matches/targets that are used from ip_tables and ip6_tables
are now implemented as xt_FOOBAR.c files and provide module aliases
to ipt_FOOBAR and ip6t_FOOBAR
o header files for xt_matches are in include/linux/netfilter/,
include/linux/netfilter_{ipv4,ipv6} contains compatibility wrappers
around the xt_FOOBAR.h headers
Based on this patchset we're going to further unify the code,
gradually getting rid of all the layer 3 specific assumptions.
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-01-13 05:30:04 +08:00
|
|
|
help
|
|
|
|
|
Helper matching allows you to match packets in dynamic connections
|
|
|
|
|
tracked by a conntrack-helper, ie. ip_conntrack_ftp
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say Y.
|
|
|
|
|
|
2009-02-19 01:39:31 +08:00
|
|
|
config NETFILTER_XT_MATCH_HL
|
|
|
|
|
tristate '"hl" hoplimit/TTL match support'
|
|
|
|
|
depends on NETFILTER_ADVANCED
|
|
|
|
|
---help---
|
|
|
|
|
HL matching allows you to match packets based on the hoplimit
|
|
|
|
|
in the IPv6 header, or the time-to-live field in the IPv4
|
|
|
|
|
header of the packet.
|
|
|
|
|
|
2008-01-15 15:42:47 +08:00
|
|
|
config NETFILTER_XT_MATCH_IPRANGE
|
|
|
|
|
tristate '"iprange" address range match support'
|
|
|
|
|
depends on NETFILTER_ADVANCED
|
|
|
|
|
---help---
|
|
|
|
|
This option adds a "iprange" match, which allows you to match based on
|
|
|
|
|
an IP address range. (Normal iptables only matches on single addresses
|
|
|
|
|
with an optional mask.)
|
|
|
|
|
|
|
|
|
|
If unsure, say M.
|
|
|
|
|
|
2010-07-23 18:42:58 +08:00
|
|
|
config NETFILTER_XT_MATCH_IPVS
|
|
|
|
|
tristate '"ipvs" match support'
|
|
|
|
|
depends on IP_VS
|
|
|
|
|
depends on NETFILTER_ADVANCED
|
|
|
|
|
depends on NF_CONNTRACK
|
|
|
|
|
help
|
|
|
|
|
This option allows you to match against IPVS properties of a packet.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
[NETFILTER] x_tables: Abstraction layer for {ip,ip6,arp}_tables
This monster-patch tries to do the best job for unifying the data
structures and backend interfaces for the three evil clones ip_tables,
ip6_tables and arp_tables. In an ideal world we would never have
allowed this kind of copy+paste programming... but well, our world
isn't (yet?) ideal.
o introduce a new x_tables module
o {ip,arp,ip6}_tables depend on this x_tables module
o registration functions for tables, matches and targets are only
wrappers around x_tables provided functions
o all matches/targets that are used from ip_tables and ip6_tables
are now implemented as xt_FOOBAR.c files and provide module aliases
to ipt_FOOBAR and ip6t_FOOBAR
o header files for xt_matches are in include/linux/netfilter/,
include/linux/netfilter_{ipv4,ipv6} contains compatibility wrappers
around the xt_FOOBAR.h headers
Based on this patchset we're going to further unify the code,
gradually getting rid of all the layer 3 specific assumptions.
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-01-13 05:30:04 +08:00
|
|
|
config NETFILTER_XT_MATCH_LENGTH
|
|
|
|
|
tristate '"length" match support'
|
2007-12-18 14:47:05 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
[NETFILTER] x_tables: Abstraction layer for {ip,ip6,arp}_tables
This monster-patch tries to do the best job for unifying the data
structures and backend interfaces for the three evil clones ip_tables,
ip6_tables and arp_tables. In an ideal world we would never have
allowed this kind of copy+paste programming... but well, our world
isn't (yet?) ideal.
o introduce a new x_tables module
o {ip,arp,ip6}_tables depend on this x_tables module
o registration functions for tables, matches and targets are only
wrappers around x_tables provided functions
o all matches/targets that are used from ip_tables and ip6_tables
are now implemented as xt_FOOBAR.c files and provide module aliases
to ipt_FOOBAR and ip6t_FOOBAR
o header files for xt_matches are in include/linux/netfilter/,
include/linux/netfilter_{ipv4,ipv6} contains compatibility wrappers
around the xt_FOOBAR.h headers
Based on this patchset we're going to further unify the code,
gradually getting rid of all the layer 3 specific assumptions.
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-01-13 05:30:04 +08:00
|
|
|
help
|
|
|
|
|
This option allows you to match the length of a packet against a
|
|
|
|
|
specific value or range of values.
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
|
|
|
|
config NETFILTER_XT_MATCH_LIMIT
|
|
|
|
|
tristate '"limit" match support'
|
2007-12-18 14:47:05 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
[NETFILTER] x_tables: Abstraction layer for {ip,ip6,arp}_tables
This monster-patch tries to do the best job for unifying the data
structures and backend interfaces for the three evil clones ip_tables,
ip6_tables and arp_tables. In an ideal world we would never have
allowed this kind of copy+paste programming... but well, our world
isn't (yet?) ideal.
o introduce a new x_tables module
o {ip,arp,ip6}_tables depend on this x_tables module
o registration functions for tables, matches and targets are only
wrappers around x_tables provided functions
o all matches/targets that are used from ip_tables and ip6_tables
are now implemented as xt_FOOBAR.c files and provide module aliases
to ipt_FOOBAR and ip6t_FOOBAR
o header files for xt_matches are in include/linux/netfilter/,
include/linux/netfilter_{ipv4,ipv6} contains compatibility wrappers
around the xt_FOOBAR.h headers
Based on this patchset we're going to further unify the code,
gradually getting rid of all the layer 3 specific assumptions.
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-01-13 05:30:04 +08:00
|
|
|
help
|
|
|
|
|
limit matching allows you to control the rate at which a rule can be
|
|
|
|
|
matched: mainly useful in combination with the LOG target ("LOG
|
|
|
|
|
target support", below) and to avoid some Denial of Service attacks.
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
|
|
|
|
config NETFILTER_XT_MATCH_MAC
|
|
|
|
|
tristate '"mac" address match support'
|
2007-12-18 14:47:05 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
[NETFILTER] x_tables: Abstraction layer for {ip,ip6,arp}_tables
This monster-patch tries to do the best job for unifying the data
structures and backend interfaces for the three evil clones ip_tables,
ip6_tables and arp_tables. In an ideal world we would never have
allowed this kind of copy+paste programming... but well, our world
isn't (yet?) ideal.
o introduce a new x_tables module
o {ip,arp,ip6}_tables depend on this x_tables module
o registration functions for tables, matches and targets are only
wrappers around x_tables provided functions
o all matches/targets that are used from ip_tables and ip6_tables
are now implemented as xt_FOOBAR.c files and provide module aliases
to ipt_FOOBAR and ip6t_FOOBAR
o header files for xt_matches are in include/linux/netfilter/,
include/linux/netfilter_{ipv4,ipv6} contains compatibility wrappers
around the xt_FOOBAR.h headers
Based on this patchset we're going to further unify the code,
gradually getting rid of all the layer 3 specific assumptions.
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-01-13 05:30:04 +08:00
|
|
|
help
|
|
|
|
|
MAC matching allows you to match packets based on the source
|
|
|
|
|
Ethernet address of the packet.
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
|
|
|
|
config NETFILTER_XT_MATCH_MARK
|
|
|
|
|
tristate '"mark" match support'
|
2009-02-28 10:23:57 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
|
|
|
|
select NETFILTER_XT_MARK
|
|
|
|
|
---help---
|
|
|
|
|
This is a backwards-compat option for the user's convenience
|
|
|
|
|
(e.g. when running oldconfig). It selects
|
|
|
|
|
CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
|
[NETFILTER] x_tables: Abstraction layer for {ip,ip6,arp}_tables
This monster-patch tries to do the best job for unifying the data
structures and backend interfaces for the three evil clones ip_tables,
ip6_tables and arp_tables. In an ideal world we would never have
allowed this kind of copy+paste programming... but well, our world
isn't (yet?) ideal.
o introduce a new x_tables module
o {ip,arp,ip6}_tables depend on this x_tables module
o registration functions for tables, matches and targets are only
wrappers around x_tables provided functions
o all matches/targets that are used from ip_tables and ip6_tables
are now implemented as xt_FOOBAR.c files and provide module aliases
to ipt_FOOBAR and ip6t_FOOBAR
o header files for xt_matches are in include/linux/netfilter/,
include/linux/netfilter_{ipv4,ipv6} contains compatibility wrappers
around the xt_FOOBAR.h headers
Based on this patchset we're going to further unify the code,
gradually getting rid of all the layer 3 specific assumptions.
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-01-13 05:30:04 +08:00
|
|
|
|
2008-10-08 17:35:17 +08:00
|
|
|
config NETFILTER_XT_MATCH_MULTIPORT
|
|
|
|
|
tristate '"multiport" Multiple port match support'
|
|
|
|
|
depends on NETFILTER_ADVANCED
|
|
|
|
|
help
|
|
|
|
|
Multiport matching allows you to match TCP or UDP packets based on
|
|
|
|
|
a series of source or destination ports: normally a rule can only
|
|
|
|
|
match a single range of ports.
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
2011-12-23 21:28:59 +08:00
|
|
|
config NETFILTER_XT_MATCH_NFACCT
|
|
|
|
|
tristate '"nfacct" match support'
|
2011-12-28 23:03:30 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
2011-12-23 21:28:59 +08:00
|
|
|
select NETFILTER_NETLINK_ACCT
|
|
|
|
|
help
|
|
|
|
|
This option allows you to use the extended accounting through
|
|
|
|
|
nfnetlink_acct.
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
2010-03-17 03:06:55 +08:00
|
|
|
config NETFILTER_XT_MATCH_OSF
|
|
|
|
|
tristate '"osf" Passive OS fingerprint match'
|
|
|
|
|
depends on NETFILTER_ADVANCED && NETFILTER_NETLINK
|
|
|
|
|
help
|
|
|
|
|
This option selects the Passive OS Fingerprinting match module
|
|
|
|
|
that allows to passively match the remote operating system by
|
|
|
|
|
analyzing incoming TCP SYN packets.
|
|
|
|
|
|
|
|
|
|
Rules and loading software can be downloaded from
|
|
|
|
|
http://www.ioremap.net/projects/osf
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
2007-12-05 15:27:38 +08:00
|
|
|
config NETFILTER_XT_MATCH_OWNER
|
|
|
|
|
tristate '"owner" match support'
|
2007-12-18 14:47:05 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
2007-12-05 15:27:38 +08:00
|
|
|
---help---
|
|
|
|
|
Socket owner matching allows you to match locally-generated packets
|
|
|
|
|
based on who created the socket: the user or group. It is also
|
|
|
|
|
possible to check whether a socket actually exists.
|
|
|
|
|
|
2006-03-21 10:03:40 +08:00
|
|
|
config NETFILTER_XT_MATCH_POLICY
|
|
|
|
|
tristate 'IPsec "policy" match support'
|
2008-10-08 17:35:18 +08:00
|
|
|
depends on XFRM
|
2007-12-18 14:47:05 +08:00
|
|
|
default m if NETFILTER_ADVANCED=n
|
2006-03-21 10:03:40 +08:00
|
|
|
help
|
|
|
|
|
Policy matching allows you to match packets based on the
|
|
|
|
|
IPsec policy that was used during decapsulation/will
|
|
|
|
|
be used during encapsulation.
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
[NETFILTER] x_tables: Abstraction layer for {ip,ip6,arp}_tables
This monster-patch tries to do the best job for unifying the data
structures and backend interfaces for the three evil clones ip_tables,
ip6_tables and arp_tables. In an ideal world we would never have
allowed this kind of copy+paste programming... but well, our world
isn't (yet?) ideal.
o introduce a new x_tables module
o {ip,arp,ip6}_tables depend on this x_tables module
o registration functions for tables, matches and targets are only
wrappers around x_tables provided functions
o all matches/targets that are used from ip_tables and ip6_tables
are now implemented as xt_FOOBAR.c files and provide module aliases
to ipt_FOOBAR and ip6t_FOOBAR
o header files for xt_matches are in include/linux/netfilter/,
include/linux/netfilter_{ipv4,ipv6} contains compatibility wrappers
around the xt_FOOBAR.h headers
Based on this patchset we're going to further unify the code,
gradually getting rid of all the layer 3 specific assumptions.
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-01-13 05:30:04 +08:00
|
|
|
config NETFILTER_XT_MATCH_PHYSDEV
|
|
|
|
|
tristate '"physdev" match support'
|
2008-10-08 17:35:18 +08:00
|
|
|
depends on BRIDGE && BRIDGE_NETFILTER
|
2007-12-18 14:47:05 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
[NETFILTER] x_tables: Abstraction layer for {ip,ip6,arp}_tables
This monster-patch tries to do the best job for unifying the data
structures and backend interfaces for the three evil clones ip_tables,
ip6_tables and arp_tables. In an ideal world we would never have
allowed this kind of copy+paste programming... but well, our world
isn't (yet?) ideal.
o introduce a new x_tables module
o {ip,arp,ip6}_tables depend on this x_tables module
o registration functions for tables, matches and targets are only
wrappers around x_tables provided functions
o all matches/targets that are used from ip_tables and ip6_tables
are now implemented as xt_FOOBAR.c files and provide module aliases
to ipt_FOOBAR and ip6t_FOOBAR
o header files for xt_matches are in include/linux/netfilter/,
include/linux/netfilter_{ipv4,ipv6} contains compatibility wrappers
around the xt_FOOBAR.h headers
Based on this patchset we're going to further unify the code,
gradually getting rid of all the layer 3 specific assumptions.
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-01-13 05:30:04 +08:00
|
|
|
help
|
|
|
|
|
Physdev packet matching matches against the physical bridge ports
|
|
|
|
|
the IP packet arrived on or will leave by.
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
|
|
|
|
config NETFILTER_XT_MATCH_PKTTYPE
|
|
|
|
|
tristate '"pkttype" packet type match support'
|
2007-12-18 14:47:05 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
[NETFILTER] x_tables: Abstraction layer for {ip,ip6,arp}_tables
This monster-patch tries to do the best job for unifying the data
structures and backend interfaces for the three evil clones ip_tables,
ip6_tables and arp_tables. In an ideal world we would never have
allowed this kind of copy+paste programming... but well, our world
isn't (yet?) ideal.
o introduce a new x_tables module
o {ip,arp,ip6}_tables depend on this x_tables module
o registration functions for tables, matches and targets are only
wrappers around x_tables provided functions
o all matches/targets that are used from ip_tables and ip6_tables
are now implemented as xt_FOOBAR.c files and provide module aliases
to ipt_FOOBAR and ip6t_FOOBAR
o header files for xt_matches are in include/linux/netfilter/,
include/linux/netfilter_{ipv4,ipv6} contains compatibility wrappers
around the xt_FOOBAR.h headers
Based on this patchset we're going to further unify the code,
gradually getting rid of all the layer 3 specific assumptions.
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-01-13 05:30:04 +08:00
|
|
|
help
|
|
|
|
|
Packet type matching allows you to match a packet by
|
|
|
|
|
its "class", eg. BROADCAST, MULTICAST, ...
|
|
|
|
|
|
|
|
|
|
Typical usage:
|
|
|
|
|
iptables -A INPUT -m pkttype --pkt-type broadcast -j LOG
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
2006-05-30 09:20:32 +08:00
|
|
|
config NETFILTER_XT_MATCH_QUOTA
|
|
|
|
|
tristate '"quota" match support'
|
2007-12-18 14:47:05 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
2006-05-30 09:20:32 +08:00
|
|
|
help
|
|
|
|
|
This option adds a `quota' match, which allows to match on a
|
|
|
|
|
byte counter.
|
|
|
|
|
|
|
|
|
|
If you want to compile it as a module, say M here and read
|
2007-03-16 21:28:43 +08:00
|
|
|
<file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
|
2006-05-30 09:20:32 +08:00
|
|
|
|
2007-12-04 20:02:19 +08:00
|
|
|
config NETFILTER_XT_MATCH_RATEEST
|
|
|
|
|
tristate '"rateest" match support'
|
2008-01-15 15:30:56 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
2007-12-04 20:02:19 +08:00
|
|
|
select NETFILTER_XT_TARGET_RATEEST
|
|
|
|
|
help
|
|
|
|
|
This option adds a `rateest' match, which allows to match on the
|
|
|
|
|
rate estimated by the RATEEST target.
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
[NETFILTER] x_tables: Abstraction layer for {ip,ip6,arp}_tables
This monster-patch tries to do the best job for unifying the data
structures and backend interfaces for the three evil clones ip_tables,
ip6_tables and arp_tables. In an ideal world we would never have
allowed this kind of copy+paste programming... but well, our world
isn't (yet?) ideal.
o introduce a new x_tables module
o {ip,arp,ip6}_tables depend on this x_tables module
o registration functions for tables, matches and targets are only
wrappers around x_tables provided functions
o all matches/targets that are used from ip_tables and ip6_tables
are now implemented as xt_FOOBAR.c files and provide module aliases
to ipt_FOOBAR and ip6t_FOOBAR
o header files for xt_matches are in include/linux/netfilter/,
include/linux/netfilter_{ipv4,ipv6} contains compatibility wrappers
around the xt_FOOBAR.h headers
Based on this patchset we're going to further unify the code,
gradually getting rid of all the layer 3 specific assumptions.
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-01-13 05:30:04 +08:00
|
|
|
config NETFILTER_XT_MATCH_REALM
|
|
|
|
|
tristate '"realm" match support'
|
2007-12-18 14:47:05 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
2011-01-14 20:36:42 +08:00
|
|
|
select IP_ROUTE_CLASSID
|
[NETFILTER] x_tables: Abstraction layer for {ip,ip6,arp}_tables
This monster-patch tries to do the best job for unifying the data
structures and backend interfaces for the three evil clones ip_tables,
ip6_tables and arp_tables. In an ideal world we would never have
allowed this kind of copy+paste programming... but well, our world
isn't (yet?) ideal.
o introduce a new x_tables module
o {ip,arp,ip6}_tables depend on this x_tables module
o registration functions for tables, matches and targets are only
wrappers around x_tables provided functions
o all matches/targets that are used from ip_tables and ip6_tables
are now implemented as xt_FOOBAR.c files and provide module aliases
to ipt_FOOBAR and ip6t_FOOBAR
o header files for xt_matches are in include/linux/netfilter/,
include/linux/netfilter_{ipv4,ipv6} contains compatibility wrappers
around the xt_FOOBAR.h headers
Based on this patchset we're going to further unify the code,
gradually getting rid of all the layer 3 specific assumptions.
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-01-13 05:30:04 +08:00
|
|
|
help
|
|
|
|
|
This option adds a `realm' match, which allows you to use the realm
|
|
|
|
|
key from the routing subsystem inside iptables.
|
2007-12-18 14:47:05 +08:00
|
|
|
|
[NETFILTER] x_tables: Abstraction layer for {ip,ip6,arp}_tables
This monster-patch tries to do the best job for unifying the data
structures and backend interfaces for the three evil clones ip_tables,
ip6_tables and arp_tables. In an ideal world we would never have
allowed this kind of copy+paste programming... but well, our world
isn't (yet?) ideal.
o introduce a new x_tables module
o {ip,arp,ip6}_tables depend on this x_tables module
o registration functions for tables, matches and targets are only
wrappers around x_tables provided functions
o all matches/targets that are used from ip_tables and ip6_tables
are now implemented as xt_FOOBAR.c files and provide module aliases
to ipt_FOOBAR and ip6t_FOOBAR
o header files for xt_matches are in include/linux/netfilter/,
include/linux/netfilter_{ipv4,ipv6} contains compatibility wrappers
around the xt_FOOBAR.h headers
Based on this patchset we're going to further unify the code,
gradually getting rid of all the layer 3 specific assumptions.
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-01-13 05:30:04 +08:00
|
|
|
This match pretty much resembles the CONFIG_NET_CLS_ROUTE4 option
|
|
|
|
|
in tc world.
|
2007-12-18 14:47:05 +08:00
|
|
|
|
[NETFILTER] x_tables: Abstraction layer for {ip,ip6,arp}_tables
This monster-patch tries to do the best job for unifying the data
structures and backend interfaces for the three evil clones ip_tables,
ip6_tables and arp_tables. In an ideal world we would never have
allowed this kind of copy+paste programming... but well, our world
isn't (yet?) ideal.
o introduce a new x_tables module
o {ip,arp,ip6}_tables depend on this x_tables module
o registration functions for tables, matches and targets are only
wrappers around x_tables provided functions
o all matches/targets that are used from ip_tables and ip6_tables
are now implemented as xt_FOOBAR.c files and provide module aliases
to ipt_FOOBAR and ip6t_FOOBAR
o header files for xt_matches are in include/linux/netfilter/,
include/linux/netfilter_{ipv4,ipv6} contains compatibility wrappers
around the xt_FOOBAR.h headers
Based on this patchset we're going to further unify the code,
gradually getting rid of all the layer 3 specific assumptions.
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-01-13 05:30:04 +08:00
|
|
|
If you want to compile it as a module, say M here and read
|
2007-03-16 21:28:43 +08:00
|
|
|
<file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
|
[NETFILTER] x_tables: Abstraction layer for {ip,ip6,arp}_tables
This monster-patch tries to do the best job for unifying the data
structures and backend interfaces for the three evil clones ip_tables,
ip6_tables and arp_tables. In an ideal world we would never have
allowed this kind of copy+paste programming... but well, our world
isn't (yet?) ideal.
o introduce a new x_tables module
o {ip,arp,ip6}_tables depend on this x_tables module
o registration functions for tables, matches and targets are only
wrappers around x_tables provided functions
o all matches/targets that are used from ip_tables and ip6_tables
are now implemented as xt_FOOBAR.c files and provide module aliases
to ipt_FOOBAR and ip6t_FOOBAR
o header files for xt_matches are in include/linux/netfilter/,
include/linux/netfilter_{ipv4,ipv6} contains compatibility wrappers
around the xt_FOOBAR.h headers
Based on this patchset we're going to further unify the code,
gradually getting rid of all the layer 3 specific assumptions.
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-01-13 05:30:04 +08:00
|
|
|
|
2008-10-08 17:35:00 +08:00
|
|
|
config NETFILTER_XT_MATCH_RECENT
|
|
|
|
|
tristate '"recent" match support'
|
|
|
|
|
depends on NETFILTER_ADVANCED
|
|
|
|
|
---help---
|
|
|
|
|
This match is used for creating one or many lists of recently
|
|
|
|
|
used addresses and then matching against that/those list(s).
|
|
|
|
|
|
|
|
|
|
Short options are available by using 'iptables -m recent -h'
|
|
|
|
|
Official Website: <http://snowman.net/projects/ipt_recent/>
|
|
|
|
|
|
[NETFILTER] x_tables: Abstraction layer for {ip,ip6,arp}_tables
This monster-patch tries to do the best job for unifying the data
structures and backend interfaces for the three evil clones ip_tables,
ip6_tables and arp_tables. In an ideal world we would never have
allowed this kind of copy+paste programming... but well, our world
isn't (yet?) ideal.
o introduce a new x_tables module
o {ip,arp,ip6}_tables depend on this x_tables module
o registration functions for tables, matches and targets are only
wrappers around x_tables provided functions
o all matches/targets that are used from ip_tables and ip6_tables
are now implemented as xt_FOOBAR.c files and provide module aliases
to ipt_FOOBAR and ip6t_FOOBAR
o header files for xt_matches are in include/linux/netfilter/,
include/linux/netfilter_{ipv4,ipv6} contains compatibility wrappers
around the xt_FOOBAR.h headers
Based on this patchset we're going to further unify the code,
gradually getting rid of all the layer 3 specific assumptions.
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-01-13 05:30:04 +08:00
|
|
|
config NETFILTER_XT_MATCH_SCTP
|
2006-07-25 13:55:29 +08:00
|
|
|
tristate '"sctp" protocol match support (EXPERIMENTAL)'
|
2008-10-08 17:35:18 +08:00
|
|
|
depends on EXPERIMENTAL
|
2007-12-18 14:47:05 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
2008-05-08 16:16:04 +08:00
|
|
|
default IP_SCTP
|
[NETFILTER] x_tables: Abstraction layer for {ip,ip6,arp}_tables
This monster-patch tries to do the best job for unifying the data
structures and backend interfaces for the three evil clones ip_tables,
ip6_tables and arp_tables. In an ideal world we would never have
allowed this kind of copy+paste programming... but well, our world
isn't (yet?) ideal.
o introduce a new x_tables module
o {ip,arp,ip6}_tables depend on this x_tables module
o registration functions for tables, matches and targets are only
wrappers around x_tables provided functions
o all matches/targets that are used from ip_tables and ip6_tables
are now implemented as xt_FOOBAR.c files and provide module aliases
to ipt_FOOBAR and ip6t_FOOBAR
o header files for xt_matches are in include/linux/netfilter/,
include/linux/netfilter_{ipv4,ipv6} contains compatibility wrappers
around the xt_FOOBAR.h headers
Based on this patchset we're going to further unify the code,
gradually getting rid of all the layer 3 specific assumptions.
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-01-13 05:30:04 +08:00
|
|
|
help
|
|
|
|
|
With this option enabled, you will be able to use the
|
|
|
|
|
`sctp' match in order to match on SCTP source/destination ports
|
|
|
|
|
and SCTP chunk types.
|
|
|
|
|
|
|
|
|
|
If you want to compile it as a module, say M here and read
|
2007-03-16 21:28:43 +08:00
|
|
|
<file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
|
[NETFILTER] x_tables: Abstraction layer for {ip,ip6,arp}_tables
This monster-patch tries to do the best job for unifying the data
structures and backend interfaces for the three evil clones ip_tables,
ip6_tables and arp_tables. In an ideal world we would never have
allowed this kind of copy+paste programming... but well, our world
isn't (yet?) ideal.
o introduce a new x_tables module
o {ip,arp,ip6}_tables depend on this x_tables module
o registration functions for tables, matches and targets are only
wrappers around x_tables provided functions
o all matches/targets that are used from ip_tables and ip6_tables
are now implemented as xt_FOOBAR.c files and provide module aliases
to ipt_FOOBAR and ip6t_FOOBAR
o header files for xt_matches are in include/linux/netfilter/,
include/linux/netfilter_{ipv4,ipv6} contains compatibility wrappers
around the xt_FOOBAR.h headers
Based on this patchset we're going to further unify the code,
gradually getting rid of all the layer 3 specific assumptions.
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-01-13 05:30:04 +08:00
|
|
|
|
2008-10-08 17:35:12 +08:00
|
|
|
config NETFILTER_XT_MATCH_SOCKET
|
|
|
|
|
tristate '"socket" match support (EXPERIMENTAL)'
|
|
|
|
|
depends on EXPERIMENTAL
|
|
|
|
|
depends on NETFILTER_TPROXY
|
|
|
|
|
depends on NETFILTER_XTABLES
|
|
|
|
|
depends on NETFILTER_ADVANCED
|
2009-05-02 06:23:10 +08:00
|
|
|
depends on !NF_CONNTRACK || NF_CONNTRACK
|
2008-10-08 17:35:12 +08:00
|
|
|
select NF_DEFRAG_IPV4
|
2010-10-25 07:38:32 +08:00
|
|
|
select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES
|
2008-10-08 17:35:12 +08:00
|
|
|
help
|
|
|
|
|
This option adds a `socket' match, which can be used to match
|
|
|
|
|
packets for which a TCP or UDP socket lookup finds a valid socket.
|
|
|
|
|
It can be used in combination with the MARK target and policy
|
|
|
|
|
routing to implement full featured non-locally bound sockets.
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
[NETFILTER] x_tables: Abstraction layer for {ip,ip6,arp}_tables
This monster-patch tries to do the best job for unifying the data
structures and backend interfaces for the three evil clones ip_tables,
ip6_tables and arp_tables. In an ideal world we would never have
allowed this kind of copy+paste programming... but well, our world
isn't (yet?) ideal.
o introduce a new x_tables module
o {ip,arp,ip6}_tables depend on this x_tables module
o registration functions for tables, matches and targets are only
wrappers around x_tables provided functions
o all matches/targets that are used from ip_tables and ip6_tables
are now implemented as xt_FOOBAR.c files and provide module aliases
to ipt_FOOBAR and ip6t_FOOBAR
o header files for xt_matches are in include/linux/netfilter/,
include/linux/netfilter_{ipv4,ipv6} contains compatibility wrappers
around the xt_FOOBAR.h headers
Based on this patchset we're going to further unify the code,
gradually getting rid of all the layer 3 specific assumptions.
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-01-13 05:30:04 +08:00
|
|
|
config NETFILTER_XT_MATCH_STATE
|
|
|
|
|
tristate '"state" match support'
|
2007-03-15 07:37:25 +08:00
|
|
|
depends on NF_CONNTRACK
|
2007-12-18 14:47:05 +08:00
|
|
|
default m if NETFILTER_ADVANCED=n
|
[NETFILTER] x_tables: Abstraction layer for {ip,ip6,arp}_tables
This monster-patch tries to do the best job for unifying the data
structures and backend interfaces for the three evil clones ip_tables,
ip6_tables and arp_tables. In an ideal world we would never have
allowed this kind of copy+paste programming... but well, our world
isn't (yet?) ideal.
o introduce a new x_tables module
o {ip,arp,ip6}_tables depend on this x_tables module
o registration functions for tables, matches and targets are only
wrappers around x_tables provided functions
o all matches/targets that are used from ip_tables and ip6_tables
are now implemented as xt_FOOBAR.c files and provide module aliases
to ipt_FOOBAR and ip6t_FOOBAR
o header files for xt_matches are in include/linux/netfilter/,
include/linux/netfilter_{ipv4,ipv6} contains compatibility wrappers
around the xt_FOOBAR.h headers
Based on this patchset we're going to further unify the code,
gradually getting rid of all the layer 3 specific assumptions.
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-01-13 05:30:04 +08:00
|
|
|
help
|
|
|
|
|
Connection state matching allows you to match packets based on their
|
|
|
|
|
relationship to a tracked connection (ie. previous packets). This
|
|
|
|
|
is a powerful tool for packet classification.
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
2006-05-30 09:21:00 +08:00
|
|
|
config NETFILTER_XT_MATCH_STATISTIC
|
|
|
|
|
tristate '"statistic" match support'
|
2007-12-18 14:47:05 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
2006-05-30 09:21:00 +08:00
|
|
|
help
|
2006-06-27 18:02:14 +08:00
|
|
|
This option adds a `statistic' match, which allows you to match
|
|
|
|
|
on packets periodically or randomly with a given percentage.
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
2006-05-30 09:21:00 +08:00
|
|
|
|
[NETFILTER] x_tables: Abstraction layer for {ip,ip6,arp}_tables
This monster-patch tries to do the best job for unifying the data
structures and backend interfaces for the three evil clones ip_tables,
ip6_tables and arp_tables. In an ideal world we would never have
allowed this kind of copy+paste programming... but well, our world
isn't (yet?) ideal.
o introduce a new x_tables module
o {ip,arp,ip6}_tables depend on this x_tables module
o registration functions for tables, matches and targets are only
wrappers around x_tables provided functions
o all matches/targets that are used from ip_tables and ip6_tables
are now implemented as xt_FOOBAR.c files and provide module aliases
to ipt_FOOBAR and ip6t_FOOBAR
o header files for xt_matches are in include/linux/netfilter/,
include/linux/netfilter_{ipv4,ipv6} contains compatibility wrappers
around the xt_FOOBAR.h headers
Based on this patchset we're going to further unify the code,
gradually getting rid of all the layer 3 specific assumptions.
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-01-13 05:30:04 +08:00
|
|
|
config NETFILTER_XT_MATCH_STRING
|
|
|
|
|
tristate '"string" match support'
|
2007-12-18 14:47:05 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
[NETFILTER] x_tables: Abstraction layer for {ip,ip6,arp}_tables
This monster-patch tries to do the best job for unifying the data
structures and backend interfaces for the three evil clones ip_tables,
ip6_tables and arp_tables. In an ideal world we would never have
allowed this kind of copy+paste programming... but well, our world
isn't (yet?) ideal.
o introduce a new x_tables module
o {ip,arp,ip6}_tables depend on this x_tables module
o registration functions for tables, matches and targets are only
wrappers around x_tables provided functions
o all matches/targets that are used from ip_tables and ip6_tables
are now implemented as xt_FOOBAR.c files and provide module aliases
to ipt_FOOBAR and ip6t_FOOBAR
o header files for xt_matches are in include/linux/netfilter/,
include/linux/netfilter_{ipv4,ipv6} contains compatibility wrappers
around the xt_FOOBAR.h headers
Based on this patchset we're going to further unify the code,
gradually getting rid of all the layer 3 specific assumptions.
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-01-13 05:30:04 +08:00
|
|
|
select TEXTSEARCH
|
|
|
|
|
select TEXTSEARCH_KMP
|
|
|
|
|
select TEXTSEARCH_BM
|
|
|
|
|
select TEXTSEARCH_FSM
|
|
|
|
|
help
|
|
|
|
|
This option adds a `string' match, which allows you to look for
|
|
|
|
|
pattern matchings in packets.
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
|
|
|
|
config NETFILTER_XT_MATCH_TCPMSS
|
|
|
|
|
tristate '"tcpmss" match support'
|
2007-12-18 14:47:05 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
[NETFILTER] x_tables: Abstraction layer for {ip,ip6,arp}_tables
This monster-patch tries to do the best job for unifying the data
structures and backend interfaces for the three evil clones ip_tables,
ip6_tables and arp_tables. In an ideal world we would never have
allowed this kind of copy+paste programming... but well, our world
isn't (yet?) ideal.
o introduce a new x_tables module
o {ip,arp,ip6}_tables depend on this x_tables module
o registration functions for tables, matches and targets are only
wrappers around x_tables provided functions
o all matches/targets that are used from ip_tables and ip6_tables
are now implemented as xt_FOOBAR.c files and provide module aliases
to ipt_FOOBAR and ip6t_FOOBAR
o header files for xt_matches are in include/linux/netfilter/,
include/linux/netfilter_{ipv4,ipv6} contains compatibility wrappers
around the xt_FOOBAR.h headers
Based on this patchset we're going to further unify the code,
gradually getting rid of all the layer 3 specific assumptions.
Signed-off-by: Harald Welte <laforge@netfilter.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-01-13 05:30:04 +08:00
|
|
|
help
|
|
|
|
|
This option adds a `tcpmss' match, which allows you to examine the
|
|
|
|
|
MSS value of TCP SYN packets, which control the maximum packet size
|
|
|
|
|
for that connection.
|
|
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
2007-09-29 05:46:43 +08:00
|
|
|
config NETFILTER_XT_MATCH_TIME
|
|
|
|
|
tristate '"time" match support'
|
2007-12-18 14:47:05 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
2007-09-29 05:46:43 +08:00
|
|
|
---help---
|
|
|
|
|
This option adds a "time" match, which allows you to match based on
|
|
|
|
|
the packet arrival time (at the machine which netfilter is running)
|
|
|
|
|
on) or departure time/date (for locally generated packets).
|
|
|
|
|
|
|
|
|
|
If you say Y here, try `iptables -m time --help` for
|
|
|
|
|
more information.
|
|
|
|
|
|
|
|
|
|
If you want to compile it as a module, say M here.
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2007-07-08 13:20:36 +08:00
|
|
|
config NETFILTER_XT_MATCH_U32
|
|
|
|
|
tristate '"u32" match support'
|
2007-12-18 14:47:05 +08:00
|
|
|
depends on NETFILTER_ADVANCED
|
2007-07-08 13:20:36 +08:00
|
|
|
---help---
|
|
|
|
|
u32 allows you to extract quantities of up to 4 bytes from a packet,
|
|
|
|
|
AND them with specified masks, shift them by specified amounts and
|
|
|
|
|
test whether the results are in any of a set of specified ranges.
|
|
|
|
|
The specification of what to extract is general enough to skip over
|
|
|
|
|
headers with lengths stored in the packet, as in IP or TCP header
|
|
|
|
|
lengths.
|
|
|
|
|
|
|
|
|
|
Details and examples are in the kernel module source.
|
|
|
|
|
|
2008-10-08 17:35:18 +08:00
|
|
|
endif # NETFILTER_XTABLES
|
2006-02-14 07:42:48 +08:00
|
|
|
|
2008-10-08 17:35:18 +08:00
|
|
|
endmenu
|
2006-02-14 07:42:48 +08:00
|
|
|
|
netfilter: ipset: IP set core support
The patch adds the IP set core support to the kernel.
The IP set core implements a netlink (nfnetlink) based protocol by which
one can create, destroy, flush, rename, swap, list, save, restore sets,
and add, delete, test elements from userspace. For simplicity (and backward
compatibilty and for not to force ip(6)tables to be linked with a netlink
library) reasons a small getsockopt-based protocol is also kept in order
to communicate with the ip(6)tables match and target.
The netlink protocol passes all u16, etc values in network order with
NLA_F_NET_BYTEORDER flag. The protocol enforces the proper use of the
NLA_F_NESTED and NLA_F_NET_BYTEORDER flags.
For other kernel subsystems (netfilter match and target) the API contains
the functions to add, delete and test elements in sets and the required calls
to get/put refereces to the sets before those operations can be performed.
The set types (which are implemented in independent modules) are stored
in a simple RCU protected list. A set type may have variants: for example
without timeout or with timeout support, for IPv4 or for IPv6. The sets
(i.e. the pointers to the sets) are stored in an array. The sets are
identified by their index in the array, which makes possible easy and
fast swapping of sets. The array is protected indirectly by the nfnl
mutex from nfnetlink. The content of the sets are protected by the rwlock
of the set.
There are functional differences between the add/del/test functions
for the kernel and userspace:
- kernel add/del/test: works on the current packet (i.e. one element)
- kernel test: may trigger an "add" operation in order to fill
out unspecified parts of the element from the packet (like MAC address)
- userspace add/del: works on the netlink message and thus possibly
on multiple elements from the IPSET_ATTR_ADT container attribute.
- userspace add: may trigger resizing of a set
Signed-off-by: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Signed-off-by: Patrick McHardy <kaber@trash.net>
2011-02-01 22:28:35 +08:00
|
|
|
source "net/netfilter/ipset/Kconfig"
|
|
|
|
|
|
2008-09-19 18:32:57 +08:00
|
|
|
source "net/netfilter/ipvs/Kconfig"
|