Fwd: Re: Port forwarding confusion

----------  Forwarded Message  ----------

Subject: Re: Port forwarding confusion
Date: Friday 24 August 2007
From: Johannes Graumann <johannes.graumann@googlemail.com>
To: Joseph Spenner <joseph85750@yahoo.com>

I'm through! Thank you so much for your help!

Joh

On Friday 24 August 2007 22:06:30 you wrote:
> --- Johannes Graumann
>
> <johannes.graumann@googlemail.com> wrote:
> > Thanks for your input. Excuse my naiveness, but
> > assuming I want to do the same
> > for ldap/sieve and co: can I do that through the
> > same 2022 tunnel or do I
> > need a new one for each protocol?
> >
> > Thanks, Joh
> >
> > > Assuming OUTSIDEBOX can connect to your
> > > OUTSIDEMAILSERVER, you should be able to connect
> >
> > using
> >
> > > the tunnel in #1, then another tunnel:
> > >
> > > 2a) ssh OutsideboxUser@localhost -L
> > > 9993:OUTSIDEMAILSERVER:993 -p 2022
> > >
> > > Then point your email client at localhost:9993
>
> You can forward anything TCP.  You just need to 'chain
> them along'.  For example:
>
> ssh OutsideboxUser@localhost -L 9993:OUTSIDEMAIL:993
> -L  3389:OUTSIDELDAP:389 -L 2000:OUTSIDESIEVE:2000 -p
> 2022
>
> Then use your client to:
> ldap localhost (port 3389)
> sieve localhost (port 2000)
>
> etc..
>
>
>
>
> ___________________________________________________________________________
> _________ Got a little couch potato?
> Check out fun summer activities for kids.
> http://search.yahoo.com/search?fr=oni_on_mail&p=summer+activities+for+kids&;
> cs=bz



-------------------------------------------------------

signature.asc
Description: This is a digitally signed message part.