From: Henrik N. <hn...@ma...> - 2001-03-25 23:53:34
|
James Stevenson wrote: > > If not using um_eth_serv, then root must create the tap devices that the > > virtual machines connect to. > > yep thats not a problem > > > Give the user who runs uml read/write access to the device. > > chmod oug+rw /dev/tap0 > cat /dev/tap0 == EPERM in the open syscall So the 2.2 kernel seems to be a bit more strict than the 2.4 kernel here then... Hmm. question: Have you configured the interface prior to attempting this? ifconfig tap0 inet ... up it won't certainly not work if the interface is not there. > > Hmm.. does it? None of mine copies of um_eth_serv know how to (thats why > > I made um_eth_tap for this purpose)... but the new um_eth_tool know how > > to instruct the driver to talk to TAP devices.. > > where would i be able to find um_eth_tap ? It is in the patch section on sourceforge. But it is currently somewhat 2.4 specific as it is written for the 2.4 TUN/TAP driver, not ETHERTAP. But adopting it to ETHERTAP should be quite trivial. > > > c) the network driver in uml dont seem to talk to > > > um_eth_serv properly > > i think it does but only for uml - uml networking um_eth_serv does not care who connects to it. um_eth_serv only provides a emulated ethernet (or actually any number of them), but is not connected anywhere. um_eth_tap is a daemon I wrote to connect a TAP device to um_eth_serv. -- Henrik Nordstrom |