Open marcel151 opened 8 months ago
Have you tried the solution here?: https://community.synology.com/enu/forum/1/post/129091
Have you tried the solution here?: https://community.synology.com/enu/forum/1/post/129091
Yes, it does behave very weirdly after reboot. The bonded interfaces suddenly show up again on their own together with bond interface and the Synology is not reachable on the IP of the bond. Also cat /proc/net/bonding folder is not created.
This is a limitation of the current driver.
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.
Description of the problem
I am following up this issue: https://github.com/bb-qq/aqc111/issues/17
Since I can't reopen that I'll open this issue.
I can't use active/passive failsafe with one of the internal NICs. The bond is created, but not used correctly. I just have Gigabit speeds. When I disconnect the Gigabit connection while using failsave bond, it does not connect at all. 5 Gbit/s works fine when using the interface on it's own.
Description of your products
Description of your environment
Output of
dmesg
commandOutput of
lsusb
commandOutput of
ifconfig -a
command