|
|
|
|
|
by justsomehnguy
1524 days ago
|
|
You probably missed > It’s a WireGuard tunnel being sent inside another WireGuard tunnel Edit: replaced with a better diagram (and again, now based on example in [0]): ▼ ▼ ▼ ▼
YOU->NL1 tunnel SE4->NL1 tunnel PLAIN/TLS
YOU ────────────────────► SE4 ───────────────────► NL1 ───────────────► CATPICS.COM
On the wire: YOU->SE4 traffic SE4->NL1 traffic NL1->CATPICS.COM traffic
┌────────────────┐ ┌────────────────┐ ┌──────┐
Inside: │YOU->NL1 traffic│ │YOU->NL1 traffic│ │ DATA │
└────────────────┘ └────────────────┘ └──────┘
[0] https://mullvad.net/en/help/wireguard-and-mullvad-vpn/ |
|
- the WireGuard public key for server 2
- the IP address for server 1
- a unique port for server2 on server 1
So all they're doing is a standard iptables redirect to the second host (which may or may not itself be under a WireGuard tunnel).