Port forwarding using the client of a multiplexed connection.

[Russell Harmon]

Looking at the code in mux.c, you handle the stdin_null_flag at line 552 by
opening /dev/null, but at line 695, you wait until the "controlee closes the
client_fd", then clean up, and terminate. Is this correct?

On Wed, Dec 24, 2008 at 10:39, Peter Stuge <peter at stuge.se> wrote:

> Hi Russell,
>
> Russell Harmon wrote:
> > I am trying to set up port forwarding using the client of a
> > multiplexed connection, but the client is dying.
> >
> > The connection paramaters I am using are as follows:
> > for the master: /usr/bin/ssh -T -n -N ..
> > for the client: /usr/bin/ssh -T -n -N ..
> ..
>
> > The master (this is only the part output when I start the client):
> ..
> > debug2: muxserver_accept_control: got fds stdin 7, stdout 8, stderr 9
> ..
> > debug2: shell request accepted on channel 0
> > debug2: channel 0: read<=0 rfd 7 len 0
> > debug2: channel 0: read failed
> > debug2: channel 0: close_read
> > debug2: channel 0: input open -> drain
> > debug2: channel 0: ibuf empty
> > debug2: channel 0: send eof
> > debug2: channel 0: input drain -> closed
> ..
>
> > The client:
> ..
> > debug2: Received EOF from master
> > debug2: Received exit status from master 0
>
> This is a bit of a wild guess, but does it work if you run the client
> without -T -N ?
>
> It seems the server is trying to read from the client stdin even
> though -T -N is given, and whey they don't return data the server
> closes down the client.
>
> I'm not sure there should be a shell request when using -T -N..
>
>
> //Peter
> _______________________________________________
> openssh-unix-dev mailing list
> openssh-unix-dev at mindrot.org
> https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev
>