After the last dist-upgrade bonding stopped working. I am using bullseye/sid and 5.6.0-1-amd64 #1 SMP Debian 5.6.7-1 (2020-04-29) x86_64 GNU/Linux

The "dist-upgrade" warned about not using ifenslave anymore but iproute2, so I tried to see how this would affect the server implied, and:

This is my /etc/network/interfaces

auto eth0
auto eth1
iface eth0 inet manual
iface eth1 inet manual

auto bond10
iface bond10 inet static
    address 192.168.10.205
    netmask 255.255.255.0
    network 192.168.10.0
    broadcast 192.168.10.255
    gateway 192.168.10.254
    bond-slaves eth0 eth1
    bond-miimon 100
    bond-mode balance-rr
    bond-downdelay 200
    bond-updelay 200

This is what it happens on every reboot:

may 18 14:58:06 hermes systemd-udevd[374]: Using default interface naming scheme 'v245'.
may 18 14:58:06 hermes systemd-udevd[374]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
may 18 14:58:06 hermes kernel: Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
may 18 14:58:06 hermes ifup[611]: /etc/network/if-pre-up.d/ifenslave: 67: Maximum function recursion depth (1000) reached
may 18 14:58:06 hermes ifup[610]: run-parts: /etc/network/if-pre-up.d/ifenslave exited with return code 2
may 18 14:58:06 hermes ifup[584]: ifup: failed to bring up bond10
may 18 14:58:06 hermes systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
may 18 14:58:06 hermes systemd[1]: networking.service: Failed with result 'exit-code'.
may 18 14:58:06 hermes systemd[1]: Failed to start Raise network interfaces.

I have to say that the alternative systemd method to setup bonding, bridging, etc. is far to be a simple, clean and clear method as it should be, in my humble opinion.

Also, but less important, I am using the traditional NIC naming scheme, using "biosdevname=0, net.ifnames=0" with GRUB, and I get these messages. I don't understand why (my /etc/udev/rules.d is empty):

may 18 14:58:02 hermes systemd-udevd[365]: Using default interface naming scheme 'v245'.
may 18 14:58:02 hermes systemd-udevd[365]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
may 18 14:58:02 hermes systemd-udevd[365]: Could not set AlternativeName= or apply AlternativeNamesPolicy= on eth0: File exists
may 18 14:58:02 hermes systemd-udevd[365]: eth0: Could not apply link config, ignoring: File exists
may 18 14:58:02 hermes systemd-udevd[365]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
may 18 14:58:02 hermes systemd-udevd[365]: Could not set AlternativeName= or apply AlternativeNamesPolicy= on eth1: File exists
may 18 14:58:02 hermes systemd-udevd[365]: eth1: Could not apply link config, ignoring: File exists

Why is systemd trying to do some NIC renaming is a mistery to me.

Regards,
-- 

Miguel A. Novo




Reply via email to