Date: Fri, 29 May 1998 15:05:19 -0400 (EDT) From: Robert Watson <robert@cyrus.watson.org> To: Jim Flowers <jflowers@ezo.net> Cc: spork <spork@super-g.com>, Open Systems Networking <opsys@mail.webspan.net>, freebsd-security@FreeBSD.ORG Subject: Re: FreeBSD Tunneling Message-ID: <Pine.BSF.3.96.980529150053.21493G-100000@fledge.watson.org> In-Reply-To: <01bd8afd$5fdb2bc0$8a8266ce@violet.eznets.canton.oh.us>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 29 May 1998, Jim Flowers wrote: > All told, I think it's a currently usable option for someone willing to > spend the time. I have one tunnel coupling two private networks over the > Internet with full encryption and encapsulation running for six months > without a hiccup. I've also had very good experience creating a VPN between two private networks using SKIP + a custom tunneling tool. It's been up and running smoothly (including reboots of both end machines of the tunnel) for a few weeks, and one of the hosts has moved IPs three times :). I have been very happy with both its performance and stability. I admit that it was work to get the configuration right, but it's been running smoothly since then. I would rather use an IPsec tunnel, but I don't know of any IPsec LKMs I can load up without spoiling my fairly clean CVSup'd source base under -stable and -current. Robert N Watson ---- Carnegie Mellon University http://www.cmu.edu/ Trusted Information Systems http://www.tis.com/ SafePort Network Services http://www.safeport.com/ robert@fledge.watson.org http://www.watson.org/~robert/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980529150053.21493G-100000>