Your message dated Thu, 3 Jun 2021 13:39:37 +0200
with message-id <20210603113937.6kc5bgn5vkzqx...@percival.namespace.at>
and subject line Re: Bug#989370: general: In bonding network configuration,
hwaddress crashes networking service, fails to restart
has caused the Debian Bug report #989370,
regarding general: In bonding network configuration, hwaddress crashes
networking service, fails to restart
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 ow...@bugs.debian.org
immediately.)
--
989370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989370
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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)
--- End Message ---
--- Begin Message ---
> Distributor ID: Raspbian
> Description: Raspbian GNU/Linux 10 (buster)
> Architecture: armv6l
> Kernel: Linux 5.10.17+
> Kernel taint flags: TAINT_CRAP
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
--- End Message ---
