You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Users in group access (user1) now cannot access to 172.16.0.21. If I change net.dns01 with net.vlan0 in ACL, user1 can ping
172.16.0.21 (and other addresses in 172.16.0/24 too which is undesirable). Previous version 0.22.3 was allowed access to hosts with /32 mask.
Environment
OS: Linux
Headscale version: 0.23.0-alpha5
Tailscale version: 1.56, 1.60
Headscale is behind a (reverse) proxy
Headscale runs in a container
To Reproduce
Have subnet router and ACLs to networks behind it.
Bug description
We have tailnet network with node1 as subnet router to
172.16.0.0/24
network.After updating to 0.23.0-alpha5 some of our users lost access to resources provided by ACL. Here short example of acl.yaml:
Users in group
access
(user1) now cannot access to 172.16.0.21. If I changenet.dns01
withnet.vlan0
in ACL, user1 can ping172.16.0.21 (and other addresses in 172.16.0/24 too which is undesirable). Previous version 0.22.3 was allowed access to hosts with /32 mask.
Environment
To Reproduce
Have subnet router and ACLs to networks behind it.
Logs and attachments
netmap with acl /32 in config:
netmap with acl /24 in config:
The text was updated successfully, but these errors were encountered: