app-emulation/libvirt: Check for more kernel configs for virtual net
authorMichal Privoznik <mprivozn@redhat.com>
Mon, 8 Apr 2019 01:08:54 +0000 (20:08 -0500)
committerMatthias Maier <tamiko@gentoo.org>
Mon, 8 Apr 2019 02:29:38 +0000 (21:29 -0500)
commit3baa88f281263a16d7143d866dd1f8e5e26bbba0
tree9a7b5ae3654061d7acb992617e271296614c6da3
parent873502fe36194d522c957996b91317a3a7f05fdf
app-emulation/libvirt: Check for more kernel configs for virtual net

After 7431b3eb9a05068e4b Libvirt starts to create chains to
insert rules into instead of placing them right at the top level
chains. These private chains are created on daemon startup and
the referenced commit made all 6 tables required (combination of
default 3 tables: nat, filter and mangle for both IPv4 and IPv6).
This was later refined in 686803a1a2e1e06, but it still makes
sense for ebuild to check for all tables being enabled in the
kernel because both IPv4 and IPv6 are used widely.

Package-Manager: Portage-2.3.62, Repoman-2.3.12
Closes: https://bugs.gentoo.org/681010
Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
Signed-off-by: Matthias Maier <tamiko@gentoo.org>
app-emulation/libvirt/libvirt-5.0.0-r1.ebuild
app-emulation/libvirt/libvirt-5.1.0.ebuild
app-emulation/libvirt/libvirt-9999.ebuild