[Bug 1759014] Re: Netplan has no way to control DHCP client
Mathieu Trudel-Lapierre
mathieu.tl at gmail.com
Tue Oct 30 14:40:54 UTC 2018
** Changed in: netplan
Status: New => Fix Committed
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Also affects: netplan.io (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: netplan.io (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: netplan.io (Ubuntu Cosmic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to netplan.io in Ubuntu.
Matching subscriptions: foundations-bugs
https://bugs.launchpad.net/bugs/1759014
Title:
Netplan has no way to control DHCP client
Status in netplan:
Fix Committed
Status in netplan.io package in Ubuntu:
New
Status in netplan.io source package in Bionic:
New
Status in netplan.io source package in Cosmic:
New
Status in netplan.io source package in Disco:
New
Bug description:
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
More information about the foundations-bugs
mailing list