Re: [Bug 1609367] Re: ifupdown does not set ipv6-only large mtu
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
Re: [Bug 1609367] Re: ifupdown does not set ipv6-only large mtu
On Tue, Aug 9, 2016 at 12:56 PM, Dan Streetman < dan.streetman+launch...@canonical.com> wrote: > > I understand this scenario; however, what I don't understand is why > > if we're setting mtu 9002 on the underlying devices, why the mtu on the > > "virtual" device (bond0) > > matters vs. the mtu setting of the ipv6 link, especially since this is > ipv6 > > only. > > I think the slave interface mtu will be used. > > > I'm testing this post-up hook which I think covers all of the cases. > > yep that script looks good. > > only thing i can think of is, what if an interface's inet6 section is > specified (and setup) first, before the interface's inet section? e.g. > > auto eth0 > iface eth0 inet6 static > address 2001:dbe::1/64 > mtu 1480 > > iface eth0 inet static > address 10.0.0.1 > mtu 1500 > > would that cause the device mtu to be (re)set to 1500, after the ipv6 > Testing the above scenario works fine. The interface has 1500 mtu, and sysctl shows ipv6 link at 1480. However, if we have a higher mtu onthe ipv6 link, like 4800, then the inet section mtu setting clobbers it and they both end up at 1500. Now, that case I still believe is *invalid* configuration; > mtu had been set? That would reset the ipv6 mtu to 1500. Can the > ordering of inet/inet6 sections always be inet before inet6? > Curtin can provide some ordering here, but ifupdown always runs from top-down. > > -- > 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
Re: [Bug 1609367] Re: ifupdown does not set ipv6-only large mtu
On Thu, Aug 4, 2016 at 5:21 PM, Dan Streetman < dan.streetman+launch...@canonical.com> wrote: > > In the original bug where one is comparing ip output of MTU; is there > something *not* working ? > > in that original bug, the user is trying to set up ipv6 tunneling: > > "This scenario is quiet common when using tunnels (e.g. Sixxs) to provide > IPv6 > connectivity. My IPv6 MTU needs to be 20 bytes smaller than may IPv4 MTU > because of the tunnel's overhead." > > > Or did we just observe that the bond interface isn't the same MTU? Can > we confirm that without > > the bond interface itself set to MTU 9202 that we don't see the correct > jumbo frames over ipv6? > > this isn't bonding-specific, the example from bug 1609861 just happens > to use bonding. But an regular interface configured with a "inet6" > section mtu of e.g. 9000 and no "inet" section (or an "inet" section but > no mtu in it) will not correctly set the device mtu to 9000. > I understand this scenario; however, what I don't understand is why if we're setting mtu 9002 on the underlying devices, why the mtu on the "virtual" device (bond0) matters vs. the mtu setting of the ipv6 link, especially since this is ipv6 only. Do we see packets actually get fragmented at the bond ? > > -- > 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
