Good to hear. Sorry about the temporary mess but Debian decided to
rename the package and this got automatically imported in Ubuntu... took
me a little while to notice and re-apply our delta...
Closing the bug as fix released
** Changed in: ifenslave (Ubuntu)
Status: Incomplete => Fix Rele
After the latest ifenslave update, my bonding configuration appears to
be working as intended. The bug has been fixed for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1280366
Title:
Bonding mod
Ok, so up until this Monday we were in a weird situation in Trusy with
regard to ifenslave. I have now merged all the Ubuntu changes into the
new source package, so it'd be good if someone could confirm whether the
bug still shows up with ifenslave 2.4ubuntu1.
** No longer affects: ifenslave-2.6 (
Workaround without /etc/rc.local.
/etc/network/interfaces
---
auto bond0
iface bond0 inet manual
address 192.168.1.42
gateway 192.168.1.1
netmask 255.255.255.0
# no bond options...
auto eth0
iface eth0 inet manual
bond-master bond0
---
/etc/modules
---
bonding
---
/etc/modprobe.d/bondin
@JS Espinosa
That workaround is causing issues with IPv6, see bug #1280362
Hope it can be fixed soon, so no workaround is needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1280366
Title:
Bonding
** Changed in: ifenslave (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1280366
Title:
Bonding mode ignored
To manage notifications about this bug go to:
htt
** Also affects: ifenslave (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1280366
Title:
Bonding mode ignored
To manage notifications about this
I removed ifenslave and ifenslave-2.6 and installed:
ifenslave-2.6_1.1.0-19ubuntu5_amd64.deb
but this did not fix that behaviour?! "bond-mode 4" was still ignored.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
@JP Espinosa (jp-a)
Thank you. Stopping and starting the physical devices after reboot did
the trick for me too - but is a pain in the . as this takes some
time and the lxc containers using those bonded bridges get disconnected
after they already had started up.
--
You received this bug noti
temp workaround working for me:
define bondX interface BEFORE real interface:
/etc/network/interfaces
auto bond0
iface bond0 inet manual
bond_mode 802.3ad
bond_miimon 100
bond_lacp_rate 1
bond_downdelay 100
bond_updelay 100
bond_slaves eth0 eth1
auto eth0
ifa
looks like this workaround does not work as expected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1280366
Title:
Bonding mode ignored
To manage notifications about this bug go to:
https://bugs.la
temporary workaround for me is:
cat /etc/modprobe.d/bonding.conf
alias netdev-bond0 bonding
alias netdev-bond1 bonding
options bonding mode=4 miimon=100
and reboot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ifenslave-2.6 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1280366
Title
** Package changed: ifenslave (Ubuntu) => ifenslave-2.6 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1280366
Title:
Bonding mode ignored
To manage notifications about this bug go to:
http
14 matches
Mail list logo