wok-current diff n2n/description.txt @ rev 25324
updated squid, squid-auth-helpers and squid-langpack (3.4.2 -> 5.6)
author | Hans-G?nter Theisgen |
---|---|
date | Fri Jul 22 17:10:45 2022 +0100 (2022-07-22) |
parents | |
children |
line diff
1.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000 1.2 +++ b/n2n/description.txt Fri Jul 22 17:10:45 2022 +0100 1.3 @@ -0,0 +1,27 @@ 1.4 +n2n is a layer-two peer-to-peer virtual private network (VPN) 1.5 +which allows users to exploit features typical of P2P 1.6 +applications at network instead of application level. 1.7 +This means that users can gain native IP visibility (e.g. two 1.8 +PCs belonging to the same n2n network can ping each other) 1.9 +and be reachable with the same network IP address regardless 1.10 +of the network where they currently belong. 1.11 +In a nutshell, as OpenVPN moved SSL from application (e.g. used 1.12 +to implement the https protocol) to network protocol, n2n moves 1.13 +P2P from application to network level. 1.14 + 1.15 +The main n2n design features are: 1.16 + 1.17 +- An n2n is an encrypted layer two private network based on a 1.18 + P2P protocol. 1.19 +- Encryption is performed on edge nodes using open protocols 1.20 + with user-defined encryption keys: you control your security 1.21 + without delegating it to companies as it happens with Skype 1.22 + or Hamachi. 1.23 +- Each n2n user can simultaneously belong to multiple networks 1.24 + (a.k.a. communities). 1.25 +- Ability to cross NAT and firewalls in the reverse traffic 1.26 + direction (i.e. from outside to inside) so that n2n nodes are 1.27 + reachable even if running on a private network. Firewalls no 1.28 + longer are an obstacle to direct communications at IP level. 1.29 +- n2n networks are not meant to be self-contained: it is possible 1.30 + to route traffic across n2n and non-n2n networks.