Skip to content
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

webvirtcloud on Debian 10 (Buster) - IPTables glitch... #233

Closed
4920441 opened this issue Apr 6, 2019 · 3 comments
Closed

webvirtcloud on Debian 10 (Buster) - IPTables glitch... #233

4920441 opened this issue Apr 6, 2019 · 3 comments

Comments

@4920441
Copy link

4920441 commented Apr 6, 2019

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,

@catborise
Copy link
Collaborator

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

@4920441
Copy link
Author

4920441 commented 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
Copy link
Author

4920441 commented 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 4920441 closed this as completed Apr 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants