Config.in.network 8.7 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283
  1. menu "Network support"
  2. config ADK_KERNEL_IP_FIB_HASH
  3. boolean
  4. default y
  5. config ADK_KERNEL_SYN_COOKIES
  6. boolean
  7. default n
  8. config ADK_KERNEL_IP_PNP_BOOTP
  9. boolean
  10. default n
  11. config ADK_KERNEL_IP_PNP_RARP
  12. boolean
  13. default n
  14. config ADK_KERNEL_NET_IPGRE_BROADCAST
  15. boolean
  16. default n
  17. config ADK_KERNEL_NET_IPGRE_DEMUX
  18. boolean
  19. default n
  20. config ADK_KERNEL_PPP_ASYNC
  21. boolean
  22. default n
  23. config ADK_KERNEL_SLHC
  24. boolean
  25. default n
  26. config ADK_KERNEL_IMQ
  27. tristate
  28. default n
  29. config ADK_KERNEL_LLC
  30. tristate
  31. default n
  32. config ADK_KERNEL_IP_MULTICAST
  33. prompt "Enable IP Multicasting"
  34. boolean
  35. default n
  36. config ADK_KERNEL_IP_MROUTE
  37. prompt "Enable IP Multicasting Routing"
  38. boolean
  39. default n
  40. config ADK_KERNEL_ATM
  41. prompt "Asynchronous Transfer Mode (ATM)"
  42. tristate
  43. default n
  44. help
  45. ATM is a high-speed networking technology for Local Area Networks
  46. and Wide Area Networks. It uses a fixed packet size and is
  47. connection oriented, allowing for the negotiation of minimum
  48. bandwidth requirements.
  49. In order to participate in an ATM network, your Linux box needs an
  50. ATM networking card. If you have that, say Y here and to the driver
  51. of your ATM card below.
  52. Note that you need a set of user-space programs to actually make use
  53. of ATM. See the file <file:Documentation/networking/atm.txt> for
  54. further details.
  55. config ADK_KERNEL_ATM_BR2684
  56. prompt "BR2684 ATM module"
  57. tristate
  58. select ADK_KERNEL_ATM
  59. default n
  60. help
  61. config ADK_KERNEL_BRIDGE
  62. prompt "802.1d Ethernet Bridging"
  63. tristate
  64. select ADK_KERNEL_LLC
  65. default m if ADK_PACKAGE_BRIDGE_UTILS
  66. default n
  67. help
  68. If you say Y here, then your Linux box will be able to act as an
  69. Ethernet bridge, which means that the different Ethernet segments it
  70. is connected to will appear as one Ethernet to the participants.
  71. Several such bridges can work together to create even larger
  72. networks of Ethernets using the IEEE 802.1 spanning tree algorithm.
  73. As this is a standard, Linux bridges will cooperate properly with
  74. other third party bridge products.
  75. In order to use the Ethernet bridge, you'll need the bridge
  76. configuration tools; see <file:Documentation/networking/bridge.txt>
  77. for location. Please read the Bridge mini-HOWTO for more
  78. information.
  79. If you enable iptables support along with the bridge support then you
  80. turn your bridge into a bridging IP firewall.
  81. iptables will then see the IP packets being bridged, so you need to
  82. take this into account when setting up your firewall rules.
  83. Enabling arptables support when bridging will let arptables see
  84. bridged ARP traffic in the arptables FORWARD chain.
  85. config ADK_KERNEL_VLAN_8021Q
  86. prompt "802.1q VLAN support"
  87. tristate
  88. default n
  89. help
  90. Select this and you will be able to create 802.1Q VLAN interfaces
  91. on your ethernet interfaces. 802.1Q VLAN supports almost
  92. everything a regular ethernet interface does, including
  93. firewalling, bridging, and of course IP traffic. You will need
  94. the 'vconfig' tool from the VLAN project in order to effectively
  95. use VLANs. See the VLAN web page for more information:
  96. <http://www.candelatech.com/~greear/vlan.html>
  97. config ADK_KERNEL_INET_TUNNEL
  98. tristate
  99. default n
  100. help
  101. config ADK_KERNEL_NET_IPIP
  102. prompt "IP in IP encapsulation support"
  103. tristate
  104. select ADK_KERNEL_INET_TUNNEL
  105. default n
  106. help
  107. Tunneling means encapsulating data of one protocol type within
  108. another protocol and sending it over a channel that understands the
  109. encapsulating protocol. This particular tunneling driver implements
  110. encapsulation of IP within IP, which sounds kind of pointless, but
  111. can be useful if you want to make your (or some other) machine
  112. appear on a different network than it physically is, or to use
  113. mobile-IP facilities (allowing laptops to seamlessly move between
  114. networks without changing their IP addresses).
  115. config ADK_KERNEL_NET_IPGRE
  116. prompt "GRE tunnels over IP"
  117. tristate
  118. select ADK_KERNEL_NET_IPGRE_BROADCAST
  119. select ADK_KERNEL_NET_IPGRE_DEMUX
  120. default m if ADK_PACKAGE_PPTP
  121. default m if ADK_PACKAGE_PPTPD
  122. default n
  123. help
  124. Tunneling means encapsulating data of one protocol type within
  125. another protocol and sending it over a channel that understands the
  126. encapsulating protocol. This particular tunneling driver implements
  127. GRE (Generic Routing Encapsulation) and at this time allows
  128. encapsulating of IPv4 or IPv6 over existing IPv4 infrastructure.
  129. This driver is useful if the other endpoint is a Cisco router: Cisco
  130. likes GRE much better than the other Linux tunneling driver ("IP
  131. tunneling" above). In addition, GRE allows multicast redistribution
  132. through the tunnel.
  133. config ADK_KERNEL_IPV6
  134. prompt "IPv6 support"
  135. tristate
  136. default m
  137. help
  138. This is complemental support for the IP version 6.
  139. You will still be able to do traditional IPv4 networking as well.
  140. For general information about IPv6, see
  141. <http://playground.sun.com/pub/ipng/html/ipng-main.html>.
  142. For Linux IPv6 development information, see <http://www.linux-ipv6.org>.
  143. For specific information about IPv6 under Linux, read the HOWTO at
  144. <http://www.bieringer.de/linux/IPv6/>.
  145. config ADK_KERNEL_IPV6_SIT
  146. prompt "IPv6-in-IPv4 tunnel (SIT driver)"
  147. tristate
  148. select ADK_KERNEL_INET_TUNNEL
  149. default n
  150. help
  151. Tunneling means encapsulating data of one protocol type within
  152. another protocol and sending it over a channel that understands the
  153. encapsulating protocol. This driver implements encapsulation of IPv6
  154. into IPv4 packets. This is useful if you want to connect two IPv6
  155. networks over an IPv4-only path.
  156. config ADK_KERNEL_PPP
  157. prompt "PPP support"
  158. tristate
  159. select ADK_KERNEL_PPP_ASYNC
  160. select ADK_KERNEL_SLHC
  161. select ADK_KERNEL_CRC_CCITT
  162. default m if ADK_PACKAGE_PPTP
  163. default m if ADK_PACKAGE_PPTPD
  164. default m if ADK_PACKAGE_PPP
  165. default n
  166. help
  167. PPP (Point to Point Protocol) is a newer and better SLIP. It serves
  168. the same purpose: sending Internet traffic over telephone (and other
  169. serial) lines. Ask your access provider if they support it, because
  170. otherwise you can't use it; most Internet access providers these
  171. days support PPP rather than SLIP.
  172. To use PPP, you need an additional program called pppd as described
  173. in the PPP-HOWTO, available at
  174. <http://www.tldp.org/docs.html#howto>. Make sure that you have
  175. the version of pppd recommended in <file:Documentation/Changes>.
  176. The PPP option enlarges your kernel by about 16 KB.
  177. There are actually two versions of PPP: the traditional PPP for
  178. asynchronous lines, such as regular analog phone lines, and
  179. synchronous PPP which can be used over digital ISDN lines for
  180. example. If you want to use PPP over phone lines or other
  181. asynchronous serial lines, you need to say Y (or M) here and also to
  182. the next option, "PPP support for async serial ports". For PPP over
  183. synchronous lines, you should say Y (or M) here and to "Support
  184. synchronous PPP", below.
  185. config ADK_KERNEL_PPP_MPPE
  186. prompt "PPP MPPE/MPPC module"
  187. tristate
  188. depends on ADK_KERNEL_PPP
  189. select ADK_KERNEL_CRYPTO
  190. select ADK_KERNEL_CRYPTO_ARC4
  191. select ADK_KERNEL_CRYPTO_SHA1
  192. select ADK_KERNEL_CRYPTO_ECB
  193. default m if ADK_PACKAGE_PPTPD
  194. default n
  195. help
  196. Support for the MPPE Encryption protocol, as employed by the
  197. Microsoft Point-to-Point Tunneling Protocol.
  198. See http://pptpclient.sourceforge.net/ for information on
  199. configuring PPTP clients and servers to utilize this method.
  200. config ADK_KERNEL_PPPOATM
  201. prompt "PPPoA (PPP over ATM) kernel support"
  202. tristate
  203. depends on ADK_KERNEL_PPP
  204. select ADK_KERNEL_ATM
  205. default n
  206. help
  207. Support for PPP over ATM
  208. config ADK_KERNEL_PPPOE
  209. prompt "PPPoE (PPP over Ethernet) kernel support"
  210. tristate
  211. depends on ADK_KERNEL_PPP
  212. default m if ADK_PACKAGE_PPP_MOD_PPPOE
  213. default n
  214. help
  215. Support for PPP over Ethernet
  216. config ADK_KERNEL_TUN
  217. prompt "Universal TUN/TAP driver"
  218. tristate
  219. default m if ADK_PACKAGE_CHILLISPOT
  220. default m if ADK_PACKAGE_AICCU
  221. default m if ADK_PACKAGE_TINC
  222. default m if ADK_PACKAGE_VTUN
  223. default m if ADK_PACKAGE_VPNC
  224. default m if ADK_PACKAGE_OPENVPN
  225. default n
  226. help
  227. Kernel support for the TUN/TAP tunneling device
  228. config ADK_KERNEL_BONDING
  229. prompt "Bonding driver support"
  230. tristate
  231. select BUSYBOX_IFENSLAVE
  232. default n
  233. help
  234. Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
  235. Channels together. This is called 'Etherchannel' by Cisco,
  236. 'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.
  237. The driver supports multiple bonding modes to allow for both high
  238. performance and high availability operation.
  239. Refer to <file:Documentation/networking/bonding.txt> for more
  240. information.
  241. source target/linux/config/Config.in.sched
  242. source target/linux/config/Config.in.ipsec
  243. source target/linux/config/Config.in.ipvs
  244. endmenu