[GH-ISSUE #233] webvirtcloud on Debian 10 (Buster) - IPTables glitch... #156

New issue

Closed

opened 2026-02-27 15:57:33 +03:00 by kerem · 3 comments

kerem commented

2026-02-27 15:57:33 +03:00

Owner

Originally created by @4920441 on GitHub (Apr 6, 2019).
Original GitHub issue: https://github.com/retspen/webvirtcloud/issues/233

Hi,
after a couple of minutes I installed everything on my test host. The 'admin' accound led into some funny errors, but a newly generated 'superuser' account seems to fix all the auth problems whatsovever....

Generating and editing a guest is now possible, but I am not able to start any virtual network device, because of this error:

Error: internal error: Failed to apply firewall rules /sbin/iptables --table filter --insert INPUT --in-interface virbr0 --protocol tcp --destination-port 67 --jump ACCEPT: iptables v1.8.2 (nf_tables): CHAIN_ADD failed (No such file or directory): chain INPUT

Any hints?

I am also nut sure what is meant by "no such file or directroy"? iptables is accessible .

Cheers,

Originally created by @4920441 on GitHub (Apr 6, 2019). Original GitHub issue: https://github.com/retspen/webvirtcloud/issues/233 Hi, after a couple of minutes I installed everything on my test host. The 'admin' accound led into some funny errors, but a newly generated 'superuser' account seems to fix all the auth problems whatsovever.... Generating and editing a guest is now possible, but I am not able to start any virtual network device, because of this error: Error: internal error: Failed to apply firewall rules /sbin/iptables --table filter --insert INPUT --in-interface virbr0 --protocol tcp --destination-port 67 --jump ACCEPT: iptables v1.8.2 (nf_tables): CHAIN_ADD failed (No such file or directory): chain INPUT Any hints? I am also nut sure what is meant by "no such file or directroy"? iptables is accessible . Cheers,

kerem closed this issue

2026-02-27 15:57:33 +03:00

kerem commented

2026-02-27 15:57:33 +03:00

Author

Owner

@catborise commented on GitHub (Apr 6, 2019):

Hi, i think it is not related with webvirtcloud. It could be a bug related with libvirt + iptables

What is your libvirt version(virsh version)

Could you try this command on host. What is the output?
Virsh net-start default

@catborise commented on GitHub (Apr 6, 2019): Hi, i think it is not related with webvirtcloud. It could be a bug related with libvirt + iptables What is your libvirt version(virsh version) Could you try this command on host. What is the output? Virsh net-start default

kerem commented

2026-02-27 15:57:33 +03:00

Author

Owner

@4920441 commented on GitHub (Apr 7, 2019):

Hi,
thanks for the hint..., do you have a solution anyway? Its the default debian buster deb package...:

virsh version
Compiled against library: libvirt 5.0.0
Using library: libvirt 5.0.0
Using API: QEMU 5.0.0
Running hypervisor: QEMU 3.1.0

virsh net-start default
error: Failed to start network default
error: internal error: Failed to apply firewall rules /sbin/iptables --table filter --insert INPUT --in-interface virbr0 --protocol tcp --destination-port 67 --jump ACCEPT: iptables v1.8.2 (nf_tables): CHAIN_ADD failed (No such file or directory): chain INPUT

@4920441 commented on GitHub (Apr 7, 2019): Hi, thanks for the hint..., do you have a solution anyway? Its the default debian buster deb package...: virsh version Compiled against library: libvirt 5.0.0 Using library: libvirt 5.0.0 Using API: QEMU 5.0.0 Running hypervisor: QEMU 3.1.0 virsh net-start default error: Failed to start network default error: internal error: Failed to apply firewall rules /sbin/iptables --table filter --insert INPUT --in-interface virbr0 --protocol tcp --destination-port 67 --jump ACCEPT: iptables v1.8.2 (nf_tables): CHAIN_ADD failed (No such file or directory): chain INPUT

kerem commented

2026-02-27 15:57:33 +03:00

Author

Owner

@4920441 commented on GitHub (Apr 7, 2019):

For Anyone who has a similiar Problem,

On Debian (10) by default the nf_tables backend is used instead of the xtables backend.

That does not work too well in his constellation, you can back to the old backend by

update-alternatives --set iptables /usr/sbin/iptables-legacy

Cheers,

4920441

@4920441 commented on GitHub (Apr 7, 2019): For Anyone who has a similiar Problem, On Debian (10) by default the nf_tables backend is used instead of the xtables backend. That does not work too well in his constellation, you can back to the old backend by update-alternatives --set iptables /usr/sbin/iptables-legacy Cheers, 4920441

kerem referenced this issue

2026-02-27 15:58:43 +03:00

[PR #156] [MERGED] Django version requirement, Libxml2->lxml change, account detail validation add, some bugs #437