2005-04-17 00:20:36 +02:00
|
|
|
#
|
|
|
|
# IP configuration
|
|
|
|
#
|
|
|
|
config IP_MULTICAST
|
|
|
|
bool "IP: multicasting"
|
|
|
|
help
|
|
|
|
This is code for addressing several networked computers at once,
|
|
|
|
enlarging your kernel by about 2 KB. You need multicasting if you
|
|
|
|
intend to participate in the MBONE, a high bandwidth network on top
|
|
|
|
of the Internet which carries audio and video broadcasts. More
|
|
|
|
information about the MBONE is on the WWW at
|
2007-02-17 19:49:13 +01:00
|
|
|
<http://www.savetz.com/mbone/>. Information about the multicast
|
2005-04-17 00:20:36 +02:00
|
|
|
capabilities of the various network cards is contained in
|
|
|
|
<file:Documentation/networking/multicast.txt>. For most people, it's
|
|
|
|
safe to say N.
|
|
|
|
|
|
|
|
config IP_ADVANCED_ROUTER
|
|
|
|
bool "IP: advanced router"
|
|
|
|
---help---
|
|
|
|
If you intend to run your Linux box mostly as a router, i.e. as a
|
|
|
|
computer that forwards and redistributes network packets, say Y; you
|
|
|
|
will then be presented with several options that allow more precise
|
|
|
|
control about the routing process.
|
|
|
|
|
|
|
|
The answer to this question won't directly affect the kernel:
|
|
|
|
answering N will just cause the configurator to skip all the
|
|
|
|
questions about advanced routing.
|
|
|
|
|
|
|
|
Note that your box can only act as a router if you enable IP
|
|
|
|
forwarding in your kernel; you can do that by saying Y to "/proc
|
|
|
|
file system support" and "Sysctl support" below and executing the
|
|
|
|
line
|
|
|
|
|
|
|
|
echo "1" > /proc/sys/net/ipv4/ip_forward
|
|
|
|
|
|
|
|
at boot time after the /proc file system has been mounted.
|
|
|
|
|
2009-02-22 09:06:20 +01:00
|
|
|
If you turn on IP forwarding, you should consider the rp_filter, which
|
2005-04-17 00:20:36 +02:00
|
|
|
automatically rejects incoming packets if the routing table entry
|
|
|
|
for their source address doesn't match the network interface they're
|
|
|
|
arriving on. This has security advantages because it prevents the
|
|
|
|
so-called IP spoofing, however it can pose problems if you use
|
|
|
|
asymmetric routing (packets from you to a host take a different path
|
|
|
|
than packets from that host to you) or if you operate a non-routing
|
|
|
|
host which has several IP addresses on different interfaces. To turn
|
2007-05-18 00:02:21 +02:00
|
|
|
rp_filter on use:
|
2005-04-17 00:20:36 +02:00
|
|
|
|
2007-05-18 00:02:21 +02:00
|
|
|
echo 1 > /proc/sys/net/ipv4/conf/<device>/rp_filter
|
2010-08-31 07:50:43 +02:00
|
|
|
or
|
2007-05-18 00:02:21 +02:00
|
|
|
echo 1 > /proc/sys/net/ipv4/conf/all/rp_filter
|
2005-04-17 00:20:36 +02:00
|
|
|
|
2009-02-22 09:06:20 +01:00
|
|
|
Note that some distributions enable it in startup scripts.
|
2009-02-23 05:40:43 +01:00
|
|
|
For details about rp_filter strict and loose mode read
|
|
|
|
<file:Documentation/networking/ip-sysctl.txt>.
|
2009-02-22 09:06:20 +01:00
|
|
|
|
2005-04-17 00:20:36 +02:00
|
|
|
If unsure, say N here.
|
|
|
|
|
2009-02-22 09:07:13 +01:00
|
|
|
choice
|
2005-06-25 02:50:53 +02:00
|
|
|
prompt "Choose IP: FIB lookup algorithm (choose FIB_HASH if unsure)"
|
|
|
|
depends on IP_ADVANCED_ROUTER
|
2005-07-18 22:55:19 +02:00
|
|
|
default ASK_IP_FIB_HASH
|
2005-06-25 02:50:53 +02:00
|
|
|
|
2005-07-18 22:55:19 +02:00
|
|
|
config ASK_IP_FIB_HASH
|
2005-06-25 02:50:53 +02:00
|
|
|
bool "FIB_HASH"
|
|
|
|
---help---
|
2009-02-22 09:07:13 +01:00
|
|
|
Current FIB is very proven and good enough for most users.
|
2005-06-25 02:50:53 +02:00
|
|
|
|
|
|
|
config IP_FIB_TRIE
|
|
|
|
bool "FIB_TRIE"
|
|
|
|
---help---
|
2009-02-22 09:07:13 +01:00
|
|
|
Use new experimental LC-trie as FIB lookup algorithm.
|
|
|
|
This improves lookup performance if you have a large
|
|
|
|
number of routes.
|
|
|
|
|
|
|
|
LC-trie is a longest matching prefix lookup algorithm which
|
|
|
|
performs better than FIB_HASH for large routing tables.
|
|
|
|
But, it consumes more memory and is more complex.
|
|
|
|
|
|
|
|
LC-trie is described in:
|
|
|
|
|
|
|
|
IP-address lookup using LC-tries. Stefan Nilsson and Gunnar Karlsson
|
|
|
|
IEEE Journal on Selected Areas in Communications, 17(6):1083-1092,
|
|
|
|
June 1999
|
|
|
|
|
|
|
|
An experimental study of compression methods for dynamic tries
|
|
|
|
Stefan Nilsson and Matti Tikkanen. Algorithmica, 33(1):19-33, 2002.
|
2010-10-18 11:03:14 +02:00
|
|
|
<http://www.csc.kth.se/~snilsson/software/dyntrie2/>
|
2009-02-22 09:07:13 +01:00
|
|
|
|
2005-06-25 02:50:53 +02:00
|
|
|
endchoice
|
|
|
|
|
|
|
|
config IP_FIB_HASH
|
2005-07-18 22:55:19 +02:00
|
|
|
def_bool ASK_IP_FIB_HASH || !IP_ADVANCED_ROUTER
|
2005-06-25 02:50:53 +02:00
|
|
|
|
2008-01-13 06:23:17 +01:00
|
|
|
config IP_FIB_TRIE_STATS
|
|
|
|
bool "FIB TRIE statistics"
|
|
|
|
depends on IP_FIB_TRIE
|
|
|
|
---help---
|
|
|
|
Keep track of statistics on structure of FIB TRIE table.
|
|
|
|
Useful for testing and measuring TRIE performance.
|
|
|
|
|
2005-04-17 00:20:36 +02:00
|
|
|
config IP_MULTIPLE_TABLES
|
|
|
|
bool "IP: policy routing"
|
|
|
|
depends on IP_ADVANCED_ROUTER
|
2006-08-04 12:39:22 +02:00
|
|
|
select FIB_RULES
|
2005-04-17 00:20:36 +02:00
|
|
|
---help---
|
|
|
|
Normally, a router decides what to do with a received packet based
|
|
|
|
solely on the packet's final destination address. If you say Y here,
|
|
|
|
the Linux router will also be able to take the packet's source
|
|
|
|
address into account. Furthermore, the TOS (Type-Of-Service) field
|
|
|
|
of the packet can be used for routing decisions as well.
|
|
|
|
|
|
|
|
If you are interested in this, please see the preliminary
|
|
|
|
documentation at <http://www.compendium.com.ar/policy-routing.txt>
|
|
|
|
and <ftp://post.tepkom.ru/pub/vol2/Linux/docs/advanced-routing.tex>.
|
|
|
|
You will need supporting software from
|
|
|
|
<ftp://ftp.tux.org/pub/net/ip-routing/>.
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
|
|
config IP_ROUTE_MULTIPATH
|
|
|
|
bool "IP: equal cost multipath"
|
|
|
|
depends on IP_ADVANCED_ROUTER
|
|
|
|
help
|
|
|
|
Normally, the routing tables specify a single action to be taken in
|
|
|
|
a deterministic manner for a given packet. If you say Y here
|
|
|
|
however, it becomes possible to attach several actions to a packet
|
|
|
|
pattern, in effect specifying several alternative paths to travel
|
|
|
|
for those packets. The router considers all these paths to be of
|
|
|
|
equal "cost" and chooses one of them in a non-deterministic fashion
|
|
|
|
if a matching packet arrives.
|
|
|
|
|
|
|
|
config IP_ROUTE_VERBOSE
|
|
|
|
bool "IP: verbose route monitoring"
|
|
|
|
depends on IP_ADVANCED_ROUTER
|
|
|
|
help
|
|
|
|
If you say Y here, which is recommended, then the kernel will print
|
|
|
|
verbose messages regarding the routing, for example warnings about
|
|
|
|
received packets which look strange and could be evidence of an
|
|
|
|
attack or a misconfigured system somewhere. The information is
|
|
|
|
handled by the klogd daemon which is responsible for kernel messages
|
|
|
|
("man klogd").
|
|
|
|
|
|
|
|
config IP_PNP
|
|
|
|
bool "IP: kernel level autoconfiguration"
|
|
|
|
help
|
|
|
|
This enables automatic configuration of IP addresses of devices and
|
|
|
|
of the routing table during kernel boot, based on either information
|
|
|
|
supplied on the kernel command line or by BOOTP or RARP protocols.
|
|
|
|
You need to say Y only for diskless machines requiring network
|
|
|
|
access to boot (in which case you want to say Y to "Root file system
|
|
|
|
on NFS" as well), because all other machines configure the network
|
|
|
|
in their startup scripts.
|
|
|
|
|
|
|
|
config IP_PNP_DHCP
|
|
|
|
bool "IP: DHCP support"
|
|
|
|
depends on IP_PNP
|
|
|
|
---help---
|
|
|
|
If you want your Linux box to mount its whole root file system (the
|
|
|
|
one containing the directory /) from some other computer over the
|
|
|
|
net via NFS and you want the IP address of your computer to be
|
|
|
|
discovered automatically at boot time using the DHCP protocol (a
|
|
|
|
special protocol designed for doing this job), say Y here. In case
|
|
|
|
the boot ROM of your network card was designed for booting Linux and
|
|
|
|
does DHCP itself, providing all necessary information on the kernel
|
|
|
|
command line, you can say N here.
|
|
|
|
|
|
|
|
If unsure, say Y. Note that if you want to use DHCP, a DHCP server
|
|
|
|
must be operating on your network. Read
|
2009-10-27 19:41:35 +01:00
|
|
|
<file:Documentation/filesystems/nfs/nfsroot.txt> for details.
|
2005-04-17 00:20:36 +02:00
|
|
|
|
|
|
|
config IP_PNP_BOOTP
|
|
|
|
bool "IP: BOOTP support"
|
|
|
|
depends on IP_PNP
|
|
|
|
---help---
|
|
|
|
If you want your Linux box to mount its whole root file system (the
|
|
|
|
one containing the directory /) from some other computer over the
|
|
|
|
net via NFS and you want the IP address of your computer to be
|
|
|
|
discovered automatically at boot time using the BOOTP protocol (a
|
|
|
|
special protocol designed for doing this job), say Y here. In case
|
|
|
|
the boot ROM of your network card was designed for booting Linux and
|
|
|
|
does BOOTP itself, providing all necessary information on the kernel
|
|
|
|
command line, you can say N here. If unsure, say Y. Note that if you
|
|
|
|
want to use BOOTP, a BOOTP server must be operating on your network.
|
2009-10-27 19:41:35 +01:00
|
|
|
Read <file:Documentation/filesystems/nfs/nfsroot.txt> for details.
|
2005-04-17 00:20:36 +02:00
|
|
|
|
|
|
|
config IP_PNP_RARP
|
|
|
|
bool "IP: RARP support"
|
|
|
|
depends on IP_PNP
|
|
|
|
help
|
|
|
|
If you want your Linux box to mount its whole root file system (the
|
|
|
|
one containing the directory /) from some other computer over the
|
|
|
|
net via NFS and you want the IP address of your computer to be
|
|
|
|
discovered automatically at boot time using the RARP protocol (an
|
|
|
|
older protocol which is being obsoleted by BOOTP and DHCP), say Y
|
|
|
|
here. Note that if you want to use RARP, a RARP server must be
|
2008-04-07 21:59:03 +02:00
|
|
|
operating on your network. Read
|
2009-10-27 19:41:35 +01:00
|
|
|
<file:Documentation/filesystems/nfs/nfsroot.txt> for details.
|
2005-04-17 00:20:36 +02:00
|
|
|
|
|
|
|
# not yet ready..
|
2009-02-22 09:07:13 +01:00
|
|
|
# bool ' IP: ARP support' CONFIG_IP_PNP_ARP
|
2005-04-17 00:20:36 +02:00
|
|
|
config NET_IPIP
|
|
|
|
tristate "IP: tunneling"
|
2006-03-28 11:12:13 +02:00
|
|
|
select INET_TUNNEL
|
2005-04-17 00:20:36 +02:00
|
|
|
---help---
|
|
|
|
Tunneling means encapsulating data of one protocol type within
|
|
|
|
another protocol and sending it over a channel that understands the
|
|
|
|
encapsulating protocol. This particular tunneling driver implements
|
|
|
|
encapsulation of IP within IP, which sounds kind of pointless, but
|
|
|
|
can be useful if you want to make your (or some other) machine
|
|
|
|
appear on a different network than it physically is, or to use
|
|
|
|
mobile-IP facilities (allowing laptops to seamlessly move between
|
|
|
|
networks without changing their IP addresses).
|
|
|
|
|
|
|
|
Saying Y to this option will produce two modules ( = code which can
|
|
|
|
be inserted in and removed from the running kernel whenever you
|
|
|
|
want). Most people won't need this and can say N.
|
|
|
|
|
2010-08-22 08:05:39 +02:00
|
|
|
config NET_IPGRE_DEMUX
|
|
|
|
tristate "IP: GRE demultiplexer"
|
|
|
|
help
|
|
|
|
This is helper module to demultiplex GRE packets on GRE version field criteria.
|
|
|
|
Required by ip_gre and pptp modules.
|
|
|
|
|
2005-04-17 00:20:36 +02:00
|
|
|
config NET_IPGRE
|
|
|
|
tristate "IP: GRE tunnels over IP"
|
2010-10-04 20:56:38 +02:00
|
|
|
depends on (IPV6 || IPV6=n) && NET_IPGRE_DEMUX
|
2005-04-17 00:20:36 +02:00
|
|
|
help
|
|
|
|
Tunneling means encapsulating data of one protocol type within
|
|
|
|
another protocol and sending it over a channel that understands the
|
|
|
|
encapsulating protocol. This particular tunneling driver implements
|
|
|
|
GRE (Generic Routing Encapsulation) and at this time allows
|
|
|
|
encapsulating of IPv4 or IPv6 over existing IPv4 infrastructure.
|
|
|
|
This driver is useful if the other endpoint is a Cisco router: Cisco
|
|
|
|
likes GRE much better than the other Linux tunneling driver ("IP
|
|
|
|
tunneling" above). In addition, GRE allows multicast redistribution
|
|
|
|
through the tunnel.
|
|
|
|
|
|
|
|
config NET_IPGRE_BROADCAST
|
|
|
|
bool "IP: broadcast GRE over IP"
|
|
|
|
depends on IP_MULTICAST && NET_IPGRE
|
|
|
|
help
|
|
|
|
One application of GRE/IP is to construct a broadcast WAN (Wide Area
|
|
|
|
Network), which looks like a normal Ethernet LAN (Local Area
|
|
|
|
Network), but can be distributed all over the Internet. If you want
|
|
|
|
to do that, say Y here and to "IP multicast routing" below.
|
|
|
|
|
|
|
|
config IP_MROUTE
|
|
|
|
bool "IP: multicast routing"
|
|
|
|
depends on IP_MULTICAST
|
|
|
|
help
|
|
|
|
This is used if you want your machine to act as a router for IP
|
|
|
|
packets that have several destination addresses. It is needed on the
|
|
|
|
MBONE, a high bandwidth network on top of the Internet which carries
|
|
|
|
audio and video broadcasts. In order to do that, you would most
|
|
|
|
likely run the program mrouted. Information about the multicast
|
|
|
|
capabilities of the various network cards is contained in
|
|
|
|
<file:Documentation/networking/multicast.txt>. If you haven't heard
|
|
|
|
about it, you don't need it.
|
|
|
|
|
ipv4: ipmr: support multiple tables
This patch adds support for multiple independant multicast routing instances,
named "tables".
Userspace multicast routing daemons can bind to a specific table instance by
issuing a setsockopt call using a new option MRT_TABLE. The table number is
stored in the raw socket data and affects all following ipmr setsockopt(),
getsockopt() and ioctl() calls. By default, a single table (RT_TABLE_DEFAULT)
is created with a default routing rule pointing to it. Newly created pimreg
devices have the table number appended ("pimregX"), with the exception of
devices created in the default table, which are named just "pimreg" for
compatibility reasons.
Packets are directed to a specific table instance using routing rules,
similar to how regular routing rules work. Currently iif, oif and mark
are supported as keys, source and destination addresses could be supported
additionally.
Example usage:
- bind pimd/xorp/... to a specific table:
uint32_t table = 123;
setsockopt(fd, IPPROTO_IP, MRT_TABLE, &table, sizeof(table));
- create routing rules directing packets to the new table:
# ip mrule add iif eth0 lookup 123
# ip mrule add oif eth0 lookup 123
Signed-off-by: Patrick McHardy <kaber@trash.net>
Signed-off-by: David S. Miller <davem@davemloft.net>
2010-04-13 07:03:23 +02:00
|
|
|
config IP_MROUTE_MULTIPLE_TABLES
|
|
|
|
bool "IP: multicast policy routing"
|
2010-04-15 13:29:27 +02:00
|
|
|
depends on IP_MROUTE && IP_ADVANCED_ROUTER
|
ipv4: ipmr: support multiple tables
This patch adds support for multiple independant multicast routing instances,
named "tables".
Userspace multicast routing daemons can bind to a specific table instance by
issuing a setsockopt call using a new option MRT_TABLE. The table number is
stored in the raw socket data and affects all following ipmr setsockopt(),
getsockopt() and ioctl() calls. By default, a single table (RT_TABLE_DEFAULT)
is created with a default routing rule pointing to it. Newly created pimreg
devices have the table number appended ("pimregX"), with the exception of
devices created in the default table, which are named just "pimreg" for
compatibility reasons.
Packets are directed to a specific table instance using routing rules,
similar to how regular routing rules work. Currently iif, oif and mark
are supported as keys, source and destination addresses could be supported
additionally.
Example usage:
- bind pimd/xorp/... to a specific table:
uint32_t table = 123;
setsockopt(fd, IPPROTO_IP, MRT_TABLE, &table, sizeof(table));
- create routing rules directing packets to the new table:
# ip mrule add iif eth0 lookup 123
# ip mrule add oif eth0 lookup 123
Signed-off-by: Patrick McHardy <kaber@trash.net>
Signed-off-by: David S. Miller <davem@davemloft.net>
2010-04-13 07:03:23 +02:00
|
|
|
select FIB_RULES
|
|
|
|
help
|
|
|
|
Normally, a multicast router runs a userspace daemon and decides
|
|
|
|
what to do with a multicast packet based on the source and
|
|
|
|
destination addresses. If you say Y here, the multicast router
|
|
|
|
will also be able to take interfaces and packet marks into
|
|
|
|
account and run multiple instances of userspace daemons
|
|
|
|
simultaneously, each one handling a single table.
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
2005-04-17 00:20:36 +02:00
|
|
|
config IP_PIMSM_V1
|
|
|
|
bool "IP: PIM-SM version 1 support"
|
|
|
|
depends on IP_MROUTE
|
|
|
|
help
|
|
|
|
Kernel side support for Sparse Mode PIM (Protocol Independent
|
|
|
|
Multicast) version 1. This multicast routing protocol is used widely
|
|
|
|
because Cisco supports it. You need special software to use it
|
|
|
|
(pimd-v1). Please see <http://netweb.usc.edu/pim/> for more
|
|
|
|
information about PIM.
|
|
|
|
|
|
|
|
Say Y if you want to use PIM-SM v1. Note that you can say N here if
|
|
|
|
you just want to use Dense Mode PIM.
|
|
|
|
|
|
|
|
config IP_PIMSM_V2
|
|
|
|
bool "IP: PIM-SM version 2 support"
|
|
|
|
depends on IP_MROUTE
|
|
|
|
help
|
|
|
|
Kernel side support for Sparse Mode PIM version 2. In order to use
|
|
|
|
this, you need an experimental routing daemon supporting it (pimd or
|
|
|
|
gated-5). This routing protocol is not used widely, so say N unless
|
|
|
|
you want to play with it.
|
|
|
|
|
|
|
|
config ARPD
|
2009-06-11 21:38:02 +02:00
|
|
|
bool "IP: ARP daemon support"
|
2005-04-17 00:20:36 +02:00
|
|
|
---help---
|
2009-06-11 21:38:02 +02:00
|
|
|
The kernel maintains an internal cache which maps IP addresses to
|
|
|
|
hardware addresses on the local network, so that Ethernet/Token Ring/
|
|
|
|
etc. frames are sent to the proper address on the physical networking
|
|
|
|
layer. Normally, kernel uses the ARP protocol to resolve these
|
|
|
|
mappings.
|
|
|
|
|
|
|
|
Saying Y here adds support to have an user space daemon to do this
|
|
|
|
resolution instead. This is useful for implementing an alternate
|
|
|
|
address resolution protocol (e.g. NHRP on mGRE tunnels) and also for
|
|
|
|
testing purposes.
|
|
|
|
|
|
|
|
If unsure, say N.
|
2005-04-17 00:20:36 +02:00
|
|
|
|
|
|
|
config SYN_COOKIES
|
2010-06-03 02:42:30 +02:00
|
|
|
bool "IP: TCP syncookie support"
|
2005-04-17 00:20:36 +02:00
|
|
|
---help---
|
|
|
|
Normal TCP/IP networking is open to an attack known as "SYN
|
|
|
|
flooding". This denial-of-service attack prevents legitimate remote
|
|
|
|
users from being able to connect to your computer during an ongoing
|
|
|
|
attack and requires very little work from the attacker, who can
|
|
|
|
operate from anywhere on the Internet.
|
|
|
|
|
|
|
|
SYN cookies provide protection against this type of attack. If you
|
|
|
|
say Y here, the TCP/IP stack will use a cryptographic challenge
|
|
|
|
protocol known as "SYN cookies" to enable legitimate users to
|
|
|
|
continue to connect, even when your machine is under attack. There
|
|
|
|
is no need for the legitimate users to change their TCP/IP software;
|
|
|
|
SYN cookies work transparently to them. For technical information
|
|
|
|
about SYN cookies, check out <http://cr.yp.to/syncookies.html>.
|
|
|
|
|
|
|
|
If you are SYN flooded, the source address reported by the kernel is
|
|
|
|
likely to have been forged by the attacker; it is only reported as
|
|
|
|
an aid in tracing the packets to their actual source and should not
|
|
|
|
be taken as absolute truth.
|
|
|
|
|
|
|
|
SYN cookies may prevent correct error reporting on clients when the
|
|
|
|
server is really overloaded. If this happens frequently better turn
|
|
|
|
them off.
|
|
|
|
|
2010-06-03 02:42:30 +02:00
|
|
|
If you say Y here, you can disable SYN cookies at run time by
|
|
|
|
saying Y to "/proc file system support" and
|
2005-04-17 00:20:36 +02:00
|
|
|
"Sysctl support" below and executing the command
|
|
|
|
|
2010-06-03 02:42:30 +02:00
|
|
|
echo 0 > /proc/sys/net/ipv4/tcp_syncookies
|
2005-04-17 00:20:36 +02:00
|
|
|
|
2010-06-03 02:42:30 +02:00
|
|
|
after the /proc file system has been mounted.
|
2005-04-17 00:20:36 +02:00
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
|
|
config INET_AH
|
|
|
|
tristate "IP: AH transformation"
|
|
|
|
select XFRM
|
|
|
|
select CRYPTO
|
|
|
|
select CRYPTO_HMAC
|
|
|
|
select CRYPTO_MD5
|
|
|
|
select CRYPTO_SHA1
|
|
|
|
---help---
|
|
|
|
Support for IPsec AH.
|
|
|
|
|
|
|
|
If unsure, say Y.
|
|
|
|
|
|
|
|
config INET_ESP
|
|
|
|
tristate "IP: ESP transformation"
|
|
|
|
select XFRM
|
|
|
|
select CRYPTO
|
2008-03-04 23:29:21 +01:00
|
|
|
select CRYPTO_AUTHENC
|
2005-04-17 00:20:36 +02:00
|
|
|
select CRYPTO_HMAC
|
|
|
|
select CRYPTO_MD5
|
2006-07-30 07:41:01 +02:00
|
|
|
select CRYPTO_CBC
|
2005-04-17 00:20:36 +02:00
|
|
|
select CRYPTO_SHA1
|
|
|
|
select CRYPTO_DES
|
|
|
|
---help---
|
|
|
|
Support for IPsec ESP.
|
|
|
|
|
|
|
|
If unsure, say Y.
|
|
|
|
|
|
|
|
config INET_IPCOMP
|
|
|
|
tristate "IP: IPComp transformation"
|
2006-03-28 11:12:13 +02:00
|
|
|
select INET_XFRM_TUNNEL
|
2008-07-25 11:54:40 +02:00
|
|
|
select XFRM_IPCOMP
|
2005-04-17 00:20:36 +02:00
|
|
|
---help---
|
|
|
|
Support for IP Payload Compression Protocol (IPComp) (RFC3173),
|
|
|
|
typically needed for IPsec.
|
2009-02-22 09:07:13 +01:00
|
|
|
|
2005-04-17 00:20:36 +02:00
|
|
|
If unsure, say Y.
|
|
|
|
|
2006-03-28 11:12:13 +02:00
|
|
|
config INET_XFRM_TUNNEL
|
|
|
|
tristate
|
|
|
|
select INET_TUNNEL
|
|
|
|
default n
|
|
|
|
|
2005-04-17 00:20:36 +02:00
|
|
|
config INET_TUNNEL
|
2006-03-28 11:12:13 +02:00
|
|
|
tristate
|
|
|
|
default n
|
2005-04-17 00:20:36 +02:00
|
|
|
|
2006-05-28 08:05:54 +02:00
|
|
|
config INET_XFRM_MODE_TRANSPORT
|
|
|
|
tristate "IP: IPsec transport mode"
|
|
|
|
default y
|
|
|
|
select XFRM
|
|
|
|
---help---
|
|
|
|
Support for IPsec transport mode.
|
|
|
|
|
|
|
|
If unsure, say Y.
|
|
|
|
|
|
|
|
config INET_XFRM_MODE_TUNNEL
|
|
|
|
tristate "IP: IPsec tunnel mode"
|
|
|
|
default y
|
|
|
|
select XFRM
|
|
|
|
---help---
|
|
|
|
Support for IPsec tunnel mode.
|
|
|
|
|
|
|
|
If unsure, say Y.
|
|
|
|
|
2006-10-04 08:47:05 +02:00
|
|
|
config INET_XFRM_MODE_BEET
|
|
|
|
tristate "IP: IPsec BEET mode"
|
|
|
|
default y
|
|
|
|
select XFRM
|
|
|
|
---help---
|
|
|
|
Support for IPsec BEET mode.
|
|
|
|
|
|
|
|
If unsure, say Y.
|
|
|
|
|
2007-08-09 07:38:05 +02:00
|
|
|
config INET_LRO
|
2010-10-03 17:37:42 +02:00
|
|
|
tristate "Large Receive Offload (ipv4/tcp)"
|
2009-05-19 06:48:38 +02:00
|
|
|
default y
|
2007-08-09 07:38:05 +02:00
|
|
|
---help---
|
|
|
|
Support for Large Receive Offload (ipv4/tcp).
|
|
|
|
|
|
|
|
If unsure, say Y.
|
|
|
|
|
[INET_DIAG]: Move the tcp_diag interface to the proper place
With this the previous setup is back, i.e. tcp_diag can be built as a module,
as dccp_diag and both share the infrastructure available in inet_diag.
If one selects CONFIG_INET_DIAG as module CONFIG_INET_TCP_DIAG will also be
built as a module, as will CONFIG_INET_DCCP_DIAG, if CONFIG_IP_DCCP was
selected static or as a module, if CONFIG_INET_DIAG is y, being statically
linked CONFIG_INET_TCP_DIAG will follow suit and CONFIG_INET_DCCP_DIAG will be
built in the same manner as CONFIG_IP_DCCP.
Now to aim at UDP, converting it to use inet_hashinfo, so that we can use
iproute2 for UDP sockets as well.
Ah, just to show an example of this new infrastructure working for DCCP :-)
[root@qemu ~]# ./ss -dane
State Recv-Q Send-Q Local Address:Port Peer Address:Port
LISTEN 0 0 *:5001 *:* ino:942 sk:cfd503a0
ESTAB 0 0 127.0.0.1:5001 127.0.0.1:32770 ino:943 sk:cfd50a60
ESTAB 0 0 127.0.0.1:32770 127.0.0.1:5001 ino:947 sk:cfd50700
TIME-WAIT 0 0 127.0.0.1:32769 127.0.0.1:5001 timer:(timewait,3.430ms,0) ino:0 sk:cf209620
Signed-off-by: Arnaldo Carvalho de Melo <acme@mandriva.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2005-08-12 17:59:17 +02:00
|
|
|
config INET_DIAG
|
|
|
|
tristate "INET: socket monitoring interface"
|
2005-04-17 00:20:36 +02:00
|
|
|
default y
|
|
|
|
---help---
|
2005-08-12 17:51:49 +02:00
|
|
|
Support for INET (TCP, DCCP, etc) socket monitoring interface used by
|
|
|
|
native Linux tools such as ss. ss is included in iproute2, currently
|
2010-11-15 20:55:34 +01:00
|
|
|
downloadable at:
|
|
|
|
|
|
|
|
http://www.linuxfoundation.org/collaborate/workgroups/networking/iproute2
|
2009-02-22 09:07:13 +01:00
|
|
|
|
2005-04-17 00:20:36 +02:00
|
|
|
If unsure, say Y.
|
|
|
|
|
[INET_DIAG]: Move the tcp_diag interface to the proper place
With this the previous setup is back, i.e. tcp_diag can be built as a module,
as dccp_diag and both share the infrastructure available in inet_diag.
If one selects CONFIG_INET_DIAG as module CONFIG_INET_TCP_DIAG will also be
built as a module, as will CONFIG_INET_DCCP_DIAG, if CONFIG_IP_DCCP was
selected static or as a module, if CONFIG_INET_DIAG is y, being statically
linked CONFIG_INET_TCP_DIAG will follow suit and CONFIG_INET_DCCP_DIAG will be
built in the same manner as CONFIG_IP_DCCP.
Now to aim at UDP, converting it to use inet_hashinfo, so that we can use
iproute2 for UDP sockets as well.
Ah, just to show an example of this new infrastructure working for DCCP :-)
[root@qemu ~]# ./ss -dane
State Recv-Q Send-Q Local Address:Port Peer Address:Port
LISTEN 0 0 *:5001 *:* ino:942 sk:cfd503a0
ESTAB 0 0 127.0.0.1:5001 127.0.0.1:32770 ino:943 sk:cfd50a60
ESTAB 0 0 127.0.0.1:32770 127.0.0.1:5001 ino:947 sk:cfd50700
TIME-WAIT 0 0 127.0.0.1:32769 127.0.0.1:5001 timer:(timewait,3.430ms,0) ino:0 sk:cf209620
Signed-off-by: Arnaldo Carvalho de Melo <acme@mandriva.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2005-08-12 17:59:17 +02:00
|
|
|
config INET_TCP_DIAG
|
|
|
|
depends on INET_DIAG
|
|
|
|
def_tristate INET_DIAG
|
|
|
|
|
2006-09-25 05:11:58 +02:00
|
|
|
menuconfig TCP_CONG_ADVANCED
|
2005-06-25 03:07:51 +02:00
|
|
|
bool "TCP: advanced congestion control"
|
|
|
|
---help---
|
|
|
|
Support for selection of various TCP congestion control
|
|
|
|
modules.
|
|
|
|
|
|
|
|
Nearly all users can safely say no here, and a safe default
|
2006-09-25 05:13:03 +02:00
|
|
|
selection will be made (CUBIC with new Reno as a fallback).
|
2005-06-25 03:07:51 +02:00
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
2006-09-25 05:11:58 +02:00
|
|
|
if TCP_CONG_ADVANCED
|
2005-06-23 21:23:25 +02:00
|
|
|
|
|
|
|
config TCP_CONG_BIC
|
|
|
|
tristate "Binary Increase Congestion (BIC) control"
|
2006-09-25 05:13:03 +02:00
|
|
|
default m
|
2005-06-23 21:23:25 +02:00
|
|
|
---help---
|
|
|
|
BIC-TCP is a sender-side only change that ensures a linear RTT
|
|
|
|
fairness under large windows while offering both scalability and
|
|
|
|
bounded TCP-friendliness. The protocol combines two schemes
|
|
|
|
called additive increase and binary search increase. When the
|
|
|
|
congestion window is large, additive increase with a large
|
|
|
|
increment ensures linear RTT fairness as well as good
|
|
|
|
scalability. Under small congestion windows, binary search
|
|
|
|
increase provides TCP friendliness.
|
|
|
|
See http://www.csc.ncsu.edu/faculty/rhee/export/bitcp/
|
|
|
|
|
2005-12-14 08:13:28 +01:00
|
|
|
config TCP_CONG_CUBIC
|
|
|
|
tristate "CUBIC TCP"
|
2006-09-25 05:13:03 +02:00
|
|
|
default y
|
2005-12-14 08:13:28 +01:00
|
|
|
---help---
|
|
|
|
This is version 2.0 of BIC-TCP which uses a cubic growth function
|
|
|
|
among other techniques.
|
|
|
|
See http://www.csc.ncsu.edu/faculty/rhee/export/bitcp/cubic-paper.pdf
|
|
|
|
|
2005-06-23 21:24:09 +02:00
|
|
|
config TCP_CONG_WESTWOOD
|
|
|
|
tristate "TCP Westwood+"
|
|
|
|
default m
|
|
|
|
---help---
|
|
|
|
TCP Westwood+ is a sender-side only modification of the TCP Reno
|
|
|
|
protocol stack that optimizes the performance of TCP congestion
|
|
|
|
control. It is based on end-to-end bandwidth estimation to set
|
|
|
|
congestion window and slow start threshold after a congestion
|
|
|
|
episode. Using this estimation, TCP Westwood+ adaptively sets a
|
|
|
|
slow start threshold and a congestion window which takes into
|
|
|
|
account the bandwidth used at the time congestion is experienced.
|
|
|
|
TCP Westwood+ significantly increases fairness wrt TCP Reno in
|
|
|
|
wired networks and throughput over wireless links.
|
|
|
|
|
2005-06-23 21:28:11 +02:00
|
|
|
config TCP_CONG_HTCP
|
|
|
|
tristate "H-TCP"
|
|
|
|
default m
|
|
|
|
---help---
|
|
|
|
H-TCP is a send-side only modifications of the TCP Reno
|
|
|
|
protocol stack that optimizes the performance of TCP
|
|
|
|
congestion control for high speed network links. It uses a
|
|
|
|
modeswitch to change the alpha and beta parameters of TCP Reno
|
|
|
|
based on network conditions and in a way so as to be fair with
|
|
|
|
other Reno and H-TCP flows.
|
|
|
|
|
2005-06-23 21:24:58 +02:00
|
|
|
config TCP_CONG_HSTCP
|
|
|
|
tristate "High Speed TCP"
|
2005-07-12 06:13:56 +02:00
|
|
|
depends on EXPERIMENTAL
|
2005-06-23 21:24:58 +02:00
|
|
|
default n
|
|
|
|
---help---
|
|
|
|
Sally Floyd's High Speed TCP (RFC 3649) congestion control.
|
|
|
|
A modification to TCP's congestion control mechanism for use
|
|
|
|
with large congestion windows. A table indicates how much to
|
|
|
|
increase the congestion window by when an ACK is received.
|
|
|
|
For more detail see http://www.icir.org/floyd/hstcp.html
|
|
|
|
|
[TCP]: Add TCP Hybla congestion control module.
TCP Hybla congestion avoidance.
- "In heterogeneous networks, TCP connections that incorporate a
terrestrial or satellite radio link are greatly disadvantaged with
respect to entirely wired connections, because of their longer round
trip times (RTTs). To cope with this problem, a new TCP proposal, the
TCP Hybla, is presented and discussed in the paper[1]. It stems from an
analytical evaluation of the congestion window dynamics in the TCP
standard versions (Tahoe, Reno, NewReno), which suggests the necessary
modifications to remove the performance dependence on RTT.[...]"[1]
[1]: Carlo Caini, Rosario Firrincieli, "TCP Hybla: a TCP enhancement for
heterogeneous networks",
International Journal of Satellite Communications and Networking
Volume 22, Issue 5 , Pages 547 - 566. September 2004.
Signed-off-by: Daniele Lacamera (root at danielinux.net)net
Signed-off-by: Stephen Hemminger <shemminger@osdl.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2005-06-23 21:26:34 +02:00
|
|
|
config TCP_CONG_HYBLA
|
|
|
|
tristate "TCP-Hybla congestion control algorithm"
|
2005-07-12 06:13:56 +02:00
|
|
|
depends on EXPERIMENTAL
|
[TCP]: Add TCP Hybla congestion control module.
TCP Hybla congestion avoidance.
- "In heterogeneous networks, TCP connections that incorporate a
terrestrial or satellite radio link are greatly disadvantaged with
respect to entirely wired connections, because of their longer round
trip times (RTTs). To cope with this problem, a new TCP proposal, the
TCP Hybla, is presented and discussed in the paper[1]. It stems from an
analytical evaluation of the congestion window dynamics in the TCP
standard versions (Tahoe, Reno, NewReno), which suggests the necessary
modifications to remove the performance dependence on RTT.[...]"[1]
[1]: Carlo Caini, Rosario Firrincieli, "TCP Hybla: a TCP enhancement for
heterogeneous networks",
International Journal of Satellite Communications and Networking
Volume 22, Issue 5 , Pages 547 - 566. September 2004.
Signed-off-by: Daniele Lacamera (root at danielinux.net)net
Signed-off-by: Stephen Hemminger <shemminger@osdl.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2005-06-23 21:26:34 +02:00
|
|
|
default n
|
|
|
|
---help---
|
|
|
|
TCP-Hybla is a sender-side only change that eliminates penalization of
|
|
|
|
long-RTT, large-bandwidth connections, like when satellite legs are
|
2006-10-03 22:34:14 +02:00
|
|
|
involved, especially when sharing a common bottleneck with normal
|
[TCP]: Add TCP Hybla congestion control module.
TCP Hybla congestion avoidance.
- "In heterogeneous networks, TCP connections that incorporate a
terrestrial or satellite radio link are greatly disadvantaged with
respect to entirely wired connections, because of their longer round
trip times (RTTs). To cope with this problem, a new TCP proposal, the
TCP Hybla, is presented and discussed in the paper[1]. It stems from an
analytical evaluation of the congestion window dynamics in the TCP
standard versions (Tahoe, Reno, NewReno), which suggests the necessary
modifications to remove the performance dependence on RTT.[...]"[1]
[1]: Carlo Caini, Rosario Firrincieli, "TCP Hybla: a TCP enhancement for
heterogeneous networks",
International Journal of Satellite Communications and Networking
Volume 22, Issue 5 , Pages 547 - 566. September 2004.
Signed-off-by: Daniele Lacamera (root at danielinux.net)net
Signed-off-by: Stephen Hemminger <shemminger@osdl.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2005-06-23 21:26:34 +02:00
|
|
|
terrestrial connections.
|
|
|
|
|
2005-06-23 21:27:19 +02:00
|
|
|
config TCP_CONG_VEGAS
|
|
|
|
tristate "TCP Vegas"
|
2005-07-12 06:13:56 +02:00
|
|
|
depends on EXPERIMENTAL
|
2005-06-23 21:27:19 +02:00
|
|
|
default n
|
|
|
|
---help---
|
|
|
|
TCP Vegas is a sender-side only change to TCP that anticipates
|
|
|
|
the onset of congestion by estimating the bandwidth. TCP Vegas
|
|
|
|
adjusts the sending rate by modifying the congestion
|
|
|
|
window. TCP Vegas should provide less packet loss, but it is
|
|
|
|
not as aggressive as TCP Reno.
|
|
|
|
|
2005-06-23 21:29:07 +02:00
|
|
|
config TCP_CONG_SCALABLE
|
|
|
|
tristate "Scalable TCP"
|
2005-07-12 06:13:56 +02:00
|
|
|
depends on EXPERIMENTAL
|
2005-06-23 21:29:07 +02:00
|
|
|
default n
|
|
|
|
---help---
|
|
|
|
Scalable TCP is a sender-side only change to TCP which uses a
|
|
|
|
MIMD congestion control algorithm which has some nice scaling
|
|
|
|
properties, though is known to have fairness issues.
|
2007-02-22 04:32:37 +01:00
|
|
|
See http://www.deneholme.net/tom/scalable/
|
2005-06-23 21:28:11 +02:00
|
|
|
|
2006-06-06 02:27:58 +02:00
|
|
|
config TCP_CONG_LP
|
|
|
|
tristate "TCP Low Priority"
|
|
|
|
depends on EXPERIMENTAL
|
|
|
|
default n
|
|
|
|
---help---
|
|
|
|
TCP Low Priority (TCP-LP), a distributed algorithm whose goal is
|
2006-10-03 22:36:44 +02:00
|
|
|
to utilize only the excess network bandwidth as compared to the
|
2006-06-06 02:27:58 +02:00
|
|
|
``fair share`` of bandwidth as targeted by TCP.
|
|
|
|
See http://www-ece.rice.edu/networks/TCP-LP/
|
|
|
|
|
2006-06-06 02:28:30 +02:00
|
|
|
config TCP_CONG_VENO
|
|
|
|
tristate "TCP Veno"
|
|
|
|
depends on EXPERIMENTAL
|
|
|
|
default n
|
|
|
|
---help---
|
|
|
|
TCP Veno is a sender-side only enhancement of TCP to obtain better
|
|
|
|
throughput over wireless networks. TCP Veno makes use of state
|
|
|
|
distinguishing to circumvent the difficult judgment of the packet loss
|
|
|
|
type. TCP Veno cuts down less congestion window in response to random
|
|
|
|
loss packets.
|
2010-10-18 11:03:14 +02:00
|
|
|
See <http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=1177186>
|
2006-06-06 02:28:30 +02:00
|
|
|
|
2007-02-22 09:23:05 +01:00
|
|
|
config TCP_CONG_YEAH
|
|
|
|
tristate "YeAH TCP"
|
|
|
|
depends on EXPERIMENTAL
|
2007-05-17 09:07:47 +02:00
|
|
|
select TCP_CONG_VEGAS
|
2007-02-22 09:23:05 +01:00
|
|
|
default n
|
|
|
|
---help---
|
|
|
|
YeAH-TCP is a sender-side high-speed enabled TCP congestion control
|
|
|
|
algorithm, which uses a mixed loss/delay approach to compute the
|
|
|
|
congestion window. It's design goals target high efficiency,
|
|
|
|
internal, RTT and Reno fairness, resilience to link loss while
|
|
|
|
keeping network elements load as low as possible.
|
|
|
|
|
|
|
|
For further details look here:
|
|
|
|
http://wil.cs.caltech.edu/pfldnet2007/paper/YeAH_TCP.pdf
|
|
|
|
|
2007-04-21 02:07:51 +02:00
|
|
|
config TCP_CONG_ILLINOIS
|
|
|
|
tristate "TCP Illinois"
|
|
|
|
depends on EXPERIMENTAL
|
|
|
|
default n
|
|
|
|
---help---
|
2007-10-20 01:34:40 +02:00
|
|
|
TCP-Illinois is a sender-side modification of TCP Reno for
|
2007-04-21 02:07:51 +02:00
|
|
|
high speed long delay links. It uses round-trip-time to
|
|
|
|
adjust the alpha and beta parameters to achieve a higher average
|
|
|
|
throughput and maintain fairness.
|
|
|
|
|
|
|
|
For further details see:
|
|
|
|
http://www.ews.uiuc.edu/~shaoliu/tcpillinois/index.html
|
|
|
|
|
2006-09-25 05:11:58 +02:00
|
|
|
choice
|
|
|
|
prompt "Default TCP congestion control"
|
2006-09-25 05:13:03 +02:00
|
|
|
default DEFAULT_CUBIC
|
2006-09-25 05:11:58 +02:00
|
|
|
help
|
|
|
|
Select the TCP congestion control that will be used by default
|
|
|
|
for all connections.
|
|
|
|
|
|
|
|
config DEFAULT_BIC
|
|
|
|
bool "Bic" if TCP_CONG_BIC=y
|
|
|
|
|
|
|
|
config DEFAULT_CUBIC
|
|
|
|
bool "Cubic" if TCP_CONG_CUBIC=y
|
|
|
|
|
|
|
|
config DEFAULT_HTCP
|
|
|
|
bool "Htcp" if TCP_CONG_HTCP=y
|
|
|
|
|
2010-03-11 10:57:27 +01:00
|
|
|
config DEFAULT_HYBLA
|
|
|
|
bool "Hybla" if TCP_CONG_HYBLA=y
|
|
|
|
|
2006-09-25 05:11:58 +02:00
|
|
|
config DEFAULT_VEGAS
|
|
|
|
bool "Vegas" if TCP_CONG_VEGAS=y
|
|
|
|
|
2010-03-11 10:57:28 +01:00
|
|
|
config DEFAULT_VENO
|
|
|
|
bool "Veno" if TCP_CONG_VENO=y
|
|
|
|
|
2006-09-25 05:11:58 +02:00
|
|
|
config DEFAULT_WESTWOOD
|
|
|
|
bool "Westwood" if TCP_CONG_WESTWOOD=y
|
|
|
|
|
|
|
|
config DEFAULT_RENO
|
|
|
|
bool "Reno"
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
|
|
endif
|
2005-06-23 21:23:25 +02:00
|
|
|
|
2006-09-25 05:13:03 +02:00
|
|
|
config TCP_CONG_CUBIC
|
2005-06-27 00:20:20 +02:00
|
|
|
tristate
|
2005-06-25 03:07:51 +02:00
|
|
|
depends on !TCP_CONG_ADVANCED
|
|
|
|
default y
|
|
|
|
|
2006-09-25 05:11:58 +02:00
|
|
|
config DEFAULT_TCP_CONG
|
|
|
|
string
|
|
|
|
default "bic" if DEFAULT_BIC
|
|
|
|
default "cubic" if DEFAULT_CUBIC
|
|
|
|
default "htcp" if DEFAULT_HTCP
|
2010-03-11 10:57:27 +01:00
|
|
|
default "hybla" if DEFAULT_HYBLA
|
2006-09-25 05:11:58 +02:00
|
|
|
default "vegas" if DEFAULT_VEGAS
|
|
|
|
default "westwood" if DEFAULT_WESTWOOD
|
2010-03-11 10:57:28 +01:00
|
|
|
default "veno" if DEFAULT_VENO
|
2006-09-25 05:11:58 +02:00
|
|
|
default "reno" if DEFAULT_RENO
|
2006-09-25 05:13:03 +02:00
|
|
|
default "cubic"
|
2006-09-25 05:11:58 +02:00
|
|
|
|
2006-11-15 04:07:45 +01:00
|
|
|
config TCP_MD5SIG
|
|
|
|
bool "TCP: MD5 Signature Option support (RFC2385) (EXPERIMENTAL)"
|
|
|
|
depends on EXPERIMENTAL
|
|
|
|
select CRYPTO
|
|
|
|
select CRYPTO_MD5
|
|
|
|
---help---
|
2007-05-09 07:12:20 +02:00
|
|
|
RFC2385 specifies a method of giving MD5 protection to TCP sessions.
|
2006-11-15 04:07:45 +01:00
|
|
|
Its main (only?) use is to protect BGP sessions between core routers
|
|
|
|
on the Internet.
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|