Your message dated Tue, 19 Mar 2019 15:19:51 +0100
with message-id <[email protected]>
and subject line Re: Bug#923249: [Pkg-libvirt-maintainers] Bug#923249:
libvirt0: libvirt sets disable_ipv6 on bridge, entirely breaking internal IPv6
networking
has caused the Debian Bug report #923249,
regarding libvirt0: libvirt sets disable_ipv6 on bridge, entirely breaking
internal IPv6 networking
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
923249: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923249
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libvirt0
Version: 5.0.0-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
After a recent upgrade, IPv6 communication between a virtual router and another
virtual client over an isolated network stopped working. I am seeing the rotuer
advertisments sent by the router on vnet0, which is attached to the bridge
virbr1, but when I capture packages on the bridge, the IPv6 traffic is gone. It
just took me several hours of debugging to realize that the reason for this is
that /proc/sys/net/ipv6/conf/virbr1/disable_ipv6 is set to 1. After setting it
to 0, IPv6 is working as expected now.
This is a regression, IPv6 used to work between virtual clients just fine
without having to manually fiddle with the network configuration.
Kind regards,
Ralf
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable-debug'), (500,
'testing-debug'), (100, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libvirt0 depends on:
ii libacl1 2.2.52-3+b1
ii libapparmor1 2.13.2-7
ii libaudit1 1:2.8.4-2
ii libavahi-client3 0.7-4+b1
ii libavahi-common3 0.7-4+b1
ii libc6 2.28-7
ii libcap-ng0 0.7.9-2
ii libcurl3-gnutls 7.64.0-1
ii libdbus-1-3 1.12.12-1
ii libdevmapper1.02.1 2:1.02.155-2
ii libgcc1 1:8.2.0-21
ii libgnutls30 3.6.6-2
ii libnl-3-200 3.4.0-1
ii libnl-route-3-200 3.4.0-1
ii libnuma1 2.0.12-1
ii libsasl2-2 2.1.27+dfsg-1
ii libselinux1 2.8-1+b1
ii libssh2-1 1.8.0-2
ii libxml2 2.9.4+dfsg1-7+b3
ii libyajl2 2.1.0-3
Versions of packages libvirt0 recommends:
ii lvm2 2.03.02-2
libvirt0 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi,
On Mon, Mar 18, 2019 at 03:13:40PM +0100, Ralf Jung wrote:
> Hi,
>
> > https://bugzilla.redhat.com/show_bug.cgi?id=1680681 indicates it's a
> > kernel issue. Can you add a link to the debian bug you filed so I can
> > close this issue but mark the other one as affecting libvirt?
> > Cheers
> > -- Guido
>
> That Debian kernel bug is at
> <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924349>.
Thanks. I'll close this one then marking 924349 as affecting libvirt.
-- Guido
--- End Message ---
