Re: VPN and @Home
- To: firstname.lastname@example.org
- Subject: Re: VPN and @Home
- From: "Josef Bergmann" <email@example.com>
- Date: Tue, 26 Jun 2001 01:07:38 +0200
- Message-id: <3B37E05A.15641.31B43A0@localhost>
- In-reply-to: <firstname.lastname@example.org>
- References: <3B37D66A.27668.2F470EB@localhost>
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. I'm
> >> 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 TCP-
connection and there also exists a Win32-port ...
Alternatives enough in a (GPL-)free world :-)
BERGMANN engineering & consulting http://bec.at/
Reason, too late perhaps, may convince you of the folly of
- George Washington