** Tags removed: sts-sru
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1224007
Title:
mtu not always set properly on bond/vlan interface
To manage notifications about this bug go to:
https://bugs.l
This bug was fixed in the package vlan - 1.9-3ubuntu10.1
---
vlan (1.9-3ubuntu10.1) trusty; urgency=medium
* If VLAN is configured with higher MTU than raw device MTU, which can
happen if VLAN is ifup'ed before raw device, then increase raw device
MTU first so the VLAN ifup
This was also released in trusty:
Proposed: 1.9-3ubuntu10.1
Release: 1.9-3ubuntu10
Copied to trusty-updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1224007
Title:
mtu not always set properly
Also thanks to Dan et all for bringing this bug back up! I was wrong
about the duplicate.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1224007
Title:
mtu not always set properly on bond/vlan interf
This bug was fixed in the package vlan - 1.9-3.2ubuntu1.16.04.1
---
vlan (1.9-3.2ubuntu1.16.04.1) xenial; urgency=medium
* If VLAN is configured with higher MTU than raw device MTU, which can
happen if VLAN is ifup'ed before raw device, then increase raw device
MTU first so
This bug was fixed in the package vlan - 1.9-3ubuntu6.1
---
vlan (1.9-3ubuntu6.1) precise; urgency=medium
* If VLAN is configured with higher MTU than raw device MTU, which can
happen if VLAN is ifup'ed before raw device, then increase raw device
MTU first so the VLAN ifup d
We've verified it in the VLAN case (without bridges) for 12.04, 14.04
and 16.04.
** Tags removed: verification-needed
** Tags added: 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/122
Hello Chris, or anyone else affected,
Accepted vlan into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/vlan/1.9-3.2ubuntu1.16.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
Uploaded, thanks! I appreciate the high quality changelog entry.
I modified the Xenial version to 1.9-3.2ubuntu1.16.04.1 since
1.9-3.2ubuntu1 also exists in Vivid and Wily. Otherwise we'd have to
work around not having something less than 1.9-3.2ubuntu1.1 available in
case of an SRU to Vivid or to
@racb i changed the version numbers in the debdiffs for precise and
trusty, i think the xenial debdiff number is already ok. thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1224007
Title:
mtu
** Patch added: "lp1224007-trusty.debdiff"
https://bugs.launchpad.net/debian/+source/vlan/+bug/1224007/+attachment/4755717/+files/lp1224007-trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
** Patch removed: "lp1224007-precise.debdiff"
https://bugs.launchpad.net/debian/+source/vlan/+bug/1224007/+attachment/4750476/+files/lp1224007-precise.debdiff
** Patch removed: "lp1224007-trusty.debdiff"
https://bugs.launchpad.net/debian/+source/vlan/+bug/1224007/+attachment/4750477/+files
Added two possible regressions potentials.
** Description changed:
* Description
When configuring a network with bonding+vlan and setting the MTU,
occasionally the MTU doesn't get set properly on the vlan interface.
In addition if one checks /var/log/upstart/networking.log whenever
This bug was fixed in the package vlan - 1.9-3.2ubuntu2
---
vlan (1.9-3.2ubuntu2) yakkety; urgency=medium
* If VLAN is configured with higher MTU than raw device MTU, which can
happen if VLAN is ifup'ed before raw device, then increase raw device
MTU first so the VLAN ifup d
The fix looks great. Uploaded to Yakkety, thank you for your efforts.
This bug is missing full SRU information, so I can't upload the SRUs
right now. This would be best done by the person most familiar with the
bug and fix to minimise risk to users. Please can you complete these,
eg. the "Regressi
** Also affects: vlan (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: vlan (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: vlan (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: vlan (Ubuntu)
Status: Confi
The patch for xenial solves this issue for me, too. How does the
timeline for getting fixed packages look like?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1224007
Title:
mtu not always set proper
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: vlan (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/1224007
Title:
mtu n
@sakishrist, thanks, I updated all the debdiffs to add the missing
space.
** Tags added: sts-sru
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1224007
Title:
mtu not always set properly on bond/vla
** Patch added: "lp1224007-yakkety.debdiff"
https://bugs.launchpad.net/debian/+source/vlan/+bug/1224007/+attachment/4750479/+files/lp1224007-yakkety.debdiff
** Patch removed: "debdiff for yakkety vlan"
https://bugs.launchpad.net/debian/+source/vlan/+bug/1224007/+attachment/4737643/+files/l
** Patch added: "lp1224007-trusty.debdiff"
https://bugs.launchpad.net/debian/+source/vlan/+bug/1224007/+attachment/4750477/+files/lp1224007-trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
** Patch removed: "lp1224007-precise.debdiff"
https://bugs.launchpad.net/debian/+source/vlan/+bug/1224007/+attachment/4743648/+files/lp1224007-precise.debdiff
** Patch removed: "lp1224007-trusty.debdiff"
https://bugs.launchpad.net/debian/+source/vlan/+bug/1224007/+attachment/4743649/+files
** Patch added: "lp1224007-xenial.debdiff"
https://bugs.launchpad.net/debian/+source/vlan/+bug/1224007/+attachment/4750478/+files/lp1224007-xenial.debdiff
** Patch removed: "debdiffv2 for yakkety vlan"
https://bugs.launchpad.net/debian/+source/vlan/+bug/1224007/+attachment/4739534/+files/l
Hi Dan,
On the first line there needs to be a space just before the closing ']'.
Otherwise the bracket is considered part of the string and it starts
complaining about not finding it.
Other than that, I just applied your patch to a few machines and it
seems to work as expected.
** Patch added: "
** Patch added: "lp1224007-precise.debdiff"
https://bugs.launchpad.net/debian/+source/vlan/+bug/1224007/+attachment/4743648/+files/lp1224007-precise.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
** Patch added: "lp1224007-xenial.debdiff"
https://bugs.launchpad.net/debian/+source/vlan/+bug/1224007/+attachment/4743650/+files/lp1224007-xenial.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
** Patch added: "lp1224007-trusty.debdiff"
https://bugs.launchpad.net/debian/+source/vlan/+bug/1224007/+attachment/4743649/+files/lp1224007-trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
** No longer affects: ifupdown (Ubuntu)
** Changed in: vlan (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1224007
Title:
mtu not always set properly on b
** Package changed: ifupdown (Debian) => vlan (Debian)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1224007
Title:
mtu not always set properly on bond/vlan interface
To manage notifications about
Subscribing ~ubuntu-sponsors
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1224007
Title:
mtu not always set properly on bond/vlan interface
To manage notifications about this bug go to:
https://bu
sorry, the first patch had an issue where it didn't raise the device mtu
if the vlan already existed. the v2 checks and increases if needed the
dev mtu, even if the vlan already exists.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "debdiffv2 for yakkety vlan"
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1224007/+attachment/4739534/+files/lp1224007-yakkety-v2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
** Patch added: "patchv2 to yakkety debian/network/if-pre-up.d/vlan script"
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1224007/+attachment/4739533/+files/lp1224007-yakkety-v2.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Tags added: rls-y-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1224007
Title:
mtu not always set properly on bond/vlan interface
To manage notifications about this bug go to:
https://b
** Changed in: ifupdown (Debian)
Status: Fix Released => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1224007
Title:
mtu not always set properly on bond/vlan interface
To manage notific
The attachment "patch to yakkety debian/network/if-pre-up.d/vlan script"
seems to be a patch. If it isn't, please remove the "patch" flag from
the attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by
** Patch added: "patch to yakkety debian/network/if-pre-up.d/vlan script"
https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1224007/+attachment/4737642/+files/lp1224007-yakkety.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
pls ignore patch from above comment; i have a simpler one i'll attach.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1224007
Title:
mtu not always set properly on bond/vlan interface
To manage noti
** Patch added: "debdiff for yakkety vlan"
https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1224007/+attachment/4737643/+files/lp1224007-yakkety.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
** Also affects: vlan (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/1224007
Title:
mtu not always set properly on bond/vlan interface
To manage
I should note that this is marked as Fix Released in debian, but from
the debian bug comments it just looks like Chris asked for that bug to
be closed as a configuration issue (which this is not).
This is actually only a VLAN issue with higher-than-default mtu. The
bond does not have anything to
** Changed in: ifupdown (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1224007
Title:
mtu not always set properly on bond/vlan interface
To manage notific
** This bug is no longer a duplicate of bug 1065077
Ifenslave pre-up doesn't wait for slaves when usr is a seperate partition
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1224007
Title:
mtu not
*** This bug is a duplicate of bug 1065077 ***
https://bugs.launchpad.net/bugs/1065077
This is definitely not a duplicate of bug #1065077. It is amazing that having
LACP+VLAN+Jumboframes configuration doesn't work since 2013 on two consecutive
LTS server editions, so I explored this problem.
*** This bug is a duplicate of bug 1065077 ***
https://bugs.launchpad.net/bugs/1065077
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ifupdown (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubu
*** This bug is a duplicate of bug 1065077 ***
https://bugs.launchpad.net/bugs/1065077
The "Waiting on network configuration" is most likely caused by bug 1065077.
I think using the documented method the real bug is this, and thus I'll mark it
a duplicate.
** This bug has been marked a dupli
In addition I've been able to set the MTU on the tagged bond using the
following:
auto bond0.123
iface bond0.123 inet static
address 192.168.122.68
netmask 255.255.255.0
gateway 192.168.122.1
mtu 9000
As the documentation mentions (for both ipv4/ipv6):
The static Method
Options
** Changed in: ifupdown (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1224007
Title:
mtu not always set properly on bond/vlan interface
To manage notification
48 matches
Mail list logo
