^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1) # SPDX-License-Identifier: GPL-2.0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 3) menu "UML Character Devices"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 4)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 5) config STDERR_CONSOLE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 6) bool "stderr console"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 7) default y
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 8) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 9) console driver which dumps all printk messages to stderr.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 10)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 11) config SSL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 12) bool "Virtual serial line"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 13) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 14) The User-Mode Linux environment allows you to create virtual serial
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 15) lines on the UML that are usually made to show up on the host as
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 16) ttys or ptys.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 17)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 18) See <http://user-mode-linux.sourceforge.net/old/input.html> for more
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 19) information and command line examples of how to use this facility.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 20)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 21) Unless you have a specific reason for disabling this, say Y.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 22)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 23) config NULL_CHAN
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 24) bool "null channel support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 25) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 26) This option enables support for attaching UML consoles and serial
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 27) lines to a device similar to /dev/null. Data written to it disappears
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 28) and there is never any data to be read.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 29)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 30) config PORT_CHAN
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 31) bool "port channel support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 32) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 33) This option enables support for attaching UML consoles and serial
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 34) lines to host portals. They may be accessed with 'telnet <host>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 35) <port number>'. Any number of consoles and serial lines may be
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 36) attached to a single portal, although what UML device you get when
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 37) you telnet to that portal will be unpredictable.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 38) It is safe to say 'Y' here.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 39)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 40) config PTY_CHAN
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 41) bool "pty channel support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 42) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 43) This option enables support for attaching UML consoles and serial
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 44) lines to host pseudo-terminals. Access to both traditional
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 45) pseudo-terminals (/dev/pty*) and pts pseudo-terminals are controlled
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 46) with this option. The assignment of UML devices to host devices
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 47) will be announced in the kernel message log.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 48) It is safe to say 'Y' here.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 49)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 50) config TTY_CHAN
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 51) bool "tty channel support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 52) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 53) This option enables support for attaching UML consoles and serial
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 54) lines to host terminals. Access to both virtual consoles
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 55) (/dev/tty*) and the slave side of pseudo-terminals (/dev/ttyp* and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 56) /dev/pts/*) are controlled by this option.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 57) It is safe to say 'Y' here.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 58)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 59) config XTERM_CHAN
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 60) bool "xterm channel support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 61) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 62) This option enables support for attaching UML consoles and serial
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 63) lines to xterms. Each UML device so assigned will be brought up in
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 64) its own xterm.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 65) It is safe to say 'Y' here.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 66)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 67) config NOCONFIG_CHAN
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 68) bool
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 69) default !(XTERM_CHAN && TTY_CHAN && PTY_CHAN && PORT_CHAN && NULL_CHAN)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 70)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 71) config CON_ZERO_CHAN
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 72) string "Default main console channel initialization"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 73) default "fd:0,fd:1"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 74) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 75) This is the string describing the channel to which the main console
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 76) will be attached by default. This value can be overridden from the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 77) command line. The default value is "fd:0,fd:1", which attaches the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 78) main console to stdin and stdout.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 79) It is safe to leave this unchanged.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 80)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 81) config CON_CHAN
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 82) string "Default console channel initialization"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 83) default "xterm"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 84) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 85) This is the string describing the channel to which all consoles
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 86) except the main console will be attached by default. This value can
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 87) be overridden from the command line. The default value is "xterm",
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 88) which brings them up in xterms.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 89) It is safe to leave this unchanged, although you may wish to change
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 90) this if you expect the UML that you build to be run in environments
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 91) which don't have X or xterm available.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 92)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 93) config SSL_CHAN
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 94) string "Default serial line channel initialization"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 95) default "pty"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 96) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 97) This is the string describing the channel to which the serial lines
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 98) will be attached by default. This value can be overridden from the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 99) command line. The default value is "pty", which attaches them to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 100) traditional pseudo-terminals.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 101) It is safe to leave this unchanged, although you may wish to change
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 102) this if you expect the UML that you build to be run in environments
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 103) which don't have a set of /dev/pty* devices.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 104)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 105) config UML_SOUND
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 106) tristate "Sound support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 107) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 108) This option enables UML sound support. If enabled, it will pull in
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 109) soundcore and the UML hostaudio relay, which acts as a intermediary
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 110) between the host's dsp and mixer devices and the UML sound system.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 111) It is safe to say 'Y' here.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 112)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 113) config SOUND
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 114) tristate
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 115) default UML_SOUND
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 116)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 117) config SOUND_OSS_CORE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 118) bool
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 119) default UML_SOUND
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 120)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 121) config HOSTAUDIO
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 122) tristate
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 123) default UML_SOUND
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 124)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 125) endmenu
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 126)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 127) menu "UML Network Devices"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 128) depends on NET
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 129)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 130) # UML virtual driver
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 131) config UML_NET
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 132) bool "Virtual network device"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 133) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 134) While the User-Mode port cannot directly talk to any physical
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 135) hardware devices, this choice and the following transport options
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 136) provide one or more virtual network devices through which the UML
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 137) kernels can talk to each other, the host, and with the host's help,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 138) machines on the outside world.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 139)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 140) For more information, including explanations of the networking and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 141) sample configurations, see
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 142) <http://user-mode-linux.sourceforge.net/old/networking.html>.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 143)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 144) If you'd like to be able to enable networking in the User-Mode
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 145) linux environment, say Y; otherwise say N. Note that you must
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 146) enable at least one of the following transport options to actually
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 147) make use of UML networking.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 148)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 149) config UML_NET_ETHERTAP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 150) bool "Ethertap transport (obsolete)"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 151) depends on UML_NET
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 152) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 153) The Ethertap User-Mode Linux network transport allows a single
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 154) running UML to exchange packets with its host over one of the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 155) host's Ethertap devices, such as /dev/tap0. Additional running
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 156) UMLs can use additional Ethertap devices, one per running UML.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 157) While the UML believes it's on a (multi-device, broadcast) virtual
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 158) Ethernet network, it's in fact communicating over a point-to-point
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 159) link with the host.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 160)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 161) To use this, your host kernel must have support for Ethertap
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 162) devices. Also, if your host kernel is 2.4.x, it must have
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 163) CONFIG_NETLINK_DEV configured as Y or M.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 164)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 165) For more information, see
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 166) <http://user-mode-linux.sourceforge.net/old/networking.html> That site
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 167) has examples of the UML command line to use to enable Ethertap
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 168) networking.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 169)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 170) NOTE: THIS TRANSPORT IS DEPRECATED AND WILL BE REMOVED SOON!!! Please
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 171) migrate to UML_NET_VECTOR.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 172)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 173) If unsure, say N.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 174)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 175) config UML_NET_TUNTAP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 176) bool "TUN/TAP transport (obsolete)"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 177) depends on UML_NET
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 178) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 179) The UML TUN/TAP network transport allows a UML instance to exchange
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 180) packets with the host over a TUN/TAP device. This option will only
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 181) work with a 2.4 host, unless you've applied the TUN/TAP patch to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 182) your 2.2 host kernel.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 183)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 184) To use this transport, your host kernel must have support for TUN/TAP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 185) devices, either built-in or as a module.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 186)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 187) NOTE: THIS TRANSPORT IS DEPRECATED AND WILL BE REMOVED SOON!!! Please
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 188) migrate to UML_NET_VECTOR.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 189)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 190) If unsure, say N.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 191)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 192) config UML_NET_SLIP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 193) bool "SLIP transport (obsolete)"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 194) depends on UML_NET
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 195) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 196) The slip User-Mode Linux network transport allows a running UML to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 197) network with its host over a point-to-point link. Unlike Ethertap,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 198) which can carry any Ethernet frame (and hence even non-IP packets),
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 199) the slip transport can only carry IP packets.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 200)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 201) To use this, your host must support slip devices.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 202)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 203) For more information, see
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 204) <http://user-mode-linux.sourceforge.net/old/networking.html>.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 205) has examples of the UML command line to use to enable slip
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 206) networking, and details of a few quirks with it.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 207)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 208) NOTE: THIS TRANSPORT IS DEPRECATED AND WILL BE REMOVED SOON!!! Please
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 209) migrate to UML_NET_VECTOR.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 210)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 211) If unsure, say N.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 212)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 213) config UML_NET_DAEMON
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 214) bool "Daemon transport (obsolete)"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 215) depends on UML_NET
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 216) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 217) This User-Mode Linux network transport allows one or more running
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 218) UMLs on a single host to communicate with each other, but not to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 219) the host.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 220)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 221) To use this form of networking, you'll need to run the UML
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 222) networking daemon on the host.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 223)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 224) For more information, see
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 225) <http://user-mode-linux.sourceforge.net/old/networking.html> That site
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 226) has examples of the UML command line to use to enable Daemon
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 227) networking.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 228)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 229) NOTE: THIS TRANSPORT IS DEPRECATED AND WILL BE REMOVED SOON!!! Please
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 230) migrate to UML_NET_VECTOR.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 231)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 232) If unsure, say N.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 233)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 234) config UML_NET_VECTOR
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 235) bool "Vector I/O high performance network devices"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 236) depends on UML_NET
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 237) select MAY_HAVE_RUNTIME_DEPS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 238) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 239) This User-Mode Linux network driver uses multi-message send
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 240) and receive functions. The host running the UML guest must have
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 241) a linux kernel version above 3.0 and a libc version > 2.13.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 242) This driver provides tap, raw, gre and l2tpv3 network transports
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 243) with up to 4 times higher network throughput than the UML network
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 244) drivers.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 245)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 246) config UML_NET_VDE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 247) bool "VDE transport (obsolete)"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 248) depends on UML_NET
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 249) select MAY_HAVE_RUNTIME_DEPS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 250) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 251) This User-Mode Linux network transport allows one or more running
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 252) UMLs on a single host to communicate with each other and also
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 253) with the rest of the world using Virtual Distributed Ethernet,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 254) an improved fork of uml_switch.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 255)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 256) You must have libvdeplug installed in order to build the vde
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 257) transport into UML.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 258)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 259) To use this form of networking, you will need to run vde_switch
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 260) on the host.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 261)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 262) For more information, see <http://wiki.virtualsquare.org/>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 263) That site has a good overview of what VDE is and also examples
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 264) of the UML command line to use to enable VDE networking.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 265)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 266) NOTE: THIS TRANSPORT IS DEPRECATED AND WILL BE REMOVED SOON!!! Please
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 267) migrate to UML_NET_VECTOR.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 268)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 269) If unsure, say N.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 270)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 271) config UML_NET_MCAST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 272) bool "Multicast transport (obsolete)"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 273) depends on UML_NET
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 274) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 275) This Multicast User-Mode Linux network transport allows multiple
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 276) UMLs (even ones running on different host machines!) to talk to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 277) each other over a virtual ethernet network. However, it requires
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 278) at least one UML with one of the other transports to act as a
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 279) bridge if any of them need to be able to talk to their hosts or any
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 280) other IP machines.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 281)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 282) To use this, your host kernel(s) must support IP Multicasting.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 283)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 284) For more information, see
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 285) <http://user-mode-linux.sourceforge.net/old/networking.html> That site
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 286) has examples of the UML command line to use to enable Multicast
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 287) networking, and notes about the security of this approach.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 288)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 289) NOTE: THIS TRANSPORT IS DEPRECATED AND WILL BE REMOVED SOON!!! Please
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 290) migrate to UML_NET_VECTOR.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 291)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 292) If unsure, say N.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 293)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 294) config UML_NET_PCAP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 295) bool "pcap transport (obsolete)"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 296) depends on UML_NET
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 297) select MAY_HAVE_RUNTIME_DEPS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 298) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 299) The pcap transport makes a pcap packet stream on the host look
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 300) like an ethernet device inside UML. This is useful for making
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 301) UML act as a network monitor for the host. You must have libcap
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 302) installed in order to build the pcap transport into UML.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 303)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 304) For more information, see
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 305) <http://user-mode-linux.sourceforge.net/old/networking.html> That site
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 306) has examples of the UML command line to use to enable this option.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 307)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 308) NOTE: THIS TRANSPORT IS DEPRECATED AND WILL BE REMOVED SOON!!! Please
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 309) migrate to UML_NET_VECTOR.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 310)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 311) If unsure, say N.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 312)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 313) config UML_NET_SLIRP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 314) bool "SLiRP transport (obsolete)"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 315) depends on UML_NET
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 316) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 317) The SLiRP User-Mode Linux network transport allows a running UML
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 318) to network by invoking a program that can handle SLIP encapsulated
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 319) packets. This is commonly (but not limited to) the application
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 320) known as SLiRP, a program that can re-socket IP packets back onto
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 321) he host on which it is run. Only IP packets are supported,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 322) unlike other network transports that can handle all Ethernet
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 323) frames. In general, slirp allows the UML the same IP connectivity
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 324) to the outside world that the host user is permitted, and unlike
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 325) other transports, SLiRP works without the need of root level
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 326) privleges, setuid binaries, or SLIP devices on the host. This
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 327) also means not every type of connection is possible, but most
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 328) situations can be accommodated with carefully crafted slirp
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 329) commands that can be passed along as part of the network device's
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 330) setup string. The effect of this transport on the UML is similar
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 331) that of a host behind a firewall that masquerades all network
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 332) connections passing through it (but is less secure).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 333)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 334) NOTE: THIS TRANSPORT IS DEPRECATED AND WILL BE REMOVED SOON!!! Please
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 335) migrate to UML_NET_VECTOR.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 336)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 337) If unsure, say N.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 338)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 339) Startup example: "eth0=slirp,FE:FD:01:02:03:04,/usr/local/bin/slirp"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 340)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 341) endmenu
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 342)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 343) config VIRTIO_UML
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 344) bool "UML driver for virtio devices"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 345) select VIRTIO
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 346) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 347) This driver provides support for virtio based paravirtual device
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 348) drivers over vhost-user sockets.
Orange Pi5 kernel
Deprecated Linux kernel 5.10.110 for OrangePi 5/5B/5+ boards
3 Commits
0 Branches
0 Tags