4 ms·

Love tailscale! Set it up a couple weeks ago and it’s very fun to use. MagicDns is great! I can go http://macmini http://macmini anywhere and it just works Jus

Love tailscale! Set it up a couple weeks ago and it’s very fun to use. MagicDns is great! I can go http://macmini http://macmini anywhere and it just works Just wish they offered more subnet routers. I’m as much hobby as hobby can be, and already hit the limit (one on my mini k8s cluster, one at home, that’s it. They don’t allow you to have more). Been stuffing the sidecar awkwardly into everything to get around it If someone from tailscale is reading this - please consider upping the limit of subnet routers. I’ll have to switch to ZeroTier once I want another one which doesn’t have those restrictions. Even paying for the hobby pro plan is just upping it from 1 -> 2

xena 4y ago
Tailscalar here. For what it's worth there's no hard limit on subnet routers at this time. My personal tailnet is using 8 of them.
- dfcarney 4y ago
  (co-founder here) 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.
  - artdigital 4y ago
    wow TIL! That makes me less anxious about that hobby pro restriction. Gonna get another subnet router deployed later :)
chipsa 4y ago
The Github team org plan (for connecting friends and family) had a subnet router limit of 5, if you want to legitly get a higher limit rather than just ignoring the limit that they don't check.
- artdigital 4y ago
  Oh what, is the limit not being enforced? I didn’t even bother trying to spin up another one because everything goes through that admin console, so I was sure there’d be a “you hit your limit” message Dang now I know what I’ll be doing tonight
  - chipsa 4y ago
    AFAIK, they've publicly said they don't enforce any of the limits, at this time, because it's not worth it to do the engineering yet, and might never be worth it.
dfcarney 4y ago
(co-founder here) 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.
- artdigital 4y ago
  thanks for the explanation! > 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). that makes sense, I also got the feeling that's the recommended way to run tailscale, and it's nice to be able to address services directly by their dns name > 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. Yes that's mainly it. I am probably an edge case because I have mini k8s clusters for different things. I have 2 main networks: My network at home, then my main k8s for my personal cloud stuff, those 2 are pretty constant (but want to spin up a separate IoT network soon that may or may not need a router). Then depending on what I work on, I might spin up other k8s clusters (I'm one of those odballs that really enjoys working with k8s for personal stuff) I think for me it's mainly to have piece of mind to not run into limitations later on, after I'm already locked in and need to rip-out tailscale to replace with ZeroTier
  - dfcarney 4y ago
    Thanks! This is helpful. We need to make some changes to our pricing/plans and every bit of input will shape that.
- 4y ago

xena 4y ago

Tailscalar here. For what it's worth there's no hard limit on subnet routers at this time. My personal tailnet is using 8 of them.

dfcarney 4y ago
(co-founder here) 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.
- artdigital 4y ago
  wow TIL! That makes me less anxious about that hobby pro restriction. Gonna get another subnet router deployed later :)

chipsa 4y ago

The Github team org plan (for connecting friends and family) had a subnet router limit of 5, if you want to legitly get a higher limit rather than just ignoring the limit that they don't check.

artdigital 4y ago
Oh what, is the limit not being enforced? I didn’t even bother trying to spin up another one because everything goes through that admin console, so I was sure there’d be a “you hit your limit” message Dang now I know what I’ll be doing tonight
- chipsa 4y ago
  AFAIK, they've publicly said they don't enforce any of the limits, at this time, because it's not worth it to do the engineering yet, and might never be worth it.

dfcarney 4y ago

(co-founder here) 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.

artdigital 4y ago
thanks for the explanation! > 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). that makes sense, I also got the feeling that's the recommended way to run tailscale, and it's nice to be able to address services directly by their dns name > 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. Yes that's mainly it. I am probably an edge case because I have mini k8s clusters for different things. I have 2 main networks: My network at home, then my main k8s for my personal cloud stuff, those 2 are pretty constant (but want to spin up a separate IoT network soon that may or may not need a router). Then depending on what I work on, I might spin up other k8s clusters (I'm one of those odballs that really enjoys working with k8s for personal stuff) I think for me it's mainly to have piece of mind to not run into limitations later on, after I'm already locked in and need to rip-out tailscale to replace with ZeroTier
- dfcarney 4y ago
  Thanks! This is helpful. We need to make some changes to our pricing/plans and every bit of input will shape that.
4y ago