[Bug 1759014] Re: Netplan has no way to control DHCP client

[Michael Steffens]

@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=3333
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
Foundations Bugs, 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: 3333

  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