Re: GatewayPorts does not open remote end
From: Darren Tucker (dtucker_at_dodgy.net.au)
Date: 01/22/05
- Next message: Darren Tucker: "Re: Status of logged in users"
- Previous message: Doug: "Re: File xfer using PSCP from PuTTY 0.54- performance drop"
- In reply to: Jan Engelhardt: "GatewayPorts does not open remote end"
- Next in thread: Jan Engelhardt: "Re: GatewayPorts does not open remote end"
- Reply: Jan Engelhardt: "Re: GatewayPorts does not open remote end"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: 22 Jan 2005 00:02:08 GMT
In article <Pine.LNX.4.61.0501212017480.23268@yvahk01.tjqt.qr>,
Jan Engelhardt <jengelh@linux01.gwdg.de> wrote:
>ssh -o GatewayPorts=yes -L 12345:localhost:22 -R 23456:localhost:22
>user@external
>
>only binds internal:12345 to the wildcard address, external:23456 is still
>bound to 127.0.0.1 only. Is there a way I can also bind 23456 to the wildcard
>address?
Make sure it's permitted by the server. On OpenSSH this is the
GatewayPorts option in sshd_config, and it defaults to "no". Other
implementations may vary.
--
Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69
Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.
- Next message: Darren Tucker: "Re: Status of logged in users"
- Previous message: Doug: "Re: File xfer using PSCP from PuTTY 0.54- performance drop"
- In reply to: Jan Engelhardt: "GatewayPorts does not open remote end"
- Next in thread: Jan Engelhardt: "Re: GatewayPorts does not open remote end"
- Reply: Jan Engelhardt: "Re: GatewayPorts does not open remote end"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
