netfilter: xtables: sort extensions alphabetically in Kconfig
Signed-off-by: Jan Engelhardt <jengelh@medozas.de> Signed-off-by: Patrick McHardy <kaber@trash.net>
This commit is contained in:
committed by
Patrick McHardy
parent
20f3c56f4d
commit
aba0d34800
@@ -62,15 +62,16 @@ config IP_NF_IPTABLES
|
|||||||
To compile it as a module, choose M here. If unsure, say N.
|
To compile it as a module, choose M here. If unsure, say N.
|
||||||
|
|
||||||
# The matches.
|
# The matches.
|
||||||
config IP_NF_MATCH_ECN
|
config IP_NF_MATCH_ADDRTYPE
|
||||||
tristate '"ecn" match support'
|
tristate '"addrtype" address type match support'
|
||||||
depends on IP_NF_IPTABLES
|
depends on IP_NF_IPTABLES
|
||||||
depends on NETFILTER_ADVANCED
|
depends on NETFILTER_ADVANCED
|
||||||
help
|
help
|
||||||
This option adds a `ECN' match, which allows you to match against
|
This option allows you to match what routing thinks of an address,
|
||||||
the IPv4 and TCP header ECN fields.
|
eg. UNICAST, LOCAL, BROADCAST, ...
|
||||||
|
|
||||||
To compile it as a module, choose M here. If unsure, say N.
|
If you want to compile it as a module, say M here and read
|
||||||
|
<file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
|
||||||
|
|
||||||
config IP_NF_MATCH_AH
|
config IP_NF_MATCH_AH
|
||||||
tristate '"ah" match support'
|
tristate '"ah" match support'
|
||||||
@@ -82,6 +83,16 @@ config IP_NF_MATCH_AH
|
|||||||
|
|
||||||
To compile it as a module, choose M here. If unsure, say N.
|
To compile it as a module, choose M here. If unsure, say N.
|
||||||
|
|
||||||
|
config IP_NF_MATCH_ECN
|
||||||
|
tristate '"ecn" match support'
|
||||||
|
depends on IP_NF_IPTABLES
|
||||||
|
depends on NETFILTER_ADVANCED
|
||||||
|
help
|
||||||
|
This option adds a `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.
|
||||||
|
|
||||||
config IP_NF_MATCH_TTL
|
config IP_NF_MATCH_TTL
|
||||||
tristate '"ttl" match support'
|
tristate '"ttl" match support'
|
||||||
depends on IP_NF_IPTABLES
|
depends on IP_NF_IPTABLES
|
||||||
@@ -92,17 +103,6 @@ config IP_NF_MATCH_TTL
|
|||||||
|
|
||||||
To compile it as a module, choose M here. If unsure, say N.
|
To compile it as a module, choose M here. If unsure, say N.
|
||||||
|
|
||||||
config IP_NF_MATCH_ADDRTYPE
|
|
||||||
tristate '"addrtype" address type match support'
|
|
||||||
depends on IP_NF_IPTABLES
|
|
||||||
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'.
|
|
||||||
|
|
||||||
# `filter', generic and specific targets
|
# `filter', generic and specific targets
|
||||||
config IP_NF_FILTER
|
config IP_NF_FILTER
|
||||||
tristate "Packet filtering"
|
tristate "Packet filtering"
|
||||||
@@ -186,6 +186,17 @@ config IP_NF_TARGET_MASQUERADE
|
|||||||
|
|
||||||
To compile it as a module, choose M here. If unsure, say N.
|
To compile it as a module, choose M here. If unsure, say N.
|
||||||
|
|
||||||
|
config IP_NF_TARGET_NETMAP
|
||||||
|
tristate "NETMAP target support"
|
||||||
|
depends on NF_NAT
|
||||||
|
depends on NETFILTER_ADVANCED
|
||||||
|
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.
|
||||||
|
|
||||||
config IP_NF_TARGET_REDIRECT
|
config IP_NF_TARGET_REDIRECT
|
||||||
tristate "REDIRECT target support"
|
tristate "REDIRECT target support"
|
||||||
depends on NF_NAT
|
depends on NF_NAT
|
||||||
@@ -198,17 +209,6 @@ config IP_NF_TARGET_REDIRECT
|
|||||||
|
|
||||||
To compile it as a module, choose M here. If unsure, say N.
|
To compile it as a module, choose M here. If unsure, say N.
|
||||||
|
|
||||||
config IP_NF_TARGET_NETMAP
|
|
||||||
tristate "NETMAP target support"
|
|
||||||
depends on NF_NAT
|
|
||||||
depends on NETFILTER_ADVANCED
|
|
||||||
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.
|
|
||||||
|
|
||||||
config NF_NAT_SNMP_BASIC
|
config NF_NAT_SNMP_BASIC
|
||||||
tristate "Basic SNMP-ALG support"
|
tristate "Basic SNMP-ALG support"
|
||||||
depends on NF_NAT
|
depends on NF_NAT
|
||||||
@@ -300,6 +300,19 @@ config IP_NF_MANGLE
|
|||||||
|
|
||||||
To compile it as a module, choose M here. If unsure, say N.
|
To compile it as a module, choose M here. If unsure, say N.
|
||||||
|
|
||||||
|
config IP_NF_TARGET_CLUSTERIP
|
||||||
|
tristate "CLUSTERIP target support (EXPERIMENTAL)"
|
||||||
|
depends on IP_NF_MANGLE && EXPERIMENTAL
|
||||||
|
depends on NF_CONNTRACK_IPV4
|
||||||
|
depends on NETFILTER_ADVANCED
|
||||||
|
select NF_CONNTRACK_MARK
|
||||||
|
help
|
||||||
|
The CLUSTERIP target allows you to build load-balancing clusters of
|
||||||
|
network servers without having a dedicated load-balancing
|
||||||
|
router/server/switch.
|
||||||
|
|
||||||
|
To compile it as a module, choose M here. If unsure, say N.
|
||||||
|
|
||||||
config IP_NF_TARGET_ECN
|
config IP_NF_TARGET_ECN
|
||||||
tristate "ECN target support"
|
tristate "ECN target support"
|
||||||
depends on IP_NF_MANGLE
|
depends on IP_NF_MANGLE
|
||||||
@@ -330,19 +343,6 @@ config IP_NF_TARGET_TTL
|
|||||||
|
|
||||||
To compile it as a module, choose M here. If unsure, say N.
|
To compile it as a module, choose M here. If unsure, say N.
|
||||||
|
|
||||||
config IP_NF_TARGET_CLUSTERIP
|
|
||||||
tristate "CLUSTERIP target support (EXPERIMENTAL)"
|
|
||||||
depends on IP_NF_MANGLE && EXPERIMENTAL
|
|
||||||
depends on NF_CONNTRACK_IPV4
|
|
||||||
depends on NETFILTER_ADVANCED
|
|
||||||
select NF_CONNTRACK_MARK
|
|
||||||
help
|
|
||||||
The CLUSTERIP target allows you to build load-balancing clusters of
|
|
||||||
network servers without having a dedicated load-balancing
|
|
||||||
router/server/switch.
|
|
||||||
|
|
||||||
To compile it as a module, choose M here. If unsure, say N.
|
|
||||||
|
|
||||||
# raw + specific targets
|
# raw + specific targets
|
||||||
config IP_NF_RAW
|
config IP_NF_RAW
|
||||||
tristate 'raw table support (required for NOTRACK/TRACE)'
|
tristate 'raw table support (required for NOTRACK/TRACE)'
|
||||||
|
@@ -56,12 +56,32 @@ config IP6_NF_IPTABLES
|
|||||||
To compile it as a module, choose M here. If unsure, say N.
|
To compile it as a module, choose M here. If unsure, say N.
|
||||||
|
|
||||||
# The simple matches.
|
# The simple matches.
|
||||||
config IP6_NF_MATCH_RT
|
config IP6_NF_MATCH_AH
|
||||||
tristate '"rt" Routing header match support'
|
tristate '"ah" match support'
|
||||||
depends on IP6_NF_IPTABLES
|
depends on IP6_NF_IPTABLES
|
||||||
depends on NETFILTER_ADVANCED
|
depends on NETFILTER_ADVANCED
|
||||||
help
|
help
|
||||||
rt matching allows you to match packets based on the routing
|
This module allows one to match AH packets.
|
||||||
|
|
||||||
|
To compile it as a module, choose M here. If unsure, say N.
|
||||||
|
|
||||||
|
config IP6_NF_MATCH_EUI64
|
||||||
|
tristate '"eui64" address check'
|
||||||
|
depends on IP6_NF_IPTABLES
|
||||||
|
depends on NETFILTER_ADVANCED
|
||||||
|
help
|
||||||
|
This module performs checking on the IPv6 source address
|
||||||
|
Compares the last 64 bits with the EUI64 (delivered
|
||||||
|
from the MAC address) address
|
||||||
|
|
||||||
|
To compile it as a module, choose M here. If unsure, say N.
|
||||||
|
|
||||||
|
config IP6_NF_MATCH_FRAG
|
||||||
|
tristate '"frag" Fragmentation header match support'
|
||||||
|
depends on IP6_NF_IPTABLES
|
||||||
|
depends on NETFILTER_ADVANCED
|
||||||
|
help
|
||||||
|
frag matching allows you to match packets based on the fragmentation
|
||||||
header of the packet.
|
header of the packet.
|
||||||
|
|
||||||
To compile it as a module, choose M here. If unsure, say N.
|
To compile it as a module, choose M here. If unsure, say N.
|
||||||
@@ -76,16 +96,6 @@ config IP6_NF_MATCH_OPTS
|
|||||||
|
|
||||||
To compile it as a module, choose M here. If unsure, say N.
|
To compile it as a module, choose M here. If unsure, say N.
|
||||||
|
|
||||||
config IP6_NF_MATCH_FRAG
|
|
||||||
tristate '"frag" Fragmentation header match support'
|
|
||||||
depends on IP6_NF_IPTABLES
|
|
||||||
depends on NETFILTER_ADVANCED
|
|
||||||
help
|
|
||||||
frag matching allows you to match packets based on the fragmentation
|
|
||||||
header of the packet.
|
|
||||||
|
|
||||||
To compile it as a module, choose M here. If unsure, say N.
|
|
||||||
|
|
||||||
config IP6_NF_MATCH_HL
|
config IP6_NF_MATCH_HL
|
||||||
tristate '"hl" match support'
|
tristate '"hl" match support'
|
||||||
depends on IP6_NF_IPTABLES
|
depends on IP6_NF_IPTABLES
|
||||||
@@ -106,15 +116,6 @@ config IP6_NF_MATCH_IPV6HEADER
|
|||||||
|
|
||||||
To compile it as a module, choose M here. If unsure, say N.
|
To compile it as a module, choose M here. If unsure, say N.
|
||||||
|
|
||||||
config IP6_NF_MATCH_AH
|
|
||||||
tristate '"ah" match support'
|
|
||||||
depends on IP6_NF_IPTABLES
|
|
||||||
depends on NETFILTER_ADVANCED
|
|
||||||
help
|
|
||||||
This module allows one to match AH packets.
|
|
||||||
|
|
||||||
To compile it as a module, choose M here. If unsure, say N.
|
|
||||||
|
|
||||||
config IP6_NF_MATCH_MH
|
config IP6_NF_MATCH_MH
|
||||||
tristate '"mh" match support'
|
tristate '"mh" match support'
|
||||||
depends on IP6_NF_IPTABLES
|
depends on IP6_NF_IPTABLES
|
||||||
@@ -124,14 +125,13 @@ config IP6_NF_MATCH_MH
|
|||||||
|
|
||||||
To compile it as a module, choose M here. If unsure, say N.
|
To compile it as a module, choose M here. If unsure, say N.
|
||||||
|
|
||||||
config IP6_NF_MATCH_EUI64
|
config IP6_NF_MATCH_RT
|
||||||
tristate '"eui64" address check'
|
tristate '"rt" Routing header match support'
|
||||||
depends on IP6_NF_IPTABLES
|
depends on IP6_NF_IPTABLES
|
||||||
depends on NETFILTER_ADVANCED
|
depends on NETFILTER_ADVANCED
|
||||||
help
|
help
|
||||||
This module performs checking on the IPv6 source address
|
rt matching allows you to match packets based on the routing
|
||||||
Compares the last 64 bits with the EUI64 (delivered
|
header of the packet.
|
||||||
from the MAC address) address
|
|
||||||
|
|
||||||
To compile it as a module, choose M here. If unsure, say N.
|
To compile it as a module, choose M here. If unsure, say N.
|
||||||
|
|
||||||
|
@@ -340,6 +340,18 @@ config NETFILTER_XT_TARGET_CONNMARK
|
|||||||
<file:Documentation/kbuild/modules.txt>. The module will be called
|
<file:Documentation/kbuild/modules.txt>. The module will be called
|
||||||
ipt_CONNMARK.ko. If unsure, say `N'.
|
ipt_CONNMARK.ko. If unsure, say `N'.
|
||||||
|
|
||||||
|
config NETFILTER_XT_TARGET_CONNSECMARK
|
||||||
|
tristate '"CONNSECMARK" target support'
|
||||||
|
depends on NETFILTER_XTABLES && NF_CONNTRACK && NF_CONNTRACK_SECMARK
|
||||||
|
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.
|
||||||
|
|
||||||
config NETFILTER_XT_TARGET_DSCP
|
config NETFILTER_XT_TARGET_DSCP
|
||||||
tristate '"DSCP" and "TOS" target support'
|
tristate '"DSCP" and "TOS" target support'
|
||||||
depends on NETFILTER_XTABLES
|
depends on NETFILTER_XTABLES
|
||||||
@@ -371,18 +383,6 @@ config NETFILTER_XT_TARGET_MARK
|
|||||||
|
|
||||||
To compile it as a module, choose M here. If unsure, say N.
|
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
|
|
||||||
depends on NETFILTER_ADVANCED
|
|
||||||
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.
|
|
||||||
|
|
||||||
config NETFILTER_XT_TARGET_NFLOG
|
config NETFILTER_XT_TARGET_NFLOG
|
||||||
tristate '"NFLOG" target support'
|
tristate '"NFLOG" target support'
|
||||||
depends on NETFILTER_XTABLES
|
depends on NETFILTER_XTABLES
|
||||||
@@ -395,6 +395,18 @@ config NETFILTER_XT_TARGET_NFLOG
|
|||||||
|
|
||||||
To compile it as a module, choose M here. If unsure, say N.
|
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
|
||||||
|
depends on NETFILTER_ADVANCED
|
||||||
|
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.
|
||||||
|
|
||||||
config NETFILTER_XT_TARGET_NOTRACK
|
config NETFILTER_XT_TARGET_NOTRACK
|
||||||
tristate '"NOTRACK" target support'
|
tristate '"NOTRACK" target support'
|
||||||
depends on NETFILTER_XTABLES
|
depends on NETFILTER_XTABLES
|
||||||
@@ -459,18 +471,6 @@ config NETFILTER_XT_TARGET_SECMARK
|
|||||||
|
|
||||||
To compile it as a module, choose M here. If unsure, say N.
|
To compile it as a module, choose M here. If unsure, say N.
|
||||||
|
|
||||||
config NETFILTER_XT_TARGET_CONNSECMARK
|
|
||||||
tristate '"CONNSECMARK" target support'
|
|
||||||
depends on NETFILTER_XTABLES && NF_CONNTRACK && NF_CONNTRACK_SECMARK
|
|
||||||
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.
|
|
||||||
|
|
||||||
config NETFILTER_XT_TARGET_TCPMSS
|
config NETFILTER_XT_TARGET_TCPMSS
|
||||||
tristate '"TCPMSS" target support'
|
tristate '"TCPMSS" target support'
|
||||||
depends on NETFILTER_XTABLES && (IPV6 || IPV6=n)
|
depends on NETFILTER_XTABLES && (IPV6 || IPV6=n)
|
||||||
@@ -607,6 +607,21 @@ config NETFILTER_XT_MATCH_ESP
|
|||||||
|
|
||||||
To compile it as a module, choose M here. If unsure, say N.
|
To compile it as a module, choose M here. If unsure, say N.
|
||||||
|
|
||||||
|
config NETFILTER_XT_MATCH_HASHLIMIT
|
||||||
|
tristate '"hashlimit" match support'
|
||||||
|
depends on NETFILTER_XTABLES && (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
|
||||||
|
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.
|
||||||
|
|
||||||
config NETFILTER_XT_MATCH_HELPER
|
config NETFILTER_XT_MATCH_HELPER
|
||||||
tristate '"helper" match support'
|
tristate '"helper" match support'
|
||||||
depends on NETFILTER_XTABLES
|
depends on NETFILTER_XTABLES
|
||||||
@@ -671,6 +686,17 @@ config NETFILTER_XT_MATCH_MARK
|
|||||||
|
|
||||||
To compile it as a module, choose M here. If unsure, say N.
|
To compile it as a module, choose M here. If unsure, say N.
|
||||||
|
|
||||||
|
config NETFILTER_XT_MATCH_MULTIPORT
|
||||||
|
tristate '"multiport" Multiple port match support'
|
||||||
|
depends on NETFILTER_XTABLES
|
||||||
|
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.
|
||||||
|
|
||||||
config NETFILTER_XT_MATCH_OWNER
|
config NETFILTER_XT_MATCH_OWNER
|
||||||
tristate '"owner" match support'
|
tristate '"owner" match support'
|
||||||
depends on NETFILTER_XTABLES
|
depends on NETFILTER_XTABLES
|
||||||
@@ -691,17 +717,6 @@ config NETFILTER_XT_MATCH_POLICY
|
|||||||
|
|
||||||
To compile it as a module, choose M here. If unsure, say N.
|
To compile it as a module, choose M here. If unsure, say N.
|
||||||
|
|
||||||
config NETFILTER_XT_MATCH_MULTIPORT
|
|
||||||
tristate '"multiport" Multiple port match support'
|
|
||||||
depends on NETFILTER_XTABLES
|
|
||||||
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.
|
|
||||||
|
|
||||||
config NETFILTER_XT_MATCH_PHYSDEV
|
config NETFILTER_XT_MATCH_PHYSDEV
|
||||||
tristate '"physdev" match support'
|
tristate '"physdev" match support'
|
||||||
depends on NETFILTER_XTABLES && BRIDGE && BRIDGE_NETFILTER
|
depends on NETFILTER_XTABLES && BRIDGE && BRIDGE_NETFILTER
|
||||||
@@ -884,20 +899,5 @@ config NETFILTER_XT_MATCH_U32
|
|||||||
|
|
||||||
Details and examples are in the kernel module source.
|
Details and examples are in the kernel module source.
|
||||||
|
|
||||||
config NETFILTER_XT_MATCH_HASHLIMIT
|
|
||||||
tristate '"hashlimit" match support'
|
|
||||||
depends on NETFILTER_XTABLES && (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
|
|
||||||
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.
|
|
||||||
|
|
||||||
endmenu
|
endmenu
|
||||||
|
|
||||||
|
Reference in New Issue
Block a user