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
I am in the process of packaging clevis for Chimera Linux, which uses initramfs-tools for initramfs. Everything works fine and clevis can decrypt both luksv1 and luksv2 with tpm.
However, I am facing one issue in the local-bottom/clevis script. When the script brings down all interfaces, the command on line 50, ip route flush dev "$iface", results in the following error Error: ipv4: FIB table does not exist
The error itself is harmless and boot proceeds like normal, but it should probably be silenced or clevis should no attempt to bring down interfaces it has not brough up
The text was updated successfully, but these errors were encountered:
Are you sure this is caused by attempting to bring down interfaces it has not brough up? The warning/error message is about accessing routing table that does not exist. Here they fixed it by simply ignoring the errors (redirecting to null).
You're right, it's missing routing tables. I got a bit confused by the comment. Would redirecting to errors /dev/null be a statisfactory solution for clevis?
You (or I) can create a Pull Request and see, what the maintainers think. For me this would be a sufficient fix, because that is kind of a warning anyway and the result is not important for the shutdown.
I am in the process of packaging clevis for Chimera Linux, which uses initramfs-tools for initramfs. Everything works fine and clevis can decrypt both luksv1 and luksv2 with tpm.
However, I am facing one issue in the local-bottom/clevis script. When the script brings down all interfaces, the command on line 50,
ip route flush dev "$iface"
, results in the following errorError: ipv4: FIB table does not exist
The error itself is harmless and boot proceeds like normal, but it should probably be silenced or clevis should no attempt to bring down interfaces it has not brough up
The text was updated successfully, but these errors were encountered: