Skip to content
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

[Bug] peers are not propagated to tagged nodes #2375

Open
4 tasks done
bartishv opened this issue Jan 24, 2025 · 1 comment
Open
4 tasks done

[Bug] peers are not propagated to tagged nodes #2375

bartishv opened this issue Jan 24, 2025 · 1 comment
Labels
bug Something isn't working policy 📝 tags

Comments

@bartishv
Copy link

Is this a support request?

  • This is not a support request

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

Given headscale 0.24.0, two tailscale 1.78.3 nodes one tagged as tag:device and the other as tag:proxy, and ACL

{
  "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.

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 as tag:proxy

Steps To Reproduce

  1. define ACLs as in "Current behavior" in a policy file.
  2. start headscale
  3. add two users
  4. generate two pre-auth keys - 1 for each user
  5. start two tailscale nodes, specifying pre-auth keys generated above
  6. in headscale terminal tag one node as described in "current behavior"

Environment

- Docker compose
- Headscale version: 0.24.0
- Tailscale version: 1.78.3

Runtime environment

  • Headscale is behind a (reverse) proxy
  • Headscale runs in a container

Anything else?

Similar problem was reported in #809

@bartishv bartishv added the bug Something isn't working label Jan 24, 2025
@DevId-E
Copy link

DevId-E commented Jan 24, 2025

I can confirm this. As soon as tags are removed peering defined in acls work as expected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working policy 📝 tags
Projects
None yet
Development

No branches or pull requests

3 participants