I can confirm that without linux-modules-extra-*, iptables is broken.
Reduced test case:
$ sudo iptables -L -n
iptables: No chain/target/match by that name.
Full test case:
$ sudo /usr/share/ufw/check-requirements -f
...
ERROR: could not create 'ufw-check-requirements'. Aborting
FAIL: check your
Marking the ufw task as Invalid. The kernel doesn't have what is needed
to run iptables.
** Changed in: ufw (Ubuntu)
Status: New => Invalid
** Changed in: ufw (Ubuntu)
Assignee: Jamie Strandboge (jdstrand) => (unassigned)
--
You received this bug notification because you are a membe
Diff between two identical instances, one with -generic and one with
-virtual.
iptables* commands working find with -generic.
** Attachment added: "kernel-diff.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823862/+attachment/5254621/+files/kernel-diff.txt
--
You received this b
Dropping ufw from the test case - just running sudo iptables-save
against the virtual kernel produces no output.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1823862
Title:
disco: unab
This might have some implications for fan usage on cloud instances as I
see some fan-* rules post switch to generic kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1823862
Title:
OK I think I've figured it out; the cloud images use the -virtual
kernel, which does not install linux-modules-extra-*.
If I install the -generic kernel or just the extra modules and reboot,
then iptables commands start working again.
** Changed in: ufw (Ubuntu)
Status: Incomplete => New
6 matches
Mail list logo
