Forums before death by AOL, social media and spammers... "We can't have nice things"
|    linux.debian.bugs.dist    |    Ohh some weird Debian bug report thing    |    28,835 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 28,538 of 28,835    |
|    zipdox to All    |
|    Bug#1128686: Transition from iptables to    |
|    22 Feb 26 13:50:01    |
      From: zipdox@protonmail.com              Package: libvirt-daemonVersion: 12.0.0-1       Severity: grave              I'm not sure I know exactly what's going on here. I marked this bug as grave       at it makes KVM completely unusable unless you don't use networking. I believe       Debian unstable moved from iptables to nftables a while ago, which broke       libvirt networking. I've        been getting around that by using an older kernel (6.17.x, don't remember       exactly which one) but that stopped working after I upgraded yesterday.              I get the following error when I try to start the default (NAT) network:       $ sudo virsh net-start default       error: Failed to start network default       error: internal error: Failed to run firewall command iptables -w --table       filter --list-rules:              Running that command manually I get:       $ sudo iptables -w --table filter --list-rules       modprobe: FATAL: Module ip_tables not found in directory /lib/mo       ules/6.18.12+deb14-rt-amd64       iptables v1.8.12 (legacy): can't initialize iptables table `filter': Table       does not exist (do you need to insmod?)       Perhaps iptables or your kernel needs to be upgraded.              Again, I'm not sure exactly what's going on here. It's possible this issue was       already reported, but I couldn't find it.              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca