This bug affects Ubuntu 10.10, Maverick Meerkat. Maverick has reached
end-of-life and is no longer supported, so I am closing the bugtask for
Maverick. Please upgrade to a newer version of Ubuntu.
More information here:
https://lists.ubuntu.com/archives/ubuntu-announce/2012-April/000158.html
This bug was fixed in the package ifenslave-2.6 -
1.1.0-15ubuntu2.11.04.1
---
ifenslave-2.6 (1.1.0-15ubuntu2.11.04.1) natty-proposed; urgency=low
* Check for previous version to be not set (on fresh install) when
comparing versions in postinst.
LP: #714904
-- Stefan Bader
Setting back to v-needed for maverick.
** Tags removed: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/714904
Title:
/etc/network/if-up.d/ifenslave is missing (installed under
Re #14: I have tested natty (apt-get purge ifenslave-2.6; apt-get
install ifenslave-2.6) and bonding works now without additional up and
down clauses in the /etc/network/interfaces file.
Relevant section of /etc/network/interfaces (two servers connected back-
to-back with each other):
auto bond0
Note that putting the bond-slaves into the master definition is
discouraged as it can cause a race. Using bond-slaves none should be
used. The slaves will get added automatically when the slave interfaces
come up.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Indeed I had read so elsewhere and have tried that but I couldn't get
bond0 up then. But the second part of your second sentence woke me up
just now:
Instead of just 'ifup bond0' and be done the command I have to do is
'ifup bond0 ifup eth1 ifup eth2 ifup eth3' :)
Thanks!
--
You received
** Tags added: verification-done verification-done-natty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/714904
Title:
/etc/network/if-up.d/ifenslave is missing (installed under if-pre-
up.d)
To
Or ifup -a :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/714904
Title:
/etc/network/if-up.d/ifenslave is missing (installed under if-pre-
up.d)
To manage notifications about this bug go to:
No worries, we all started at some point. :)
Basically synaptics update should have updated the package and in theory
it should have worked then. I am not sure though, whether this still all
works that well. Problem is that there are a lot of ways to milk a cow.
From a graphical end I would use
Again, Many thanks..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/714904
Title:
/etc/network/if-up.d/ifenslave is missing (installed under if-pre-
up.d)
To manage notifications about this
Wow, I'm so impressed with the way you have handled my questions. Not a
hint of get off your a@# and figure it out yourself. Especially in an
area like this which draws programmers and the like who are expected to
have a lot of understanding before they ask the same old question over
and over
One kind of problem I found was that the man page was not particularly
helpful. Though, at least with Natty, the files in
/usr/share/doc/ifenslave-2.6/... (README.Debian and examples/) are
consistent as far as I can see.
My configuration in Natty (which does not require a modprobe) looks
like:
Sorry I didn't get back to you a little sooner but I had some other
things to get done first. I uninstalled Ifenslave-2.6 from the natty
proposed repository and then re-installed it.The first time I just
updated it, if that made a difference. But now it seems to be running
fine..
I have two
Jim, update or fresh install should not make a difference (except if the
currently installed version would be way old (older than Hardy) which is
unlikely). The main difference to look out for would be that neither
installation nor upgrade print a line about preserving old configuration
files.
Not really convinced that it is appropriate for me to give testing
feedback, so maybe someone else also affected could be so kind and add
feedback. So at least for me install and update seem to work on Maverick
and Natty. The message about preserving configuration files does not
show up and the
I'm somewhat new to Ubuntu and am working on natty (11.04). I installed
what I thought was the update from the proposed repository and still
have to use modprobe bonding to bring up the bonding interface. The
upgrade version I fount was 1.1.0-15ubuntu2.11.04.1. Is this the
correct version?
--
Excerpts from Jim Taitt's message of Tue Jun 14 21:55:37 UTC 2011:
I'm somewhat new to Ubuntu and am working on natty (11.04). I installed
what I thought was the update from the proposed repository and still
have to use modprobe bonding to bring up the bonding interface. The
upgrade version
Accepted ifenslave-2.6 into maverick-proposed, the package will build
now and be available in a few hours. Please test and give feedback here.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you in advance!
** Changed in: ifenslave-2.6
** Branch linked: lp:ubuntu/maverick-proposed/ifenslave-2.6
** Branch linked: lp:ubuntu/natty-proposed/ifenslave-2.6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/714904
Title:
Stefan's proposed fixes both build (i386 tested) on their target
releases - uploaded to -proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/714904
Title:
/etc/network/if-up.d/ifenslave is
So I tested the ifenslave-2.6 (1.1.0-17ubuntu1) from oneiric, compiled
under natty and with natty. The installation (after removing the old
package version) works now and does not remove anything. From the code I
would think, the same for upgrades from higher versions. I am still not
sure about
** Also affects: ifenslave-2.6 (Ubuntu Maverick)
Importance: Undecided
Status: New
** Also affects: ifenslave-2.6 (Ubuntu Natty)
Importance: Undecided
Status: New
** Changed in: ifenslave-2.6 (Ubuntu Maverick)
Status: New = Triaged
** Changed in: ifenslave-2.6 (Ubuntu
** Patch added: Proposed fix for Maverick
https://bugs.launchpad.net/ubuntu/+source/ifenslave-2.6/+bug/714904/+attachment/2131105/+files/maverick.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: Proposed fix for Natty
https://bugs.launchpad.net/ubuntu/+source/ifenslave-2.6/+bug/714904/+attachment/2131106/+files/natty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Will this fix land in the repository for natty and maverick?
I came across this issue today (and it took me quite a while to find the
duplicated /etc/network/if-up.d/ifenslave).
As of today the latest version in the repository is:
ii ifenslave-2.6 1.1.0-15ubuntu2
At least i
** Changed in: ifenslave-2.6 (Ubuntu)
Assignee: (unassigned) = Steve Langasek (vorlon)
** Changed in: ifenslave-2.6 (Ubuntu)
Status: Confirmed = Triaged
** Changed in: ifenslave-2.6 (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a
This bug was fixed in the package ifenslave-2.6 - 1.1.0-17ubuntu1
---
ifenslave-2.6 (1.1.0-17ubuntu1) oneiric; urgency=low
* Merge from Debian unstable (closes LP: #714904), remaining changes:
- ifstate is no longer in /etc/network/run, but rather in /var/run/network.
- Fix
I am not completely sure how this should get fixed in the end.
Definitely there is something wrong with the postinst script. It looks
like the intention there is to check the package version and when
updating from a version = 1.1.0-6 save the files in if-up.d and if-
post-down.d as defaults by
I can confirm the issue with bond mode not being correct across reboots.
Using the fix suggested in this bug I am able to get the bond0 device to
start, but it ignores the mode on reboot and comes up mode=0 instead of
mode=1. Only the gross solution of changing the mode manually and
restarting
Here are the steps necessary to correct the package files after apt-get
install ifenslave-2.6 results in the observed state, this solution also
corrects the above mentioned issue I observed regarding the preservation
of mode across reboots without any changes using the approved hotplug
method.
$
Since this effectively breaks bond0 and makes the correct implementation
of bonding in 10.10, I feel this issue should be escalated and repaired.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/714904
I forgot to mention that I'm using the same 1.1.0-15ubuntu2 version from
ifenslave-2.6 than Rob. And my kernel is 2.6.35-25-server #44-Ubuntu
SMP.
The info in /proc/net/bonding/bond0 wasn't actually outdated. There is
some problem setting up the bonding device and it's settings. I had to
take the
32 matches
Mail list logo
