On Mon, Nov 26, 2018 at 11:11 PM Jay Vosburgh <1671...@bugs.launchpad.net> wrote: > > Regarding #2 from comment #19: > > As the defined range for the ipv6.mtu is from IPV6_MIN_MTU to the > device's MTU, and the existing API returns an error if the ipv6.mtu is > out of range, I think it's reasonable for a configuration with the > ipv6.mtu > device MTU to fail.
I think that's reasonable too. We'll need to file a separate bug with MAAS to ensure that it knows it should set device MTU >= to the ipv6 MTU configured. This will ensure the configuration that gets generated will include both a raised device MTU and an IPV6 MTU. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1671951 > > Title: > networkd should allow configuring IPV6 MTU > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1671951/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1671951 Title: networkd should allow configuring IPV6 MTU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1671951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs