Lines Matching refs:host
12 kernels can talk to each other, the host, and with the host's help,
29 running UML to exchange packets with its host over one of the
30 host's Ethertap devices, such as /dev/tap0. Additional running
34 link with the host.
36 To use this, your host kernel must have support for Ethertap
37 devices. Also, if your host kernel is 2.4.x, it must have
45 If you'd like to set up an IP network with the host and/or the
56 packets with the host over a TUN/TAP device. This option will only
57 work with a 2.4 host, unless you've applied the TUN/TAP patch to
58 your 2.2 host kernel.
60 To use this transport, your host kernel must have support for TUN/TAP
68 network with its host over a point-to-point link. Unlike Ethertap,
72 To use this, your host must support slip devices.
82 multiple hosts), Ethertap (to network with the host and the
84 UMLs on a single host). You may choose more than one without
92 UMLs on a single host to communicate with each other, but not to
93 the host.
96 networking daemon on the host.
103 If you'd like to set up a network with other UMLs on a single host,
106 the host and/or other IP machines, say Y to the Ethertap or Slip
116 UMLs on a single host to communicate with each other and also
124 on the host.
138 UMLs (even ones running on different host machines!) to talk to
144 To use this, your host kernel(s) must support IP Multicasting.
162 The pcap transport makes a pcap packet stream on the host look
164 UML act as a network monitor for the host. You must have libcap
171 If you intend to use UML as a network monitor for the host, say
182 the host on which it is run. Only IP packets are supported,
185 to the outside world that the host user is permitted, and unlike
187 privleges, setuid binaries, or SLIP devices on the host. This
192 that of a host behind a firewall that masquerades all network
196 accessible on the host, and have read its documentation. If you