Dear Maintainer,

* What led up to the situation?
Created a network configuration via /etc/network/interfacess file method for a single ethernet NIC,
i.e. eth0, and WiFi adapter, i.e. wlan0.  Both had customized MAC addresses via the 'hwaddress' option.
This configuration worked as expected with no issues.

* What exactly did you do (or not do) that was effective (or ineffective)?
Changed the configuration to a bonding configuration adding bond0 interface, and changing the eth0
and wlan0 configuration to work as slaves under a simple active-backup bonding configuration.

* What was the outcome of this action?
On reboot or systemctl restart networking, the networking service fails, and network connectivity is
broken, nonfunctional.  ONLY AFTER REMOVING 'hwaddress' option under bond0 interface configuration,
did networking start as expected.  Did not expect the 'hwaddress' option to working on slave interfaces,
but it should have worked on the bond, i.e. bond0 interface.  Nowhere in the documentation, that I
have found as yet, is the 'hwaddress' feature excluded from a bonding configuration.

* What outcome did you expect instead?
MAC address set per 'hwaddress' option of bond0 interface, at a minimum, set as expected, and networking
being functional.  Fail to understand why hwaddress option fails on bond0 interface when bond0 configuration
is functional without said option being used.  At a minimum, if eth0 interface as primary has a 'hwaddress'
option set, the bond0 configuration should accept it.  But a better implementation would be for the bond0
interface to accept use of the hwaddress option.  Which apparently is not the case now.

Please do not file bugs that happen on derivatives against Debian,
as we do not know about their changes. Instead, please use the
derivative (Raspbian) bug tracker.

If you can reproduce this on a current, supported Debian release,
please file a bug against the correct Debian package (i.e. not
"general").

Best,
Chris

Chris,

Please open this bug again... I have confirmed the bug exists on
straight Debian 10 (on AMD64 Hardware).  On reboot or direct restart of
networking, the networking is broken.  The only change between the two
files below is first has hwaddr set under bond0, the other file that
line is commented out.

The following interfaces file fails... Note the hwaddr line under bond0
is enabled...

-----

# cat /etc/network/interfaces

source-directory /etc/network/interfaces.d

auto lo
iface lo inet loopback

auto bond0
iface bond0 inet dhcp
         hwaddress 01:02:03:04:05:06

         #address 192.168.1.71
         #netmask 255.255.255.0
         #gateway 192.168.1.1

         bond-slaves ens33 ens36
         #bond-slaves none

         bond-mode active-backup
         bond-miimon 100
         bond-downdelay 200
         bond-updelay 200

auto ens33
iface ens33 inet manual
         #00:0C:29:88:B0:32
         #Below Ignored As Expected
         hwaddr 00:00:00:00:00:33
         bond-master bond0
         bond-primary ens33
         bond-mode active-backup

auto ens36
iface ens36 inet manual
         #00:0C:29:88:B0:3C
         #Below Ignored As Expected
         hwaddr 00:00:00:00:00:36
         bond-master bond0
         bond-primary ens33
         bond-mode active-backup

-----


Comment out the hwaddr line under the bond0 configuration the interface
file works...

-----

# cat /etc/network/interfaces

source-directory /etc/network/interfaces.d

auto lo
iface lo inet loopback

auto bond0
iface bond0 inet dhcp
         #hwaddress 01:02:03:04:05:06

         #address 192.168.1.71
         #netmask 255.255.255.0
         #gateway 192.168.1.1

         bond-slaves ens33 ens36
         #bond-slaves none

         bond-mode active-backup
         bond-miimon 100
         bond-downdelay 200
         bond-updelay 200

auto ens33
iface ens33 inet manual
         #00:0C:29:88:B0:32
         #Below Ignored As Expected
         hwaddr 00:00:00:00:00:33
         bond-master bond0
         bond-primary ens33
         bond-mode active-backup

auto ens36
iface ens36 inet manual
         #00:0C:29:88:B0:3C
         #Below Ignored As Expected
         hwaddr 00:00:00:00:00:36
         bond-master bond0
         bond-primary ens33
         bond-mode active-backup

# ping www.google.com
PING www.google.com (142.250.188.228) 56(84) bytes of data.
64 bytes from lax31s15-in-f4.1e100.net (142.250.188.228): icmp_seq=1
ttl=115 time=16.4 ms
64 bytes from lax31s15-in-f4.1e100.net (142.250.188.228): icmp_seq=2
ttl=115 time=17.4 ms
^C
--- www.google.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 3ms
rtt min/avg/max/mdev = 16.355/16.862/17.369/0.507 ms
root@insane:~# ping -c 1 www.google.com
PING www.google.com (142.250.188.228) 56(84) bytes of data.
64 bytes from lax31s15-in-f4.1e100.net (142.250.188.228): icmp_seq=1
ttl=115 time=15.7 ms

--- www.google.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 15.737/15.737/15.737/0.000 ms

-----

Debian 10 Information...

# cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 10 (buster)"
NAME="Debian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

# uname -a
Linux insane 4.19.0-16-amd64 #1 SMP Debian 4.19.181-1 (2021-03-19)
x86_64 GNU/Linux

-----

Thanks,

Reassigning to ifupdown, which is the package having the
/etc/network/interfaces conffile.

Chris

El 04/06/21 a las 14:55, Chris Hofstaedtler escribió:

The bonding functionality is handled by the ifenslave package.
Reassinging it accordingly.

Cheers,