-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suspected bug with ip_prefixes #1050
Comments
Signed-off-by: Kristoffer Dalby <kristoffer@tailscale.com>
Signed-off-by: Kristoffer Dalby <kristoffer@tailscale.com>
Signed-off-by: Kristoffer Dalby <kristoffer@tailscale.com>
Signed-off-by: Kristoffer Dalby <kristoffer@tailscale.com>
I think we might have actually implemented this without testing or having a purpose for this. It actually looks like it is not supported in the client https://github.com/search?q=repo%3Atailscale%2Ftailscale%20IsTailscaleIP&type=code. I'll make a PR to indicate this in the docs. |
Please use supported ranges. |
hi @juanfont Does this mean we cannot use two headscale networks? Is there a way to create two headscale networks and have a user connect to both and avoid conflicting IP addresses with other users on either network? I don't see a way to safely do that without having separate prefixes? |
@juanfont I suppose this is the right way for now: https://tailscale.com/blog/fast-user-switching/ This works perfectly and is great for what I need! |
Hi,
Thanks for your work on headscale.
I would be grateful if someone could reproduce the the following, which seems like a bug to me:
headscale v0.17.0
tailscale v1.34.0
Ubuntu 22.04
Following headscale config file:
registering nodes works fine, and headscale node list shows the expected ip addresses for the registered machines.
The problem is when you do tailscale status or tailscale ping:
Similarly from test2:
If the ip_prefixes is set to 100.64.0.0/16 it all works fine.
Thanks.
The text was updated successfully, but these errors were encountered: