Bug#731950: ssh -g has no effect if master socket already open

To: Ken Sharp <imwellcushtymelike@googlemail.com>
Cc: 731950@bugs.debian.org
Subject: Bug#731950: ssh -g has no effect if master socket already open
From: Russ Allbery <rra@debian.org>
Date: Wed, 11 Dec 2013 13:29:03 -0800
Message-id: <[🔎] 87fvpz2i1s.fsf@windlord.stanford.edu>
Reply-to: Russ Allbery <rra@debian.org>, 731950@bugs.debian.org
In-reply-to: <[🔎] 52A87F2E.6000406@googlemail.com> (Ken Sharp's message of "Wed, 11 Dec 2013 15:05:18 +0000")
References: <[🔎] 52A87F2E.6000406@googlemail.com>

Ken Sharp <imwellcushtymelike@googlemail.com> writes:

> However, if it isn't then -g is ignored on subsequent attempts to forward
> ports:

So far as I can tell, this is true for all port forwarding when used with
ControlMaster.  Across the board, it appears that all port forwarding has
to be specified on the original connection and is ignored for subsequent
connections.

I suspect this is inherent in the design.

-- 
Russ Allbery (rra@debian.org)               <http://www.eyrie.org/~eagle/>

Reply to:

Follow-Ups:
- Bug#731950: ssh -g has no effect if master socket already open
  - From: Ken Sharp <imwellcushtymelike@googlemail.com>

References:
- Bug#731950: ssh -g has no effect if master socket already open
  - From: Ken Sharp <imwellcushtymelike@googlemail.com>

Prev by Date: Bug#71494: (no subject)
Next by Date: Bug#731950: ssh -g has no effect if master socket already open
Previous by thread: Processed: ssh -g has no effect if master socket already open
Next by thread: Bug#731950: ssh -g has no effect if master socket already open
Index(es):
- Date
- Thread