-
Notifications
You must be signed in to change notification settings - Fork 59
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
Cannot alias iptables-nft as iptables with alternatives
#342
Comments
LorbusChris
added a commit
to LorbusChris/fedora-coreos-config
that referenced
this issue
Jan 10, 2020
by adding a COSA postprocess script to raise its priority above (from 5 to 15) iptables-legacy's priority (10) with `updates-alternatives`. This workaround will be dropped once iptables-nft becomes the default implementation in F32: https://fedoraproject.org/wiki/Changes/iptables-nft-default Tracker Issue: coreos/fedora-coreos-tracker#342
LorbusChris
added a commit
to LorbusChris/fedora-coreos-config
that referenced
this issue
Jan 10, 2020
by adding a COSA postprocess script to raise its priority above (from 5 to 15) iptables-legacy's priority (10) with `update-alternatives`. This workaround will be dropped once iptables-nft becomes the default implementation in F32: https://fedoraproject.org/wiki/Changes/iptables-nft-default Tracker Issue: coreos/fedora-coreos-tracker#342
LorbusChris
added a commit
to LorbusChris/fedora-coreos-config
that referenced
this issue
Jan 10, 2020
by adding a COSA postprocess script to raise its priority above (from 5 to 15) iptables-legacy's priority (10) with `update-alternatives`. This workaround will be dropped once iptables-nft becomes the default implementation in F32: https://fedoraproject.org/wiki/Changes/iptables-nft-default Tracker Issue: coreos/fedora-coreos-tracker#342
LorbusChris
changed the title
Cannot use iptables-nft
Cannot alias iptables-nft as iptables with Jan 10, 2020
alternatives
Here is the previous conversation around firewalling: #26 This simply sounds like a bug that needs to be fixed (and you've linked to one). Can you just workaround it in ignition with the equivalent of:
|
Changing the symlink in |
14 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Fedora in F32 will use the nft implementation of iptables by default (see https://fedoraproject.org/wiki/Changes/iptables-nft-default).
Right now, however, it is not possible to alias it as
iptables
in FCOS withalternatives
even though it is installed, as one cannot change thealternatives
priority on rpm-ostree based systems (fedora-sysv/chkconfig#27) andiptables
therefore always points toiptables-legacy
.RHCOS already and exclusively uses the nft implementation, leading FCOS in that regard.
Context:
iptables-legacy
is suspected to be the cause of https://bugzilla.redhat.com/show_bug.cgi?id=1781575 which only seems to appear on systems that still use the legacy implementation.The text was updated successfully, but these errors were encountered: