Leaderboard

Wait.. in this case it's even possible to configure any BitTorrent client for this if the client offers the option to set which IP address is announced to the trackers. libtorrent-rasterbar can do that via the announce_ip option, at least (qBittorrent: Settings > Advanced > Announced IP address to trackers (Restart required)). It's a bit of a hassle, though, as you will need to know the second exit address in advance. But it should work if the tracker supports the ip parameter.

Hi, FWIW P2P DC++ client AirDC has the option to configure "External / WAN IP". I grabbed the exit 2 IP for the target device from Client's Area Ports section and copied it into the mentioned field in the p2p client paired with a couple pool#2 ports (UDP and TCP). Everything works as expected.

Hello! p2p is allowed on pool 2 but it can be really used only by those programs that let you configure which IP address to announce (non existing, as far as we know). More in general, pool 2 is not suitable for any program which announces itself autonomously. In AirVPN infrastructure, the VPN traffic reaches the Internet through one exit IP address, but "pool 2" is the set of ports of another IP address (let's name it exit IP address 2, in brief exit 2). If a program receives an unsolicited incoming packet from the Internet through exit 2, it will reply properly. This happens whenever you advertise on your own how to reach your service (a web or FTP server, a game server, and so on). However, with p2p programs, it's the program itself which must advertise. DHT or a tracker will record the address they receive the advertisement (of the port etc.) from, and they will say to other peers that your p2p program is reachable on exit 1, with its pool 1 ports; however, if you have remotely forwarded a pool 2 port, peers would never be able to reach your program, because they would send packets to a port of another IP address (exit 1, the address recorded by DHT and/or trackers). The problem could be resolved by manual setting (see for example https://userpages.umbc.edu/~hamilton/btclientconfig.html#BTConfig ) when you need to seed only - additional tests are required. This is an important limitation that might be overcome in the future, for example by letting the user pick which exit IP address its traffic must go to the Internet through. In the meantime, by using pool 2 (and when necessary additional pools) for anything different from p2p and crypto wallets, port exhaustion problem is solved (in most cases only 1 forwarded port is needed for p2p). Kind regards

It eventually started working but with the same config I was having issues with. Persistence won round but it wasn't worth it. The cpu couldn't seem to handle openvpn and speeds were too slow.