-
-
Notifications
You must be signed in to change notification settings - Fork 360
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] -ls23 and onwards has issue with adding iptables rules #325
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
I have the same issue on qnap. uname -r |
Same issue here in a arm64 uname -a I solved it, using "legacy" version --> arm64v8-1.0.20210914-legacy |
Looks like this here is the culprit: https://git.alpinelinux.org/aports/tree/main/iptables/iptables.post-upgrade?h=3.19-stable We'll evaluate internally how best to move forward. |
My solution/workaround was to pin the version to "v1.0.20210914-ls22". That way there is no need for the "legacy" build. |
For what it's worth, I had to |
Is there an existing issue for this?
Current Behavior
when there is a PostUp command iptables break:
[#] iptables -A FORWARD -i wg0 -j ACCEPT; iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE iptables v1.8.10 (nf_tables): Could not fetch rule set generation id: Invalid argument
Expected Behavior
The tunnel should be up
Steps To Reproduce
add to Interface
PostUp = iptables -A FORWARD -i wg0 -j ACCEPT; iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: