To xena's point, we're not currently enforcing the limits :) We've been very cautious about that since, as I mentioned in a comment elsewhere, the limits have always been an experiment.
We're definitely considering it. We introduced the limits a while back as an experiment. In most cases, I believe the current limits don't make a lot of sense. Fundamentally, we were hoping to encourage the deployment of Tailscale to end devices (partially to increase users' security, partially to get a better idea of how widely Tailscale is actually being used). Unfortunately, the limits introduce the kinds of headaches that you're describing (and for IoT it can be a showstopper). The net effect across all users could be to actually discourage people from having fun and tinkering with Tailscale, which is the last thing we want.
Would you mind describing some of the other use cases you have for subnet routers? Do you have other mini k8s clusters you want to use them for? Other things? I'd love to learn more.
It’s a deep hole for a company to dig itself out of, not to mention changing the habits of people to explicitly document things elsewhere.
It would be neat if Slack reported stats on searches so that, for example, a company could better understand what key conversations should be moved into proper documents…but this is likely against Slack’s interests.
I wouldn't say mistimed so much as "we were excited to get the post up". Node sharing is indeed in invite-only beta, though we're planning on opening that up very soon. Apologies for any frustration/confusion.
I was on the "silicon level debugging" team, which took test cases like this and boiled them down to x86, then through the CMS to p95 assembler, then down to the circuit and device level to figure out the speed paths. There were definitely some crazy issues we found. Honestly, I couldn't have done that job without relying on 80%+ of my undergrad courses (Computer Engineering @ Waterloo).
The issue I remember the most clearly was one that an engineer Simon Barrett discovered: a specific sequence of MMX instructions would cross-talk (and cause the occasional bit to flip) on two perpendicular busses in the pipeline when run at a specific voltage/frequency. It sounds simple enough, but imagine trying to figure that one out.
I worked at Transmeta for a short time (about a year) after my undergrad. I loved it. However, there was always a running joke that the stock ticker symbol should have been “HYPE”. It was sad to see things implode the way they did.
(Co-founder here). It's coming, I promise. I'm as excited as you are. We wanted to iron out the kinks on mobile (i.e. iOS) before duplicating them on another platform. Thankfully, we're past that point now.
(Co-founder here). If you're referring to the free tier, it only supports a single email address at the moment. What some people have been doing is to create a fake Gmail address and sharing that with their family/friends to use as a common login.
We've been exploring the idea for a free (or significantly discounted) "family" plan (or even something like that for small teams). Please stay tuned over the coming weeks for some updates to our pricing and tiers.
(Tailscale co-founder here). I certainly appreciate the feedback and suggestions. We've had pricing inquiries from individuals all the way to enterprise. Finding the right set of features at the right price is something we're going to spend a lot of time exploring (for instance, some larger companies don't care too much about ACLs, but some smaller ones really, really do). Right now, all I can say for certain is that our pricing page will change and that we're open to discussion.
I'd love to hear more of your thoughts on where you think we can add value and what it might be worth to you. If you're up for it, please email me at [email protected] Regardless, thanks again for the input.
(Tailscale co-founder here). I also loved Crawshaw's post. It really took me back, though I certainly wasn't doing the kind of hacking he was.
I, for one, really appreciate the nod. I agree our motivations align and I look forward to hearing more about what you and team come up with. All the best on things at ZeroTier.
(Co-founder of Tailscale here) To that end, we started publishing a "blueprint" for people who want to DIY. There's more to explain (and questions encouraged). Please check it out: https://tailscale.com/blog/how-tailscale-works/
Building on what katnegermis said, this is what we're trying to help with. We integrate with identity management systems and handle the key management (and NAT traversal) on top of WireGuard, making it easier to deploy and manage.
This is what we (https://tailscale.com) are working on! WireGuard is incredible, but adding some key management (that integrates with your IAM system) and NAT traversal really helps to round things out. I'd love to hear suggestions and feedback on what we're building.
https://motion-project.github.io/ made it really easy for me to setup a webcam on my Raspberry Pi. Accessing that using HTTP over WireGuard (via Tailscale) from my iPhone when out of the house was one of those "delight and amaze" moments.
We integrate with existing identity providers (for instance, GSuite, Okta, Ping, AD) to perform authentication and generate keypairs. Public keys are shared via a coordination server (and each device's private keys never leave it). There's an (optional) additional layer of authorization required in which an admin reviews the endpoints asking to connect. A combination of user and machine certificates makes it possible to ensure that both the users and machines are managed properly.
So, basically, we're enabling the "enforcement" side of identity and policy management at the networking layer, with visibility into users and their devices.
I hope this helps! Please keep the questions coming.