Live data from Hacker News

Warp – Mobile VPN

blog.cloudflare.com

361–370 of 500 posts

Re: Warp – Mobile VPN

#361
post #350

Earlier quoted context omitted.

An interesting trick - if Cloudflare allows it - would be Device -> Tor -> This -> Internet. Tor provides anonymity, this provides protection against exit nodes maliciously modifying traffic (you can find a number of examples of this just by searching).

Yes! Routing VPNs through Tor is a great way to avoid site discrimination against Tor users. But there are two key problems. One is that you degrade Tor anonymity, because Tor can't switch circuits (normally at ~10 minute interval). And also because you typically must pay for VPN services. The other problem is that Tor only routes TCP traffic. So when you use TCP-based VPNs routed through Tor, and are using HTTPS or…

> Warp via Tor via Warp

Warp would see all your incoming packets and all your outgoing packets, so why bother with Tor?

Re: Warp – Mobile VPN

#362

Earlier quoted context omitted.

It's only near you when you're at home though. This works around the world.

wouldn't be that difficult to write a script that checks geoip and launches a VPS in the region closest to your current devices public address. You could even create an iOS shortcut to allow you to do it from your iPhone

Several billion-dollar businesses have been built doing things that "wouldn't be that difficult".

In this case, I agree that a single VPS is usually enough for most but never underestimate the market power of making things simpler and faster.

Re: Warp – Mobile VPN

#363
How is Cloudflare handling IP allocation here? I might be mis-understanding how WireGuard works, but it doesn't look like there is an official method for IP dynamic assignment.

Re: Warp – Mobile VPN

#364
post #149

Earlier quoted context omitted.

I consider myself fairly competent, and I couldn’t understand the wireguard documentation enough to setup my own install without resorting to algo [0]. There’s real value in wrapping a system like WireGuard into a product, because it democratizes technology rather than making it available only to those knowledgable enough to understand how to set it up. I think Warp is great in that regard. [0]: https://github.com/tr…

I am still trying to figure it out how to setup a Wireguard server on Kubernetes/GKE to personal use. Outline and OpenVPN clients have some problems that's why I want to try Wireguard.

You could put it in a micro VM in the same VPC as the GKE cluster, and then have a 2019-grade bastion host.

Re: Warp – Mobile VPN

#365

Earlier quoted context omitted.

Yes! Routing VPNs through Tor is a great way to avoid site discrimination against Tor users. But there are two key problems. One is that you degrade Tor anonymity, because Tor can't switch circuits (normally at ~10 minute interval). And also because you typically must pay for VPN services. The other problem is that Tor only routes TCP traffic. So when you use TCP-based VPNs routed through Tor, and are using HTTPS or…

> Warp via Tor via Warp Warp would see all your incoming packets and all your outgoing packets, so why bother with Tor?

Good point. I was getting carried away, there.

But still, if it were done right, that's not necessarily true. I mean, I can have two accounts with some VPN service. I connect to server1.vpn.com using one account. Then I connect to the Tor network via that VPN tunnel. And then I connect to server2.vpn.com via Tor, using the other account. Even better, I connect to server2.onion, using the other account.

Even then, Cloudflare could easily do traffic correlation. But as it is now, the NSA can easily do traffic correlation. So hey.

Re: Warp – Mobile VPN

#366
post #275

Earlier quoted context omitted.

Ouch. Do you know which PoP (point of presence) you're hitting? To find out, Look at the last three letters in the CF-Ray header on any response from a Cloudflare site, e.g. curl -v cloudflare.com 2>&1 | grep -i CF-Ray The letters should correspond to an airport code nearby the CF server you landed on. Let me know what it says.

CF-RAY: 4c0c98839feb5ff3-MRS Its hitting the Marseille, France POP. I posted the issue (bad route) on the community forum a few months ago. https://community.cloudflare.com/t/high-ping-sri-lanka/15276...

OK, so it seems like Cloudflare in general is not serving your ISP very well for some reason. :( Hopefully our network team will be able to look into it.

Re: Warp – Mobile VPN

#367
post #363

How is Cloudflare handling IP allocation here? I might be mis-understanding how WireGuard works, but it doesn't look like there is an official method for IP dynamic assignment.

From what I reckon this (and almost any other VPN, or even Tor) will give you the outside appearance of the IP of the exit node. Think like NAT.

Re: Warp – Mobile VPN

#368

They've glossed over a few details that I'm curious about: 1. What will the exit IPs be? Will I get to stay with-in my region and access region specific content, or can I bypass censors, both government (porn, "glory of Islam", etc), and private (Netflix region-specific content, GDPR non-compliant websites that accidentally block my region). 2. Can I select my own exit region? 3. How do they handle abuse? Can I spam…

1. It will exit close to you, unless you have Warp+ in which case we might route it to a different PoP closer to your destination if that makes it faster. It is not designed to bypass censors. 2. No 3. Exactly what an actually nefarious person WOULD say!

Thank you for your answers!

> Exactly what an actually nefarious person WOULD say!

It's hard to distinguish between curious and nefarious people after a point, I suppose ;) but that's still not an answer :)

Re: Warp – Mobile VPN

#369
This is so awesome from the general safety, convenience (super simple to use!) and speed perspective. I would gladly pay to have the option to be able to choose which datacenter I connect to.

Re: Warp – Mobile VPN

#370
post #284

>TCP, the foundational protocol of the Internet, was never designed for a mobile environment. Amusingly, this is actually not true. TCP was originally developed to run on an inter-network over two networks: the ARPANET which has the reliability characteristics of a "traditional" network, and an extremely mobile network with lots of packet loss: ship-to-ship packet radio. TCP today seems very poorly suited for the mob…

My interpretation of “not designed for mobile” is mobile devices, not mobile network. In particular, TCP is not designed for a scenario where the device keeps leaving old networks and joining new ones, or where a device routinely has 2 network interfaces where one has better performance than the other but which one is better changes frequently.
Post reply on HN