Re: VPN and @Home
thanks Josef, for the quick response.
I will consider CIPE, however, I'm still looking for a (better) solution to
connect directly to network A (the one around the block), rather than
through B, to improve network performance. The reason is Quake II. My server
will be the dedicated Quake server and it's standing inside my LAN behind
the firewall ("obelix").
If I run in trouble, I'll know how to find you... :))
----- Original Message -----
From: Josef Bergmann <email@example.com>
Sent: Tuesday, June 26, 2001 1:07 AM
Subject: Re: VPN and @Home
> On 25 Jun 2001, at 22:39, Ken Seefried wrote in a personal reply:
> > >> @Home is blocking a port! I get the same response from @home here.
> > >> thinking of the following solution:
> > >
> > > In this case I will recommend CIPE.
> > > http://sites.inka.de/sites/bigred/devel/cipe.html
> > I was about to recommend the same thing. CIPE works quite well.
> > You could also use http-tunnel
> > (http://www.nocrew.org/software/httptunnel.html), stunnel
> > (http://www.stunnel.org/) or OpenSSH (www.openbsd.org) depending on your
> > exact needs.
> And it would probably also work with Zebedee (Zlib compression, Blowfish
> encryption, Diffie-Hellman key agreement) which also uses just a simple
> connection and there also exists a Win32-port ...
> Alternatives enough in a (GPL-)free world :-)
> bye Josef
> BERGMANN engineering & consulting http://bec.at/
> Reason, too late perhaps, may convince you of the folly of
> misspending time.
> - George Washington
> To UNSUBSCRIBE, email to firstname.lastname@example.org
> with a subject of "unsubscribe". Trouble? Contact