Kconfig 22 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634
  1. #
  2. # IP configuration
  3. #
  4. config IP_MULTICAST
  5. bool "IP: multicasting"
  6. help
  7. This is code for addressing several networked computers at once,
  8. enlarging your kernel by about 2 KB. You need multicasting if you
  9. intend to participate in the MBONE, a high bandwidth network on top
  10. of the Internet which carries audio and video broadcasts. More
  11. information about the MBONE is on the WWW at
  12. <http://www.savetz.com/mbone/>. Information about the multicast
  13. capabilities of the various network cards is contained in
  14. <file:Documentation/networking/multicast.txt>. For most people, it's
  15. safe to say N.
  16. config IP_ADVANCED_ROUTER
  17. bool "IP: advanced router"
  18. ---help---
  19. If you intend to run your Linux box mostly as a router, i.e. as a
  20. computer that forwards and redistributes network packets, say Y; you
  21. will then be presented with several options that allow more precise
  22. control about the routing process.
  23. The answer to this question won't directly affect the kernel:
  24. answering N will just cause the configurator to skip all the
  25. questions about advanced routing.
  26. Note that your box can only act as a router if you enable IP
  27. forwarding in your kernel; you can do that by saying Y to "/proc
  28. file system support" and "Sysctl support" below and executing the
  29. line
  30. echo "1" > /proc/sys/net/ipv4/ip_forward
  31. at boot time after the /proc file system has been mounted.
  32. If you turn on IP forwarding, you will also get the rp_filter, which
  33. automatically rejects incoming packets if the routing table entry
  34. for their source address doesn't match the network interface they're
  35. arriving on. This has security advantages because it prevents the
  36. so-called IP spoofing, however it can pose problems if you use
  37. asymmetric routing (packets from you to a host take a different path
  38. than packets from that host to you) or if you operate a non-routing
  39. host which has several IP addresses on different interfaces. To turn
  40. rp_filter on use:
  41. echo 1 > /proc/sys/net/ipv4/conf/<device>/rp_filter
  42. or
  43. echo 1 > /proc/sys/net/ipv4/conf/all/rp_filter
  44. If unsure, say N here.
  45. choice
  46. prompt "Choose IP: FIB lookup algorithm (choose FIB_HASH if unsure)"
  47. depends on IP_ADVANCED_ROUTER
  48. default ASK_IP_FIB_HASH
  49. config ASK_IP_FIB_HASH
  50. bool "FIB_HASH"
  51. ---help---
  52. Current FIB is very proven and good enough for most users.
  53. config IP_FIB_TRIE
  54. bool "FIB_TRIE"
  55. ---help---
  56. Use new experimental LC-trie as FIB lookup algorithm.
  57. This improves lookup performance if you have a large
  58. number of routes.
  59. LC-trie is a longest matching prefix lookup algorithm which
  60. performs better than FIB_HASH for large routing tables.
  61. But, it consumes more memory and is more complex.
  62. LC-trie is described in:
  63. IP-address lookup using LC-tries. Stefan Nilsson and Gunnar Karlsson
  64. IEEE Journal on Selected Areas in Communications, 17(6):1083-1092, June 1999
  65. An experimental study of compression methods for dynamic tries
  66. Stefan Nilsson and Matti Tikkanen. Algorithmica, 33(1):19-33, 2002.
  67. http://www.nada.kth.se/~snilsson/public/papers/dyntrie2/
  68. endchoice
  69. config IP_FIB_HASH
  70. def_bool ASK_IP_FIB_HASH || !IP_ADVANCED_ROUTER
  71. config IP_MULTIPLE_TABLES
  72. bool "IP: policy routing"
  73. depends on IP_ADVANCED_ROUTER
  74. select FIB_RULES
  75. ---help---
  76. Normally, a router decides what to do with a received packet based
  77. solely on the packet's final destination address. If you say Y here,
  78. the Linux router will also be able to take the packet's source
  79. address into account. Furthermore, the TOS (Type-Of-Service) field
  80. of the packet can be used for routing decisions as well.
  81. If you are interested in this, please see the preliminary
  82. documentation at <http://www.compendium.com.ar/policy-routing.txt>
  83. and <ftp://post.tepkom.ru/pub/vol2/Linux/docs/advanced-routing.tex>.
  84. You will need supporting software from
  85. <ftp://ftp.tux.org/pub/net/ip-routing/>.
  86. If unsure, say N.
  87. config IP_ROUTE_MULTIPATH
  88. bool "IP: equal cost multipath"
  89. depends on IP_ADVANCED_ROUTER
  90. help
  91. Normally, the routing tables specify a single action to be taken in
  92. a deterministic manner for a given packet. If you say Y here
  93. however, it becomes possible to attach several actions to a packet
  94. pattern, in effect specifying several alternative paths to travel
  95. for those packets. The router considers all these paths to be of
  96. equal "cost" and chooses one of them in a non-deterministic fashion
  97. if a matching packet arrives.
  98. config IP_ROUTE_MULTIPATH_CACHED
  99. bool "IP: equal cost multipath with caching support (EXPERIMENTAL)"
  100. depends on IP_ROUTE_MULTIPATH
  101. help
  102. Normally, equal cost multipath routing is not supported by the
  103. routing cache. If you say Y here, alternative routes are cached
  104. and on cache lookup a route is chosen in a configurable fashion.
  105. If unsure, say N.
  106. config IP_ROUTE_MULTIPATH_RR
  107. tristate "MULTIPATH: round robin algorithm"
  108. depends on IP_ROUTE_MULTIPATH_CACHED
  109. help
  110. Mulitpath routes are chosen according to Round Robin
  111. config IP_ROUTE_MULTIPATH_RANDOM
  112. tristate "MULTIPATH: random algorithm"
  113. depends on IP_ROUTE_MULTIPATH_CACHED
  114. help
  115. Multipath routes are chosen in a random fashion. Actually,
  116. there is no weight for a route. The advantage of this policy
  117. is that it is implemented stateless and therefore introduces only
  118. a very small delay.
  119. config IP_ROUTE_MULTIPATH_WRANDOM
  120. tristate "MULTIPATH: weighted random algorithm"
  121. depends on IP_ROUTE_MULTIPATH_CACHED
  122. help
  123. Multipath routes are chosen in a weighted random fashion.
  124. The per route weights are the weights visible via ip route 2. As the
  125. corresponding state management introduces some overhead routing delay
  126. is increased.
  127. config IP_ROUTE_MULTIPATH_DRR
  128. tristate "MULTIPATH: interface round robin algorithm"
  129. depends on IP_ROUTE_MULTIPATH_CACHED
  130. help
  131. Connections are distributed in a round robin fashion over the
  132. available interfaces. This policy makes sense if the connections
  133. should be primarily distributed on interfaces and not on routes.
  134. config IP_ROUTE_VERBOSE
  135. bool "IP: verbose route monitoring"
  136. depends on IP_ADVANCED_ROUTER
  137. help
  138. If you say Y here, which is recommended, then the kernel will print
  139. verbose messages regarding the routing, for example warnings about
  140. received packets which look strange and could be evidence of an
  141. attack or a misconfigured system somewhere. The information is
  142. handled by the klogd daemon which is responsible for kernel messages
  143. ("man klogd").
  144. config IP_PNP
  145. bool "IP: kernel level autoconfiguration"
  146. help
  147. This enables automatic configuration of IP addresses of devices and
  148. of the routing table during kernel boot, based on either information
  149. supplied on the kernel command line or by BOOTP or RARP protocols.
  150. You need to say Y only for diskless machines requiring network
  151. access to boot (in which case you want to say Y to "Root file system
  152. on NFS" as well), because all other machines configure the network
  153. in their startup scripts.
  154. config IP_PNP_DHCP
  155. bool "IP: DHCP support"
  156. depends on IP_PNP
  157. ---help---
  158. If you want your Linux box to mount its whole root file system (the
  159. one containing the directory /) from some other computer over the
  160. net via NFS and you want the IP address of your computer to be
  161. discovered automatically at boot time using the DHCP protocol (a
  162. special protocol designed for doing this job), say Y here. In case
  163. the boot ROM of your network card was designed for booting Linux and
  164. does DHCP itself, providing all necessary information on the kernel
  165. command line, you can say N here.
  166. If unsure, say Y. Note that if you want to use DHCP, a DHCP server
  167. must be operating on your network. Read
  168. <file:Documentation/nfsroot.txt> for details.
  169. config IP_PNP_BOOTP
  170. bool "IP: BOOTP support"
  171. depends on IP_PNP
  172. ---help---
  173. If you want your Linux box to mount its whole root file system (the
  174. one containing the directory /) from some other computer over the
  175. net via NFS and you want the IP address of your computer to be
  176. discovered automatically at boot time using the BOOTP protocol (a
  177. special protocol designed for doing this job), say Y here. In case
  178. the boot ROM of your network card was designed for booting Linux and
  179. does BOOTP itself, providing all necessary information on the kernel
  180. command line, you can say N here. If unsure, say Y. Note that if you
  181. want to use BOOTP, a BOOTP server must be operating on your network.
  182. Read <file:Documentation/nfsroot.txt> for details.
  183. config IP_PNP_RARP
  184. bool "IP: RARP support"
  185. depends on IP_PNP
  186. help
  187. If you want your Linux box to mount its whole root file system (the
  188. one containing the directory /) from some other computer over the
  189. net via NFS and you want the IP address of your computer to be
  190. discovered automatically at boot time using the RARP protocol (an
  191. older protocol which is being obsoleted by BOOTP and DHCP), say Y
  192. here. Note that if you want to use RARP, a RARP server must be
  193. operating on your network. Read <file:Documentation/nfsroot.txt> for
  194. details.
  195. # not yet ready..
  196. # bool ' IP: ARP support' CONFIG_IP_PNP_ARP
  197. config NET_IPIP
  198. tristate "IP: tunneling"
  199. select INET_TUNNEL
  200. ---help---
  201. Tunneling means encapsulating data of one protocol type within
  202. another protocol and sending it over a channel that understands the
  203. encapsulating protocol. This particular tunneling driver implements
  204. encapsulation of IP within IP, which sounds kind of pointless, but
  205. can be useful if you want to make your (or some other) machine
  206. appear on a different network than it physically is, or to use
  207. mobile-IP facilities (allowing laptops to seamlessly move between
  208. networks without changing their IP addresses).
  209. Saying Y to this option will produce two modules ( = code which can
  210. be inserted in and removed from the running kernel whenever you
  211. want). Most people won't need this and can say N.
  212. config NET_IPGRE
  213. tristate "IP: GRE tunnels over IP"
  214. help
  215. Tunneling means encapsulating data of one protocol type within
  216. another protocol and sending it over a channel that understands the
  217. encapsulating protocol. This particular tunneling driver implements
  218. GRE (Generic Routing Encapsulation) and at this time allows
  219. encapsulating of IPv4 or IPv6 over existing IPv4 infrastructure.
  220. This driver is useful if the other endpoint is a Cisco router: Cisco
  221. likes GRE much better than the other Linux tunneling driver ("IP
  222. tunneling" above). In addition, GRE allows multicast redistribution
  223. through the tunnel.
  224. config NET_IPGRE_BROADCAST
  225. bool "IP: broadcast GRE over IP"
  226. depends on IP_MULTICAST && NET_IPGRE
  227. help
  228. One application of GRE/IP is to construct a broadcast WAN (Wide Area
  229. Network), which looks like a normal Ethernet LAN (Local Area
  230. Network), but can be distributed all over the Internet. If you want
  231. to do that, say Y here and to "IP multicast routing" below.
  232. config IP_MROUTE
  233. bool "IP: multicast routing"
  234. depends on IP_MULTICAST
  235. help
  236. This is used if you want your machine to act as a router for IP
  237. packets that have several destination addresses. It is needed on the
  238. MBONE, a high bandwidth network on top of the Internet which carries
  239. audio and video broadcasts. In order to do that, you would most
  240. likely run the program mrouted. Information about the multicast
  241. capabilities of the various network cards is contained in
  242. <file:Documentation/networking/multicast.txt>. If you haven't heard
  243. about it, you don't need it.
  244. config IP_PIMSM_V1
  245. bool "IP: PIM-SM version 1 support"
  246. depends on IP_MROUTE
  247. help
  248. Kernel side support for Sparse Mode PIM (Protocol Independent
  249. Multicast) version 1. This multicast routing protocol is used widely
  250. because Cisco supports it. You need special software to use it
  251. (pimd-v1). Please see <http://netweb.usc.edu/pim/> for more
  252. information about PIM.
  253. Say Y if you want to use PIM-SM v1. Note that you can say N here if
  254. you just want to use Dense Mode PIM.
  255. config IP_PIMSM_V2
  256. bool "IP: PIM-SM version 2 support"
  257. depends on IP_MROUTE
  258. help
  259. Kernel side support for Sparse Mode PIM version 2. In order to use
  260. this, you need an experimental routing daemon supporting it (pimd or
  261. gated-5). This routing protocol is not used widely, so say N unless
  262. you want to play with it.
  263. config ARPD
  264. bool "IP: ARP daemon support (EXPERIMENTAL)"
  265. depends on EXPERIMENTAL
  266. ---help---
  267. Normally, the kernel maintains an internal cache which maps IP
  268. addresses to hardware addresses on the local network, so that
  269. Ethernet/Token Ring/ etc. frames are sent to the proper address on
  270. the physical networking layer. For small networks having a few
  271. hundred directly connected hosts or less, keeping this address
  272. resolution (ARP) cache inside the kernel works well. However,
  273. maintaining an internal ARP cache does not work well for very large
  274. switched networks, and will use a lot of kernel memory if TCP/IP
  275. connections are made to many machines on the network.
  276. If you say Y here, the kernel's internal ARP cache will never grow
  277. to more than 256 entries (the oldest entries are expired in a LIFO
  278. manner) and communication will be attempted with the user space ARP
  279. daemon arpd. Arpd then answers the address resolution request either
  280. from its own cache or by asking the net.
  281. This code is experimental and also obsolete. If you want to use it,
  282. you need to find a version of the daemon arpd on the net somewhere,
  283. and you should also say Y to "Kernel/User network link driver",
  284. below. If unsure, say N.
  285. config SYN_COOKIES
  286. bool "IP: TCP syncookie support (disabled per default)"
  287. ---help---
  288. Normal TCP/IP networking is open to an attack known as "SYN
  289. flooding". This denial-of-service attack prevents legitimate remote
  290. users from being able to connect to your computer during an ongoing
  291. attack and requires very little work from the attacker, who can
  292. operate from anywhere on the Internet.
  293. SYN cookies provide protection against this type of attack. If you
  294. say Y here, the TCP/IP stack will use a cryptographic challenge
  295. protocol known as "SYN cookies" to enable legitimate users to
  296. continue to connect, even when your machine is under attack. There
  297. is no need for the legitimate users to change their TCP/IP software;
  298. SYN cookies work transparently to them. For technical information
  299. about SYN cookies, check out <http://cr.yp.to/syncookies.html>.
  300. If you are SYN flooded, the source address reported by the kernel is
  301. likely to have been forged by the attacker; it is only reported as
  302. an aid in tracing the packets to their actual source and should not
  303. be taken as absolute truth.
  304. SYN cookies may prevent correct error reporting on clients when the
  305. server is really overloaded. If this happens frequently better turn
  306. them off.
  307. If you say Y here, note that SYN cookies aren't enabled by default;
  308. you can enable them by saying Y to "/proc file system support" and
  309. "Sysctl support" below and executing the command
  310. echo 1 >/proc/sys/net/ipv4/tcp_syncookies
  311. at boot time after the /proc file system has been mounted.
  312. If unsure, say N.
  313. config INET_AH
  314. tristate "IP: AH transformation"
  315. select XFRM
  316. select CRYPTO
  317. select CRYPTO_HMAC
  318. select CRYPTO_MD5
  319. select CRYPTO_SHA1
  320. ---help---
  321. Support for IPsec AH.
  322. If unsure, say Y.
  323. config INET_ESP
  324. tristate "IP: ESP transformation"
  325. select XFRM
  326. select CRYPTO
  327. select CRYPTO_HMAC
  328. select CRYPTO_MD5
  329. select CRYPTO_CBC
  330. select CRYPTO_SHA1
  331. select CRYPTO_DES
  332. ---help---
  333. Support for IPsec ESP.
  334. If unsure, say Y.
  335. config INET_IPCOMP
  336. tristate "IP: IPComp transformation"
  337. select XFRM
  338. select INET_XFRM_TUNNEL
  339. select CRYPTO
  340. select CRYPTO_DEFLATE
  341. ---help---
  342. Support for IP Payload Compression Protocol (IPComp) (RFC3173),
  343. typically needed for IPsec.
  344. If unsure, say Y.
  345. config INET_XFRM_TUNNEL
  346. tristate
  347. select INET_TUNNEL
  348. default n
  349. config INET_TUNNEL
  350. tristate
  351. default n
  352. config INET_XFRM_MODE_TRANSPORT
  353. tristate "IP: IPsec transport mode"
  354. default y
  355. select XFRM
  356. ---help---
  357. Support for IPsec transport mode.
  358. If unsure, say Y.
  359. config INET_XFRM_MODE_TUNNEL
  360. tristate "IP: IPsec tunnel mode"
  361. default y
  362. select XFRM
  363. ---help---
  364. Support for IPsec tunnel mode.
  365. If unsure, say Y.
  366. config INET_XFRM_MODE_BEET
  367. tristate "IP: IPsec BEET mode"
  368. default y
  369. select XFRM
  370. ---help---
  371. Support for IPsec BEET mode.
  372. If unsure, say Y.
  373. config INET_DIAG
  374. tristate "INET: socket monitoring interface"
  375. default y
  376. ---help---
  377. Support for INET (TCP, DCCP, etc) socket monitoring interface used by
  378. native Linux tools such as ss. ss is included in iproute2, currently
  379. downloadable at <http://linux-net.osdl.org/index.php/Iproute2>.
  380. If unsure, say Y.
  381. config INET_TCP_DIAG
  382. depends on INET_DIAG
  383. def_tristate INET_DIAG
  384. menuconfig TCP_CONG_ADVANCED
  385. bool "TCP: advanced congestion control"
  386. ---help---
  387. Support for selection of various TCP congestion control
  388. modules.
  389. Nearly all users can safely say no here, and a safe default
  390. selection will be made (CUBIC with new Reno as a fallback).
  391. If unsure, say N.
  392. if TCP_CONG_ADVANCED
  393. config TCP_CONG_BIC
  394. tristate "Binary Increase Congestion (BIC) control"
  395. default m
  396. ---help---
  397. BIC-TCP is a sender-side only change that ensures a linear RTT
  398. fairness under large windows while offering both scalability and
  399. bounded TCP-friendliness. The protocol combines two schemes
  400. called additive increase and binary search increase. When the
  401. congestion window is large, additive increase with a large
  402. increment ensures linear RTT fairness as well as good
  403. scalability. Under small congestion windows, binary search
  404. increase provides TCP friendliness.
  405. See http://www.csc.ncsu.edu/faculty/rhee/export/bitcp/
  406. config TCP_CONG_CUBIC
  407. tristate "CUBIC TCP"
  408. default y
  409. ---help---
  410. This is version 2.0 of BIC-TCP which uses a cubic growth function
  411. among other techniques.
  412. See http://www.csc.ncsu.edu/faculty/rhee/export/bitcp/cubic-paper.pdf
  413. config TCP_CONG_WESTWOOD
  414. tristate "TCP Westwood+"
  415. default m
  416. ---help---
  417. TCP Westwood+ is a sender-side only modification of the TCP Reno
  418. protocol stack that optimizes the performance of TCP congestion
  419. control. It is based on end-to-end bandwidth estimation to set
  420. congestion window and slow start threshold after a congestion
  421. episode. Using this estimation, TCP Westwood+ adaptively sets a
  422. slow start threshold and a congestion window which takes into
  423. account the bandwidth used at the time congestion is experienced.
  424. TCP Westwood+ significantly increases fairness wrt TCP Reno in
  425. wired networks and throughput over wireless links.
  426. config TCP_CONG_HTCP
  427. tristate "H-TCP"
  428. default m
  429. ---help---
  430. H-TCP is a send-side only modifications of the TCP Reno
  431. protocol stack that optimizes the performance of TCP
  432. congestion control for high speed network links. It uses a
  433. modeswitch to change the alpha and beta parameters of TCP Reno
  434. based on network conditions and in a way so as to be fair with
  435. other Reno and H-TCP flows.
  436. config TCP_CONG_HSTCP
  437. tristate "High Speed TCP"
  438. depends on EXPERIMENTAL
  439. default n
  440. ---help---
  441. Sally Floyd's High Speed TCP (RFC 3649) congestion control.
  442. A modification to TCP's congestion control mechanism for use
  443. with large congestion windows. A table indicates how much to
  444. increase the congestion window by when an ACK is received.
  445. For more detail see http://www.icir.org/floyd/hstcp.html
  446. config TCP_CONG_HYBLA
  447. tristate "TCP-Hybla congestion control algorithm"
  448. depends on EXPERIMENTAL
  449. default n
  450. ---help---
  451. TCP-Hybla is a sender-side only change that eliminates penalization of
  452. long-RTT, large-bandwidth connections, like when satellite legs are
  453. involved, especially when sharing a common bottleneck with normal
  454. terrestrial connections.
  455. config TCP_CONG_VEGAS
  456. tristate "TCP Vegas"
  457. depends on EXPERIMENTAL
  458. default n
  459. ---help---
  460. TCP Vegas is a sender-side only change to TCP that anticipates
  461. the onset of congestion by estimating the bandwidth. TCP Vegas
  462. adjusts the sending rate by modifying the congestion
  463. window. TCP Vegas should provide less packet loss, but it is
  464. not as aggressive as TCP Reno.
  465. config TCP_CONG_SCALABLE
  466. tristate "Scalable TCP"
  467. depends on EXPERIMENTAL
  468. default n
  469. ---help---
  470. Scalable TCP is a sender-side only change to TCP which uses a
  471. MIMD congestion control algorithm which has some nice scaling
  472. properties, though is known to have fairness issues.
  473. See http://www.deneholme.net/tom/scalable/
  474. config TCP_CONG_LP
  475. tristate "TCP Low Priority"
  476. depends on EXPERIMENTAL
  477. default n
  478. ---help---
  479. TCP Low Priority (TCP-LP), a distributed algorithm whose goal is
  480. to utilize only the excess network bandwidth as compared to the
  481. ``fair share`` of bandwidth as targeted by TCP.
  482. See http://www-ece.rice.edu/networks/TCP-LP/
  483. config TCP_CONG_VENO
  484. tristate "TCP Veno"
  485. depends on EXPERIMENTAL
  486. default n
  487. ---help---
  488. TCP Veno is a sender-side only enhancement of TCP to obtain better
  489. throughput over wireless networks. TCP Veno makes use of state
  490. distinguishing to circumvent the difficult judgment of the packet loss
  491. type. TCP Veno cuts down less congestion window in response to random
  492. loss packets.
  493. See http://www.ntu.edu.sg/home5/ZHOU0022/papers/CPFu03a.pdf
  494. choice
  495. prompt "Default TCP congestion control"
  496. default DEFAULT_CUBIC
  497. help
  498. Select the TCP congestion control that will be used by default
  499. for all connections.
  500. config DEFAULT_BIC
  501. bool "Bic" if TCP_CONG_BIC=y
  502. config DEFAULT_CUBIC
  503. bool "Cubic" if TCP_CONG_CUBIC=y
  504. config DEFAULT_HTCP
  505. bool "Htcp" if TCP_CONG_HTCP=y
  506. config DEFAULT_VEGAS
  507. bool "Vegas" if TCP_CONG_VEGAS=y
  508. config DEFAULT_WESTWOOD
  509. bool "Westwood" if TCP_CONG_WESTWOOD=y
  510. config DEFAULT_RENO
  511. bool "Reno"
  512. endchoice
  513. endif
  514. config TCP_CONG_CUBIC
  515. tristate
  516. depends on !TCP_CONG_ADVANCED
  517. default y
  518. config DEFAULT_TCP_CONG
  519. string
  520. default "bic" if DEFAULT_BIC
  521. default "cubic" if DEFAULT_CUBIC
  522. default "htcp" if DEFAULT_HTCP
  523. default "vegas" if DEFAULT_VEGAS
  524. default "westwood" if DEFAULT_WESTWOOD
  525. default "reno" if DEFAULT_RENO
  526. default "cubic"
  527. config TCP_MD5SIG
  528. bool "TCP: MD5 Signature Option support (RFC2385) (EXPERIMENTAL)"
  529. depends on EXPERIMENTAL
  530. select CRYPTO
  531. select CRYPTO_MD5
  532. ---help---
  533. RFC2385 specifices a method of giving MD5 protection to TCP sessions.
  534. Its main (only?) use is to protect BGP sessions between core routers
  535. on the Internet.
  536. If unsure, say N.
  537. source "net/ipv4/ipvs/Kconfig"