Public bug reported:
There is a problem when running a bond on top of vlans. Running ifup
with verbose enabled shows run-parts being executed in (what seems like)
alphabetical order, but to enslave a vlan interface, run-part
/etc/network/if-pre-up.d/vlan should be executed before run-part
/etc/network/if-pre-up.d/ifenslave.
Our workaround has been to add "pre-up export IFACE=<name>
IF_VLAN_RAW_DEVICE=<raw device name>; /etc/network/if-pre-up.d/vlan" to
all vlan slaves, but it would be better to fix this in the ifup scripts
themselves by reordering the run-parts.
Tested with version 1.9-3ubuntu10.4
** Affects: ifupdown (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
There is a problem when running a bond on top of vlans. Running ifup
with verbose enabled shows run-parts being executed in (what seems like)
alphabetical order, but to enslave a vlan interface, run-part
/etc/network/if-pre-up.d/vlan should be executed before run-part
/etc/network/if-pre-up.d/ifenslave.
Our workaround has been to add "pre-up export IFACE=<name>
IF_VLAN_RAW_DEVICE=<raw device name>; /etc/network/if-pre-up.d/vlan" to
all vlan slaves, but it would be better to fix this in the ifup scripts
themselves by reordering the run-parts.
+
+ Tested with version 1.9-3ubuntu10.4
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1768235
Title:
Ifenslave failing when bonding vlans
Status in ifupdown package in Ubuntu:
New
Bug description:
There is a problem when running a bond on top of vlans. Running ifup
with verbose enabled shows run-parts being executed in (what seems
like) alphabetical order, but to enslave a vlan interface, run-part
/etc/network/if-pre-up.d/vlan should be executed before run-part
/etc/network/if-pre-up.d/ifenslave.
Our workaround has been to add "pre-up export IFACE=<name>
IF_VLAN_RAW_DEVICE=<raw device name>; /etc/network/if-pre-up.d/vlan"
to all vlan slaves, but it would be better to fix this in the ifup
scripts themselves by reordering the run-parts.
Tested with version 1.9-3ubuntu10.4
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1768235/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
