Greetings, So, the typical use of -Ocancel is quite straightforward:> ssh -Oforward -R 12345:127.0.0.1:56789 user at remote > ssh -Ocancel -R 12345:127.0.0.1:56789 user at remoteBut this is not so good:> ssh -Oforward -R 0:127.0.0.1:56789 user at remoteAllocated port 12345 for remote forward to 127.0.0.1:56789 12345> ssh -Ocancel -R 0:127.0.0.1:56789 user at remotemux_client_forward: forwarding request failed: port not in permitted opens muxclient: master cancel forward request failed> ssh -Ocancel -R 12345:127.0.0.1:56789 user at remotemux_client_forward: forwarding request failed: port not forwarded muxclient: master cancel forward request failed I'm not sure whether this is a "bug" or not, because I really don't understand what the intended behavior is. But I think that at least in the second case, where you know what port is allocated, using -Ocancel should work to cancel the forwarding request. -Sean Patrick Santos
On Fri, 28 Mar 2014, Sean Patrick Santos wrote:> I'm not sure whether this is a "bug" or not, because I really don't > understand what the intended behavior is. But I think that at least in > the second case, where you know what port is allocated, using -Ocancel > should work to cancel the forwarding request.Right - this is a bug; cancelling the actually allocated port should work. Could you file it at https://bugzilla.mindrot.org/ ? Thanks, Damien
Reasonably Related Threads
- [Bug 2219] New: Can't use -Ocancel on forward of dynamically allocated remote port
- ISDN channels
- [Bug 58735] New: GeForce 680, HDMI output no good after passing through HDMI-to-DVI converter
- [PATCH] drm/nouveau/clock: fix support for more than 2 monitors on nve0
- [PATCH 1/1] fix regress/multiplex.sh