B
balu66
Bekanntes Mitglied
- Dabei seit
- 06.01.2008
- Beiträge
- 50
- Reaktionspunkte
- 0
n2n is a layer-two peer-to-peer virtual private network (VPN) which allows users to exploit features typical of P2P applications at network instead of application level. This means that users can gain native IP visibility (e.g. two PCs belonging to the same n2n network can ping each other) and be reachable with the same network IP address regardless of the network where they currently belong. In a nutshell, as OpenVPN moved SSL from application (e.g. used to implement the https protocol) to network protocol, n2n moves P2P from application to network level.
The main n2n design features are:
The n2n architecture is based on two components:
Edge nodes talk by means of virtual tap interfaces. Each tap interface is an n2n edge node. Each PC can have multiple tap interfaces, one per n2n network, so that the same PC can belong to multiple communities.
http://www.ntop.org/n2n/
http://www.vpnhosting.cz/index.php/N2n-at-vpnhosting.cz.html
Changelog n2n gui:
http://www.vpnhosting.cz/index.php/Changelog.html
sourcecode n2n gui:
http://www.vpnhosting.cz/n2nguisource.zip
N2n gui mit client part of n2n (edge.exe)
http://www.vpnhosting.cz/n2nguien.exe
Langsam aber sicher kommen die hamachi alternativen mit n2n und P2PVPN .
The main n2n design features are:
- An n2n is an encrypted layer two private network based on a P2P protocol.
- Encryption is performed on edge nodes using open protocols with user-defined encryption keys: you control your security without delegating it to companies as it happens with Skype or Hamachi.
- Each n2n user can simultaneously belong to multiple networks (a.k.a. communities).
- Ability to cross NAT and firewalls in the reverse traffic direction (i.e. from outside to inside) so that n2n nodes are reachable even if running on a private network. Firewalls no longer are an obstacle to direct communications at IP level.
- n2n networks are not meant to be self-contained, but it is possible to route traffic across n2n and non n2n networks.
The n2n architecture is based on two components:
- edge nodes: applications installed on user PCs that allow the n2n network to be build. Practically each edge node creates a tun/tap device that is then the entry point to the n2n network.
- an supernode: it is used by edge nodes at startup or for reaching nodes behind symmetrical firewalls. This application is basically a directory register and a packet router for those nodes that cannot talk directly.
Edge nodes talk by means of virtual tap interfaces. Each tap interface is an n2n edge node. Each PC can have multiple tap interfaces, one per n2n network, so that the same PC can belong to multiple communities.
http://www.ntop.org/n2n/
http://www.vpnhosting.cz/index.php/N2n-at-vpnhosting.cz.html
source code of n2n is available via svn repository at ntop.org (author's
site), source code of gui is available via svn repository at vpnhosting.cz
(currently down due to maintenance, we a migrating some services to new
server). It will be back within a couple of days, address will be
svn.vpnhosting.cz, anonymous access allowed of cource.
N2n can be used for building big anonymous networks, there is only one
limitation, maximum number of users in one network is 254, but this value
can be easily adjusted. N2n gui uses client part of n2n (edge.exe), You can
download server part via n2n repository.
Changelog n2n gui:
http://www.vpnhosting.cz/index.php/Changelog.html
sourcecode n2n gui:
http://www.vpnhosting.cz/n2nguisource.zip
N2n gui mit client part of n2n (edge.exe)
http://www.vpnhosting.cz/n2nguien.exe
Langsam aber sicher kommen die hamachi alternativen mit n2n und P2PVPN .
Zuletzt bearbeitet: