If you run a VPN for people in Russia, a plain full tunnel to a foreign VPS breaks things like banking apps: they see a foreign hosting address and refuse it. The setup I keep running for a few friends fixes that with two VPS.

Devices connect to an entry server in Russia. Traffic to Russian IP ranges leaves from there directly, and everything else goes through an AmneziaWG tunnel to a second server abroad. AmneziaWG is a WireGuard fork with obfuscation; plain WireGuard gets blocked there.

The split lives entirely on the entry: an ipset with the Russian ranges, a firewall mark and a separate routing table. Clients keep one ordinary config, and when the exit’s address gets blocked, I replace the exit without touching anyone’s phone.

Caveats: IPv4 only, and the entry sees all client traffic, so it has to be a box you trust. The write-up has the setup on Debian or Ubuntu, how to check both paths, and which commands are safe to post when you ask for help. The installer and the routing script are plain bash under MIT: https://github.com/bivlked/amneziawg-installer

I went with ipset and fwmark because it keeps the clients dumb. If you split traffic like this some other way, I’d like to hear how.