Heya. Yes, Hamachi is similar to echoWare, and I agree
it's a clever solution. Some important differences:

1. With echoWare, the service provider (eg, you) own and run your
own echoServer. It doesn't rely on my continued uptime (eg,
as a mediation server) in any way.

2. AFIAK, Hamachi uses a UDP hole-punching technique to bypass
firewalls and routers. The resulting connection is then
directly peer-to-peer. This has about a 95% success rate, as
UDP hole-punching is a neat workaround, but not something
that's firewall/router/proxy vendors actively support. With
echoWare, the echoServer acts as a TCP relay between the two
endpoints. The latency is increased, as is the connection

3. EchoWare (the client-side component that connects to the
echoServer) is open-source, making it easier to include in
other open-source projects. For instance, we added it into
the TightVNC's Windows platform pretty easily. Hopefully
our Linux version will be done soon as well.

Also, the echoServer is hardly "only for VNC" -- echoWare
will work for any user-to-user application. We wrapped a GUI around
echoWare and call it "EchoVNC", but the echoServer itself is good
for any echoWare-enabled application.

Hamachi's approach of creating a virtual interface on
both sides of the connection is an interesting one -- as you say,
it solves for all layer-3 connections all at once, rather than
echoWare's per-application approach. Maybe I should spend the
time to create an EchoVPN product, based on echoWare.


On Thu, 17 Nov 2005, Ken's Comtex Email at Home wrote:

> Just thought I would put in my two cents worth here. Scott, your EchoServer
> sounds very much like Hamachi ( except that it is only for
> VNC connections while Hamachi is a full-fledged (well, almost)
> software-based VPN tunnel. Hamachi would be a better solution if they are
> wanting to have access to other types of resources from the office PC in the
> future, as it's a simple matter of configuring the OS to allow whatever
> access is required; the VPN tunnel lets any traffic through.
> Hamachi works by connecting to a mediation server to get the tunnels
> established with other computers on your list. If their server goes down,
> the tunnels persist as long as the individual PCs can maintain the links.
> For the most part, this has proven to work flawlessly even when both PCs
> tested were on separate networks completely behind a firewall NAT router.
> The only thing Hamachi doesn't work through is SOCKS or other proxies. They
> are working on that though.
> The current version is but there are pre-release versions of 1.0
> available in the forums if you look for them.
> No, I don't work for Hamachi. I just really like the product and when the
> premium version comes out, I'm going to be the first to support it!
> Undrhil
> -------Original Message-------
> From: Scott C. Best
> Date: 11/17/05 02:00:34
> To: Dale Jones
> Cc:
> Subject: [VPN] Re: FW: VPN
> Dale:
> Heya. Unless I misunderstood you, it sounds like you don't
> need a VPN for your boss to the office. All (I think) you need is a
> remote desktop solution, so that she can see/control the office PC
> from home.
> If that's correct, the best browser-based solution I know
> of is the free LogMeIn solution:
> For a non web-browser solution...and at the risk of being
> company recently released a firewall-friendly
> VNC-based remote desktop system:
> The advantage of the EchoWare Remote Support System is that
> you (the service provider) own all of the pieces -- it doesn't rely
> on any relay/rendezvous-servers run by someone else.
> hope that helps,
> Scott
> On Wed, 16 Nov 2005, Dale Jones wrote:
>>> What is the simplest way to VPN my boss from her house to our office.
>>> We are all on XP Pro on a peer to peer , I only need to her to see
>>> backend Access tables at the office - mostly viewing not updates or
>>> transactions.
>>> Dale Jones
>>> Account Manager
>>> Certified Drivers of America
>>> 469.335.0020 Office

> _______________________________________________
> VPN mailing list

VPN mailing list