Hi!
On Set 06 2021, Pieter Hollander wrote:
> PS: Additionally, I forgot to mention that adding dad-attempts 0 to the br0
> inet6 config also solves the issues of networking failing.
> > Using a dummy port to perform DAD sounds like the best solution to me.
> > Back to the workaround: It also so
Hi,
* Santiago Garcia Mantinan [Mon Sep 06, 2021 at 11:04:58AM +0200]:
> I'm CCing Josué because this seems to be more on ifupdown's side than on
> bridge-utils.
[...]
> I know we are having quite some trouble with the random bridge mac address,
> but this doesn't seem to be one of those cases.
This is more a bug with the kernel than bridge-utils. brctl just
configures the kernel ioctls for the bridge. Same with systemd-networkd.
Lodge the bug against the kernel! I have had issues with these kernel
bridges, and switched to running openvswitch as that is what Open
Stack uses extensively
PS: Additionally, I forgot to mention that adding dad-attempts 0 to the
br0 inet6 config also solves the issues of networking failing.
On 06/09/2021 14:17, Pieter Hollander wrote:
Hi all,
I tried the fixes proposed here. Unfortunately, adding bridge_ports or
bridge_hw did not solve the issue.
Hi all,
I tried the fixes proposed here. Unfortunately, adding bridge_ports or
bridge_hw did not solve the issue.
The workaround of changing exit 1 to exit 0 in the
/lib/ifupdown/settle-dad.sh "DAD timed out: section did cause networking
to start up successfully, although it still logs the tim
Hi!
I'm CCing Josué because this seems to be more on ifupdown's side than on
bridge-utils.
> > auto br0
> > iface br0 inet static
> > address 10.10.10.1
> > netmask 255.255.255.0
> > bridge_ports none
> > bridge_stp off
> > bridge_fd 0
> >
> > iface br0 i
I also encountered this.
My working hypothesis is that it may be related to this (from README.Debian):
> Since version 1.6-6 we support multiple stanzas of the interface usefull,
> for example, to describe the IPv4 and IPv6 addresses of an interface. The
> only requirement for this is that all of
X-Debbugs-CC: Pieter Hollander
> auto br0
> iface br0 inet static
> address 10.10.10.1
> netmask 255.255.255.0
> bridge_ports none
> bridge_stp off
> bridge_fd 0
>
> iface br0 inet6 static
> address 2001:db8::2
> netmask 64
These stanzas
Package: bridge-utils
Version: 1.7-1
Severity: critical
Tags: ipv6
Justification: breaks unrelated software
After upgrading from Buster to Bullseye, bridge-utils no longer
configures my IPv6 network bridge correctly.
It fails to bring up br0 and therefore also breaks Unbound on my system,
as th
9 matches
Mail list logo