Hello, all

Interesting problem here.  I have ssh 1.2.26 on a client and a server here.
 This is a testbed, with the intention being to use ppp over a commercial
copy to hook up a bunch of telecommuters once I have proven that it works.
For some reason, I am not seeing any connection attempts.

I did one test on my local net, wherin I have a win box chatting happily to
my firewall running sshd, using a passphrase free rsa file.  This works
fine with several different clients.

When I try to connect to the remote ssh daemon, it fails.  To be precise,
on the originating host, I see 

[root@weaseldns ssh-1.2.26]# ssh1 -v -i /home/scott/.ssh/id_nopass thebes
SSH Version 1.2.26 [i686-unknown-linux], protocol version 1.5.
Standard version.  Does not use RSAREF.
weaseldns.iceweasel.com: Reading configuration data /etc/ssh/ssh_config
weaseldns.iceweasel.com: ssh_connect: getuid 0 geteuid 0 anon 0
weaseldns.iceweasel.com: Connecting to thebes [199.106.132.33] port 22.
weaseldns.iceweasel.com: Allocated local port 1023.

I do not see "Connection established" like I would expect.

On the destination, despite having facist logging on, I see virtually no
messages.

May 27 02:25:11 thebes sshd[5358]: log: Received SIGHUP; restarting.
May 27 02:25:11 thebes sshd[5358]: debug: sshd version 1.2.26
[i686-unknown-linux]
May 27 02:25:11 thebes sshd[5392]: debug: Initializing random number
generator;
seed file /etc/ssh/ssh_random_seed
May 27 02:25:11 thebes sshd[5392]: log: Server listening on port 22.
May 27 02:25:11 thebes sshd[5392]: log: Generating 768 bit RSA key.
May 27 02:25:12 thebes sshd[5392]: log: RSA key generation complete.

Note no logging of the attempt.

The version is direct from the rpm files at replay, which is also why I am
using .26 rather than .27.  I still have not gotten version 2 to work
compiling from the source.  While that is likely my fault, I would rather
try to track down one failure at a time.

Nothing is shown in /var/log/secure, I have port 22 open in the firewalls
between us, and telnets work.  I have tried both the linux ssh client as
above, and tera term.

Is there an easy way to watch the data coming in to a certain port, so I
can at least get some idea where to look?  I have checked hosts.allow and
/etc/ssh_config, but have had no luck.

Scott

Reply via email to