https://github.com/exaexa/cloudvpn

Meshing VPN tool.
https://github.com/exaexa/cloudvpn

Last synced: about 1 year ago
JSON representation

Meshing VPN tool.

• Host: GitHub
• URL: https://github.com/exaexa/cloudvpn
• Owner: exaexa
• License: gpl-3.0
• Created: 2013-10-20T18:54:28.000Z (over 12 years ago)
• Default Branch: master
• Last Pushed: 2013-10-20T18:55:59.000Z (over 12 years ago)
• Last Synced: 2023-04-01T11:12:28.635Z (about 3 years ago)
• Language: C
• Size: 613 KB
• Stars: 7
• Watchers: 4
• Forks: 5
• Open Issues: 0
• Metadata Files:
  • Readme: README
  • License: LICENSE

Awesome Lists containing this project

README

          


      __                __ ___ ___ ______ _______ 

.----|  |-----.--.--.--|  |   |   |   __ \    |  |

|  __|  |  _  |  |  |  _  |   |   |    __/       |

|____|__|_____|_____|_____|\_____/|___|  |__|____|

                                                    

The multi-purpose mesh networking tool by [exa]. This is version 2.

Project goals:

- Create a nice alternative to IP/IPv6 that works with meshes.

- Move network stack to userspace, to increase flexibility.

- Retain simple usage for tunneling and multicasting of stuff.

Made by:

[exa] exa.exa@gmail.com

License:

GNU GPLv3 (see LICENSE file)

Website:

http://e-x-a.org/?view=cloudvpn

(if you are not searching for technical info, check the quick howto:

http://e-x-a.org/?view=cloudvpn-howto )

*** HISTORY

To anyone who is confused why I deleted most of stuff, please use the git and checkout the original revision (probably v1.99.8 branch or so). That project is probably dead (but still working), as I realized that I made many design flaws, therefore rewriting the thing from scratch.

Basically:

1- cloudvpn started as a simple meshed Ethernet VPN which was cool.

2- we had some new features

3- I realized some small design flaws and possibilities that could open,

   started cloudvpn 2.0. That was given 'gates' tunneling concept.

4- More flaws discovered, complete rewrite suggested.

Also, I'm a little disappointed about ipv6. The most annoying concept is the

once-again-limited address length, then the absolutely missing NAT solution, weirdness in special meanings of prefixes and suffixes, BGP problems,...

*** ARCHITECTURE

- plugin based (keepin'em dynamic and loaded)

- similar to forward-only linux netfilter chains

- plugins are here for routing, filtering, transporting data, configuring other

  plugins...

- interfaces kept as simple as possible

- multicore support.