Lines Matching refs:IP

915      networking, or if you don't want to allocate an IP to your UML
960   tap0 interface an IP address.
964   Note that the IP address you assign to the host end of the tap device
965   must be different than the IP you assign to the eth device inside UML.
967   you can reuse the host's eth IP address for the host ends of the tap
1021   device IP address.  It will provide the address fe:fd:nn:nn:nn:nn
1022   where nn.nn.nn.nn is the device IP address.  This is nearly always
1028      may conflict with the UML IP address-based scheme
1030   o  You aren't going to use the device for IP networking, so you don't
1031      assign the device an IP address
1034      sure that the device IP address is known before the interface is
1154   machine with different IP addresses:
1205   module if necessary, configuring the device, and setting up IP
1213   If you specify an IP address for the host side of the device, the
1222        eth <n> =tuntap,,, <IP address>
1229   IP address
1239   Note that the IP address that must be used for the eth device inside
1243   It prevents a nasty UML user from doing things like setting the UML IP
1294   o  Configure the device IP (change IP addresses and device name to
1417   Note that 'br0' should be setup using ifconfig with the existing IP
1418   address of eth0, as eth0 no longer has its own IP.
1479        eth <n> =ethertap, <device> , <ethernet address> , <tap IP address>
1493   ethernet address fe:fd:0:0:0:1, and assigns the IP address
1502   The presence of the tap IP address will cause the helper to run and do
1658   IP.
1665        ethn=slip,slip IP
1670   The slip IP argument is the IP address that will be assigned to the
1686   slirp uses an external program, usually /usr/bin/slirp, to provide IP
1687   only networking connectivity through the host. This is similar to IP
1704   with an ethernet address based upon the initial IP address of the
1716   The eth0 interface on UML should be set up with the IP 10.2.0.15,
1728   slirp provides a number of useful IP addresses which can be used by
1730   in /etc/resolv.conf on the host or the IP given in the 'dns' option
1784   needed to get things working (the examples use a host-side IP of
1785   192.168.0.251 and a UML-side IP of 192.168.0.250 - adjust to suit your
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.
3929   IP Masquerading on the host.  Usually this is only experienced when
3930   using private IP addresses (192.168.x.x or 10.x.x.x) for host/UML
3932   connected to.  UML does not enable IP Masquerading, so you will need
3946   Documentation on IP Masquerading, and SNAT, can be found at
3955        route add default gw gateway IP
3960   The gateway IP can be any machine on the local net that knows how to