From: Jeff Dike <jdike@ka...> - 2001-05-28 20:30:10
> I'm using 2.4.5 and that the latest patch and having some problems
> accessing the host machine using the umn device? Is the umn device
> still available or have some of the recent developments replaced it.
It's been replaced with eth0=slip,...
There are some oddities with it besides configuring an eth device to talk
slip. The device will appear inside UML as 'umn', not 'eth0'.
I'll fix this at some point, and make it possible to select 'umn' as the
device name from the command line.
> umn_helper (which replaces umn_ifconfig I assume?) is within the path.
And, in turn, umn_helper has been replaced with uml_net.
> Will the new (or the ethertap) networking driver allow you to assign
> an IP that is *not* on your hosts subnet to the virtual (or slip or
> whatever) interface(s) use to access UML boxes?
Yes. I've done that, and it seems to work fine.
> I guess what I'm envisioning is something like Vmware's host-only
> networking which sets of a vmnet1 on the host that is on the same
> network as the eth0 within the virtual machine, all of which may be
> private and have no relation to the the eth0 of hsot machine.
I don't think the two ends of the device even need to be on the same network.
You could configure the host end of a tap device to be in the host's subnet
and configure the UML end to be in a completely different subnet.
> Is the hardware address supposed to show up in the ifconfig?
> sl0 Link encap:Serial Line IP
> inet addr:192.168.10.99 P-t-P:192.168.10.99
These should be different.