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

Use nftables instead of iptables-legacy #3673

Merged
merged 1 commit into from
Aug 22, 2024
Merged

Conversation

thallgren
Copy link
Member

Some time ago, we introduced iptables-legacy because users had problems using Telepresence with Fly.io where nftables wasn't supported by the kernel. Fly.io has since fixed this, so Telepresence will now use nftables again. This in turn, ensures that modern systems that lack support for iptables-legacy will work.

Closes #3542

Some time ago, we introduced iptables-legacy because users had problems
using Telepresence with Fly.io where nftables wasn't supported by the
kernel. Fly.io has since fixed this, so Telepresence will now use
nftables again. This in turn, ensures that modern systems that lack
support for iptables-legacy will work.

Closes #3542

Signed-off-by: Thomas Hallgren <[email protected]>
@thallgren thallgren added the ok to test Applied by maintainers when a PR is ready to have tests run on it label Aug 22, 2024
@github-actions github-actions bot removed the ok to test Applied by maintainers when a PR is ready to have tests run on it label Aug 22, 2024
@thallgren thallgren merged commit 890ad63 into release/v2 Aug 22, 2024
11 checks passed
@thallgren thallgren deleted the thallgren/nftables branch August 22, 2024 15:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Traffic-agent using incompatible iptables-variant (legacy instead of nft)
1 participant