Kconfig.net 7.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180
  1. menu "UML Network Devices"
  2. depends on NET
  3. # UML virtual driver
  4. config UML_NET
  5. bool "Virtual network device"
  6. help
  7. While the User-Mode port cannot directly talk to any physical
  8. hardware devices, this choice and the following transport options
  9. provide one or more virtual network devices through which the UML
  10. kernels can talk to each other, the host, and with the host's help,
  11. machines on the outside world.
  12. For more information, including explanations of the networking and
  13. sample configurations, see
  14. <http://user-mode-linux.sourceforge.net/networking.html>.
  15. If you'd like to be able to enable networking in the User-Mode
  16. linux environment, say Y; otherwise say N. Note that you must
  17. enable at least one of the following transport options to actually
  18. make use of UML networking.
  19. config UML_NET_ETHERTAP
  20. bool "Ethertap transport"
  21. depends on UML_NET
  22. help
  23. The Ethertap User-Mode Linux network transport allows a single
  24. running UML to exchange packets with its host over one of the
  25. host's Ethertap devices, such as /dev/tap0. Additional running
  26. UMLs can use additional Ethertap devices, one per running UML.
  27. While the UML believes it's on a (multi-device, broadcast) virtual
  28. Ethernet network, it's in fact communicating over a point-to-point
  29. link with the host.
  30. To use this, your host kernel must have support for Ethertap
  31. devices. Also, if your host kernel is 2.4.x, it must have
  32. CONFIG_NETLINK_DEV configured as Y or M.
  33. For more information, see
  34. <http://user-mode-linux.sourceforge.net/networking.html> That site
  35. has examples of the UML command line to use to enable Ethertap
  36. networking.
  37. If you'd like to set up an IP network with the host and/or the
  38. outside world, say Y to this, the Daemon Transport and/or the
  39. Slip Transport. You'll need at least one of them, but may choose
  40. more than one without conflict. If you don't need UML networking,
  41. say N.
  42. config UML_NET_TUNTAP
  43. bool "TUN/TAP transport"
  44. depends on UML_NET
  45. help
  46. The UML TUN/TAP network transport allows a UML instance to exchange
  47. packets with the host over a TUN/TAP device. This option will only
  48. work with a 2.4 host, unless you've applied the TUN/TAP patch to
  49. your 2.2 host kernel.
  50. To use this transport, your host kernel must have support for TUN/TAP
  51. devices, either built-in or as a module.
  52. config UML_NET_SLIP
  53. bool "SLIP transport"
  54. depends on UML_NET
  55. help
  56. The slip User-Mode Linux network transport allows a running UML to
  57. network with its host over a point-to-point link. Unlike Ethertap,
  58. which can carry any Ethernet frame (and hence even non-IP packets),
  59. the slip transport can only carry IP packets.
  60. To use this, your host must support slip devices.
  61. For more information, see
  62. <http://user-mode-linux.sourceforge.net/networking.html>. That site
  63. has examples of the UML command line to use to enable slip
  64. networking, and details of a few quirks with it.
  65. The Ethertap Transport is preferred over slip because of its
  66. limitations. If you prefer slip, however, say Y here. Otherwise
  67. choose the Multicast transport (to network multiple UMLs on
  68. multiple hosts), Ethertap (to network with the host and the
  69. outside world), and/or the Daemon transport (to network multiple
  70. UMLs on a single host). You may choose more than one without
  71. conflict. If you don't need UML networking, say N.
  72. config UML_NET_DAEMON
  73. bool "Daemon transport"
  74. depends on UML_NET
  75. help
  76. This User-Mode Linux network transport allows one or more running
  77. UMLs on a single host to communicate with each other, but not to
  78. the host.
  79. To use this form of networking, you'll need to run the UML
  80. networking daemon on the host.
  81. For more information, see
  82. <http://user-mode-linux.sourceforge.net/networking.html> That site
  83. has examples of the UML command line to use to enable Daemon
  84. networking.
  85. If you'd like to set up a network with other UMLs on a single host,
  86. say Y. If you need a network between UMLs on multiple physical
  87. hosts, choose the Multicast Transport. To set up a network with
  88. the host and/or other IP machines, say Y to the Ethertap or Slip
  89. transports. You'll need at least one of them, but may choose
  90. more than one without conflict. If you don't need UML networking,
  91. say N.
  92. config UML_NET_MCAST
  93. bool "Multicast transport"
  94. depends on UML_NET
  95. help
  96. This Multicast User-Mode Linux network transport allows multiple
  97. UMLs (even ones running on different host machines!) to talk to
  98. each other over a virtual ethernet network. However, it requires
  99. at least one UML with one of the other transports to act as a
  100. bridge if any of them need to be able to talk to their hosts or any
  101. other IP machines.
  102. To use this, your host kernel(s) must support IP Multicasting.
  103. For more information, see
  104. <http://user-mode-linux.sourceforge.net/networking.html> That site
  105. has examples of the UML command line to use to enable Multicast
  106. networking, and notes about the security of this approach.
  107. If you need UMLs on multiple physical hosts to communicate as if
  108. they shared an Ethernet network, say Y. If you need to communicate
  109. with other IP machines, make sure you select one of the other
  110. transports (possibly in addition to Multicast; they're not
  111. exclusive). If you don't need to network UMLs say N to each of
  112. the transports.
  113. config UML_NET_PCAP
  114. bool "pcap transport"
  115. depends on UML_NET && EXPERIMENTAL
  116. help
  117. The pcap transport makes a pcap packet stream on the host look
  118. like an ethernet device inside UML. This is useful for making
  119. UML act as a network monitor for the host. You must have libcap
  120. installed in order to build the pcap transport into UML.
  121. For more information, see
  122. <http://user-mode-linux.sourceforge.net/networking.html> That site
  123. has examples of the UML command line to use to enable this option.
  124. If you intend to use UML as a network monitor for the host, say
  125. Y here. Otherwise, say N.
  126. config UML_NET_SLIRP
  127. bool "SLiRP transport"
  128. depends on UML_NET
  129. help
  130. The SLiRP User-Mode Linux network transport allows a running UML
  131. to network by invoking a program that can handle SLIP encapsulated
  132. packets. This is commonly (but not limited to) the application
  133. known as SLiRP, a program that can re-socket IP packets back onto
  134. the host on which it is run. Only IP packets are supported,
  135. unlike other network transports that can handle all Ethernet
  136. frames. In general, slirp allows the UML the same IP connectivity
  137. to the outside world that the host user is permitted, and unlike
  138. other transports, SLiRP works without the need of root level
  139. privleges, setuid binaries, or SLIP devices on the host. This
  140. also means not every type of connection is possible, but most
  141. situations can be accomodated with carefully crafted slirp
  142. commands that can be passed along as part of the network device's
  143. setup string. The effect of this transport on the UML is similar
  144. that of a host behind a firewall that masquerades all network
  145. connections passing through it (but is less secure).
  146. To use this you should first have slirp compiled somewhere
  147. accessible on the host, and have read its documentation. If you
  148. don't need UML networking, say N.
  149. Startup example: "eth0=slirp,FE:FD:01:02:03:04,/usr/local/bin/slirp"
  150. endmenu