warp-cli is Cloudflare’s program to use their Warp VPN/DNS thingy. Since it only allows for closest server being used, I thought about putting it on my VPS.
So I did. I enabled the connection, and oh, SSH froze. No worries, I’ll reconnect.
Unless… Yeah, it blocks incoming connections.
Tailscale comes to rescue.
But anyway, the warp-cli settings only allow excluding IP ranges for both directions, so 0.0.0.0/0 makes it pointless.
My only current idea is caveman solution - another VPS (for static IP) as first hop, excluding just that IP on second hop, for third hop to Warp.
Sadly, RackNerd has finally removed all the old offers, so no more $10.29/year VPSs.
Oh, and Tailscale will only work over relay when Warp is connected, so that’s not an option.
Dumbass here…why would a VPN block incoming connections? Seems counter to what a VPN does.
The Cloudflare bit, at least their consumer product in question only works as a public VPN (such as Mullvad, IVPN, etc…), meaning it’s more of an encrypted proxy. So it doesn’t counter anything.
Why it blocks incoming connections on other interfaces ¯\_(ツ)_/¯
It only makes sense for it to capture all outgoing connections not destined to split-tunneled IP ranges, as to prevent leaks.Weird
Microvms or containers could give you external control of the networking. Then you would put whatever you want behind warp inside the warp container/vm.
