802.3ad LACP bond missing after reboot

[phiten]

Description of the problem

I have two RTL8156B on my DS918+. Both get detected and are working. I can create a 802.3ad LACP bond which also creates and works fine.

"Bond 1" consists of the two 1G internal NICs
"Bond 2" consists of the two 2.5G RTL8156B external NICs
Both bonds work and can be accessed. I can confirm that in my switch:

ch2 is "Bond 1"
ch3 is "Bond 2"

But after a reboot the bond is missing and both RTL8156B show as individual NIC again:

The bond consisting of the two internal NICs is fine.

I took the requested commands with a working bond:

Description of your products

• DS918+
  • Linux hostname 4.4.302+ #69057 SMP Fri Jan 12 17:02:59 CST 2024 x86_64 GNU/Linux synology_apollolake_918+
  • DSM version DSM 7.2.1-69057 Update 4
• Aliexpress RTL8156B USB3.0 Ethernet Adapter

Description of your environment

• connected to a switch
  • PC: irrelevant
  • Ethernet switch: Lancom GS-4530XUP
• cable category: Cat.6/a

Output of dmesg command

[ds918+_dmesg.txt](https://github.com/bb-qq/r8152/files/14425985/ds918%2B_dmesg.txt)

Output of lsusb command

|__usb1          1d6b:0002:0404 09  2.00  480MBit/s 0mA 1IF  (Linux 4.4.302+ xhci-hcd xHCI Host Controller 0000:00:15.0) hub
  |__1-4         f400:f400:0100 00  2.00  480MBit/s 200mA 1IF  (Synology DiskStation 650078EBA7E41684)
|__usb2          1d6b:0003:0404 09  3.00 5000MBit/s 0mA 1IF  (Linux 4.4.302+ xhci-hcd xHCI Host Controller 0000:00:15.0) hub
  |__2-1         0bda:8156:3104 00  3.20 5000MBit/s 256mA 1IF  (Realtek USB 10/100/1G/2.5G LAN 4013000001)
  |__2-2         0bda:8156:3100 00  3.20 5000MBit/s 256mA 1IF  (Realtek USB 10/100/1G/2.5G LAN 0013000001)

Output of ifconfig -a command

bond0     Link encap:Ethernet  HWaddr 00:11:32:7E:EB:D3
          inet addr:10.100.10.140  Bcast:10.100.10.255  Mask:255.255.255.0
          inet6 addr: fe80::211:32ff:fe7e:ebd3/64 Scope:Link
          UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
          RX packets:4849 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9766 errors:0 dropped:1 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:765808 (747.8 KiB)  TX bytes:12471527 (11.8 MiB)

bond1     Link encap:Ethernet  HWaddr 00:E0:4C:68:02:B3
          inet addr:10.10.10.26  Bcast:10.10.10.255  Mask:255.255.255.0
          inet6 addr: fe80::2e0:4cff:fe68:2b3/64 Scope:Link
          inet6 addr: 2a04::/64 Scope:Global
          UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
          RX packets:6019 errors:0 dropped:0 overruns:0 frame:0
          TX packets:14990 errors:0 dropped:32 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:877196 (856.6 KiB)  TX bytes:18375158 (17.5 MiB)

eth0      Link encap:Ethernet  HWaddr 00:11:32:7E:EB:D3
          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
          RX packets:1368 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9631 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:167372 (163.4 KiB)  TX bytes:12425679 (11.8 MiB)

eth1      Link encap:Ethernet  HWaddr 00:11:32:7E:EB:D3
          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
          RX packets:3481 errors:0 dropped:0 overruns:0 frame:0
          TX packets:135 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:598436 (584.4 KiB)  TX bytes:45848 (44.7 KiB)

eth2      Link encap:Ethernet  HWaddr 00:E0:4C:68:02:B3
          inet addr:169.254.178.11  Bcast:169.254.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
          RX packets:1049 errors:0 dropped:0 overruns:0 frame:0
          TX packets:15009 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:110623 (108.0 KiB)  TX bytes:18385274 (17.5 MiB)

eth3      Link encap:Ethernet  HWaddr 00:E0:4C:68:02:B3
          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
          RX packets:4970 errors:0 dropped:0 overruns:0 frame:0
          TX packets:115 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:766573 (748.6 KiB)  TX bytes:15133 (14.7 KiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:9266 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9266 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1
          RX bytes:1313956 (1.2 MiB)  TX bytes:1313956 (1.2 MiB)

sit0      Link encap:IPv6-in-IPv4
          NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

[FlorianHeigl]

I had the same issues with a bond (1x 1g internal + 1x 2.5g external). It'll work, but come apart on reboot.
I suspect they initialize their bonding way before USB devices are fully loaded.

[bb-qq]

Under the current mechanism, drivers are loaded after the package system is ready, so LACP BOND, which is prepared at an earlier stage, is not restored at startup.

If the drivers are loaded at the same time as other kernel modules are loaded at startup, the LACP configuration can be enabled. But I have not found a good way to do that.