http://bugzilla.opensuse.org/show_bug.cgi?id=929564
http://bugzilla.opensuse.org/show_bug.cgi?id=929564#c1
andreas bittner changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |abittner@opensuse.org
--- Comment #1 from andreas bittner ---
dont know if related, but I am having also serious ssh login issues. They
started maybe like months ago already, but sometimes they are *really* bad.
SSH login from remote often accepts password via the ssh client application (i
see putty logs on windows), but until the shell is offered and available often
many tens of seconds, and worst case scenario I just experienced was 10minutes
later I was only offered the shell.
I even remember some days ago on a machine, I even had a login session timeout,
I think the sshd or some component replied back that the login hasnt been
completed within many minutes and it was logging me out again.
Just to make it clear. All I am trying to do is ssh (putty) connecting to
various opensuse machines (13.2, x64 is all I have running at the moment for
production use), and especially after reboots but also happens with long
uptime, sometimes logging in via ssh is just insanely painstakingly slow to
complete that procedure.
These machines came a long way, and have mostly ipv4 only connection, but some
have ipv6+ipv4 dualstack connection, and they mostly all behave the same bad
way, no matter what I do.
I dont think these kind of things happened with 13.1 (before 13.2), because it
would have driven me insane long ago if these problems had existed in the past.
Also I dont think it is about dns issues or something, because the host I am
connecting from has proper dns entries set and available on the public
internet.
So I am really wondering what is amiss here, it is really driving me crazy by
now with these 10minute delays to complete the logon process.
--------------
2015-10-01 17:30:49 Looking up host "pubhostname"
2015-10-01 17:30:49 Connecting to a.b.c.d port 22
2015-10-01 17:30:49 We claim version: SSH-2.0-PuTTY_Snapshot_2015
2015-10-01 17:30:49 Server version: SSH-2.0-OpenSSH_6.6.1
2015-10-01 17:30:49 We believe remote version has SSH-2 channel request bug
2015-10-01 17:30:49 Using SSH protocol version 2
2015-10-01 17:30:49 Server supports delayed compression; will try this later
2015-10-01 17:30:49 Doing ECDH key exchange with curve Curve25519 and hash
SHA-256
2015-10-01 17:30:49 Host key fingerprint is:
2015-10-01 17:30:49 ecdsa-sha2-nistp256 256 xxxxxxxxxxxx
2015-10-01 17:30:49 Initialised AES-256 SDCTR client->server encryption
2015-10-01 17:30:49 Initialised HMAC-SHA-256 client->server MAC algorithm
2015-10-01 17:30:49 Initialised AES-256 SDCTR server->client encryption
2015-10-01 17:30:49 Initialised HMAC-SHA-256 server->client MAC algorithm
2015-10-01 17:30:53 Attempting keyboard-interactive authentication
2015-10-01 17:30:56 Access granted
2015-10-01 17:30:56 Initiating key re-exchange (enabling delayed
compression)
2015-10-01 17:30:56 Opening session as main channel
2015-10-01 17:40:54 Server supports delayed compression; will try this later
2015-10-01 17:40:54 Doing ECDH key exchange with curve Curve25519 and hash
SHA-256
2015-10-01 17:40:54 Initialised AES-256 SDCTR client->server encryption
2015-10-01 17:40:54 Initialised HMAC-SHA-256 client->server MAC algorithm
2015-10-01 17:40:54 Initialised zlib (RFC1950) compression
2015-10-01 17:40:54 Initialised AES-256 SDCTR server->client encryption
2015-10-01 17:40:54 Initialised HMAC-SHA-256 server->client MAC algorithm
2015-10-01 17:40:54 Initialised zlib (RFC1950) decompression
2015-10-01 17:40:54 Opened main channel
2015-10-01 17:40:54 Local port x forwarding to a
2015-10-01 17:40:54 Local port y forwarding to b
2015-10-01 17:40:54 Local port z forwarding to c
2015-10-01 17:40:54 Allocated pty (ospeed 38400bps, ispeed 38400bps)
2015-10-01 17:40:54 Started a shell/command
Notice the lines after the access granted, there is a ten minute delay there.
What is happening during that time on the server side?
--
You are receiving this mail because:
You are on the CC list for the bug.