[plug] SSH Tunnel
Michael L. Benjamin
mike.benjamin at clarinet.com.au
Thu Apr 6 12:04:49 WST 2006
Ok, not quite there yet...
I'm using this command now...
#ssh -L 110:mail.iinet.net.au:110 <localIP> -l username
I can connect locally on that server to 110 and get the POP3 session
from the iinet mailserver. So that part of
things is working nicely.
Remotely I cannot connect though. Iptables is set to allow through 110
so this is not the issue.
I can connect up via PuTTY, and open localhost 110 on the XP machine,
but it closes the connection off immediately.
I'm using a tunnel with source port 110 with PuTTY. <server1_IP>:110 is
the destination.
What I'm seeing is that <server1_IP> is not listening on port 110...
argh. A telnet to that address on port 110
results in a connect failed.
Now I'm confused...
Mike.
-----Original Message-----
From: plug-bounces at plug.org.au [mailto:plug-bounces at plug.org.au] On
Behalf Of Russell Steicke
Sent: Thursday, April 06, 2006 11:00 AM
To: plug at plug.org.au
Subject: Re: [plug] SSH Tunnel
Blinded by the question, I was.
As others have pointed out:
ssh -L 9999:server2:110 server1
--
Russell Steicke
-- Fortune says:
Arnold's Laws of Documentation:
(1) If it should exist, it doesn't.
(2) If it does exist, it's out of date.
(3) Only documentation for useless programs transcends the
first two laws.
_______________________________________________
PLUG discussion list: plug at plug.org.au
http://www.plug.org.au/mailman/listinfo/plug
Committee e-mail: committee at plug.linux.org.au
More information about the plug
mailing list