|
|
Secure Shell
Reverse port forwarding (-R) seems not working Nov 10 2009 10:17PM Vincenzo Romano (Vincenzo Romano notorand it) (3 replies) Re: Reverse port forwarding (-R) seems not working Nov 11 2009 01:10PM Greg Wooledge (wooledg eeg ccf org) Re: Reverse port forwarding (-R) seems not working Nov 11 2009 04:40AM Darren Tucker (dtucker zip com au) (2 replies) Re: Reverse port forwarding (-R) seems not working Nov 11 2009 10:01AM Vincenzo Romano (Vincenzo Romano notorand it) (1 replies) Re: Reverse port forwarding (-R) seems not working Nov 11 2009 05:49AM Vincenzo Romano (Vincenzo Romano notorand it) Re: Reverse port forwarding (-R) seems not working Nov 11 2009 03:38AM Joseph Spenner (joseph85750 yahoo com) |
|
Privacy Statement |
> 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 (at) remotehost (dot) net [email concealed]". 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.
[ reply ]