Bug#989370: closed by Chris Hofstaedtler <zeha@debian.org> (Re: Bug#989370: general: In bonding network configuration, hwaddress crashes networking service, fails to restart)
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,
-DD
On 6/3/2021 04:42, Debian Bug Tracking System wrote:
This is an automatic notification regarding your Bug report
which was filed against the general package:
#989370: general: In bonding network configuration, hwaddress crashes networking service, fails to restart
It has been closed by Chris Hofstaedtler <zeha@debian.org>.
Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Chris Hofstaedtler <zeha@debian.org> by
replying to this email.
Reply to: