[Touch-packages] [Bug 1753431] Re: bonding does not works

2019-04-28 Thread Unishop
Year later still same problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1753431 Title: bonding does not works Status in systemd package in Ubuntu: Expired Bug de

[Touch-packages] [Bug 1753431] Re: bonding does not works

2018-06-17 Thread Launchpad Bug Tracker
[Expired for systemd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bu

[Touch-packages] [Bug 1753431] Re: bonding does not works

2018-04-18 Thread Laurent Spagnol
Physical interfaces are only used by bonding interfaces. - bond0 have an ip address - bond1 is user by bridges and vlans I've solved my problem: - by adding LACP parameters at module loading: /etc/modprobe.d/netcf.conf alias bond0 bonding alias bond1 bonding options bonding mode=4 lacp_rate=1 xmi

[Touch-packages] [Bug 1753431] Re: bonding does not works

2018-04-17 Thread Mathieu Trudel-Lapierre
Your original config in comment #1 is correct: you must specify the underlying devices, because those names are matched later for "interfaces:" in the bond config. The issue with 802.3ad is likely a driver issue or a bug in systemd; the right mode needs to be set by networkd (which may require reb