It's ok. Problem solved. The mac addresses were being remembered in udev rules by Slackware and because I got a different address each time, the eth device number was being incremented. With a fixed mac address on the eth0= startup parameter and a reset of the udev rules it now works.
Dave. On Wednesday 17 October 2007 10:44 pm David Houlden wrote: > Hi, > > I'm running a 2.6.22.10 host with 2.6.23 guest. Both are Slackware. I'm > trying to use udev in the guest and it works apart from the fact I can't > get networking to work in the guest. I'm using tun/tap with the uml_net > helper but I get the same problem if I do the set up of the tap0 device > myself using tunctl. > > If I don't use udev in the guest, I start the guest with > eth0=tuntap,,,192.168.1.50 and in the guest eth0 comes up with its assigned > ip of 192.168.1.51. > > Using udev, the tap0 interface doesn't come up on the host and in the guest > I get device not found from "ifconfig eth0 192.168.1.51 up". What I have > found is that in /proc/net/dev on the guest I have a device eth17. Next > time I boot the guest it will be eth18 and so on. > > Any ideas why this happens and what I can do to fix it. > > Thanks, > Dave. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ User-mode-linux-user mailing list User-mode-linux-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/user-mode-linux-user
