Re: Reverse port forwarding (-R) seems not working
- From: Darren Tucker <dtucker@xxxxxxxxxx>
- Date: Thu, 12 Nov 2009 05:34:25 +1100
On Wed, Nov 11, 2009 at 11:01:28AM +0100, Vincenzo Romano wrote:
It's not yet working though.
If I enable the GatewayPorts on the sshd_config (not ssh_config), then
no RPF works anymore on the dummy interfaces or the loopback.
They all fail with:
Warning: remote port forwarding failed for listen port 139, despite
there's no process listening on that interface and that port.
In your original example you had "user@xxxxxxxxxxxxxx". If "user" is
not root then you probably don't have permissions to bind to
low-numbered ports (with or without sshd).
If that's not it, I suggest running the server in debug mode
(eg /path/to/sshd -ddde -p222 to run it on port 222), point your client
at it and see what the reason given for the bind failure is.
--
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.
- References:
- Reverse port forwarding (-R) seems not working
- From: Vincenzo Romano
- Re: Reverse port forwarding (-R) seems not working
- From: Darren Tucker
- Re: Reverse port forwarding (-R) seems not working
- From: Vincenzo Romano
- Reverse port forwarding (-R) seems not working
- Prev by Date: Re: Reverse port forwarding (-R) seems not working
- Next by Date: SOLUTION ! [BUG?] sshd closes the connection after 2^16 bytes
- Previous by thread: Re: Reverse port forwarding (-R) seems not working
- Next by thread: Re: Reverse port forwarding (-R) seems not working
- Index(es):
Relevant Pages
|
