public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Zhu, Binbin (Nokia - CN/Hangzhou)" <binbin.zhu@nokia.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: ssh ControlMaster re-broken
Date: Wed, 18 Nov 2015 12:28:00 -0000	[thread overview]
Message-ID: <8ADFA0E0FC6B6F4A96E106C224E204F30EE3F9E3@SGSIMBX006.nsn-intra.net> (raw)

Hi,

Specifically, it worked in 
2.2.0(0.289/5/3) 2015-08-03 12:49 i686 Cygwin

But failed in 
2.2.0(0.289/5/3) 2015-08-03 12:49 i686 Cygwin

Both i686 and x86_64...

Br, Bin
LTE C-PLANE

-----Original Message-----
From: Zhu, Binbin (Nokia - CN/Hangzhou) 
Sent: Tuesday, November 17, 2015 8:46 PM
To: 'cygwin@cygwin.com' <cygwin@cygwin.com>
Subject: ssh ControlMaster re-broken

Hi,

It worked month ago, but it failed after reinstall.

1. Create shared session: ssh -vvv -nNf -o ControlMaster=yes -o ControlPath="$HOME/.ssh/ctl/%L-%r@%h:%p"  remote-host
Output in accepting new connection: 
$ debug1: multiplexing control connection
debug3: fd 5 is O_NONBLOCK
debug3: fd 5 is O_NONBLOCK
debug1: channel 1: new [mux-control]
debug3: channel_post_mux_listener: new mux channel 1 fd 5
debug3: mux_master_read_cb: channel 1: hello sent
debug3: mux_master_read_cb: channel 1 packet type 0x00000001 len 4
debug2: process_mux_master_hello: channel 1 slave version 4
debug3: mux_master_read_cb: channel 1 packet type 0x10000004 len 4
debug2: process_mux_alive_check: channel 1: alive check
debug3: mux_master_read_cb: channel 1 packet type 0x10000002 len 41
debug2: process_mux_new_session: channel 1: request tty 1, X 0, agent 0, subsys 0, term "xterm", cmd "", env 0
mm_receive_fd: no message header
process_mux_new_session: failed to receive fd 0 from slave

2. Client output:
$ ssh -vvv -o ControlPath="$HOME/.ssh/ctl/%L-%r@%h:%p" remote-host
OpenSSH_7.1p1, OpenSSL 1.0.2d 9 Jul 2015
debug2: fd 3 setting O_NONBLOCK
debug2: mux_client_hello_exchange: master version 4
debug3: mux_client_forwards: request forwardings: 0 local, 0 remote
debug3: mux_client_request_session: entering
debug3: mux_client_request_alive: entering
debug3: mux_client_request_alive: done pid = 10144
debug3: mux_client_request_session: session request sent
mux_client_request_session: read from master failed: Connection reset by peer
debug2: ssh_connect: needpriv 0

Could you help?

Br, Bin


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

             reply	other threads:[~2015-11-18 12:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-18 12:28 Zhu, Binbin (Nokia - CN/Hangzhou) [this message]
2015-11-18 15:53 ` Larry Hall (Cygwin)
  -- strict thread matches above, loose matches on Subject: below --
2015-11-23  8:51 Zhu, Binbin (Nokia - CN/Hangzhou)
2015-11-17 12:46 Zhu, Binbin (Nokia - CN/Hangzhou)
2015-11-18 17:32 ` Corinna Vinschen
2015-11-19 16:45   ` Andrew Schulman
2015-11-20  9:38     ` Corinna Vinschen
2015-11-20 13:42       ` Andrew Schulman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8ADFA0E0FC6B6F4A96E106C224E204F30EE3F9E3@SGSIMBX006.nsn-intra.net \
    --to=binbin.zhu@nokia.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).