Package: general
Severity: important

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.

-- System Information:
Distributor ID: Raspbian
Description:    Raspbian GNU/Linux 10 (buster)
Release:        10
Codename:       buster
Architecture: armv6l

Kernel: Linux 5.10.17+
Kernel taint flags: TAINT_CRAP
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 /usr/bin/dash
Init: systemd (via /run/systemd/system)

Reply via email to