[Touch-packages] [Bug 1759014] Re: Netplan has no way to control DHCP client
@Tom Matthews: Are you sure that https://bugs.launchpad.net/netplan/+bug/1759014/comments/62 is netplan's fault? On my test box the systemd renderer DHCP settings end up in the same stanza for IPv4 and IPv6, like [DHCP] RouteMetric= UseMTU=true UseRoutes=false UseDNS=false netplan even complains in case of differences: "ERROR: ens4: networkd requires that use-dns has the same value in both dhcp4_overrides and dhcp6_overrides". Looks like it's systemd not honoring that value for IPv6 as expected, doesn't it? -- 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/1759014 Title: Netplan has no way to control DHCP client Status in netplan: Fix Released Status in netplan.io package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Confirmed Status in netplan.io source package in Bionic: Fix Committed Status in systemd source package in Bionic: Confirmed Status in netplan.io source package in Cosmic: Fix Committed Status in systemd source package in Cosmic: Confirmed Status in netplan.io source package in Disco: Fix Released Status in systemd source package in Disco: Confirmed Bug description: [Impact] DHCP configurations where custom settings (routes, nameservers, etc.) need to be applied. [Test case] 1) Configure netplan for the particulars of the network by configuring an appropriate dhcp{4,6}-override stanza: network: version: 2 ethernets: engreen: dhcp4: true dhcp4-overrides: use-dns: false use-routes: false route-metric: Additionally, if so required, add a custom DNS / routes to the configuration. e.g. nameservers: search: [lab, kitchen] addresses: [8.8.8.8] (See https://netplan.io/reference#dhcp-overrides for the available options) 2) Run 'netplan apply' or reboot to have the configuration applied. 3) Validate that the routes / DNS are properly ignored and/or replaced by the defined values. [Regression potential] Minimal; this adds new values to the configuration generated for networkd or NetworkManager. Existing configurations will remain unchanged, but new configurations using the dhcp{4,6}-overrides fields will benefit from additional flexibility. --- Currently DHCP appears to be an all or nothing boolean, which is insufficient for many network configurations. Ideally all of the DHCP configuration options supported by systemd would also be supported in netplan: https://www.freedesktop.org/software/systemd/man/systemd.network.html#%5BDHCP%5D%20Section%20Options As an example, consider the following netplan configuration: network: version: 2 renderer: networkd ethernets: enp0s3: dhcp4: yes nameservers: [8.8.8.8,8.8.4.4] After running netplan apply I check the nameservers with systemd- resolve --status and it shows: DNS Servers: 8.8.8.8 8.8.4.4 192.168.1.1 Here, "192.168.1.1" was provided by my DHCP server. On this particular node, I only want the manually configured DNS servers, but netplan has no way to indicate this. To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1759014/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1759014] Re: Netplan has no way to control DHCP client
Verified netplan.io 0.96-0ubuntu0.18.10.3 using network: version: 2 ethernets: ens3: dhcp4: true dhcp4-overrides: use-dns: false nameservers: search: [lab, kitchen] addresses: [8.8.8.8] match: macaddress: fa:16:3e:09:85:54 set-name: ens3 ens4: dhcp4: true dhcp4-overrides: use-routes: false use-dns: false route-metric: match: macaddress: fa:16:3e:56:2f:d6 set-name: ens4 Routes are configured as expected, so is DNS. ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- 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/1759014 Title: Netplan has no way to control DHCP client Status in netplan: Fix Released Status in netplan.io package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Confirmed Status in netplan.io source package in Bionic: Fix Committed Status in systemd source package in Bionic: Confirmed Status in netplan.io source package in Cosmic: Fix Committed Status in systemd source package in Cosmic: Confirmed Status in netplan.io source package in Disco: Fix Released Status in systemd source package in Disco: Confirmed Bug description: [Impact] DHCP configurations where custom settings (routes, nameservers, etc.) need to be applied. [Test case] 1) Configure netplan for the particulars of the network by configuring an appropriate dhcp{4,6}-override stanza: network: version: 2 ethernets: engreen: dhcp4: true dhcp4-overrides: use-dns: false use-routes: false route-metric: Additionally, if so required, add a custom DNS / routes to the configuration. e.g. nameservers: search: [lab, kitchen] addresses: [8.8.8.8] (See https://netplan.io/reference#dhcp-overrides for the available options) 2) Run 'netplan apply' or reboot to have the configuration applied. 3) Validate that the routes / DNS are properly ignored and/or replaced by the defined values. [Regression potential] Minimal; this adds new values to the configuration generated for networkd or NetworkManager. Existing configurations will remain unchanged, but new configurations using the dhcp{4,6}-overrides fields will benefit from additional flexibility. --- Currently DHCP appears to be an all or nothing boolean, which is insufficient for many network configurations. Ideally all of the DHCP configuration options supported by systemd would also be supported in netplan: https://www.freedesktop.org/software/systemd/man/systemd.network.html#%5BDHCP%5D%20Section%20Options As an example, consider the following netplan configuration: network: version: 2 renderer: networkd ethernets: enp0s3: dhcp4: yes nameservers: [8.8.8.8,8.8.4.4] After running netplan apply I check the nameservers with systemd- resolve --status and it shows: DNS Servers: 8.8.8.8 8.8.4.4 192.168.1.1 Here, "192.168.1.1" was provided by my DHCP server. On this particular node, I only want the manually configured DNS servers, but netplan has no way to indicate this. To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1759014/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1759014] Re: Netplan has no way to control DHCP client
Verified netplan.io 0.96-0ubuntu0.18.04.4 with the configuration from https://bugs.launchpad.net/netplan/+bug/1759014/comments/52. Routes are configured as expected, as is DNS. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-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/1759014 Title: Netplan has no way to control DHCP client Status in netplan: Fix Released Status in netplan.io package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Confirmed Status in netplan.io source package in Bionic: Fix Committed Status in systemd source package in Bionic: Confirmed Status in netplan.io source package in Cosmic: Fix Committed Status in systemd source package in Cosmic: Confirmed Status in netplan.io source package in Disco: Fix Released Status in systemd source package in Disco: Confirmed Bug description: [Impact] DHCP configurations where custom settings (routes, nameservers, etc.) need to be applied. [Test case] 1) Configure netplan for the particulars of the network by configuring an appropriate dhcp{4,6}-override stanza: network: version: 2 ethernets: engreen: dhcp4: true dhcp4-overrides: use-dns: false use-routes: false route-metric: Additionally, if so required, add a custom DNS / routes to the configuration. e.g. nameservers: search: [lab, kitchen] addresses: [8.8.8.8] (See https://netplan.io/reference#dhcp-overrides for the available options) 2) Run 'netplan apply' or reboot to have the configuration applied. 3) Validate that the routes / DNS are properly ignored and/or replaced by the defined values. [Regression potential] Minimal; this adds new values to the configuration generated for networkd or NetworkManager. Existing configurations will remain unchanged, but new configurations using the dhcp{4,6}-overrides fields will benefit from additional flexibility. --- Currently DHCP appears to be an all or nothing boolean, which is insufficient for many network configurations. Ideally all of the DHCP configuration options supported by systemd would also be supported in netplan: https://www.freedesktop.org/software/systemd/man/systemd.network.html#%5BDHCP%5D%20Section%20Options As an example, consider the following netplan configuration: network: version: 2 renderer: networkd ethernets: enp0s3: dhcp4: yes nameservers: [8.8.8.8,8.8.4.4] After running netplan apply I check the nameservers with systemd- resolve --status and it shows: DNS Servers: 8.8.8.8 8.8.4.4 192.168.1.1 Here, "192.168.1.1" was provided by my DHCP server. On this particular node, I only want the manually configured DNS servers, but netplan has no way to indicate this. To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1759014/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1759014] Re: Netplan has no way to control DHCP client
The systemd issue on Bionic has been resolved with systemd 237-3ubuntu10.21: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804478 -- 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/1759014 Title: Netplan has no way to control DHCP client Status in netplan: Fix Released Status in netplan.io package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Confirmed Status in netplan.io source package in Bionic: Fix Committed Status in systemd source package in Bionic: Confirmed Status in netplan.io source package in Cosmic: Fix Committed Status in systemd source package in Cosmic: Confirmed Status in netplan.io source package in Disco: Fix Released Status in systemd source package in Disco: Confirmed Bug description: [Impact] DHCP configurations where custom settings (routes, nameservers, etc.) need to be applied. [Test case] 1) Configure netplan for the particulars of the network by configuring an appropriate dhcp{4,6}-override stanza: network: version: 2 ethernets: engreen: dhcp4: true dhcp4-overrides: use-dns: false use-routes: false route-metric: Additionally, if so required, add a custom DNS / routes to the configuration. e.g. nameservers: search: [lab, kitchen] addresses: [8.8.8.8] (See https://netplan.io/reference#dhcp-overrides for the available options) 2) Run 'netplan apply' or reboot to have the configuration applied. 3) Validate that the routes / DNS are properly ignored and/or replaced by the defined values. [Regression potential] Minimal; this adds new values to the configuration generated for networkd or NetworkManager. Existing configurations will remain unchanged, but new configurations using the dhcp{4,6}-overrides fields will benefit from additional flexibility. --- Currently DHCP appears to be an all or nothing boolean, which is insufficient for many network configurations. Ideally all of the DHCP configuration options supported by systemd would also be supported in netplan: https://www.freedesktop.org/software/systemd/man/systemd.network.html#%5BDHCP%5D%20Section%20Options As an example, consider the following netplan configuration: network: version: 2 renderer: networkd ethernets: enp0s3: dhcp4: yes nameservers: [8.8.8.8,8.8.4.4] After running netplan apply I check the nameservers with systemd- resolve --status and it shows: DNS Servers: 8.8.8.8 8.8.4.4 192.168.1.1 Here, "192.168.1.1" was provided by my DHCP server. On this particular node, I only want the manually configured DNS servers, but netplan has no way to indicate this. To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1759014/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1759014] Re: Netplan has no way to control DHCP client
netplan.io 0.96-0ubuntu0.18.04.3 with systemd 237-3ubuntu10.19: network: version: 2 ethernets: ens3: dhcp4: true dhcp4-overrides: use-dns: false nameservers: search: [lab, kitchen] addresses: [8.8.8.8] match: macaddress: fa:16:3e:28:d1:28 set-name: ens3 ens4: dhcp4: true dhcp4-overrides: use-routes: false use-dns: false route-metric: match: macaddress: fa:16:3e:d7:41:1b set-name: ens4 Works fine, except the known issue with systemd addressed with https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1823730. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-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/1759014 Title: Netplan has no way to control DHCP client Status in netplan: Fix Released Status in netplan.io package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Confirmed Status in netplan.io source package in Bionic: Fix Committed Status in systemd source package in Bionic: Confirmed Status in netplan.io source package in Cosmic: Fix Committed Status in systemd source package in Cosmic: Confirmed Status in netplan.io source package in Disco: Fix Released Status in systemd source package in Disco: Confirmed Bug description: [Impact] DHCP configurations where custom settings (routes, nameservers, etc.) need to be applied. [Test case] 1) Configure netplan for the particulars of the network by configuring an appropriate dhcp{4,6}-override stanza: network: version: 2 ethernets: engreen: dhcp4: true dhcp4-overrides: use-dns: false use-routes: false route-metric: Additionally, if so required, add a custom DNS / routes to the configuration. e.g. nameservers: search: [lab, kitchen] addresses: [8.8.8.8] (See https://netplan.io/reference#dhcp-overrides for the available options) 2) Run 'netplan apply' or reboot to have the configuration applied. 3) Validate that the routes / DNS are properly ignored and/or replaced by the defined values. [Regression potential] Minimal; this adds new values to the configuration generated for networkd or NetworkManager. Existing configurations will remain unchanged, but new configurations using the dhcp{4,6}-overrides fields will benefit from additional flexibility. --- Currently DHCP appears to be an all or nothing boolean, which is insufficient for many network configurations. Ideally all of the DHCP configuration options supported by systemd would also be supported in netplan: https://www.freedesktop.org/software/systemd/man/systemd.network.html#%5BDHCP%5D%20Section%20Options As an example, consider the following netplan configuration: network: version: 2 renderer: networkd ethernets: enp0s3: dhcp4: yes nameservers: [8.8.8.8,8.8.4.4] After running netplan apply I check the nameservers with systemd- resolve --status and it shows: DNS Servers: 8.8.8.8 8.8.4.4 192.168.1.1 Here, "192.168.1.1" was provided by my DHCP server. On this particular node, I only want the manually configured DNS servers, but netplan has no way to indicate this. To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1759014/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1759014] Re: Netplan has no way to control DHCP client
Submitted https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1823730. -- 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/1759014 Title: Netplan has no way to control DHCP client Status in netplan: Fix Released Status in netplan.io package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Confirmed Status in netplan.io source package in Bionic: Fix Committed Status in systemd source package in Bionic: Confirmed Status in netplan.io source package in Cosmic: Fix Committed Status in systemd source package in Cosmic: Confirmed Status in netplan.io source package in Disco: Fix Released Status in systemd source package in Disco: Confirmed Bug description: [Impact] DHCP configurations where custom settings (routes, nameservers, etc.) need to be applied. [Test case] 1) Configure netplan for the particulars of the network by configuring an appropriate dhcp{4,6}-override stanza: network: version: 2 ethernets: engreen: dhcp4: true dhcp4-overrides: use-dns: false use-routes: false route-metric: Additionally, if so required, add a custom DNS / routes to the configuration. e.g. nameservers: search: [lab, kitchen] addresses: [8.8.8.8] (See https://netplan.io/reference#dhcp-overrides for the available options) 2) Run 'netplan apply' or reboot to have the configuration applied. 3) Validate that the routes / DNS are properly ignored and/or replaced by the defined values. [Regression potential] Minimal; this adds new values to the configuration generated for networkd or NetworkManager. Existing configurations will remain unchanged, but new configurations using the dhcp{4,6}-overrides fields will benefit from additional flexibility. --- Currently DHCP appears to be an all or nothing boolean, which is insufficient for many network configurations. Ideally all of the DHCP configuration options supported by systemd would also be supported in netplan: https://www.freedesktop.org/software/systemd/man/systemd.network.html#%5BDHCP%5D%20Section%20Options As an example, consider the following netplan configuration: network: version: 2 renderer: networkd ethernets: enp0s3: dhcp4: yes nameservers: [8.8.8.8,8.8.4.4] After running netplan apply I check the nameservers with systemd- resolve --status and it shows: DNS Servers: 8.8.8.8 8.8.4.4 192.168.1.1 Here, "192.168.1.1" was provided by my DHCP server. On this particular node, I only want the manually configured DNS servers, but netplan has no way to indicate this. To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1759014/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823730] [NEW] Bionic: interface stuck in state "configuring" on a VM with two NICs, DHCP, and the secondary NIC configured to ignore routes from DHCP
Public bug reported: [Impact] Network interfaces not using route information from DHCP4 do not reach configured state, but remain 'configuring' on Bionic. [Test Case] 1) Launch a VM with two network interfaces connected to ports on distinct network, each configured using DHCP4. 2) Configure systemd-networkd to set up both interfaces via DHCP, but to ignore DHCP route information (plus possibly other system wide configuration supposed to be unambiguous, like DNS) from secondary interface. You can do so * either directly in /etc/systemd/network/, as shown in https://github.com/systemd/systemd/issues/9289, * or via netplan.io 0.96-0ubuntu0.18.04.2, as shown in https://bugs.launchpad.net/netplan/+bug/1759014/comments/48. 3) Reboot. 4) Both interfaces should now be reported as configured: # networkctl -a IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 ens3 ether routableconfigured 3 ens4 ether routableconfigured 3 links listed. [Other Info] The issue is known for systemd releases before 239, and was fixed with https://github.com/systemd/systemd/commit/223932c786ada7f758a7b7878a6ad2dae0d1e5fb. I have tested it by manually merging that fix into sources of systemd 237-3ubuntu10.15, rebuilding and installing the package. Worked fine. See also https://bugs.launchpad.net/netplan/+bug/1759014 and https://bugs.launchpad.net/netplan/+bug/1776228. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: bionic dhcp4 ** Tags added: bionic dhcp4 ** Description changed: [Impact] Network interfaces not using route information from DHCP4 do not reach configured state, but remain 'configuring' on Bionic. [Test Case] - 1) Launch a VM with two network interfaces connected to ports on + 1) Launch a VM with two network interfaces connected to ports on distinct network, each configured using DHCP4. - 2) Configure systemd-networkd to set up both interfaces via DHCP, but to ignore DHCP route information (plus possibly other system wide configuration supposed to be unambiguous, like DNS) from secondary interface. You can do so - * either directly in /etc/systemd/network/, as shown in https://github.com/systemd/systemd/issues/9289, - * or via netplan.io 0.96-0ubuntu0.18.04.2, as shown in https://bugs.launchpad.net/netplan/+bug/1759014/comments/48. + 2) Configure systemd-networkd to set up both interfaces via DHCP, but to ignore DHCP route information (plus possibly other system wide configuration supposed to be unambiguous, like DNS) from secondary interface. You can do so + * either directly in /etc/systemd/network/, as shown in https://github.com/systemd/systemd/issues/9289, + * or via netplan.io 0.96-0ubuntu0.18.04.2, as shown in https://bugs.launchpad.net/netplan/+bug/1759014/comments/48. - 3) Reboot. + 3) Reboot. - 4) Both interfaces should now be reported as configured: + 4) Both interfaces should now be reported as configured: - # networkctl -a - IDX LINK TYPE OPERATIONAL SETUP - 1 lo loopback carrier unmanaged - 2 ens3 ether routableconfigured - 3 ens4 ether routableconfigured + # networkctl -a + IDX LINK TYPE OPERATIONAL SETUP + 1 lo loopback carrier unmanaged + 2 ens3 ether routableconfigured + 3 ens4 ether routableconfigured - 3 links listed. + 3 links listed. [Other Info] The issue is known for systemd releases before 239, and was fixed with https://github.com/systemd/systemd/commit/223932c786ada7f758a7b7878a6ad2dae0d1e5fb. I have tested it by manually merging that fix into sources of systemd 237-3ubuntu10.15, rebuilding and installing the package. Worked fine. See also https://bugs.launchpad.net/netplan/+bug/1759014 and - https://bugs.launchpad.net/netplan/+bug/1771736. + https://bugs.launchpad.net/netplan/+bug/1776228. -- 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/1823730 Title: Bionic: interface stuck in state "configuring" on a VM with two NICs, DHCP, and the secondary NIC configured to ignore routes from DHCP Status in systemd package in Ubuntu: New Bug description: [Impact] Network interfaces not using route information from DHCP4 do not reach configured state, but remain 'configuring' on Bionic. [Test Case] 1) Launch a VM with two network interfaces connected to ports on distinct network, each configured using DHCP4. 2) Configure systemd-networkd to set up both interfaces
[Touch-packages] [Bug 1759014] Re: Netplan has no way to control DHCP client
Applied https://github.com/systemd/systemd/commit/223932c786ada7f758a7b7878a6ad2dae0d1e5fb to systemd 237-3ubuntu10.15 on Bionic. It does indeed fix the issue in https://bugs.launchpad.net/netplan/+bug/1759014/comments/48 and https://bugs.launchpad.net/netplan/+bug/1776228/comments/14. Should I log a separate request to get this included in Bionic systemd? Or will this be picked up from here? -- 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/1759014 Title: Netplan has no way to control DHCP client Status in netplan: Fix Released Status in netplan.io package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Confirmed Status in netplan.io source package in Bionic: Fix Committed Status in systemd source package in Bionic: Confirmed Status in netplan.io source package in Cosmic: Fix Committed Status in systemd source package in Cosmic: Confirmed Status in netplan.io source package in Disco: Fix Released Status in systemd source package in Disco: Confirmed Bug description: [Impact] DHCP configurations where custom settings (routes, nameservers, etc.) need to be applied. [Test case] 1) Configure netplan for the particulars of the network by configuring an appropriate dhcp{4,6}-override stanza: network: version: 2 ethernets: engreen: dhcp4: true dhcp4-overrides: use-dns: false use-routes: false route-metric: Additionally, if so required, add a custom DNS / routes to the configuration. e.g. nameservers: search: [lab, kitchen] addresses: [8.8.8.8] (See https://netplan.io/reference#dhcp-overrides for the available options) 2) Run 'netplan apply' or reboot to have the configuration applied. 3) Validate that the routes / DNS are properly ignored and/or replaced by the defined values. [Regression potential] Minimal; this adds new values to the configuration generated for networkd or NetworkManager. Existing configurations will remain unchanged, but new configurations using the dhcp{4,6}-overrides fields will benefit from additional flexibility. --- Currently DHCP appears to be an all or nothing boolean, which is insufficient for many network configurations. Ideally all of the DHCP configuration options supported by systemd would also be supported in netplan: https://www.freedesktop.org/software/systemd/man/systemd.network.html#%5BDHCP%5D%20Section%20Options As an example, consider the following netplan configuration: network: version: 2 renderer: networkd ethernets: enp0s3: dhcp4: yes nameservers: [8.8.8.8,8.8.4.4] After running netplan apply I check the nameservers with systemd- resolve --status and it shows: DNS Servers: 8.8.8.8 8.8.4.4 192.168.1.1 Here, "192.168.1.1" was provided by my DHCP server. On this particular node, I only want the manually configured DNS servers, but netplan has no way to indicate this. To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1759014/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1759014] Re: Netplan has no way to control DHCP client
Verified using netplan.io 0.96-0ubuntu0.18.04.2 and systemd 237-3ubuntu10.15 with network: version: 2 ethernets: ens3: dhcp4: true dhcp4-overrides: use-dns: false nameservers: search: [lab, kitchen] addresses: [8.8.8.8] match: macaddress: fa:16:3e:28:d1:28 set-name: ens3 ens4: dhcp4: true dhcp4-overrides: use-routes: false use-dns: false route-metric: match: macaddress: fa:16:3e:d7:41:1b set-name: ens4 Resulting DNS and routes configured as expected, but interface ens4 remains in state 'configuring' due to known issue of systemd v237. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-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/1759014 Title: Netplan has no way to control DHCP client Status in netplan: Fix Released Status in netplan.io package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Confirmed Status in netplan.io source package in Bionic: Fix Committed Status in systemd source package in Bionic: Confirmed Status in netplan.io source package in Cosmic: Fix Committed Status in systemd source package in Cosmic: Confirmed Status in netplan.io source package in Disco: Fix Released Status in systemd source package in Disco: Confirmed Bug description: [Impact] DHCP configurations where custom settings (routes, nameservers, etc.) need to be applied. [Test case] 1) Configure netplan for the particulars of the network by configuring an appropriate dhcp{4,6}-override stanza: network: version: 2 ethernets: engreen: dhcp4: true dhcp4-overrides: use-dns: false use-routes: false route-metric: Additionally, if so required, add a custom DNS / routes to the configuration. e.g. nameservers: search: [lab, kitchen] addresses: [8.8.8.8] (See https://netplan.io/reference#dhcp-overrides for the available options) 2) Run 'netplan apply' or reboot to have the configuration applied. 3) Validate that the routes / DNS are properly ignored and/or replaced by the defined values. [Regression potential] Minimal; this adds new values to the configuration generated for networkd or NetworkManager. Existing configurations will remain unchanged, but new configurations using the dhcp{4,6}-overrides fields will benefit from additional flexibility. --- Currently DHCP appears to be an all or nothing boolean, which is insufficient for many network configurations. Ideally all of the DHCP configuration options supported by systemd would also be supported in netplan: https://www.freedesktop.org/software/systemd/man/systemd.network.html#%5BDHCP%5D%20Section%20Options As an example, consider the following netplan configuration: network: version: 2 renderer: networkd ethernets: enp0s3: dhcp4: yes nameservers: [8.8.8.8,8.8.4.4] After running netplan apply I check the nameservers with systemd- resolve --status and it shows: DNS Servers: 8.8.8.8 8.8.4.4 192.168.1.1 Here, "192.168.1.1" was provided by my DHCP server. On this particular node, I only want the manually configured DNS servers, but netplan has no way to indicate this. To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1759014/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1759014] Re: Netplan has no way to control DHCP client
Verified using netplan.io 0.96-0ubuntu0.18.10.2 and systemd 239-7ubuntu10.10 with network: version: 2 ethernets: ens3: dhcp4: true dhcp4-overrides: use-dns: false nameservers: search: [lab, kitchen] addresses: [8.8.8.8] match: macaddress: fa:16:3e:34:e2:ff set-name: ens3 ens4: dhcp4: true dhcp4-overrides: use-routes: false use-dns: false route-metric: match: macaddress: fa:16:3e:cd:a4:90 set-name: ens4 Resulting DNS and routes configured as expected. ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- 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/1759014 Title: Netplan has no way to control DHCP client Status in netplan: Fix Released Status in netplan.io package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Confirmed Status in netplan.io source package in Bionic: Fix Committed Status in systemd source package in Bionic: Confirmed Status in netplan.io source package in Cosmic: Fix Committed Status in systemd source package in Cosmic: Confirmed Status in netplan.io source package in Disco: Fix Released Status in systemd source package in Disco: Confirmed Bug description: [Impact] DHCP configurations where custom settings (routes, nameservers, etc.) need to be applied. [Test case] 1) Configure netplan for the particulars of the network by configuring an appropriate dhcp{4,6}-override stanza: network: version: 2 ethernets: engreen: dhcp4: true dhcp4-overrides: use-dns: false use-routes: false route-metric: Additionally, if so required, add a custom DNS / routes to the configuration. e.g. nameservers: search: [lab, kitchen] addresses: [8.8.8.8] (See https://netplan.io/reference#dhcp-overrides for the available options) 2) Run 'netplan apply' or reboot to have the configuration applied. 3) Validate that the routes / DNS are properly ignored and/or replaced by the defined values. [Regression potential] Minimal; this adds new values to the configuration generated for networkd or NetworkManager. Existing configurations will remain unchanged, but new configurations using the dhcp{4,6}-overrides fields will benefit from additional flexibility. --- Currently DHCP appears to be an all or nothing boolean, which is insufficient for many network configurations. Ideally all of the DHCP configuration options supported by systemd would also be supported in netplan: https://www.freedesktop.org/software/systemd/man/systemd.network.html#%5BDHCP%5D%20Section%20Options As an example, consider the following netplan configuration: network: version: 2 renderer: networkd ethernets: enp0s3: dhcp4: yes nameservers: [8.8.8.8,8.8.4.4] After running netplan apply I check the nameservers with systemd- resolve --status and it shows: DNS Servers: 8.8.8.8 8.8.4.4 192.168.1.1 Here, "192.168.1.1" was provided by my DHCP server. On this particular node, I only want the manually configured DNS servers, but netplan has no way to indicate this. To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1759014/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1759014] Re: Netplan has no way to control DHCP client
Hi Mathieu, I don't think Cosmic or Disco systemd are affected. They are both >= v239, and Cosmic behaved fine when verifying https://bugs.launchpad.net/netplan/+bug/1776228. It would just be a shame having the LTS release remain broken with DHCP configurations, that used to work before. -- 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/1759014 Title: Netplan has no way to control DHCP client Status in netplan: Fix Released Status in netplan.io package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Confirmed Status in netplan.io source package in Bionic: Fix Committed Status in systemd source package in Bionic: Confirmed Status in netplan.io source package in Cosmic: Fix Committed Status in systemd source package in Cosmic: Confirmed Status in netplan.io source package in Disco: Fix Released Status in systemd source package in Disco: Confirmed Bug description: [Impact] DHCP configurations where custom settings (routes, nameservers, etc.) need to be applied. [Test case] 1) Configure netplan for the particulars of the network by configuring an appropriate dhcp{4,6}-override stanza: network: version: 2 ethernets: engreen: dhcp4: true dhcp4-overrides: use-dns: false use-routes: false route-metric: Additionally, if so required, add a custom DNS / routes to the configuration. e.g. nameservers: search: [lab, kitchen] addresses: [8.8.8.8] (See https://netplan.io/reference#dhcp-overrides for the available options) 2) Run 'netplan apply' or reboot to have the configuration applied. 3) Validate that the routes / DNS are properly ignored and/or replaced by the defined values. [Regression potential] Minimal; this adds new values to the configuration generated for networkd or NetworkManager. Existing configurations will remain unchanged, but new configurations using the dhcp{4,6}-overrides fields will benefit from additional flexibility. --- Currently DHCP appears to be an all or nothing boolean, which is insufficient for many network configurations. Ideally all of the DHCP configuration options supported by systemd would also be supported in netplan: https://www.freedesktop.org/software/systemd/man/systemd.network.html#%5BDHCP%5D%20Section%20Options As an example, consider the following netplan configuration: network: version: 2 renderer: networkd ethernets: enp0s3: dhcp4: yes nameservers: [8.8.8.8,8.8.4.4] After running netplan apply I check the nameservers with systemd- resolve --status and it shows: DNS Servers: 8.8.8.8 8.8.4.4 192.168.1.1 Here, "192.168.1.1" was provided by my DHCP server. On this particular node, I only want the manually configured DNS servers, but netplan has no way to indicate this. To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1759014/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780807] Re: Please provide ED25519 support in 18.04 OpenSSL
** Description changed: Current libss1.1 version in Bionic is 1.1.0g-2ubuntu4.1 and lacking support for the ED25519 signature algorithm. As ED25519 is quickly gaining traction as most demanded and preferred elliptic curve algorithm, it would be a substantial issue not to have - any support for it in the remaining lifetime of Ubuntu LTS releases most + any support for it in the remaining lifetime of Ubuntu LTS released most recently. OpenSSL is introducing ED25519 with their 1.1.1 release, which is currently in beta (openssl-1.1.1-pre8 as of today). I suggest to upgrade Bionic libss1.1 to OpenSSL 1.1.1, once finally released by OpenSSL. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1780807 Title: Please provide ED25519 support in 18.04 OpenSSL Status in openssl package in Ubuntu: New Bug description: Current libss1.1 version in Bionic is 1.1.0g-2ubuntu4.1 and lacking support for the ED25519 signature algorithm. As ED25519 is quickly gaining traction as most demanded and preferred elliptic curve algorithm, it would be a substantial issue not to have any support for it in the remaining lifetime of Ubuntu LTS released most recently. OpenSSL is introducing ED25519 with their 1.1.1 release, which is currently in beta (openssl-1.1.1-pre8 as of today). I suggest to upgrade Bionic libss1.1 to OpenSSL 1.1.1, once finally released by OpenSSL. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1780807/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780807] [NEW] Please provide ED25519 support in 18.04 OpenSSL
Public bug reported: Current libss1.1 version in Bionic is 1.1.0g-2ubuntu4.1 and lacking support for the ED25519 signature algorithm. As ED25519 is quickly gaining traction as most demanded and preferred elliptic curve algorithm, it would be a substantial issue not to have any support for it in the remaining lifetime of Ubuntu LTS releases most recently. OpenSSL is introducing ED25519 with their 1.1.1 release, which is currently in beta (openssl-1.1.1-pre8 as of today). I suggest to upgrade Bionic libss1.1 to OpenSSL 1.1.1, once finally released by OpenSSL. ** Affects: openssl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1780807 Title: Please provide ED25519 support in 18.04 OpenSSL Status in openssl package in Ubuntu: New Bug description: Current libss1.1 version in Bionic is 1.1.0g-2ubuntu4.1 and lacking support for the ED25519 signature algorithm. As ED25519 is quickly gaining traction as most demanded and preferred elliptic curve algorithm, it would be a substantial issue not to have any support for it in the remaining lifetime of Ubuntu LTS releases most recently. OpenSSL is introducing ED25519 with their 1.1.1 release, which is currently in beta (openssl-1.1.1-pre8 as of today). I suggest to upgrade Bionic libss1.1 to OpenSSL 1.1.1, once finally released by OpenSSL. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1780807/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp