** Package changed: ifupdown (Debian) => ubuntu
** No longer affects: ubuntu
** Changed in: ifupdown (Ubuntu)
Assignee: Andrew Shadura (andrew.sh) => Chris J Arges (arges)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: 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/1295304
Title:
ifdown -a
This bug does not effect Precise when I tested it.
** Changed in: ifupdown (Ubuntu Precise)
Importance: High = Undecided
** Changed in: ifupdown (Ubuntu Precise)
Assignee: Chris J Arges (arges) = (unassigned)
** No longer affects: ifupdown (Ubuntu Precise)
--
You received this bug
** Also affects: ifupdown (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: ifupdown (Ubuntu Precise)
Assignee: (unassigned) = Chris J Arges (arges)
** Changed in: ifupdown (Ubuntu Precise)
Importance: Undecided = High
** Changed in: ifupdown (Ubuntu Precise)
Please reopen this bug. And also please add me to a proper ACL so I can
control bugs normally.
** Also affects: ifupdown (Debian)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Stéphane, why haven't you forwarded this bug to me and have silently
patched the code out? It's not how issues are supposed to be dealt with.
** Changed in: ifupdown (Ubuntu)
Assignee: Chris J Arges (arges) = Andrew Shadura (andrew.sh)
--
You received this bug notification because you are
Hi Andrew, my understanding from back when you introduced that support
into ifupdown was that you intended for people to use ifupdown directly
for bridge and vlan management rather than through the hooks provided by
bridge-utils and vlan.
Since Ubuntu is doing a bit of weird magic here (compared
The problem specifically here is that both vlan's post-down hook and ifupdown
both try to destroy the vlan, which obviously fails.
We could obviously make the deletion of the interface in ifupdown non-fatal,
but I'm not convinced it's the right course of action if you intend people to
use
As for ACLs, there's no way for me to add per-package bug management
ACLs in Launchpad so I'm afraid I can't help there.
As far as this particular issue is concerned, it's been resolved in a
way that we feel like we can support for the LTS and which is consistent
with our existing documentation
This bug was fixed in the package ifupdown - 0.7.47.2ubuntu2
---
ifupdown (0.7.47.2ubuntu2) trusty; urgency=medium
[ Stéphane Graber ]
* Allow setting the MTU and HWADDR on manual interfaces. (LP: #1294807)
* The above change also means that manual interfaces will now be
As a workaround I was able to issue 'ifdown -a' 3 times and all
interfaces came down properly. Then 'ifup -a' brought all interfaces
back up.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1295304
Tested with https://launchpad.net/~stgraber/+archive/experimental
(0.7.47.2ubuntu2~ppa2) and it fixes this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1295304
Title:
ifdown -a fails with
12 matches
Mail list logo
