[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 00:38:16 +00:00
|
|
|
menu "Core Netfilter Configuration"
|
2006-12-12 08:27:46 +00: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 00:38:16 +00:00
|
|
|
|
2005-08-10 02:30:24 +00:00
|
|
|
config NETFILTER_NETLINK
|
|
|
|
tristate "Netfilter netlink interface"
|
|
|
|
help
|
|
|
|
If this option is enabled, the kernel will include support
|
|
|
|
for the new netfilter netlink interface.
|
2005-08-10 02:44:15 +00:00
|
|
|
|
|
|
|
config NETFILTER_NETLINK_QUEUE
|
|
|
|
tristate "Netfilter NFQUEUE over NFNETLINK interface"
|
|
|
|
depends on NETFILTER_NETLINK
|
|
|
|
help
|
2006-03-22 21:53:48 +00:00
|
|
|
If this option is enabled, the kernel will include support
|
2005-08-10 02:44:15 +00:00
|
|
|
for queueing packets via NFNETLINK.
|
|
|
|
|
2005-08-10 02:58:39 +00:00
|
|
|
config NETFILTER_NETLINK_LOG
|
|
|
|
tristate "Netfilter LOG over NFNETLINK interface"
|
|
|
|
depends on NETFILTER_NETLINK
|
|
|
|
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.
|
|
|
|
|
2006-12-03 06:05:46 +00:00
|
|
|
config NF_CONNTRACK_ENABLED
|
|
|
|
tristate "Netfilter connection tracking support"
|
|
|
|
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 00:38:16 +00: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 06:05:46 +00:00
|
|
|
This is required to do Masquerading or other kinds of Network
|
|
|
|
Address Translation (except for Fast NAT). It can also be used to
|
|
|
|
enhance packet filtering (see `Connection state match support'
|
|
|
|
below).
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
|
|
choice
|
|
|
|
prompt "Netfilter connection tracking support"
|
|
|
|
depends on NF_CONNTRACK_ENABLED
|
|
|
|
|
|
|
|
config NF_CONNTRACK_SUPPORT
|
2007-01-04 20:16:06 +00:00
|
|
|
bool "Layer 3 Independent Connection tracking"
|
2006-12-03 06:05:46 +00: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 00:38:16 +00:00
|
|
|
Layer 3 independent connection tracking is experimental scheme
|
|
|
|
which generalize ip_conntrack to support other layer 3 protocols.
|
|
|
|
|
2006-12-03 06:05:46 +00:00
|
|
|
This is required to do Masquerading or other kinds of Network
|
|
|
|
Address Translation (except for Fast NAT). It can also be used to
|
|
|
|
enhance packet filtering (see `Connection state match support'
|
|
|
|
below).
|
|
|
|
|
|
|
|
config IP_NF_CONNTRACK_SUPPORT
|
2006-12-03 06:11:01 +00:00
|
|
|
bool "Layer 3 Dependent Connection tracking (OBSOLETE)"
|
2006-12-03 06:05:46 +00:00
|
|
|
help
|
|
|
|
The old, Layer 3 dependent ip_conntrack subsystem of netfilter.
|
|
|
|
|
|
|
|
This is required to do Masquerading or other kinds of Network
|
|
|
|
Address Translation (except for Fast NAT). It can also be used to
|
|
|
|
enhance packet filtering (see `Connection state match support'
|
|
|
|
below).
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
|
|
config NF_CONNTRACK
|
|
|
|
tristate
|
|
|
|
default m if NF_CONNTRACK_SUPPORT && NF_CONNTRACK_ENABLED=m
|
|
|
|
default y if NF_CONNTRACK_SUPPORT && NF_CONNTRACK_ENABLED=y
|
|
|
|
|
|
|
|
config IP_NF_CONNTRACK
|
|
|
|
tristate
|
|
|
|
default m if IP_NF_CONNTRACK_SUPPORT && NF_CONNTRACK_ENABLED=m
|
|
|
|
default y if IP_NF_CONNTRACK_SUPPORT && NF_CONNTRACK_ENABLED=y
|
[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 00:38:16 +00:00
|
|
|
|
|
|
|
config NF_CT_ACCT
|
|
|
|
bool "Connection tracking flow accounting"
|
|
|
|
depends on NF_CONNTRACK
|
|
|
|
help
|
|
|
|
If this option is enabled, the connection tracking code will
|
|
|
|
keep per-flow packet and byte counters.
|
|
|
|
|
|
|
|
Those counters can be used for flow-based accounting or the
|
|
|
|
`connbytes' match.
|
|
|
|
|
|
|
|
If unsure, say `N'.
|
|
|
|
|
|
|
|
config NF_CONNTRACK_MARK
|
|
|
|
bool 'Connection mark tracking support'
|
|
|
|
depends on NF_CONNTRACK
|
|
|
|
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 07:31:46 +00:00
|
|
|
config NF_CONNTRACK_SECMARK
|
|
|
|
bool 'Connection tracking security mark support'
|
|
|
|
depends on NF_CONNTRACK && NETWORK_SECMARK
|
|
|
|
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'.
|
|
|
|
|
[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 00:38:16 +00:00
|
|
|
config NF_CONNTRACK_EVENTS
|
2005-12-05 21:36:25 +00:00
|
|
|
bool "Connection tracking events (EXPERIMENTAL)"
|
|
|
|
depends on EXPERIMENTAL && 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 00:38:16 +00: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-22 21:53:48 +00: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 00:38:16 +00:00
|
|
|
|
|
|
|
If unsure, say `N'.
|
|
|
|
|
2006-12-03 06:09:41 +00:00
|
|
|
config NF_CT_PROTO_GRE
|
|
|
|
tristate
|
2007-01-04 20:16:06 +00:00
|
|
|
depends on NF_CONNTRACK
|
2006-12-03 06:09:41 +00:00
|
|
|
|
[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 00:38:16 +00:00
|
|
|
config NF_CT_PROTO_SCTP
|
2006-12-03 06:11:01 +00:00
|
|
|
tristate 'SCTP protocol connection tracking support (EXPERIMENTAL)'
|
[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 00:38:16 +00:00
|
|
|
depends on EXPERIMENTAL && NF_CONNTRACK
|
|
|
|
default n
|
|
|
|
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
|
|
|
|
Documentation/modules.txt. If unsure, say `N'.
|
|
|
|
|
2006-12-03 06:08:26 +00:00
|
|
|
config NF_CONNTRACK_AMANDA
|
2007-01-04 20:16:06 +00:00
|
|
|
tristate "Amanda backup protocol support"
|
|
|
|
depends on NF_CONNTRACK
|
2006-12-03 06:08:26 +00: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 00:38:16 +00:00
|
|
|
config NF_CONNTRACK_FTP
|
2007-01-04 20:16:06 +00:00
|
|
|
tristate "FTP protocol support"
|
|
|
|
depends on 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 00:38:16 +00: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 06:08:46 +00:00
|
|
|
config NF_CONNTRACK_H323
|
|
|
|
tristate "H.323 protocol support (EXPERIMENTAL)"
|
|
|
|
depends on EXPERIMENTAL && NF_CONNTRACK
|
|
|
|
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 06:09:06 +00:00
|
|
|
config NF_CONNTRACK_IRC
|
2007-01-04 20:16:06 +00:00
|
|
|
tristate "IRC protocol support"
|
|
|
|
depends on NF_CONNTRACK
|
2006-12-03 06:09:06 +00: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.
|
|
|
|
|
2006-12-03 06:09:24 +00:00
|
|
|
config NF_CONNTRACK_NETBIOS_NS
|
|
|
|
tristate "NetBIOS name service protocol support (EXPERIMENTAL)"
|
|
|
|
depends on EXPERIMENTAL && NF_CONNTRACK
|
|
|
|
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.
|
|
|
|
|
2006-12-03 06:09:41 +00:00
|
|
|
config NF_CONNTRACK_PPTP
|
2007-01-04 20:16:06 +00:00
|
|
|
tristate "PPtP protocol support"
|
|
|
|
depends on NF_CONNTRACK
|
2006-12-03 06:09:41 +00: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:
|
|
|
|
- Blindy assumes that control connections are always established
|
|
|
|
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.
|
|
|
|
|
2006-12-03 06:09:57 +00:00
|
|
|
config NF_CONNTRACK_SIP
|
|
|
|
tristate "SIP protocol support (EXPERIMENTAL)"
|
|
|
|
depends on EXPERIMENTAL && NF_CONNTRACK
|
|
|
|
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 06:10:18 +00:00
|
|
|
config NF_CONNTRACK_TFTP
|
2007-01-04 20:16:06 +00:00
|
|
|
tristate "TFTP protocol support"
|
|
|
|
depends on NF_CONNTRACK
|
2006-12-03 06:10:18 +00: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-05 20:19:05 +00:00
|
|
|
config NF_CT_NETLINK
|
|
|
|
tristate 'Connection tracking netlink interface (EXPERIMENTAL)'
|
|
|
|
depends on EXPERIMENTAL && NF_CONNTRACK && NETFILTER_NETLINK
|
|
|
|
depends on NF_CONNTRACK!=y || NETFILTER_NETLINK!=m
|
|
|
|
help
|
|
|
|
This option enables support for a netlink-based userspace interface
|
|
|
|
|
[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-12 21:30:04 +00:00
|
|
|
config NETFILTER_XTABLES
|
|
|
|
tristate "Netfilter Xtables support (required for ip_tables)"
|
|
|
|
help
|
|
|
|
This is required if you intend to use any of ip_tables,
|
|
|
|
ip6_tables or arp_tables.
|
|
|
|
|
|
|
|
# alphabetically ordered list of targets
|
|
|
|
|
|
|
|
config NETFILTER_XT_TARGET_CLASSIFY
|
|
|
|
tristate '"CLASSIFY" target support'
|
|
|
|
depends on NETFILTER_XTABLES
|
|
|
|
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'
|
|
|
|
depends on NETFILTER_XTABLES
|
|
|
|
depends on IP_NF_MANGLE || IP6_NF_MANGLE
|
2006-02-15 23:21:31 +00:00
|
|
|
depends on (IP_NF_CONNTRACK && IP_NF_CONNTRACK_MARK) || (NF_CONNTRACK_MARK && NF_CONNTRACK)
|
[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-12 21:30:04 +00:00
|
|
|
help
|
|
|
|
This option adds a `CONNMARK' target, which allows one to manipulate
|
|
|
|
the connection mark value. Similar to the MARK target, but
|
|
|
|
affects the connection mark value rather than the packet mark value.
|
|
|
|
|
|
|
|
If you want to compile it as a module, say M here and read
|
|
|
|
<file:Documentation/modules.txt>. The module will be called
|
|
|
|
ipt_CONNMARK.o. If unsure, say `N'.
|
|
|
|
|
2006-08-22 07:30:26 +00:00
|
|
|
config NETFILTER_XT_TARGET_DSCP
|
|
|
|
tristate '"DSCP" target support'
|
|
|
|
depends on NETFILTER_XTABLES
|
|
|
|
depends on IP_NF_MANGLE || IP6_NF_MANGLE
|
|
|
|
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.
|
|
|
|
|
|
|
|
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-12 21:30:04 +00:00
|
|
|
config NETFILTER_XT_TARGET_MARK
|
|
|
|
tristate '"MARK" target support'
|
|
|
|
depends on NETFILTER_XTABLES
|
|
|
|
help
|
|
|
|
This option adds a `MARK' target, which allows you to create rules
|
|
|
|
in the `mangle' table which alter the netfilter mark (nfmark) field
|
|
|
|
associated with the packet prior to routing. This can change
|
|
|
|
the routing method (see `Use netfilter MARK value as routing
|
|
|
|
key') and can also be used by other subsystems to change their
|
|
|
|
behavior.
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
|
|
config NETFILTER_XT_TARGET_NFQUEUE
|
|
|
|
tristate '"NFQUEUE" target Support'
|
|
|
|
depends on NETFILTER_XTABLES
|
|
|
|
help
|
2006-03-22 21:53:48 +00:00
|
|
|
This target replaced the old obsolete QUEUE target.
|
[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-12 21:30:04 +00:00
|
|
|
|
|
|
|
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.
|
|
|
|
|
2006-11-29 01:35:38 +00:00
|
|
|
config NETFILTER_XT_TARGET_NFLOG
|
|
|
|
tristate '"NFLOG" target support'
|
|
|
|
depends on NETFILTER_XTABLES
|
|
|
|
help
|
|
|
|
This option enables the NFLOG target, which allows to LOG
|
|
|
|
messages through the netfilter logging API, which can use
|
|
|
|
either the old LOG target, the old ULOG target or nfnetlink_log
|
|
|
|
as backend.
|
|
|
|
|
|
|
|
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-12 21:30:04 +00:00
|
|
|
config NETFILTER_XT_TARGET_NOTRACK
|
|
|
|
tristate '"NOTRACK" target support'
|
|
|
|
depends on NETFILTER_XTABLES
|
|
|
|
depends on IP_NF_RAW || IP6_NF_RAW
|
|
|
|
depends on IP_NF_CONNTRACK || NF_CONNTRACK
|
|
|
|
help
|
|
|
|
The NOTRACK target allows a select rule to specify
|
|
|
|
which packets *not* to enter the conntrack/NAT
|
|
|
|
subsystem with all the consequences (no ICMP error tracking,
|
|
|
|
no protocol helpers for the selected packets).
|
|
|
|
|
|
|
|
If you want to compile it as a module, say M here and read
|
|
|
|
<file:Documentation/modules.txt>. If unsure, say `N'.
|
|
|
|
|
2006-06-09 07:30:57 +00:00
|
|
|
config NETFILTER_XT_TARGET_SECMARK
|
|
|
|
tristate '"SECMARK" target support'
|
|
|
|
depends on NETFILTER_XTABLES && NETWORK_SECMARK
|
|
|
|
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.
|
|
|
|
|
2006-06-09 07:32:39 +00:00
|
|
|
config NETFILTER_XT_TARGET_CONNSECMARK
|
|
|
|
tristate '"CONNSECMARK" target support'
|
2006-10-12 21:08:41 +00:00
|
|
|
depends on NETFILTER_XTABLES && \
|
|
|
|
((NF_CONNTRACK && NF_CONNTRACK_SECMARK) || \
|
|
|
|
(IP_NF_CONNTRACK && IP_NF_CONNTRACK_SECMARK))
|
2006-06-09 07:32:39 +00:00
|
|
|
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.
|
|
|
|
|
[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-12 21:30:04 +00:00
|
|
|
config NETFILTER_XT_MATCH_COMMENT
|
|
|
|
tristate '"comment" match support'
|
|
|
|
depends on NETFILTER_XTABLES
|
|
|
|
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
|
|
|
|
<file:Documentation/modules.txt>. If unsure, say `N'.
|
|
|
|
|
|
|
|
config NETFILTER_XT_MATCH_CONNBYTES
|
|
|
|
tristate '"connbytes" per-connection counter match support'
|
|
|
|
depends on NETFILTER_XTABLES
|
2006-02-15 23:21:31 +00:00
|
|
|
depends on (IP_NF_CONNTRACK && IP_NF_CT_ACCT) || (NF_CT_ACCT && NF_CONNTRACK)
|
[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-12 21:30:04 +00: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
|
|
|
|
<file:Documentation/modules.txt>. If unsure, say `N'.
|
|
|
|
|
|
|
|
config NETFILTER_XT_MATCH_CONNMARK
|
|
|
|
tristate '"connmark" connection mark match support'
|
|
|
|
depends on NETFILTER_XTABLES
|
2006-02-15 23:21:31 +00:00
|
|
|
depends on (IP_NF_CONNTRACK && IP_NF_CONNTRACK_MARK) || (NF_CONNTRACK_MARK && NF_CONNTRACK)
|
[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-12 21:30:04 +00:00
|
|
|
help
|
|
|
|
This option adds a `connmark' match, which allows you to match the
|
|
|
|
connection mark value previously set for the session by `CONNMARK'.
|
|
|
|
|
|
|
|
If you want to compile it as a module, say M here and read
|
|
|
|
<file:Documentation/modules.txt>. The module will be called
|
|
|
|
ipt_connmark.o. If unsure, say `N'.
|
|
|
|
|
|
|
|
config NETFILTER_XT_MATCH_CONNTRACK
|
|
|
|
tristate '"conntrack" connection tracking match support'
|
|
|
|
depends on NETFILTER_XTABLES
|
|
|
|
depends on IP_NF_CONNTRACK || NF_CONNTRACK
|
|
|
|
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.
|
|
|
|
|
|
|
|
config NETFILTER_XT_MATCH_DCCP
|
|
|
|
tristate '"DCCP" protocol match support'
|
|
|
|
depends on NETFILTER_XTABLES
|
|
|
|
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
|
|
|
|
<file:Documentation/modules.txt>. If unsure, say `N'.
|
|
|
|
|
2006-08-22 07:29:37 +00:00
|
|
|
config NETFILTER_XT_MATCH_DSCP
|
|
|
|
tristate '"DSCP" match support'
|
|
|
|
depends on NETFILTER_XTABLES
|
|
|
|
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.
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
2006-04-01 10:22:30 +00:00
|
|
|
config NETFILTER_XT_MATCH_ESP
|
|
|
|
tristate '"ESP" match support'
|
|
|
|
depends on NETFILTER_XTABLES
|
|
|
|
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.
|
|
|
|
|
[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-12 21:30:04 +00:00
|
|
|
config NETFILTER_XT_MATCH_HELPER
|
|
|
|
tristate '"helper" match support'
|
|
|
|
depends on NETFILTER_XTABLES
|
|
|
|
depends on IP_NF_CONNTRACK || NF_CONNTRACK
|
|
|
|
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.
|
|
|
|
|
|
|
|
config NETFILTER_XT_MATCH_LENGTH
|
|
|
|
tristate '"length" match support'
|
|
|
|
depends on NETFILTER_XTABLES
|
|
|
|
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'
|
|
|
|
depends on NETFILTER_XTABLES
|
|
|
|
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'
|
|
|
|
depends on NETFILTER_XTABLES
|
|
|
|
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'
|
|
|
|
depends on NETFILTER_XTABLES
|
|
|
|
help
|
|
|
|
Netfilter mark matching allows you to match packets based on the
|
|
|
|
`nfmark' value in the packet. This can be set by the MARK target
|
|
|
|
(see below).
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
2006-03-21 02:03:40 +00:00
|
|
|
config NETFILTER_XT_MATCH_POLICY
|
|
|
|
tristate 'IPsec "policy" match support'
|
|
|
|
depends on NETFILTER_XTABLES && XFRM
|
|
|
|
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.
|
|
|
|
|
2006-04-01 10:22:54 +00:00
|
|
|
config NETFILTER_XT_MATCH_MULTIPORT
|
|
|
|
tristate "Multiple port match support"
|
|
|
|
depends on NETFILTER_XTABLES
|
|
|
|
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.
|
|
|
|
|
[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-12 21:30:04 +00:00
|
|
|
config NETFILTER_XT_MATCH_PHYSDEV
|
|
|
|
tristate '"physdev" match support'
|
2006-10-02 23:10:47 +00:00
|
|
|
depends on NETFILTER_XTABLES && BRIDGE && BRIDGE_NETFILTER
|
[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-12 21:30:04 +00: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'
|
|
|
|
depends on NETFILTER_XTABLES
|
|
|
|
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 01:20:32 +00:00
|
|
|
config NETFILTER_XT_MATCH_QUOTA
|
|
|
|
tristate '"quota" match support'
|
|
|
|
depends on NETFILTER_XTABLES
|
|
|
|
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
|
|
|
|
<file:Documentation/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-12 21:30:04 +00:00
|
|
|
config NETFILTER_XT_MATCH_REALM
|
|
|
|
tristate '"realm" match support'
|
|
|
|
depends on NETFILTER_XTABLES
|
|
|
|
select NET_CLS_ROUTE
|
|
|
|
help
|
|
|
|
This option adds a `realm' match, which allows you to use the realm
|
|
|
|
key from the routing subsystem inside iptables.
|
|
|
|
|
|
|
|
This match pretty much resembles the CONFIG_NET_CLS_ROUTE4 option
|
|
|
|
in tc world.
|
|
|
|
|
|
|
|
If you want to compile it as a module, say M here and read
|
|
|
|
<file:Documentation/modules.txt>. If unsure, say `N'.
|
|
|
|
|
|
|
|
config NETFILTER_XT_MATCH_SCTP
|
2006-07-25 05:55:29 +00:00
|
|
|
tristate '"sctp" protocol match support (EXPERIMENTAL)'
|
|
|
|
depends on NETFILTER_XTABLES && EXPERIMENTAL
|
[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-12 21:30:04 +00: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
|
|
|
|
<file:Documentation/modules.txt>. If unsure, say `N'.
|
|
|
|
|
|
|
|
config NETFILTER_XT_MATCH_STATE
|
|
|
|
tristate '"state" match support'
|
|
|
|
depends on NETFILTER_XTABLES
|
|
|
|
depends on IP_NF_CONNTRACK || NF_CONNTRACK
|
|
|
|
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 01:21:00 +00:00
|
|
|
config NETFILTER_XT_MATCH_STATISTIC
|
|
|
|
tristate '"statistic" match support'
|
|
|
|
depends on NETFILTER_XTABLES
|
|
|
|
help
|
2006-06-27 10:02:14 +00: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 01:21:00 +00: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-12 21:30:04 +00:00
|
|
|
config NETFILTER_XT_MATCH_STRING
|
|
|
|
tristate '"string" match support'
|
|
|
|
depends on NETFILTER_XTABLES
|
|
|
|
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'
|
|
|
|
depends on NETFILTER_XTABLES
|
|
|
|
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.
|
|
|
|
|
2006-11-29 01:35:36 +00:00
|
|
|
config NETFILTER_XT_MATCH_HASHLIMIT
|
|
|
|
tristate '"hashlimit" match support'
|
2007-01-31 05:36:09 +00:00
|
|
|
depends on NETFILTER_XTABLES && (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
|
2006-11-29 01:35:36 +00:00
|
|
|
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.
|
|
|
|
|
2006-02-13 23:42:48 +00:00
|
|
|
endmenu
|
|
|
|
|