Menu
▾
▴
[uml-user] uml differences on the same root_fs (ssh, nslookup, pam, ..)
|
From: Markus H. <Ma...@ho...> - 2005-05-31 23:46:11
|
Hi, i've a problem in my uml: booted with kernel linux-2.4.19-5=20 (http://user-mode-linux.sourceforge.net/dl-sf.html) ssh connects to the uml= =20 work. nslookup work. (the working uml) booted with my own compiled linux-2.6.11.11 ssh connects to the uml doesn't= =20 work (Connection closed by IP), nslookup segfaults. (the disfunction uml) root_fs and command line options are always the same. the root_fs is a debi= an=20 sarge builded with debootstrap. fs mounted after boot of linux-2.6.11.11,=20 kernel network ability, lsmod: # mount /dev/ubda on / type ext3 (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=3D5,mode=3D620) tmpfs on /dev/shm type tmpfs (rw) # dmesg | grep -i net NET: Registered protocol family 16 Netdevice 0 : TUN/TAP backend -=20 NET: Registered protocol family 2 NET: Registered protocol family 15 NET: Registered protocol family 8 NET: Registered protocol family 20 NET: Registered protocol family 1 NET: Registered protocol family 10 # lsmod Module Size Used by ipv6 237504 8=20 unix 23124 10=20 i tried the linux-2.6.11.11 with and without devfs (automount). the problem= =20 keeps. i've tried a lot of options in the uml kernel concerning ipv4. the linux-2.6.11.11 is reachable with ping, also you can make ssh connectio= ns=20 from the uml to other hosts. ssh to the uml, even from the uml to its self= =20 gives the following error: # ssh -v localhost OpenSSH_3.8.1p1 Debian-8.sarge.4, OpenSSL 0.9.7e 25 Oct 2004 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Connecting to localhost [127.0.0.1] port 22. debug1: Connection established. debug1: identity file /root/.ssh/identity type -1 debug1: identity file /root/.ssh/id_rsa type -1 debug1: identity file /root/.ssh/id_dsa type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_3.8.1p= 1=20 Deb ian-8.sarge.4 debug1: match: OpenSSH_3.8.1p1 Debian-8.sarge.4 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_3.8.1p1 Debian-8.sarge.4 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-cbc hmac-md5 none debug1: kex: client->server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host 'localhost' is known and matches the RSA host key. debug1: Found key in /root/.ssh/known_hosts:1 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,keyboard-interactive debug1: Next authentication method: publickey debug1: Trying private key: /root/.ssh/identity debug1: Trying private key: /root/.ssh/id_rsa debug1: Trying private key: /root/.ssh/id_dsa debug1: Next authentication method: keyboard-interactive Connection closed by 127.0.0.1 when booted with linux-2.4.19-5 this works as it should, so the network=20 configuration (/etc/hosts, /etc/resolv.conf, ..) is correct. when ssh fails i get a pam error in the sshd logs. so i've found similar=20 problems on the ml but no solution. so, now the best thing comes: # nslookup www.heise.de Segmentation fault # after reinstalling nslookup multiple times i boot with linux-2.4.19-5 and=20 nslookup works nicely. but after that when back with linux-2.6.11.11 it=20 segfaults (the same root_fs). my next thinking was that it has to do with the uml kernel. and perhaps=20 nothing to to with the kernel options!? so i compiled my linux-2.6.11.11 on= =20 debian woody with gcc 2.95.4-11woody and on debian sarge with gcc 3.3.5-12.= =20 bit the problem is still there. a little info of the host: debian kernel-source-2.4.25 with kernel-patch-s= =20 3-9.2 . is more info needed to track the problem? it would be very nice if someone has suggestions what can i do to let my um= l=20 with kernel 2.6.x work correctly. perhaps some of the kernel option can cau= se=20 this? i also tried kernel 2.6.11 with the same (bad) results. perhaps my=20 problem gets solved :-) the others with similar problems could be helped? and i read in this ml that kernel 2.4.x for host and kernel 2.6.x for uml i= s=20 the proposed way. so i thought (hoped) this works flawless. well, i keep on compiling... :-) =2D-=20 greetings eMHa |