trojan VS natter

A fellow Aussie currently in China, a Trojan [0] server has been working fine for the last week I've been here. I've got it hosted through a VPS (smaller provider) in LA. While it's a bit of a pain to setup, reliability has been rock solid and definitely useable - my laptop is connected 24/7 and I can access the unfiltered web, including video, just fine. V2ray also supposedly works quite well, but I haven't looked into it.

[0] https://github.com/trojan-gfw/trojan

Normal VPNs that you can see ads all over the place like N*rdVPN won't work, period. The correct way is to rent a few servers from different providers, make sure their ips are not blocked, and build your own V2Ray or Trojan service first. The Chinese gov will not be able to distinguish your Trojan traffic from ordinary https traffic, so the only thing that's sus to them would be the fact that all your traffic goes to one foreign ip, but I've been doing it for a few years without officials knocking on my door so yeah I think it will work for you as well. I don't take responsibility tho, do your research.

(TrojanGFW)[https://github.com/trojan-gfw/trojan] and (V2Ray)[https://github.com/v2fly/v2ray-core]. But you need your own server to do it, and some few tweaks. For first-timer it might be quite confusing to configure, but you will understand how it works in the long run. You could also tunnel your connection to your server which then forward it to protonvpn (which what I'm doing rn).

v2ray or Trojan

I dabbled with QUIC a few years ago and I cannot agree more. It was pleasant to work with, and because it's UDP based, suddenly you can do NAT hole punching more easily.

Funny that you mentioned a VPN, because I make a little experimental project back then to hole punch between two behind-the-NAT machines and deliver traffic between them over QUIC. I was able to make my own L2 and L3 bridge across the WAN, or just port forward from one natted endpoint to an endpoint behind a different NAT.

At one point I used it to L2 bridge my company's network (10.x) to my home network (192.168.x), and I was able to ping my home server from the bridging host. It was quite fun.

Here's the project if anyone is interested: https://github.com/binwiederhier/natter -- it's probably defunct, but it was only experimental anyway.