-
Notifications
You must be signed in to change notification settings - Fork 2.1k
util/linuxfw, wgengine: allow ingress to magicsock UDP port on Linux #10370
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
Conversation
Updates #9084. Currently, we have to tell users to manually open UDP ports on Linux when certain firewalls (like ufw) are enabled. This change automates the process of adding and updating those firewall rules as magicsock changes what port it listens on. Signed-off-by: Naman Sood <mail@nsood.in>
8524910 to
15d5e0d
Compare
Signed-off-by: Naman Sood <mail@nsood.in>
Signed-off-by: Naman Sood <mail@nsood.in>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This all looks great! Have you had a chance to test this on a variety of linux distros? No better test coverage than tests that arent tests lol
And afaict youre mostly changing the wiring in userspace.go - that should apply to use in both tailscaled.go and tsnet.go, but maybe double check the way that tsnet initializes all the subsystems is compatible with your changes?
Signed-off-by: Naman Sood <mail@nsood.in>
|
@twitchyliquid64 tested on arch+no firewall, fedora+firewalld, and ubuntu+ufw, seems to correctly create the iptables/nftables rules in all of those cases. looking at tsnet/tsnet.go, it seems like tsnet uses a fake router, not the linux one, so this should not affect tsnet at all, I think? |
|
Excellante! |
Updates #9084.
Currently, we have to tell users to manually open UDP ports on Linux when certain firewalls (like ufw) are enabled. This change automates the process of adding and updating those firewall rules as magicsock changes what port it listens on.