Your message dated Sat, 9 Nov 2019 01:01:59 +0100
with message-id <[email protected]>
and subject line Re: Bug#941603: udev: bond interface does not inherit mac 
address of a slave
has caused the Debian Bug report #941603,
regarding udev: bond interface does not inherit mac address of a slave
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.)


-- 
941603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941603
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: udev
Version: 242-7
Severity: normal

When I create a bonding interface on an older Debian system, it
naturally inherits one of the slave's mac address.  With new Debian
testing (systemd=242-7) the bonding interface gets a strange MAC
address.

The issue is, if I connect 2 Debian systems with a bonding interface,
then the 2 ends of the link has the same MAC address, and it all breaks.

I tried to downgrade systemd to Debian buster version 241-7~deb10u1, and
it did not help (systemd, libsystemd0, libpam-systemd, systemd-coredump
packages).  Then I downgraded udev as well (udev, libudev1, libudev-dev, 
libudev1:i386, libudev-dev:i386 packages).  Bonding interfaces got
different MAC addresses and started to work properly.


I.e. it is a regression in udev. which assigns some strange MAC address
to a just-created bonding interface; with a high chance that the
addresses of 2 link ends are the same.


To reproduce:
sudo ip link add bond0 type bond mode 1
cat /sys/devices/virtual/net/bond0/addr_assign_type
ip li li dev bond0

I expect to see NET_ADDR_RANDOM=1 as the addr_assign_type, and different
MAC addresses on different systems as a result of the "ip" command.
With the last udev, I see NET_ADDR_SET=3 as the addr_assign_type, and
the same MAC address on both ends of my bond link.



-- Package-specific info:

-- System Information:
Debian Release: bullseye/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 
'testing'), (500, 'stable'), (200, 'experimental'), (30, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.2.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages udev depends on:
ii  adduser       3.118
ii  dpkg          1.19.7
ii  libacl1       2.2.53-5
ii  libblkid1     2.34-0.1
ii  libc6         2.29-2
ii  libkmod2      26-3
ii  libselinux1   2.9-2+b2
ii  libudev1      242-7
ii  systemd-sysv  242-7
ii  util-linux    2.34-0.1

udev recommends no packages.

udev suggests no packages.

Versions of packages udev is related to:
ii  systemd  242-7

-- debconf information:
  udev/reboot_needed:
  udev/title/upgrade:
  udev/new_kernel_needed: false
  udev/sysfs_deprecated_incompatibility:

-- 
Alexandra N. Kossovsky
OKTET Labs (http://www.oktetlabs.ru/)

--- End Message ---
--- Begin Message ---
On Tue, 5 Nov 2019 16:48:29 +0300 "Alexandra N. Kossovsky"
<[email protected]> wrote:
> On 05/11/2019 16:41, Michael Biebl wrote:
> > On Thu, 3 Oct 2019 13:57:09 +0200 Michael Biebl <[email protected]> wrote:
> >> Am 03.10.19 um 13:12 schrieb Alexandra N. Kossovsky:
> >>> Thank you for your patience.
> >>>
> >>> I've submitted the part of the issue which (by my opinion) is a clear
> >>> bug: https://github.com/systemd/systemd/issues/13712
> >>>
> >>
> > 
> > If I read the upstream bug report correctly, this issue was caused by
> > two machines having an identical /etc/machine-id, which is not a
> > supported configuration, as the machine-id is supposed to be unique.
> 
> Yes, you are right.

Ok, let's close this bug report then.
The main issue of the bug report as I understand is was this in your
initial email:
"The issue is, if I connect 2 Debian systems with a bonding interface,
then the 2 ends of the link has the same MAC address, and it all breaks."
Which we figured out in the mean time was due to the identical
/etc/machine-id.

Regards,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---

Reply via email to