[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cloud-init (Ubuntu Eoan) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

I'm trying to understand if there is any work still required on this bug for cloud-init. I've tested two network configurations (in lxd containers). The first: version: 2 ethernets: eth0: dhcp4: true dhcp6: true ipv6-mtu: 1337 As this is just a passthrough to netplan,

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

** Merge proposal linked: https://code.launchpad.net/~paride/curtin/+git/curtin/+merge/387218 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1671951 Title: networkd

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

** Changed in: cloud-init (Ubuntu Disco) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1671951 Title: networkd should allow configuring

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

This bug was fixed in the package systemd - 237-3ubuntu10.39 --- systemd (237-3ubuntu10.39) bionic; urgency=medium [ Dariusz Gadomski ] * d/p/lp1762391/0001-Call-getgroups-to-know-size-of-supplementary-groups-.patch, d/p/lp1762391/0002-user-util-tweak-to-in_gid.patch,

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

This bug was fixed in the package systemd - 242-7ubuntu3.7 --- systemd (242-7ubuntu3.7) eoan; urgency=medium [ Dariusz Gadomski ] * d/p/lp1762391/0001-Call-getgroups-to-know-size-of-supplementary-groups-.patch, d/p/lp1762391/0002-user-util-tweak-to-in_gid.patch,

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

** Tags removed: verification-needed verification-needed-bionic verification-needed-eoan ** Tags added: verification-done verification-done-bionic verification-done-eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

Verified Eoan systemd 242-7ubuntu3.7 correctly sets IPv6 MTU Verified Bionic systemd 237-3ubuntu10.39 correctly sets IPv6 MTU ** Attachment added: "curtin vmtest logs for ipv6 mtu verification"

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

Hello Ryan, or anyone else affected, Accepted systemd into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/242-7ubuntu3.7 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

This SRU needs to be reuploaded, due to security update that trumped this in progress SRU. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1671951 Title: networkd should

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

This SRU needs to be reuploaded, due to security update that trumped this in progress SRU. ** Changed in: systemd (Ubuntu Eoan) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

This bug was fixed in the package systemd - 237-3ubuntu10.38 --- systemd (237-3ubuntu10.38) bionic-security; urgency=medium * SECURITY UPDATE: local privilege escalation via DynamicUser - debian/patches/CVE-2019-384x-1.patch: introduce seccomp_restrict_suid_sgid() for

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

Curtin vmtest verification for bionic using systemd from -proposed has run successfully. (neipa) ipv6_mtu % egrep "237-3ubuntu10.34" output/BionicTestNetworkMtu/logs/install-serial.log [ 126.923480] cloud-init[1176]: Get:10 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

Curtin vmtest verification for eoan using systemd from -proposed has run successfully. (neipa) ipv6_mtu % egrep "242-7ubuntu3.3" output/EoanTestNetworkMtu/logs/install-serial.log [ 136.520219] cloud-init[765]: Get:12 http://archive.ubuntu.com/ubuntu eoan-proposed/main amd64 libnss-systemd

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

** Attachment added: "curtin vmtest logs for ipv6 mtu verification" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1671951/+attachment/5325665/+files/bug-1671951-curtin-vmtest-verification.tar.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

Hello Ryan, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.34 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

Hello Ryan, or anyone else affected, Accepted systemd into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/242-7ubuntu3.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

This bug was fixed in the package systemd - 244.1-0ubuntu2 --- systemd (244.1-0ubuntu2) focal; urgency=medium [ Dimitri John Ledkov ] * shutdown: do not detach autoclear loopback devices Author: Dimitri John Ledkov File:

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

as disco is EOL next week, marking this won't fix for disco. ** Changed in: systemd (Ubuntu Disco) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

** Merge proposal linked: https://code.launchpad.net/~ddstreet/ubuntu/+source/systemd/+git/systemd/+merge/376801 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1671951

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

** Also affects: cloud-init (Ubuntu Focal) Importance: Undecided Status: Confirmed ** Also affects: systemd (Ubuntu Focal) Importance: Medium Status: Fix Released ** Also affects: netplan.io (Ubuntu Focal) Importance: Undecided Status: Fix Released ** Also affects:

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

I opened this upstream https://github.com/systemd/systemd/pull/13915 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1671951 Title: networkd should allow configuring IPV6

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

Testing with @ddstreet's systemd ppa, I can confirm that bionic, disco and eoan correctly set MTU on first boot, no systemd-restart needed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

@ddstreet You systemd builds in the PPA fix the issue for me on Bionic and Disco, IPv6 MTU is applied after reboot with the configuration. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

I have not tested first boot, @raharper could you please test that? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1671951 Title: networkd should allow configuring IPV6

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

In my test I modified a multipass launched VM's netplan config to: multipass@safe-hornet:~$ cat /etc/netplan/50-cloud-init.yaml # This file is generated from information provided by # the datasource. Changes to it will not persist across an instance. # To disable cloud-init's network

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

> cloud-init is not doing anything special here, we render the config and call netplan generate Sorry, yes I meant that netplan should be putting the MTUBytes inside the .network and not using a .link file. -- You received this bug notification because you are a member of Ubuntu Touch seeded

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

@Dan, Ill try the ppa and report back. cloud-init is not doing anything special here, we render the config and call netplan generate. If we take cloud-init out of the picture, and just have a file in /etc/netplan it will still fail due to the udev issue you specify. Shouldn't netplan itself

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

@raharper could you give the systemd in this ppa a test: https://launchpad.net/~ddstreet/+archive/ubuntu/systemd also, you're setting the MTUBytes via .link file, but that won't work inside an lxd container as that setting only has any effect during udev processing of interface 'add' uevent,

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

@Balint, after further testing, here's where things are: - On LXD Containers - On Bionic 1) First boot: neither interface mtu, nor ipv6 mtu is applied. 2) Restarting systemd-networkd: neither interface nor ipv6-mtu is applied 3) netplan apply: interface

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

@raharper, do I understand correctly that this occurs only on first boot and is fixed when installing eoan's netplan.io on bionic? Also a full Disco systemd works or not? (Disco system, Disco netplan.io, Disco systemd) -- You received this bug notification because you are a member of Ubuntu

Re: [Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

On Fri, Oct 25, 2019 at 1:31 PM Dan Streetman 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

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

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. -- You received this bug notification because you

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

Thanks. Let's put both tasks as Triaged again then, since it's obviously not fixed in disco and bionic. I don't think this qualifies as a regression though, since the feature was never available before. It's just not finished since the systemd side of this isn't complete. ** Changed in: systemd

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

I did some more testing today. I upgraded systemd and netplan.io to disco level, rebooted and tested the MTU settings; disco packages fail as well. I then upgraded to eoan systemd/netplan.io rebooted and the MTU settings are correct. -- You received this bug notification because you are a

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

In the Eoan version of systemd, I can see in the logs these messages: Oct 24 18:52:32.753746 ubuntu systemd-networkd[1167]: Setting '/proc/sys/net/ipv6/conf/interface1/proxy_ndp' to '0' Oct 24 18:52:32.753848 ubuntu systemd-networkd[1167]: Setting

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

The original netplan yaml I was testing was simpler, but also failed so I tried to see if additional settings would make a difference, but it did not. network: version: 2 ethernets: interface0: dhcp4: true match: macaddress:

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

I cannot verify this is working on bionic with ipv6 static addresses. root@ubuntu:~# lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20191021 root@ubuntu:~# uname -a Linux ubuntu 4.15.0-66-generic

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

This bug was fixed in the package systemd - 237-3ubuntu10.31 --- systemd (237-3ubuntu10.31) bionic; urgency=medium [ Dimitri John Ledkov ] * Add conflicts with upstart and systemd-shim. (LP: #1773859) * d/p/debian/UBUNTU-units-disable-journald-watchdog.patch - units:

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

This bug was fixed in the package netplan.io - 0.98-0ubuntu1~19.04.1 --- netplan.io (0.98-0ubuntu1~19.04.1) disco; urgency=medium * Backport netplan.io 0.98 to 19.04. (LP: #1840832) -- Mathieu Trudel-Lapierre Mon, 26 Aug 2019 16:41:36 -0400 ** Changed in: netplan.io (Ubuntu

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

This bug was fixed in the package netplan.io - 0.98-0ubuntu1~18.04.1 --- netplan.io (0.98-0ubuntu1~18.04.1) bionic; urgency=medium * Backport netplan.io 0.98 to 18.04. (LP: #1840832) * Keep patches specific to 18.04 support: - disable-networkd-tunnels-ipip-gre.patch: disable

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

** Also affects: cloud-init (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: netplan.io (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: netplan.io (Ubuntu

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

Verification-done on disco: ubuntu@ip-172-30-0-243:~$ lsb_release -cs disco ubuntu@ip-172-30-0-243:~$ dpkg -l netplan.io systemd | grep ii ii netplan.io 0.98-0ubuntu1~19.04.1 amd64YAML network configuration abstraction for various backends ii systemd240-6ubuntu5.7

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

Verification-done on bionic: ubuntu@ip-172-30-0-140:/run/systemd/network$ lsb_release -cs bionic ubuntu@ip-172-30-0-140:/run/systemd/network$ dpkg -l netplan.io | grep ii ii netplan.io 0.98-0ubuntu1~18.04.1 amd64YAML network configuration abstraction for various backends

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

Hello Ryan, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.30 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

** Changed in: systemd (Ubuntu Bionic) Status: Fix Committed => In Progress ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Balint Reczey (rbalint) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

** Tags added: id-5d67fe691c14484db556d212 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1671951 Title: networkd should allow configuring IPV6 MTU Status in cloud-init

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

See comment #20; ipv6 mtu is 1280 -> DEVICE_MTU. I'm testing something in the middle now. On Eoan with: network: version: 2 ethernets: ens3: addresses: [10.5.0.16/16] gateway4: 10.5.0.1 dhcp4: false match:

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

err, on Eoan, I used ipv6-mtu 6000. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1671951 Title: networkd should allow configuring IPV6 MTU Status in cloud-init package

Re: [Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

I thought custom ipv6 MTU may not be lower than ipv4 one. Hence request for 6000 ipv6 is not valid, when link is on 8958. Can you try 9000? On Wed, 28 Aug 2019, 15:41 Ryan Harper, <1671...@bugs.launchpad.net> wrote: > I launched a bionic image on serverstack, updated the netplan.io to >

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

I tested with your single-file approach and that also fails. Note that bionic now has systemd 237, so maybe something is missing (or regressed) ? $ apt-cache policy systemd systemd: Installed: 237-3ubuntu10.26 Candidate: 237-3ubuntu10.26 Version table: *** 237-3ubuntu10.26 500 500

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

Followup on my comments, are any changes required in networkd to support this in bionic? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1671951 Title: networkd should

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

I launched a bionic image on serverstack, updated the netplan.io to proposed, modified the network config to set ipv6-mtu to 6000 and rebooted. root@b-test-ipv6-mtu:~# apt-cache policy netplan.io netplan.io: Installed: 0.98-0ubuntu1~18.04.1 Candidate: 0.98-0ubuntu1~18.04.1 Version table:

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

Hello Ryan, or anyone else affected, Accepted netplan.io into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/netplan.io/0.98-0ubuntu1~18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package.

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

** Description changed: + = netplan.io = + + [Impact] + +  * IPv6 traffic failing to send/receive due to incompatible/low MTU + setting. Specifically, IPv6 traffic may have higher MTU requirements + than IPv4 traffic and thus may need to be overridden and/or set to a + higher value than IPv6

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

This bug was fixed in the package netplan.io - 0.98-0ubuntu1 --- netplan.io (0.98-0ubuntu1) eoan; urgency=medium * New upstream release: 0.98 (LP: #1840832) - Added new "feature flags" to identify new features - Added support for "use-domains" for DHCP overrides - Added

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

** Changed in: netplan.io (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1671951 Title: networkd should allow configuring IPV6

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

** Tags added: id-5cc72cfe22e00d7a830c4ce4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1671951 Title: networkd should allow configuring IPV6 MTU Status in cloud-init

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

This was done inside a VM. This was all done in a single /etc/systemd/network/10-netplan-ens3.network file. Note that [Link] is a valid section in a .network file. Note that i took netplan generated .network file as a base, and then modified it with above shown options. Disabled netplan.

Re: [Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

On Tue, Dec 4, 2018 at 9:31 AM Ryan Harper wrote: > > > On Tue, Dec 4, 2018 at 6:31 AM Dimitri John Ledkov > wrote: > >> Using systemd 237-3ubuntu10.10 >> >> Using: >> [Match] >> Name=ens3 >> [Network] >> DHCP=ipv4 >> IPv6MTUBytes=1600 >> [Link] >> MTUBytes=1800 >> [DHCP] >> UseMTU=no >>

Re: [Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

On Tue, Dec 4, 2018 at 6:31 AM Dimitri John Ledkov wrote: > Using systemd 237-3ubuntu10.10 > > Using: > [Match] > Name=ens3 > [Network] > DHCP=ipv4 > IPv6MTUBytes=1600 > [Link] > MTUBytes=1800 > [DHCP] > UseMTU=no > RouteMetric=100 > Do you put this in the same .network file or .link file? --

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

Using systemd 237-3ubuntu10.10 Using: [Match] Name=ens3 [Network] DHCP=ipv4 IPv6MTUBytes=1600 [Link] MTUBytes=1800 [DHCP] UseMTU=no RouteMetric=100 I do get: $ cat /sys/class/net/ens3/mtu 1800 $ cat /proc/sys/net/ipv6/conf/ens3/mtu 1600 Thus one can set a different from the device,

Re: [Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

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

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

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. -- You received this bug

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

It seems there are some limitations to what systemd will do with IPv6BytesMTU. 1) if LinkLocalAddressing is not disabled, it will clobber any IPv6BytesMTU value set. [Network] LinkLocalAddressing=ipv6 Address=10.10.10.10/24 IPv6MTUBytes=1470 This results in: /proc/sys/net/ipv6/conf//mtu having

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

Hello Ryan, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.8 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

** Description changed: + = systemd = + + [Impact] + + * IPv6 traffic failing to send/receive due to incompatible/low MTU + setting. Specifically, IPv6 traffic may have higher MTU requirements + than IPv4 traffic and thus may need to be overridden and/or set to a + higher value than IPv6

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

** Changed in: systemd (Ubuntu Bionic) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1671951 Title: networkd should allow configuring

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

** Changed in: cloud-init (Ubuntu) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

Re: [Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

This may now be a cloud-init bug if the support is there since this is a network-config v1 -> cloud-init renders netplan. On Fri, Sep 28, 2018 at 9:12 AM Scott Moser wrote: > > Hm... > > Our tests show that this is not fixed in cosmic or bionic. > >

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

Actually there needs to be changes to netplan to emit the correct IPV6BytesMtu setting to networkd; and then cloud-init can emit the correct netplan yaml for that. This feature is on the netplan roadmap here: https://trello.com/c/nIjLIRSG/6-support-ipv6-mtu-bytes-configuration ** Also

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

Hm... Our tests show that this is not fixed in cosmic or bionic. https://jenkins.ubuntu.com/server/job/curtin-vmtest-devel-amd64/533/console shows curtin's vmtest failing. Partial output shows: == ERROR:

Re: [Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

On Wed, Aug 29, 2018 at 8:41 AM Dimitri John Ledkov wrote: > > Do we need this in bionic? Yes > > -- > 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

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

This is now in cosmic. ** Changed in: systemd (Ubuntu) Status: Confirmed => Fix Released ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

Do we need this in bionic? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1671951 Title: networkd should allow configuring IPV6 MTU Status in systemd package in Ubuntu:

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

** Tags added: id-5b74352f76a21f210334eafd -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1671951 Title: networkd should allow configuring IPV6 MTU Status in systemd

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

The v239 merge for cosmic is in progress at the moment. There are a few regressions that need to be worked around. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1671951

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

I've just seen that upstream systemd v239 claims to support IPV6MtuBytes https://lwn.net/Articles/758128/ * networkd's .network files now support a new IPv6MTUBytes= option for setting the MTU used by IPv6 explicitly as well as a new MTUBytes= option in the [Route] section to configure the MTU

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

** Tags added: id-5a6a5c89cfbc4063786d54f6 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1671951 Title: networkd should allow configuring IPV6 MTU Status in systemd

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1671951 Title: networkd should allow configuring IPV6 MTU

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

** Branch linked: lp:~raharper/curtin/trunk.vmtest-remove-bug-timers -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1671951 Title: networkd should allow configuring IPV6

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

Unsubscribing sponsors based upon IRC discussion with rharper: 10:57 < nacc> rharper: is LP: #1671951 actually ready to sponsor? 10:57 < ubottu> Launchpad bug 1671951 in systemd (Ubuntu) "networkd should allow configuring IPV6 MTU" [Medium,New]

Re: [Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

On Wed, May 17, 2017 at 1:14 PM, Dimitri John Ledkov wrote: > I'm very naive, so please bear with me if this is a silly question. As > far as I can tell the existing MTU setting in networkd will apply to > both ipv4 and ipv6 simultaniously. Are you arguing that you want

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

I'm very naive, so please bear with me if this is a silly question. As far as I can tell the existing MTU setting in networkd will apply to both ipv4 and ipv6 simultaniously. Are you arguing that you want specific control of MTU and use different values for ipv4 and ipv6? Would it not be

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

This also needs some discussion w.r.t how to handle IPV6-only devices; namely if you want to set the IPV6 MTU to something higher than the underlying device's current setting then the device MTU would need to be raised as well. That needs to be implemented and added to the patch. -- You

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

Please submit this as a pullrequest upstream. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1671951 Title: networkd should allow configuring IPV6 MTU Status in systemd

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

** Changed in: systemd (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1671951 Title: networkd should allow configuring IPV6

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

** Tags added: zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1671951 Title: networkd should allow configuring IPV6 MTU Status in systemd package in Ubuntu: New

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

The attachment "ipv6_mtu.debdiff" seems to be a debdiff. The ubuntu- sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

I've a build of this fix here: https://launchpad.net/~raharper/+archive/ubuntu/cloud-init-dev (systemd=232-19ubuntu3~fixbuild1) I've tested this minimally in a Zesty VM and it's successfully applies an IPV6MTU in addition to the device mtu (if that's also included). -- You received this bug

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

** Patch added: "ipv6_mtu.debdiff" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1671951/+attachment/4835554/+files/ipv6_mtu.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.