wok annotate n2n/description.txt @ rev 25421
Update some web_site
| author | Pascal Bellard <pascal.bellard@slitaz.org> |
|---|---|
| date | Wed Aug 10 07:02:08 2022 +0000 (21 months ago) |
| parents | |
| children |
| rev | line source |
|---|---|
| Hans-G?nter@24944 | 1 n2n is a layer-two peer-to-peer virtual private network (VPN) |
| Hans-G?nter@24944 | 2 which allows users to exploit features typical of P2P |
| Hans-G?nter@24944 | 3 applications at network instead of application level. |
| Hans-G?nter@24944 | 4 This means that users can gain native IP visibility (e.g. two |
| Hans-G?nter@24944 | 5 PCs belonging to the same n2n network can ping each other) |
| Hans-G?nter@24944 | 6 and be reachable with the same network IP address regardless |
| Hans-G?nter@24944 | 7 of the network where they currently belong. |
| Hans-G?nter@24944 | 8 In a nutshell, as OpenVPN moved SSL from application (e.g. used |
| Hans-G?nter@24944 | 9 to implement the https protocol) to network protocol, n2n moves |
| Hans-G?nter@24944 | 10 P2P from application to network level. |
| Hans-G?nter@24944 | 11 |
| Hans-G?nter@24944 | 12 The main n2n design features are: |
| Hans-G?nter@24944 | 13 |
| Hans-G?nter@24944 | 14 - An n2n is an encrypted layer two private network based on a |
| Hans-G?nter@24944 | 15 P2P protocol. |
| Hans-G?nter@24944 | 16 - Encryption is performed on edge nodes using open protocols |
| Hans-G?nter@24944 | 17 with user-defined encryption keys: you control your security |
| Hans-G?nter@24944 | 18 without delegating it to companies as it happens with Skype |
| Hans-G?nter@24944 | 19 or Hamachi. |
| Hans-G?nter@24944 | 20 - Each n2n user can simultaneously belong to multiple networks |
| Hans-G?nter@24944 | 21 (a.k.a. communities). |
| Hans-G?nter@24944 | 22 - Ability to cross NAT and firewalls in the reverse traffic |
| Hans-G?nter@24944 | 23 direction (i.e. from outside to inside) so that n2n nodes are |
| Hans-G?nter@24944 | 24 reachable even if running on a private network. Firewalls no |
| Hans-G?nter@24944 | 25 longer are an obstacle to direct communications at IP level. |
| Hans-G?nter@24944 | 26 - n2n networks are not meant to be self-contained: it is possible |
| Hans-G?nter@24944 | 27 to route traffic across n2n and non-n2n networks. |