btw, anyone interested in something like this? I have an extensive codebase after trying to build a business around p2p vpn/filesync software. The business didn't go too well (various reasons) but the code is very high quality and still lying around collecting digital dust. We had (we think we had :-)) the best NAT traversal algorithms at that time. Multiplatform - Linux, Win, Mac. Written mostly in very readable old school die hard ANSI C :-)<p>In the wake of the recent NSA-related news I thought that this stuff may find a new use. If you have an idea and would like to devote some time and effort - you're welcome (I guess my contact info is visible in the profile).<p>I have no issues opensourcing it, it contains no close licensed and/or GPL-poisoned code. Everything we borrowed was BSD-type licensed. I just want to have some product to opensource instead of just dumping it on the Github and then waiting 4 billion years for life to conceive itself there :-)<p>Sorry for shameless plug.<p>Update for "Github ++" commenters: I'm all in to put it on Github (BitBucket is more natural in my case, because it's a Hg repo). But: the architecture was quite well thought out and internal APIs are quite clear, but they're not documented. We didn't have immediate open source plans. You wont be able to figure out how to use it, especially if you're going to use our "lower" layer - NAT traversal and friends. You need to know how it works to build a more universal API on top of it. Trust me, I know what I'm talking about - I did a few experiments with this code about a year ago and I spent a _lot_ of time figuring out how we did this and that. And it was _our_ code, we wrote it and discussed it daily for two years.
After skimming the website and the FAQ[1] it seems to be a safer tinc[2]. It's a very cool piece of software and I always wanted to set something like that up between my servers and routers but never found a need convincing enough to go through the trouble.<p>[1] <a href="http://www.freelan.org/page/faq" rel="nofollow">http://www.freelan.org/page/faq</a><p>[2] <a href="http://www.tinc-vpn.org/" rel="nofollow">http://www.tinc-vpn.org/</a>
A little pet peeve, why do people always overlook the most ubiquitous VPN solution of them all?<p>OpenSSH<p>Can create a full spectrum VPN & supports a stronger and a broader range of ciphers than virtually all competing software, is entirely open source, runs on every platform I can think of, the list goes on. Heck via pointopoint it can even mimic freelan and be peer to peer :)
When comparing with OpenVPN, they say the latter "does not allow direct client-to-client communication." Can anyone explain it? I thought point-to-point mode was not only supported, but the default.
Could this take advantage of Google's new QUIC protocol, or get any benefits from it?<p><a href="http://en.wikipedia.org/wiki/QUIC" rel="nofollow">http://en.wikipedia.org/wiki/QUIC</a>
I'm sure there are major typos in the configuration wiki( <a href="https://github.com/freelan-developers/freelan-all/wiki/Two-hosts-configuration-sample" rel="nofollow">https://github.com/freelan-developers/freelan-all/wiki/Two-h...</a> ), which prevent me setup two nodes within the same LAN.
anyone tried to install on windows 2003 server? no service creates on installation. Also I tried to install service manually "freelan --install" but getting an error.
Error: An invalid argument was supplied.<p>Any idea how to run on Windows 2003 32bit server.