There are many VPN solutions on the market, but they do not take into account an important problem: all clients that use VPN are not accessible from the Internet. Hence, if the whole swarm is behind VPN then there will be no one to seed.
BitTorrent exchange requires that at least one peer in a pair has a white IP and the client port is open on it.
But then the chicken and egg dilemma follows. We have conflicting requirements:
1. Support P2P exchange
Connecting to p2p network directly via ISP link will reveal your data. Absolutely everyone on the Internet (including copyright trolls) knows what movies you have on the disk. Your ISP's public address:port gives them enough information to trace you and then pursuit.
Another problem to p2p exchange: firewall restrictions.
To bypass firewall restrictions, the tracker can be reached through a proxy server. But not every protocol allows you to open a port on a server. Only the SOCKS protocol allows you to open a port on the server. But not every torrent client can do this. SOCKS also has no encryption.
Let's say a torrent client (a BitTorrent application for downloading) has a VPN connection. Let's say we pass the white IP to the torrent client via VPN. This reduces the security of the host running the torrent client, because all ports are accessible from the Internet, and only paranoid users have strong passwords and security policies on home appliances.
If you are not concerned about copyright infringement, you would not want to transmit all the traffic through the VPN - this will slow down the p2p exchange. Then the VPN is needed primarily for access to the tracker. So you don't need to transfer p2p traffic over the VPN. This is solved by routing - the VPN is configured accordingly.
It is possible to configure a static port on a torrent client, and configure a static port mapping on a vpn server. The question is, how do the other peers learn about the external IP? In principle, the tracker can be accessed from the same white address of the vpn server on which the port is open, or on the vpn server you can intercept requests to the tracker and insert the argument "ip=" into the announce request. But the torrent client still exchanges peers via the PEX, DHT and uTP protocols, which, according to this idea, go past the VPN directly through the provider. So you need to ensure that the torrent client knows its public IP. Perhaps this is configured in configuration files in some clients. But absolutely all torrent clients support UPnP-IGD and NAT-PMP protocols. According to these protocols, the torrent client: 1) opens a port on a white address; 2) recognizes the white address of the gateway. Thus, by placing the UPnP-IGD service on the VPN server, we will deliver the white IP address to the torrent client with a strict level of security.
It turns out that the ports on the VPN server will be open for different torrent clients on the same white IP, which will add anonymity.
For users don't bother copytight infirgement risks and looking for network firewall bypass only (government/corporate restrictions bypass) we may offer an optimized setup to speed up downloading. The service is based on OpenVPN technology.
Now we are starting the testing period for our service. For a couple of weeks we are offering the service for free. To submit request jot down an email to firstname.lastname@example.org.