Hi Dan, Yes; I have a curtin modification and test-cases to handle all of our scenarios.
https://code.launchpad.net/~raharper/curtin/trunk.more-ipv6 In particular, you can see the final scripts (a pre-hook and post is needed) http://bazaar.launchpad.net/~raharper/curtin/trunk.more- ipv6/view/head:/curtin/commands/apply_net.py#L29 And the various test-cases that we now pass on this branch, on precise, trusty, xenial and yakkety with different versions of ifupdown. http://bazaar.launchpad.net/~raharper/curtin/trunk.more- ipv6/view/head:/examples/tests/network_mtu.yaml While we could see about getting the script included in yakkety (or y+1); curtin will still need to handle this unless we want to SRU ifdowndown in precise, trusty and xenial. This has an enormous impact; so it's not something we should take lightly. On Fri, Aug 26, 2016 at 2:23 PM, Dan Streetman < dan.streetman+launch...@canonical.com> wrote: > Ryan are you working on adding the script to ifupdown in ubuntu and/or > debian? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1609367 > > Title: > ifupdown does not set ipv6-only large mtu > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/ > 1609367/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1609367 Title: ifupdown does not set ipv6-only large mtu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1609367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
