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, if you also say Y to "Use TOS
- value as routing key" below, the TOS (Type-Of-Service) field of the
- packet can be used for routing decisions as well. In addition, if
- you say Y here and to "Fast network address translation" below,
- the router will also be able to modify source and destination
- addresses of forwarded packets.
+ 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>
If you say Y here, you will be able to specify different routes for
packets with different mark values (see iptables(8), MARK target).
-config IP_ROUTE_NAT
- bool "IP: fast network address translation"
- depends on IP_MULTIPLE_TABLES
- help
- If you say Y here, your router will be able to modify source and
- destination addresses of packets that pass through it, in a manner
- you specify. General information about Network Address Translation
- can be gotten from the document
- <http://www.hasenstein.com/linux-ip-nat/diplom/nat.html>.
-
config IP_ROUTE_MULTIPATH
bool "IP: equal cost multipath"
depends on IP_ADVANCED_ROUTER
equal "cost" and chooses one of them in a non-deterministic fashion
if a matching packet arrives.
-config IP_ROUTE_TOS
- bool "IP: use TOS value as routing key"
- depends on IP_ADVANCED_ROUTER
- help
- The header of every IP packet carries a TOS (Type Of Service) value
- with which the packet requests a certain treatment, e.g. low
- latency (for interactive traffic), high throughput, or high
- reliability. If you say Y here, you will be able to specify
- different routes for packets with different TOS values.
-
config IP_ROUTE_VERBOSE
bool "IP: verbose route monitoring"
depends on IP_ADVANCED_ROUTER
config NET_IPIP
tristate "IP: tunneling"
depends on INET
- select XFRM
+ select INET_TUNNEL
---help---
Tunneling means encapsulating data of one protocol type within
another protocol and sending it over a channel that understands the
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; check out
- <http://anchor.cs.binghamton.edu/~mobileip/LJ/index.html>).
+ 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
config INET_AH
tristate "IP: AH transformation"
+ depends on INET
select XFRM
select CRYPTO
select CRYPTO_HMAC
config INET_ESP
tristate "IP: ESP transformation"
+ depends on INET
select XFRM
select CRYPTO
select CRYPTO_HMAC
config INET_IPCOMP
tristate "IP: IPComp transformation"
+ depends on INET
select XFRM
+ select INET_TUNNEL
select CRYPTO
select CRYPTO_DEFLATE
---help---
- Support for IP Paylod Compression (RFC3173), typically needed
- for IPsec.
+ Support for IP Payload Compression Protocol (IPComp) (RFC3173),
+ typically needed for IPsec.
If unsure, say Y.
+config INET_TUNNEL
+ tristate "IP: tunnel transformation"
+ depends on INET
+ select XFRM
+ ---help---
+ Support for generic IP tunnel transformation, which is required by
+ the IP tunneling module as well as tunnel mode IPComp.
+
+ If unsure, say Y.
+
+config IP_TCPDIAG
+ tristate "IP: TCP socket monitoring interface"
+ depends on INET
+ default y
+ ---help---
+ Support for TCP socket monitoring interface used by native Linux
+ tools such as ss. ss is included in iproute2, currently downloadable
+ at <http://developer.osdl.org/dev/iproute2>. If you want IPv6 support
+ and have selected IPv6 as a module, you need to build this as a
+ module too.
+
+ If unsure, say Y.
+
+config IP_TCPDIAG_IPV6
+ def_bool (IP_TCPDIAG=y && IPV6=y) || (IP_TCPDIAG=m && IPV6)
+
source "net/ipv4/ipvs/Kconfig"