dedicated wg vpn

Tom,

Wired up a new VPN server. Your client conf + creds are in the attached zip.

Quick picture: WireGuard itself never goes out on the wire. Your laptop talks WG to localhost, and a tiny wrapper stuffs it inside normal HTTPS to 24.89.146.106:443. From an ISP’s view it just looks like HTTPS. Your tunnel IP is 10.88.0.10. Right now the door only opens if you’re coming from a 172.x address.

Zip password: I sent in a text
it's AES-256, so you'll need to use winrar or 7-Zip . . .

1 Unzip the attach with 7-Zip.

2 Install WireGuard and Python 3 if you don’t have them.

3 From the unzipped folder, run this and leave it open:

4 python cover\videotun.py client --host 24.89.146.106 --port 443 --token-file cover\token --pin-cert cover\server.crt

5 In WireGuard, import wireguard\tom.conf and hit Activate.

6 Ping anything inside the network, e.g. try to the rustdesk server, 192.168.1.78 or .145 or .70 ... it should respond back through the tunnel, confirm you're connected

I'm sorry it grew complex, it got complicated with the HTTPS obfuscation, and I am sorry I am to blame. So, I am developing a windows binary with individual keys+everything bundled into it, so we can just distribute/execute a single binary for other users... However, for now we will need to use python and wireguard. The reason you will need python is because I added an additional layer of obfuscation and encapsulation over-top the wireguard protocol, for all intents and purposes, it looks like HTTPS web traffic from client < -- > ubiquity 24.89.146.106

Right now, the inbound NAT only applies to 2 class 8's 172.0.0.0/8 and 50.0.0.0/8 source ranges. . . class A for now because I'm developing it.

Let me know if this will work for you. I'm attaching the zip and will text you a password now.