We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Given headscale 0.24.0, two tailscale 1.78.3 nodes one tagged as tag:device and the other as tag:proxy, and ACL
tag:device
tag:proxy
{ "tagOwners": { "tag:device": [], "tag:proxy": [] }, "acls": [ { "action": "accept", "src": ["tag:device"], "dst": ["tag:proxy:*"] } ] }
tailscale nodes tagged as tag:device do not receive peers. Meaning tailscale status returns only one record of the node itself.
tailscale status
Changing ACL to use users or groups instead of tags - works like a charm.
nodes tagged as tag:device should receive a peer tagged as tag:proxy
- Docker compose - Headscale version: 0.24.0 - Tailscale version: 1.78.3
Similar problem was reported in #809
The text was updated successfully, but these errors were encountered:
I can confirm this. As soon as tags are removed peering defined in acls work as expected.
Sorry, something went wrong.
No branches or pull requests
Is this a support request?
Is there an existing issue for this?
Current Behavior
Given headscale 0.24.0, two tailscale 1.78.3 nodes one tagged as
tag:device
and the other astag:proxy
, and ACLtailscale nodes tagged as
tag:device
do not receive peers. Meaningtailscale status
returns only one record of the node itself.Changing ACL to use users or groups instead of tags - works like a charm.
Expected Behavior
nodes tagged as
tag:device
should receive a peer tagged astag:proxy
Steps To Reproduce
Environment
Runtime environment
Anything else?
Similar problem was reported in #809
The text was updated successfully, but these errors were encountered: