2005-04-16 22:20:36 +00:00
|
|
|
#
|
|
|
|
# IP netfilter configuration
|
|
|
|
#
|
|
|
|
|
|
|
|
menu "IP: Netfilter Configuration"
|
|
|
|
depends on 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
|
|
|
config NF_CONNTRACK_IPV4
|
2007-01-04 20:16:06 +00:00
|
|
|
tristate "IPv4 connection tracking support (required for NAT)"
|
|
|
|
depends on NF_CONNTRACK
|
2007-12-18 06:47:05 +00: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 00:38:16 +00:00
|
|
|
---help---
|
|
|
|
Connection tracking keeps a record of what packets have passed
|
|
|
|
through your machine, in order to figure out how they are related
|
|
|
|
into connections.
|
|
|
|
|
|
|
|
This is IPv4 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-11-29 01:35:20 +00:00
|
|
|
config NF_CONNTRACK_PROC_COMPAT
|
|
|
|
bool "proc/sysctl compatibility with old connection tracking"
|
2006-12-03 06:04:24 +00:00
|
|
|
depends on NF_CONNTRACK_IPV4
|
2006-11-29 01:35:20 +00:00
|
|
|
default y
|
|
|
|
help
|
|
|
|
This option enables /proc and sysctl compatibility with the old
|
|
|
|
layer 3 dependant connection tracking. This is needed to keep
|
|
|
|
old programs that have not been adapted to the new names working.
|
|
|
|
|
|
|
|
If unsure, say Y.
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
config IP_NF_QUEUE
|
2005-08-10 02:44:15 +00:00
|
|
|
tristate "IP Userspace queueing via NETLINK (OBSOLETE)"
|
2007-12-18 06:47:05 +00:00
|
|
|
depends on NETFILTER_ADVANCED
|
2005-04-16 22:20:36 +00:00
|
|
|
help
|
|
|
|
Netfilter has the ability to queue packets to user space: the
|
|
|
|
netlink device can be used to access them using this driver.
|
|
|
|
|
2005-08-10 02:44:15 +00:00
|
|
|
This option enables the old IPv4-only "ip_queue" implementation
|
|
|
|
which has been obsoleted by the new "nfnetlink_queue" code (see
|
|
|
|
CONFIG_NETFILTER_NETLINK_QUEUE).
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
|
|
config IP_NF_IPTABLES
|
|
|
|
tristate "IP tables support (required for filtering/masq/NAT)"
|
2007-12-18 06:47:05 +00:00
|
|
|
default m if NETFILTER_ADVANCED=n
|
2007-02-12 19:15:02 +00:00
|
|
|
select NETFILTER_XTABLES
|
2005-04-16 22:20:36 +00:00
|
|
|
help
|
|
|
|
iptables is a general, extensible packet identification framework.
|
|
|
|
The packet filtering and full NAT (masquerading, port forwarding,
|
|
|
|
etc) subsystems now use this: say `Y' or `M' here if you want to use
|
|
|
|
either of those.
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
|
|
# The matches.
|
|
|
|
config IP_NF_MATCH_RECENT
|
2007-12-05 07:31:59 +00:00
|
|
|
tristate '"recent" match support'
|
2005-04-16 22:20:36 +00:00
|
|
|
depends on IP_NF_IPTABLES
|
2007-12-18 06:47:05 +00:00
|
|
|
depends on NETFILTER_ADVANCED
|
2005-04-16 22:20:36 +00:00
|
|
|
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/>
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
|
|
config IP_NF_MATCH_ECN
|
2007-12-05 07:31:59 +00:00
|
|
|
tristate '"ecn" match support'
|
2005-04-16 22:20:36 +00:00
|
|
|
depends on IP_NF_IPTABLES
|
2007-12-18 06:47:05 +00:00
|
|
|
depends on NETFILTER_ADVANCED
|
2005-04-16 22:20:36 +00:00
|
|
|
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.
|
|
|
|
|
2006-04-01 10:22:30 +00:00
|
|
|
config IP_NF_MATCH_AH
|
2007-12-05 07:31:59 +00:00
|
|
|
tristate '"ah" match support'
|
2005-04-16 22:20:36 +00:00
|
|
|
depends on IP_NF_IPTABLES
|
2007-12-18 06:47:05 +00:00
|
|
|
depends on NETFILTER_ADVANCED
|
2005-04-16 22:20:36 +00:00
|
|
|
help
|
2006-04-01 10:22:30 +00:00
|
|
|
This match extension allows you to match a range of SPIs
|
|
|
|
inside AH header of IPSec packets.
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
|
|
config IP_NF_MATCH_TTL
|
2007-12-05 07:31:59 +00:00
|
|
|
tristate '"ttl" match support'
|
2005-04-16 22:20:36 +00:00
|
|
|
depends on IP_NF_IPTABLES
|
2007-12-18 06:47:05 +00:00
|
|
|
depends on NETFILTER_ADVANCED
|
2005-04-16 22:20:36 +00:00
|
|
|
help
|
|
|
|
This adds CONFIG_IP_NF_MATCH_TTL option, which enabled the user
|
|
|
|
to match packets by their TTL value.
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
|
|
config IP_NF_MATCH_ADDRTYPE
|
2007-12-05 07:31:59 +00:00
|
|
|
tristate '"addrtype" address type match support'
|
2005-04-16 22:20:36 +00:00
|
|
|
depends on IP_NF_IPTABLES
|
2007-12-18 06:47:05 +00:00
|
|
|
depends on NETFILTER_ADVANCED
|
2005-04-16 22:20:36 +00:00
|
|
|
help
|
|
|
|
This option allows you to match what routing thinks of an address,
|
|
|
|
eg. UNICAST, LOCAL, BROADCAST, ...
|
2007-12-18 06:47:05 +00:00
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
If you want to compile it as a module, say M here and read
|
2007-10-30 20:37:19 +00:00
|
|
|
<file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
# `filter', generic and specific targets
|
|
|
|
config IP_NF_FILTER
|
|
|
|
tristate "Packet filtering"
|
|
|
|
depends on IP_NF_IPTABLES
|
2007-12-18 06:47:05 +00:00
|
|
|
default m if NETFILTER_ADVANCED=n
|
2005-04-16 22:20:36 +00:00
|
|
|
help
|
|
|
|
Packet filtering defines a table `filter', which has a series of
|
|
|
|
rules for simple packet filtering at local input, forwarding and
|
|
|
|
local output. See the man page for iptables(8).
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
|
|
config IP_NF_TARGET_REJECT
|
|
|
|
tristate "REJECT target support"
|
|
|
|
depends on IP_NF_FILTER
|
2007-12-18 06:47:05 +00:00
|
|
|
default m if NETFILTER_ADVANCED=n
|
2005-04-16 22:20:36 +00:00
|
|
|
help
|
|
|
|
The REJECT target allows a filtering rule to specify that an ICMP
|
|
|
|
error should be issued in response to an incoming packet, rather
|
|
|
|
than silently being dropped.
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
|
|
config IP_NF_TARGET_LOG
|
|
|
|
tristate "LOG target support"
|
|
|
|
depends on IP_NF_IPTABLES
|
2007-12-18 06:47:05 +00:00
|
|
|
default m if NETFILTER_ADVANCED=n
|
2005-04-16 22:20:36 +00:00
|
|
|
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.
|
|
|
|
|
|
|
|
config IP_NF_TARGET_ULOG
|
2006-04-25 00:15:54 +00:00
|
|
|
tristate "ULOG target support"
|
2005-04-16 22:20:36 +00:00
|
|
|
depends on IP_NF_IPTABLES
|
2007-12-18 06:47:05 +00:00
|
|
|
default m if NETFILTER_ADVANCED=n
|
2005-04-16 22:20:36 +00:00
|
|
|
---help---
|
2005-10-11 03:51:53 +00:00
|
|
|
|
|
|
|
This option enables the old IPv4-only "ipt_ULOG" implementation
|
|
|
|
which has been obsoleted by the new "nfnetlink_log" code (see
|
|
|
|
CONFIG_NETFILTER_NETLINK_LOG).
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
This option adds a `ULOG' target, which allows you to create rules in
|
|
|
|
any iptables table. The packet is passed to a userspace logging
|
|
|
|
daemon using netlink multicast sockets; unlike the LOG target
|
|
|
|
which can only be viewed through syslog.
|
|
|
|
|
2006-10-03 20:34:14 +00:00
|
|
|
The appropriate userspace logging daemon (ulogd) may be obtained from
|
2005-04-16 22:20:36 +00:00
|
|
|
<http://www.gnumonks.org/projects/ulogd/>
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
2006-12-03 06:07:13 +00:00
|
|
|
# NAT + specific targets: nf_conntrack
|
|
|
|
config NF_NAT
|
|
|
|
tristate "Full NAT"
|
2006-12-12 08:28:09 +00:00
|
|
|
depends on IP_NF_IPTABLES && NF_CONNTRACK_IPV4
|
2007-12-18 06:47:05 +00:00
|
|
|
default m if NETFILTER_ADVANCED=n
|
2006-12-03 06:07:13 +00:00
|
|
|
help
|
|
|
|
The Full NAT option allows masquerading, port forwarding and other
|
|
|
|
forms of full Network Address Port Translation. It is controlled by
|
|
|
|
the `nat' table in iptables: see the man page for iptables(8).
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
|
|
config NF_NAT_NEEDED
|
|
|
|
bool
|
|
|
|
depends on NF_NAT
|
2005-04-16 22:20:36 +00:00
|
|
|
default y
|
|
|
|
|
|
|
|
config IP_NF_TARGET_MASQUERADE
|
|
|
|
tristate "MASQUERADE target support"
|
2007-03-14 23:37:25 +00:00
|
|
|
depends on NF_NAT
|
2007-12-18 06:47:05 +00:00
|
|
|
default m if NETFILTER_ADVANCED=n
|
2005-04-16 22:20:36 +00:00
|
|
|
help
|
|
|
|
Masquerading is a special case of NAT: all outgoing connections are
|
|
|
|
changed to seem to come from a particular interface's address, and
|
|
|
|
if the interface goes down, those connections are lost. This is
|
|
|
|
only useful for dialup accounts with dynamic IP address (ie. your IP
|
|
|
|
address will be different on next dialup).
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
|
|
config IP_NF_TARGET_REDIRECT
|
|
|
|
tristate "REDIRECT target support"
|
2007-03-14 23:37:25 +00:00
|
|
|
depends on NF_NAT
|
2007-12-18 06:47:05 +00:00
|
|
|
depends on NETFILTER_ADVANCED
|
2005-04-16 22:20:36 +00:00
|
|
|
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.
|
|
|
|
|
|
|
|
config IP_NF_TARGET_NETMAP
|
|
|
|
tristate "NETMAP target support"
|
2007-03-14 23:37:25 +00:00
|
|
|
depends on NF_NAT
|
2007-12-18 06:47:05 +00:00
|
|
|
depends on NETFILTER_ADVANCED
|
2005-04-16 22:20:36 +00:00
|
|
|
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. It is similar to Fast NAT, except that
|
|
|
|
Netfilter's connection tracking doesn't work well with Fast NAT.
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
2006-12-03 06:10:34 +00:00
|
|
|
config NF_NAT_SNMP_BASIC
|
2008-01-15 07:31:36 +00:00
|
|
|
tristate "Basic SNMP-ALG support"
|
|
|
|
depends on NF_NAT
|
2007-12-18 06:47:05 +00:00
|
|
|
depends on NETFILTER_ADVANCED
|
2006-12-03 06:10:34 +00:00
|
|
|
---help---
|
|
|
|
|
|
|
|
This module implements an Application Layer Gateway (ALG) for
|
|
|
|
SNMP payloads. In conjunction with NAT, it allows a network
|
2005-04-16 22:20:36 +00:00
|
|
|
management system to access multiple private networks with
|
|
|
|
conflicting addresses. It works by modifying IP addresses
|
|
|
|
inside SNMP payloads to match IP-layer NAT mapping.
|
|
|
|
|
|
|
|
This is the "basic" form of SNMP-ALG, as described in RFC 2962
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
2006-12-03 06:07:44 +00:00
|
|
|
# If they want FTP, set to $CONFIG_IP_NF_NAT (m or y),
|
|
|
|
# or $CONFIG_IP_NF_FTP (m or y), whichever is weaker.
|
|
|
|
# From kconfig-language.txt:
|
|
|
|
#
|
|
|
|
# <expr> '&&' <expr> (6)
|
|
|
|
#
|
|
|
|
# (6) Returns the result of min(/expr/, /expr/).
|
2006-12-03 06:09:41 +00:00
|
|
|
config NF_NAT_PROTO_GRE
|
|
|
|
tristate
|
|
|
|
depends on NF_NAT && NF_CT_PROTO_GRE
|
|
|
|
|
2006-12-03 06:07:44 +00:00
|
|
|
config NF_NAT_FTP
|
|
|
|
tristate
|
|
|
|
depends on IP_NF_IPTABLES && NF_CONNTRACK && NF_NAT
|
|
|
|
default NF_NAT && NF_CONNTRACK_FTP
|
|
|
|
|
2006-12-03 06:09:06 +00:00
|
|
|
config NF_NAT_IRC
|
|
|
|
tristate
|
|
|
|
depends on IP_NF_IPTABLES && NF_CONNTRACK && NF_NAT
|
|
|
|
default NF_NAT && NF_CONNTRACK_IRC
|
|
|
|
|
2006-12-03 06:10:18 +00:00
|
|
|
config NF_NAT_TFTP
|
|
|
|
tristate
|
|
|
|
depends on IP_NF_IPTABLES && NF_CONNTRACK && NF_NAT
|
|
|
|
default NF_NAT && NF_CONNTRACK_TFTP
|
|
|
|
|
2006-12-03 06:08:26 +00:00
|
|
|
config NF_NAT_AMANDA
|
|
|
|
tristate
|
|
|
|
depends on IP_NF_IPTABLES && NF_CONNTRACK && NF_NAT
|
|
|
|
default NF_NAT && NF_CONNTRACK_AMANDA
|
|
|
|
|
2006-12-03 06:09:41 +00:00
|
|
|
config NF_NAT_PPTP
|
|
|
|
tristate
|
|
|
|
depends on IP_NF_IPTABLES && NF_CONNTRACK && NF_NAT
|
|
|
|
default NF_NAT && NF_CONNTRACK_PPTP
|
|
|
|
select NF_NAT_PROTO_GRE
|
|
|
|
|
2006-12-03 06:08:46 +00:00
|
|
|
config NF_NAT_H323
|
|
|
|
tristate
|
|
|
|
depends on IP_NF_IPTABLES && NF_CONNTRACK && NF_NAT
|
|
|
|
default NF_NAT && NF_CONNTRACK_H323
|
|
|
|
|
2006-12-03 06:09:57 +00:00
|
|
|
config NF_NAT_SIP
|
|
|
|
tristate
|
|
|
|
depends on IP_NF_IPTABLES && NF_CONNTRACK && NF_NAT
|
|
|
|
default NF_NAT && NF_CONNTRACK_SIP
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
# mangle + specific targets
|
|
|
|
config IP_NF_MANGLE
|
|
|
|
tristate "Packet mangling"
|
|
|
|
depends on IP_NF_IPTABLES
|
2007-12-18 06:47:05 +00:00
|
|
|
default m if NETFILTER_ADVANCED=n
|
2005-04-16 22:20:36 +00:00
|
|
|
help
|
|
|
|
This option adds a `mangle' table to iptables: see the man page for
|
|
|
|
iptables(8). This table is used for various packet alterations
|
|
|
|
which can effect how the packet is routed.
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
|
|
config IP_NF_TARGET_ECN
|
|
|
|
tristate "ECN target support"
|
|
|
|
depends on IP_NF_MANGLE
|
2007-12-18 06:47:05 +00:00
|
|
|
depends on NETFILTER_ADVANCED
|
2005-04-16 22:20:36 +00:00
|
|
|
---help---
|
|
|
|
This option adds a `ECN' target, which can be used in the iptables mangle
|
|
|
|
table.
|
|
|
|
|
|
|
|
You can use this target to remove the ECN bits from the IPv4 header of
|
|
|
|
an IP packet. This is particularly useful, if you need to work around
|
|
|
|
existing ECN blackholes on the internet, but don't want to disable
|
|
|
|
ECN support in general.
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
2005-08-28 05:37:03 +00:00
|
|
|
config IP_NF_TARGET_TTL
|
|
|
|
tristate 'TTL target support'
|
|
|
|
depends on IP_NF_MANGLE
|
2007-12-18 06:47:05 +00:00
|
|
|
depends on NETFILTER_ADVANCED
|
2005-08-28 05:37:03 +00:00
|
|
|
help
|
|
|
|
This option adds a `TTL' target, which enables the user to modify
|
|
|
|
the TTL value of the IP header.
|
|
|
|
|
|
|
|
While it is safe to decrement/lower the TTL, this target also enables
|
|
|
|
functionality to increment and set the TTL value of the IP header to
|
|
|
|
arbitrary values. This is EXTREMELY DANGEROUS since you can easily
|
|
|
|
create immortal packets that loop forever on the network.
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
config IP_NF_TARGET_CLUSTERIP
|
|
|
|
tristate "CLUSTERIP target support (EXPERIMENTAL)"
|
2005-11-21 05:09:55 +00:00
|
|
|
depends on IP_NF_MANGLE && EXPERIMENTAL
|
2007-03-14 23:37:25 +00:00
|
|
|
depends on NF_CONNTRACK_IPV4
|
2007-12-18 06:47:05 +00:00
|
|
|
depends on NETFILTER_ADVANCED
|
2007-03-14 23:37:25 +00:00
|
|
|
select NF_CONNTRACK_MARK
|
2005-04-16 22:20:36 +00:00
|
|
|
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
|
|
|
|
config IP_NF_RAW
|
|
|
|
tristate 'raw table support (required for NOTRACK/TRACE)'
|
|
|
|
depends on IP_NF_IPTABLES
|
2007-12-18 06:47:05 +00:00
|
|
|
depends on NETFILTER_ADVANCED
|
2005-04-16 22:20:36 +00:00
|
|
|
help
|
|
|
|
This option adds a `raw' table to iptables. This table is the very
|
|
|
|
first in the netfilter framework and hooks in at the PREROUTING
|
|
|
|
and OUTPUT chains.
|
|
|
|
|
|
|
|
If you want to compile it as a module, say M here and read
|
2007-10-30 20:37:19 +00:00
|
|
|
<file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
# ARP tables
|
|
|
|
config IP_NF_ARPTABLES
|
|
|
|
tristate "ARP tables support"
|
2007-02-12 19:15:02 +00:00
|
|
|
select NETFILTER_XTABLES
|
2007-12-18 06:47:05 +00:00
|
|
|
depends on NETFILTER_ADVANCED
|
2005-04-16 22:20:36 +00:00
|
|
|
help
|
|
|
|
arptables is a general, extensible packet identification framework.
|
|
|
|
The ARP packet filtering and mangling (manipulation)subsystems
|
|
|
|
use this: say Y or M here if you want to use either of those.
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
|
|
config IP_NF_ARPFILTER
|
|
|
|
tristate "ARP packet filtering"
|
|
|
|
depends on IP_NF_ARPTABLES
|
|
|
|
help
|
|
|
|
ARP packet filtering defines a table `filter', which has a series of
|
|
|
|
rules for simple ARP packet filtering at local input and
|
|
|
|
local output. On a bridge, you can also specify filtering rules
|
|
|
|
for forwarded ARP packets. See the man page for arptables(8).
|
|
|
|
|
|
|
|
To compile it as a module, choose M here. If unsure, say N.
|
|
|
|
|
|
|
|
config IP_NF_ARP_MANGLE
|
|
|
|
tristate "ARP payload mangling"
|
|
|
|
depends on IP_NF_ARPTABLES
|
|
|
|
help
|
|
|
|
Allows altering the ARP packet payload: source and destination
|
|
|
|
hardware and network addresses.
|
|
|
|
|
|
|
|
endmenu
|
|
|
|
|