virtual/uml/UserModeLinux-HOWTO.txt

47      6.6 TUN/TAP with the uml_net helper
48      6.7 TUN/TAP with a preconfigured tap device
110      13.8 TUN/TAP networking doesn't work on a 2.4 host
397   o  tunctl - Configuration tool to create and delete tap devices
399   o  uml_net - Setuid binary for automatic tap device configuration
863   o  TUN/TAP
875      The TUN/TAP, ethertap, slip, and slirp transports allow a UML
899   o  TUN/TAP - if you want access to the host networking and it is
900      running 2.4.  Also, the TUN/TAP transport is able to use a
912      ethertap and TUN/TAP are just not available for some reason
920      Ethertap is available on 2.4 and works fine.  TUN/TAP is preferred
923      run occasionally for TUN/TAP, rather than handling every packet, as
964   Note that the IP address you assign to the host end of the tap device
967   you can reuse the host's eth IP address for the host ends of the tap
1016   Below, you will see that the TUN/TAP, ethertap, and daemon interfaces
1197   6.6.  TUN/TAP with the uml_net helper
1199   TUN/TAP is the preferred mechanism on 2.4 to exchange packets with the
1200   host.  The TUN/TAP backend has been in UML since 2.4.9-3um.
1209   section to see how to have UML use a preconfigured tap device, which
1215   requirement is that TUN/TAP be available, either built in to the host
1218   The format of the command line switch to attach a device to a TUN/TAP
1228   available tap device and assign an ethernet address to it based on its
1241   TUN/TAP device on the host.  You can use a different one, but it won't
1247   There are a couple potential problems with running the TUN/TAP
1250   o  TUN/TAP seems not to work on 2.4.3 and earlier.  Upgrade the host
1253   o  With an upgraded kernel, TUN/TAP may fail with
1272   6.7.  TUN/TAP with a preconfigured tap device
1275   insecure), with UML 2.4.17-11, you can set up a TUN/TAP device
1435   ate useless tap devices (useless because they can't configure them),
1437   to create a group containing all the users who have preconfigured tap
1447      If you don't want that tap device any more, you can make it non-
1451        host#  tunctl -d tap device
1457   output only the name of the tap device it created.  This makes it
1461        host#  TAP=`tunctl -u 1000 -b`
1479        eth <n> =ethertap, <device> , <ethernet address> , <tap IP address>
1494   192.168.0.254 to the tap device.
1498   The tap device is mandatory, but the others are optional.  If the
1502   The presence of the tap IP address will cause the helper to run and do
1508   If it is absent, then you must configure the tap device and whatever
1512   tap device doesn't support SIGIO, which UML needs in order to use
1527        mknod /dev/tap <minor>  c 36  <minor>  + 16
1572   host network (but see -tap, below).
1602         -tap tap0
1608   Note that the tap device must be preconfigured (see "TUN/TAP with a
1609   preconfigured tap device", above).  If you're using a different tap
1788   o  The device needs to be configured with its IP address.  Tap devices
1808   o  If a tap device is being set up, a route is set to the UML IP.
3900   13.8.  TUN/TAP networking doesn't work on a 2.4 host
4350   Yon Uriarte - Fixed the TUN/TAP network backend while I slept.