371–380 of 500 posts
This sounds super cool. Any chance more of the client will be open sourced? (I presume this uses the recently-released Rust WireGuard core?)
Not right now. The burden of supporting that as open source would be too high.
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 couldn’t understand the wireguard documentation enough to setup my own install without resorting to algo Not sure what you mean. Algo has no relationship to WireGuard; it's basically a customized StrongSwan setup under the hood, which utilizes IKEv2 (not WireGuard) as the transport.
Earlier quoted context omitted.
Here's what I posted to our blog when this question came up: https://blog.cloudflare.com/boringtun-userspace-wireguard-ru... We communicated with Jason throughout the process and have a ton of respect for him and the entire WireGuard community. In the short term, we need the flexibility to quickly update BoringTun's code base to support the project we built it for. That's harder when you need to coordinate with peopl…
I guess that doesn't make sense to me. If Jason offered you your own sub-project to run with, why can't you "move fast"? >I thought the invitation to put their engineers as the head of a WireGuard subproject was a cool invitation, but alas. https://lists.zx2c4.com/pipermail/wireguard/2019-March/00404... I mean no offense, but the response comes off as corporate approved PR. "We need to move fast" when you haven't act…
More importantly, without having already tried it, it’s hard to predict how much overhead there will be.
Since CloudFlare had a (self-imposed) deadline, working fast had to take priority over optics. After all, the project can always be folded into the WireGuard organization later.
It seems to me that in practice, Cloudflare's mission is not actually to build a better Internet, but to offer an alternative, proprietary network (one could call it the CloudflareNet), and convince content providers and consumers to use that network. Because I don't want any single company to have too much power, I'll stick with the standard Internet, which is not owned by any single company. However, I realize that…
Having worked in an ISP, only one thing mattered to costumers, and only one thing: YouTube.
Earlier quoted context omitted.
Netflix will never even try to show you 4K on a mobile device. The ISPs know this. They just want to throttle Netflix so that you'll prefer the ISPs streaming service to Netflix.
I think it's more about double dipping and getting extra money for network agreements and near-side content servers from Netflix.
Earlier quoted context omitted.
From personal experience: When coupled with an DNS based ad blocker Wireguard can actually make your internet faster than when not using it. More so on Android than iOS and more so on mobile than fixed, but still feels so much smoother. you can even only forward the DNS requests and not the rest of the data so your home upload speed won't become your bottleneck.
This is precisely my setup, and I couldn't be happier. I have a lot of internal infrastructure including pi-hole, confluence and a number of self-hosted services. WireGuard lets me go anywhere on my laptop and its like I never left home, and I just keep two configurations for when I want to forward only internal IP addresses, or all my traffic.
The only thing I was never able to get working was the IPv6 support. Oh well...
>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.
Just as an aside, I thought that was an exceptionally well-written product announcement, or press release, or whatever you'd call it. It was long, but I didn't mind reading the whole thing. It answered all the basic questions about why I should use it, how they plan to make money, and with enough technical detail that I understood essentially how it works. It was very much the opposite of the marketing material you g…
> exceptionally well-written product announcement Yup... a rare beast these days. My niece is a gifted writer - one of less than a half dozen that I personally know. She graduated recently and had her pick of several positions due to her portfolio of work.
Aside from previous job experience, what sort of things are in a portfolio like this?
>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.
> We built Warp around WireGuard So basically Cloudflare created an app with Cloudflare branding and set up a Wireguard server for everyone. No bad, but just check out the original: https://www.wireguard.com While I am not a big fan of VPNs in general, I have to admit, that Wireguard performs exceptionally well. I tested it a week ago and the added latency is pretty much just the network latency and the bandwidth los…
You can go on the wait-list for WARP+ which sounds like it’ll route everything over the VPN.