-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12.05.15 Carlos E. R. wrote:
On 2015-05-11 21:05, Johannes Kastl wrote:
I would have thought we either need some kind of drop-in file that libvirt places somewhere Susefirewall2 reads it or a way that Susefirewall2 can tell libvirt to reload its rules.
Have a look at /etc/sysconfig/scripts/SuSEfirewall2-custom
That was the example I had in mind.
I don't know if that is what you want, but maybe similar.
I know I can trigger custom rules with this file, but I have no idea how to use it with libvirtd? Can libvirtd put its rules in a file like that, which is then used within SuseFirewall2? That would be something for the developers, I fear. I can test and try to support, but I am lacking knowledge of both libvirtd and Susefirewall2-interna... Regards, Johannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlVSO0EACgkQzi3gQ/xETbLp3gCgm2WdJ/6STpxqj7mTHOqcXDtt kJUAnRAaPqvRA6okp/PO0KjGktv/kwV0 =U0Uv -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org