Re: Wide-open local port forwarding
From: Edward Leiper (E.Leiper_at_sms.ed.ac.uk)
Date: 11/25/05
- Next message: Richard E. Silverman: "Re: Tunneled IP Addresses?"
- Previous message: menel.hej_at_interia.pl: "Wide-open local port forwarding"
- In reply to: menel.hej_at_interia.pl: "Wide-open local port forwarding"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Fri, 25 Nov 2005 17:04:09 +0000
I have vague memories of a problem like this where putting the
external IP instead of localhost did the trick - but I can't remember
if it was the same problem that I was trying to solve.
It looks like you're trying to make SSH available on port 60022 as
well as 22. If this is the case, then you'll be better off with a
firewall rule along these lines:
iptables -t nat -A PREROUTING -p tcp --dport 60022 -j REDIRECT --to-ports 22
If you're trying to forward any old port, try running the ssh process
with the -v option and see if it sees the incoming connection to port
60022. If not then there may be a firewall blocking things somewhere.
If that doesn't work, post the output of the ssh process which is
forwarding the ports and the ssh process (use -v again) which is
trying to connect, then it'll be easier for us to work out what's
going on.
Hope that helps!
~Ed
- Next message: Richard E. Silverman: "Re: Tunneled IP Addresses?"
- Previous message: menel.hej_at_interia.pl: "Wide-open local port forwarding"
- In reply to: menel.hej_at_interia.pl: "Wide-open local port forwarding"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|