Bootstrapper nodes as relay server

[tangdou1]

No description provided.

[danimesq]

Move the rest of the title as issue description

[danimesq]

About your IPv6 pull request?
Please can you resolve the conflicts with the latest ZeroNet updates?
@HelloZeroNet @shortcutme when you will review this pull request?

[tangdou1]

About your IPv6 pull request?
Please can you resolve the conflicts with the latest ZeroNet updates?
@HelloZeroNet @shortcutme when you will review this pull request?

It is a small conflict, just the number of version.
If shortcutme is ready to ignore that ipv6 pull request, there will be more conflict files. Anyway, hope that ipv6 pull request can provide a little help to the future ipv6 function designed by shortcutme in zeronet.

[HelloZeroNet]

Original title: "A idea that improve current performance of connecting : based on the fact that many users are passive users, while only a few users are active users ( means having public ip), a picture or any optional file uploaded by user A(passive) can be downloaded by user B (also passive), only when a kind and active user C is willing to seed this file of user A and the user B luckly find user C through trackers. However, these active and kind users are so few compared to the number of passive users ( I would say 99.99999% of users in china is passive users). A suggestion is that the zero tracker ( bootstrapper tracker) can aslo pay a role like a relay server in software Syncthing which just help user B connect to A."

[tangdou1]

Reference
https://github.com/ntop/n2n

Introduction for N2N

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:

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: 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.

[tangdou1]

Oh, I found simeone has presneted this suggestion before. see: #844