"Tunnel" should pass the name of the used to "LocalCommand". This would allow things like: LocalCommand /sbin/ifup %d
Fair point - I'll look at this once the tunnel forwarding bugs are fixed, so my diffs don't collide.
This could also be implemented by resolving #1766, and letting LocalCommand read the OpenSSH_tunnel environment variable.
Retarget unclosed bugs from 5.7=>5.8
Retarget unresolved bugs/features to 6.0 release
Retarget unresolved bugs/features to 6.0 release (try again - bugzilla's "change several" isn't)
Retarget from 6.0 to 6.1
Retarget 6.0 => 6.1
Retarget uncompleted bugs from 6.1 => 6.2
Retarget bugs from 6.1 => 6.2
retarget to openssh-6.3
Retarget to openssh-6.4
Retarget 6.3 -> 6.4
Retarget incomplete bugs / feature requests to 6.6 release
Retarget to 6.7 release, since 6.6 was mostly bugfixing.
Remove from 6.6 tracking bug
Retarget incomplete bugs to 6.8 release.
These bugs are no longer targeted at the imminent 6.7 release
OpenSSH 6.8 is approaching release and closed for major work. Retarget these bugs for the next release.
Retarget to 6.9
Retarget pending bugs to openssh-7.1
I noticed the last update on this bug is from 2015. I recently tested a patch in this thread: https://lists.mindrot.org/pipermail/openssh-unix-dev/2017-October/036318.html ... and it seemed to work quite well. Any chance that patch could be pushed upstream anytime soon?
This is in -current and will be in OpenSSH 7.7 commit b7548b12a6b2b4abf4d057192c353147e0abba08 Author: djm@openbsd.org <djm@openbsd.org> Date: Mon Oct 23 05:08:00 2017 +0000 upstream commit Expose devices allocated for tun/tap forwarding. At the client, the device may be obtained from a new %T expansion for LocalCommand. At the server, the allocated devices will be listed in a SSH_TUNNEL variable exposed to the environment of any user sessions started after the tunnel forwarding was established. ok markus Upstream-ID: e61e53f8ae80566e9ddc0d67a5df5bdf2f3c9f9e
closing resolved bugs as of 8.6p1 release