Year later still same problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753431
Title:
bonding does not works
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+s
[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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/175343
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
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
I miss some important informations ...
I'm running Ubuntu 18.04
My original configuration was working fine before updates (5/3/2018)
nplan 0.32 => 0.33
There was no updates for "ifupdown", but netplan AND ifupdown where not
working anymore AFTER the update. So the problem is probably not nplan
or
Summary of WORKING CONFIGURATION:
/etc/modprobe.d/netcf.conf
alias bond0 bonding
alias bond1 bonding
options bonding mode=4 lacp_rate=1 xmit_hash_policy=2 miimon=100 downdelay=200
updelay=200
auto eno3
iface eno3 inet manual
bond-master bond1
auto eno4
iface eno4 inet manual
bond-master bon
So i have done same test with nplan:
/etc/netplan/01-netcfg.yaml
network:
version: 2
renderer: networkd
ethernets:
eno1:
dhcp4: false
dhcp6: false
eno2:
dhcp4: false
dhcp6: false
bonds:
bond0:
interfaces:
- eno1
- eno2
addresses: [10.5.1.174
Okay.
I have checked my conf files, i had used some examples found on Ubuntu website.
For ifupdown:
https://help.ubuntu.com/community/UbuntuBonding#Descriptions_of_bonding_modes
For nplan:
https://insights.ubuntu.com/2017/07/05/quick-and-easy-network-configuration-with-netplan
https://insights.ub
There are some tries:
cat /etc/netplan/01-netcfg.yaml
network:
version: 2
renderer: networkd
bonds:
bond0:
interfaces:
- eno1
- eno2
parameters:
mode: 802.3ad
lacp-rate: fast
transmit-hash-policy: layer2+3
addresses: [10.5.1.174/24]
gate
Ok.
But this config was working until the update of nplan !
Finally, the main issue is "man": i was not able to find a good doc about
"netplan" ...
Netplan is installed by default instead of "ifupdown" but migration between
them is painfull and netplan is very poorly documented.
Do you have good
There are a number of problems with your configuration in both cases.
For netplan, you shouldn't specify any network-level configuration for
an interface that is later expected to participate in a bond. Anything
later in the file will clobber anything specified previously, leading to
unexpected be
This bug affects "netplan" but also "ifudown". I guess it's an issue with
ifenslave ?
My configs:
/etc/netplan/01-netcfg.yaml
network:
version: 2
renderer: networkd
ethernets:
eno1:
dhcp4: false
dhcp6: false
eno2:
dhcp4: false
dhcp6: false
eno3:
dhcp4: false
12 matches
Mail list logo
