@ddstreet tested with the latest version of ifupdown and vlan from your
PPA with my 4 testscenario's and can confirm it works as expected.
Interfaces come up correctly both when doing an "ifup -a" and during
boot.
One small thing I've noticed is a variation in the number of "Set name-
type for VLA
We've been doing a lot more testing and debugging and I'd like to share
our findings:
1) Unfortunately it turns out this change does not fix the issue of interfaces
not coming up correctly for a bond with a (static) network configuration. The
race condition seems to be removed so at least there
Hi @ddstreet. Completely understand your need to limit the scope of this
bug. Just shared our findings, but feel free to ignore the stuff in #28
under item 2. We did a lot of extensive testing over the weekend with
the latest version of your PPA package and here are our main findings:
1) We migrat
Neither issue is fixed by the downgrade. As said, neither seems to have
to do with vlan but with ifupdown.
--
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/1701023
Title:
(
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/net
Public bug reported:
Due to an upgrade (of probably of the ifupdown or vlan package), this specific
network configuration no longer comes up automatically:
1) Two or more network interfaces bonded
2) An untagged network configured on that bond
3) A vlan on top of that untagged network
What does
@ddstreet I opened a separate ticket as requested a while ago. Some eyes
on it would be very welcome. It's bug 1759573
--
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/1636708
Been doing some troubleshooting and we think we've found the fix for
this issue:
The script /etc/network/if-pre-up.d/vlan contains the following section
of code starting at line 62:
if [ ! -e "/sys/class/net/$IFACE" ]; then
# Try ifup for the raw device, if it fails then bring it up directly
Got right on it! Tested your PPA version on the same testcases and it
works perfectly. Indeed the same issue and the same type of resolution.
Your ifquery is more elegant though, so definitely go with that!
Would love to see this released and pushed a.s.a.p. because this is
breaking our production
*** This bug is a duplicate of bug 1701023 ***
https://bugs.launchpad.net/bugs/1701023
Totally support marking this as a duplicate. As long as we get this fix
pushed a.s.a.p. :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribe
@ddstreet here's how I reproduced: I created a VirtualBox VM with Xenial
and 3 interfaces: enp0s3 and enp0s8 on an internal network, enp0s9 on a
bridge to my LAN). Then I applied each of the 4 configurations below and
ran "ifup -a". Try it and you'll see the same behavior.
You are correct: the pro
We upgraded to the vlan 1.9-3.2ubuntu1.16.04.3 package and our
networking broke horribly in a very similar way.
Let me start with our networking configuration. Two slaves, a bond and a
vlan on top of that bond:
auto eno1
iface eno1 inet manual
mtu 1500
bond-master bond1
bond-primary eno1
12 matches
Mail list logo
