1 |
On Monday 18 February 2008, Willie Wong wrote: |
2 |
> On Mon, Feb 18, 2008 at 07:26:28PM +0000, Penguin Lover Mick squawked: |
3 |
> > > ssh -p 443 -L 2222:smtpserver:25 me@remote_sshd.com |
4 |
> > > |
5 |
> > > and configure your mail client to send to localhost, port 2222. |
6 |
> > > Another alternative (depending upon how many ports you need to forward) |
7 |
> > > could be to use SOCKS. |
8 |
> > |
9 |
> > With option -D on the server. Hmm, need to explain that the ssh server |
10 |
> > is NOT the mail server (and last time I looked gmail did not accept ssh |
11 |
> > connections to their mail servers!), but a router I run at home. The |
12 |
> > idea is that I will set up corresponding forwarding rules on the router. |
13 |
> > Is that sound? |
14 |
> |
15 |
> Does your mail server at home have a real ip address? You can do |
16 |
> |
17 |
> ssh -l <username> -p 443 -N ssh.server.address -L |
18 |
> localport:mail.server.address:remoteport |
19 |
> |
20 |
> And you don't need to worry about setting up forwarding rules on the |
21 |
> router. |
22 |
|
23 |
The mail server is on the Internet, not accessible by ssh. I intended to use |
24 |
the router to bounce the ssh connection and forward it to the mail server. |
25 |
|
26 |
laptop --> |firewall| --> router --> mailserver |
27 |
ssh ssh ssl |
28 |
|
29 |
Essentially, thinking of using the router as a proxy server. |
30 |
-- |
31 |
Regards, |
32 |
Mick |