On 12/14/18 00:27, Максим wrote:
> Hello,
> I've got a PC running OpenBSD current.
> After the latest upgrade I cannot ssh to it.
>
> When I run "ssh 10.26.5.70"
> I get this:
> "Connection to 10.26.5.70 closed by remote host.
>  Connection to 10.26.5.70 closed."
> As an SSH client I use another OpenBSD box and a Linux machine
> with the same result.
> When I run "ssh -vvv 10.26.5.70"
> the last messages are:
> 
> "debug3: receive packet: type 52
> debug1: Authentication succeeded (publickey).
> Authenticated to 10.26.5.70 ([10.26.5.70]:22).
> debug1: channel 0: new [client-session]
> debug3: ssh_session2_open: channel_new: 0
> debug2: channel 0: send open
> debug3: send packet: type 90
> debug1: Requesting no-more-sessi...@openssh.com
> debug3: send packet: type 80
> debug1: Entering interactive session.
> debug1: pledge: network
> debug3: send packet: type 1
> debug1: channel 0: free: client-session, nchannels 1
> debug3: channel 0: status: The following connections are open:
>   #0 client-session (t3 nr0 i0/0 o0/0 e[write]/0 fd 4/5/6 sock -1 cc -1)
> 
> debug3: fd 1 is not O_NONBLOCK
> Connection to 10.26.5.70 closed by remote host.
> Connection to 10.26.5.70 closed.
> Transferred: sent 2644, received 1932 bytes, in 0.0 seconds
> Bytes per second: sent 1085498.2, received 793185.5
> debug1: Exit status -1"
> 
> 
> No errors in /var/log/daemon
> No errors in /var/log/authlog
> 
> The result doesn't depend on the user which I use to login.

I just happened to have upgraded a system last night to the most recent
snapshot, I am NOT having any such problem.
OpenBSD 6.4-current (GENERIC.MP) #510: Thu Dec 13 06:20:42 MST 2018
    dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP

So ... Doesn't appear to be a systemic problem, most likely either a
knob you twisted before the upgrade or something about your upgrade process.

You need to provide more details about what you did...both before and
during the upgrade...and some indication of what platform you are
running and the snapshot you upgraded to.

Nick.

Reply via email to