use-dns doesn't work with NetworkManager:
network:
version: 2
renderer: NetworkManager
wifis:
wlan0:
optional: true
dhcp4: true
dhcp4-overrides:
use-dns: no
use-routes: false
nameservers:
addresses: [192.168.77.1]
access-points:
The fix for dns override for dhcp4 does not work with network manager.
Netplan Generated config:
[ipv4]
method=auto
dns=8.8.8.8;1.1.1.1
What is actually in /var/run/systemd/resolve/resolv.conf :
nameserver 192.168.1.254
nameserver 8.8.8.8
nameserver 1.1.1.1
search attlocal.net
Required fix for
@ddstreet I've been looking into a different issue, which is due to the Netplan
renderer.
The renderer defaults to networkd on server/cloud and NetworkManager on
Desktop. Some apps expect NetworkManager, and break on systems configured with
networkd (e.g. UI network config, apt-daily, etc).
** Also affects: baltix-default-settings
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759014
Title:
Netplan has no way to control DHCP client
To
@francogpellegrini, @fernando-sismonda, I just tested with netplan yaml
similar to yours, and i can't reproduce any problem; the dhcp dns server
is correctly ignored on my test system. What versions of netplan, and
systemd, do you have installed? Also, what's the content of your
Hi all, I'm using ubuntu 20.04 on a raspberry pi (64bit version). And
the problem is still present. My netplan:
root@rbpi3-002:/etc/netplan# cat /etc/resolv.conf
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients
I'm using the version 0.98-0ubuntu1~18.04.1, and the bug is NOT fixed
using this:
network:
version: 2
renderer: NetworkManager
ethernets:
# === fibertel ===
enp1s0:
dhcp4: yes
dhcp4-overrides:
use-dns: no
dhcp6: no
nameservers:
>From reading the comments, I believe the only systemd issue was fixed in
bug 1804478, so I marked this as fix released for systemd. If that's
incorrect and there is still a systemd problem, please feel free to
reopen and comment, or open new bug.
** Changed in: systemd (Ubuntu)
Status:
I just want to note here is that it seems not working still for me in
ubuntu 18.04 running on aws ec2 ami.
root@adc1:~# dpkg -l|grep netplan
ii netplan.io 0.97-0ubuntu1~18.04.1 amd64
YAML network configuration abstraction for various backends
root@adc1:~#
This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.10.3
---
netplan.io (0.96-0ubuntu0.18.10.3) cosmic; urgency=medium
* debian/patches/git_revert_explicit_renderer_def_ebc212a.patch: revert
commit ebc212a: make renderer values explicit at the end of each parsing
This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.04.4
---
netplan.io (0.96-0ubuntu0.18.04.4) bionic; urgency=medium
* debian/patches/git_revert_explicit_renderer_def_ebc212a.patch: revert
commit ebc212a: make renderer values explicit at the end of each parsing
I needed :
[IPv6AcceptRA]
UseDNS=no
But no way for netplan to provide that it seemed, I reverted to purely
using systemd.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759014
Title:
Netplan has
@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
Is it possible to get this into 18.04.3 release? Not that fond of
waiting until January 2020 for the .4 release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759014
Title:
Netplan has no way to
netplan.io 0.96
systemd 240
It seems that dhcp6-overrides don't work for ignoring DHCP provided DNS
servers :
# cat /etc/netplan/10-enp3s0-init.yaml
network:
version: 2
renderer: networkd
ethernets:
enp3s0:
critical: true
dhcp4: true
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]
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
Is it possible to get this into 18.04.3 release? Not that fond of
waiting until January 2020 for the .4 release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759014
Title:
Netplan has no way to
Hello Alan, 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.96-0ubuntu0.18.04.4 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package.
Hello Alan, or anyone else affected,
Accepted netplan.io into cosmic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/netplan.io/0.96-0ubuntu0.18.10.3 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package.
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759014
A possible SRU regression has been reported against netplan.io
0.96-0ubuntu0.18.10.2 in LP: #1825206. This version has been rolled
back to -proposed while the investigation is ongoing.
** Changed in: netplan.io (Ubuntu Cosmic)
Status: Fix Released => Fix Committed
--
You received this
This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.10.2
---
netplan.io (0.96-0ubuntu0.18.10.2) cosmic; urgency=medium
* d/p/0001-Partially-revert-the-change-for-enabling-systemd-net.patch:
Partially revert changes to networkd jobs ordering: leave systemd-networkd
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:
Hello Alan, 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.96-0ubuntu0.18.04.3 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package.
Submitted
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1823730.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759014
Title:
Netplan has no way to control DHCP client
To manage
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
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]
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]
Short installation instructions for the netplan.io 0.96 package on
Ubuntu 18.04:
sudo echo "deb http://archive.ubuntu.com/ubuntu/ bionic-proposed restricted
main multiverse universe" > /etc/apt/sources.list.d/proposed-updates.list
sudo apt update
sudo apt-get install -y
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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759014
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu Cosmic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759014
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759014
This means we'll need to identify what patches need to be applied on top
of v237 to make this work.
Is this crippling? Are we able to verify that dhcp customization work
despite anything missing in systemd? I think it's the case; but I'd like
a second opinion. To be clear: I think we can verify
Verification of https://bugs.launchpad.net/netplan/+bug/1776228
confirmed that systemd v237 has issues triggered by customizing DHCP
config, which systemd v239 corrected.
Are there any plans to apply these systemd fixes in the Ubuntu LTS
release?
--
You received this bug notification because
Mathieu, quick search reveals that this bug
https://bugs.launchpad.net/netplan/+bug/1802004 might be related to
systemd v237, and that v239 supposedly fixes it. I stumbled upon it
after I tried to re-build the latest netplan on bionic, that's why I've
just rebuilt current bionic version with PR#48
There is no dependency on v239 for netplan backports. Bionic ships with
v237 (and some patches); the dependency on systemd is for >=
235-3ubuntu3 in netplan.io. I do not believe a newer version than that
is required.
Alexey, I really appreciate the work done to make such a backport
available, but
Hi Timo, this is good news. Just out of curiosity, how did you overcome
systemd v239 dependency, which is needed by recent netplan versions,
apparently to fix another bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello Alan, or anyone else affected,
Accepted netplan.io into cosmic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/netplan.io/0.96-0ubuntu0.18.10.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package.
Thank You Alexey for your feature backport. I tested with your script,
and the updated version correctly handled the new options when using
networkd as the renderer on "Ubuntu 18.04.2 LTS (GNU/Linux
4.18.0-16-generic x86_64)". (NetworkManager not currently supported)
dhcp4-overrides:
For those who needs the bionic package with just this feature
backported, I've made one. Install it with `curl -s
https://packagecloud.io/install/repositories/l21/netplan/script.deb.sh |
sudo bash`.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Description changed:
- Currently DHCP appears to be an all or nothing boolean, which is
- insufficient for many network configurations.
+ [Impact]
+ DHCP configurations where custom settings (routes, nameservers, etc.) need to
be applied.
+
+ [Test case]
+ 1) Configure netplan for the
Another vote here, fighting this sadness with some VERY sad wrapper
scripts. Netplan should never have been in any LTS if it can not support
some of these basic options, honestly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
If the maintainers are willing to accept it, I have backported this to
18.04 here:
https://github.com/CanonicalLtd/netplan/pull/73
(Note: I am the author of the original fix for this bug.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This is a very important feature to have backported to 18.04 as being
able to override default gateways for multi-homed hosts (configured to
use dhcp for multiple interfaces) and being able to avoid using DNS
servers provided by a DHCP server(s) are quite common requirements.
--
You received
We also just ran into problems due to not being able to specify DHCP
options in netplan. Please backport the fix to standard 18.04.
Thanks, Lars
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759014
Just wanted to add another vote for backporting this fix to 18.04, would
be really great and as other commenters have pointed out - it should not
change behaviour for exiting configurations.
Thanks,
Anders
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Please backport fix to 18.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759014
Title:
Netplan has no way to control DHCP client
To manage notifications about this bug go to:
In relation to the above comment, Canonical recently announced that Long
Term Support for 18.04 is now extended to a 10 year period. It would be
beneficial to have this fix backported to the long term Ubuntu release.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Are there any plans to bring this fix to what I consider to be a
regression (lack of feature parity with what was possibly previously in
dhclient) into the current LTS release (Bionic 18.04)?
This bug shows as confirmed for Bionic, and being the current LTS, is
what my company is allowing us to
This bug was fixed in the package netplan.io - 0.90
---
netplan.io (0.90) disco; urgency=medium
* New upstream release:
- build: fixes for building on RPM-based distros
- build: code prettiness changes (make indentation consistent)
- Fix device name-changes detection
^^^ I accidentally did that, won't let me set it back to Fix Committed.
Sorry!
** Changed in: netplan
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: netplan.io (Ubuntu Cosmic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759014
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: netplan.io (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759014
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: netplan.io (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759014
Title:
The attachment "replace_dhcp_dns.patch" seems to be a patch. If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
** 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
Package in Ubuntu was renamed from nplan to netplan.io; but regardless
this bug is relevant to the netplan project in general; just moving bugs
around here.
** Package changed: nplan (Ubuntu) => netplan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
59 matches
Mail list logo
