Menu
▾
▴
[uml-devel] Re: UML 0.090 networking - can't get even basic pings working.
|
From: James R. L. <jl...@mi...> - 2001-03-01 19:30:08
|
I think your running into a problem with the pathname of the tun device. I have it hardcoded to /dev/tun. Edit: arch/um/driver/eth_user.c: uml_net_user_open() Change /dev/tun to whatever the name of your tun device is. Jim On Thu, Mar 01, 2001 at 01:36:59PM -0500, William Stearns wrote: > Good day, all, > Ive been trying to get the 2.4.2 UML kernel to get a basic IP > connection to the host - no luck yet. For the moment, I'm not interested > in bridging to the host lan, so I'm using "UML to Host connection - > technique 2" from Jim's readme. > For the impatient that don't feel like wading through the > following error report, I'm getting "uml_net_open: failed(-107)". > > Details: > - Host: > 2.4.2-ac5 > rh7.0 > /etc/modules.conf > alias char-major-10-200 tun > lsmod: > [root@sparrow /etc]# lsmod > Module Size Used by > wvlan_cs 24816 1 > tun 3480 0 (unused) > tap0 3036 1 (autoclean) > dummy 1424 0 (unused) > [root@sparrow /dev]# ls -al /dev/net/tun /dev/misc/net/tun > crw-r--r-- 1 wstearns root 10, 200 Feb 28 15:57 /dev/misc/net/tun > crw-r--r-- 1 wstearns root 10, 200 Feb 28 15:57 /dev/net/tun > > I changed the ownership to wstearns back when I was trying to get > the uml networking working as a non-root user. For the following tests, > I'm running uml as root to avoid any question of whether a non-root user > can make the network connection. > > UML > rh6.2 > 2.4.2 +Feb 27th patch (with linker change reverted to 2.4.2-uml) > > In host: > > [root@sparrow /root]# ifconfig tap0 > tap0 Link encap:Ethernet HWaddr FE:FD:00:00:00:00 > inet addr:192.168.1.4 Bcast:192.168.1.255 Mask:255.255.255.0 > UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > Interrupt:5 > > I didn't run any uml specific commands on the host, just the > ifconfig to bring up IP on the tap0 interface. > > In uml: > um_eth_tool -i eth0 -a tap0 #Run before any attempts to bring up the network. > printed: > eth0 will connect to TUNTAP interface tap0 > Redhat's init scripts said: > ... > Bringing up interface lo [ OK ] > Bringing up interface eth0 [ OK ] > Starting portmapper: [ OK ] > ... > but didn't actually assign an address to eth0: > bash# ifconfig > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:3904 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > > OK, try to bring it up by hand: > > bash# ifconfig eth0 192.168.1.5 netmask 255.255.255.0 broadcast 192.168.1.255 up > uml_net_open: failed(-107) > SIOCSIFFLAGS: Network is unreachable > uml_net_open: failed(-107) > SIOCSIFFLAGS: Network is unreachable > > , which is the same error I get trying to bring up 0.090 > networking every time. > dmesg and /var/log/messages in uml only list the same > uml_net_open: failed (-107) message. > > Is there a problem with having the old tap modules still in place > in /etc/modules.conf?: > alias tap0 ethertap > options tap0 -o tap0 unit=0 > alias tap1 ethertap > options tap1 -o tap1 unit=1 > > Can anyone even suggest a basic set of commands that they've used > to get the 0.090 networking working with 2.4.2? > Cheers, > - Bill > > --------------------------------------------------------------------------- > /* > * Leonard, I'll tie you, draw around you a pentagram > * and read this file. Aloud. > */ > - from kernel 2.3.40-pre6's drivers/block/DAC960.c > -------------------------------------------------------------------------- > William Stearns (wst...@po...). Mason, Buildkernel, named2hosts, > and ipfwadm2ipchains are at: http://www.pobox.com/~wstearns > LinuxMonth; articles for Linux Enthusiasts! http://www.linuxmonth.com > -------------------------------------------------------------------------- -- James R. Leu |