On Fri, Oct 25, 2019 at 1:31 PM Dan Streetman <email address hidden>
wrote:
> I looked at this for a few minutes, and it seems strange that it works
> at all (at boot) since networkd sets the ipv6 mtu before bringing the
> link up, but the kernel resets the ipv6 mtu to the device mtu on link
> up. I must be missing something.
>
I'm glad you saw that. I'm seeing this as well on my curtin vmtest
(automated deployment and data collection during first boot).
I have to restart networkd for it to work on the first boot.
Subsequent boots it seems to work fine without a restart of networkd.
On Fri, Oct 25, 2019 at 1:31 PM Dan Streetman <email address hidden>
wrote:
> I looked at this for a few minutes, and it seems strange that it works
> at all (at boot) since networkd sets the ipv6 mtu before bringing the
> link up, but the kernel resets the ipv6 mtu to the device mtu on link
> up. I must be missing something.
>
I'm glad you saw that. I'm seeing this as well on my curtin vmtest
(automated deployment and data collection during first boot).
I have to restart networkd for it to work on the first boot.
Subsequent boots it seems to work fine without a restart of networkd.
> -- /bugs.launchpad .net/bugs/ 1671951 /bugs.launchpad .net/ubuntu/ +source/ cloud-init/ +bug/1671951/ +subscriptions
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> networkd should allow configuring IPV6 MTU
>
> To manage notifications about this bug go to:
>
> https:/
>