On Saturday 23 October 2004 04:48 pm, Paul Ollion wrote:
Jim, I think you are finding the good solution or quite close to it, and I am beginning to see some light. Here is the output on my main machine, after 2 fruitless attempts, I got this :
atelier:/home/paulus # sshd -d debug1: sshd version OpenSSH_3.8p1 debug1: private host key: #0 type 0 RSA1 debug1: read PEM private key done: type RSA debug1: private host key: #1 type 1 RSA debug1: read PEM private key done: type DSA debug1: private host key: #2 type 2 DSA debug1: Bind to port 22 on ::. Server listening on :: port 22. Generating 768 bit RSA key. RSA key generation complete.
Fruitless attempts and then it starts? I'm perplexed, it shouldn't be hit or miss.
And after typing
ssh paulus@192.168.0.1 on my laptop, I got the warning "permanently added '192.168.0.1' (RSA) to the list of known hosts "
This should have occurred the very first login attempt!
I was asked my password, I gave it and after giving the date and time it said 'Have a lot of fun' Which is not unpleasant, Then "Environment "USER=paulus "LOGNAME=paulus "HOME=/home/paulus "PATH=/usr/bin:/bin:/usr/sbin:/sbin "MAIL=/var/mail/paulus "SHELL=/bin/bash "SSH_CLIENT=::ffff:192.168.0.3 32779 22 "SSH_CONNECTION=::ffff:192.168.0.3 32779 ::ffff:192.168.0.1 22 "SSH_TTY=/dev/pts/49 "TERM=xterm
Now we know that ssh is indeed possible. Lets check for dropped packets, possibly indicating failure on the physical level (your patch cord and connections). A quick read of man ping, and then as root# ping -f <ip of other machine>. Wiggle the patch cord connectors gently during the test. 15-20 sec should be ample. Ctrl c to stop and view results. -- Jim Barnes -- Certainly the game is rigged. Don't let that stop you; if you don't bet, you can't win. -Lazarus Long -- Linux 2.6.5-7.111-default