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

To: Russ Allbery <rra@debian.org>
Cc: 731950@bugs.debian.org
Subject: Bug#731950: ssh -g has no effect if master socket already open
From: Ken Sharp <imwellcushtymelike@googlemail.com>
Date: Wed, 11 Dec 2013 21:49:23 +0000
Message-id: <[🔎] 52A8DDE3.6010302@googlemail.com>
Reply-to: Ken Sharp <imwellcushtymelike@googlemail.com>, 731950@bugs.debian.org
In-reply-to: <[🔎] 87fvpz2i1s.fsf@windlord.stanford.edu>
References: <[🔎] 52A87F2E.6000406@googlemail.com> <[🔎] 87fvpz2i1s.fsf@windlord.stanford.edu>

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.

No I can add as many port forwards as I like after the master connectionis established. All options I have tried are honoured except for -g.

Reply to:

Follow-Ups:
- Bug#731950: ssh -g has no effect if master socket already open
  - From: Russ Allbery <rra@debian.org>

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

Prev by Date: Bug#731950: ssh -g has no effect if master socket already open
Next by Date: Bug#731950: ssh -g has no effect if master socket already open
Previous by thread: Bug#731950: 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