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 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
/run/systemd/netw
** Also affects: baltix-default-settings
Importance: Undecided
Status: New
--
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 co
@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).
It
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
I can confirm that on an up-to-date Ubuntu 22.04 use-dns doesn't work
with the NetworkManager renderer. It does work with networkd.
network:
ethernets:
enp2s0:
dhcp4: true
dhcp4-overrides:
use-dns: false
nameservers:
addresses: [9.9.9.9, 149.112.112.112]
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
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 bu
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.launch
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. Se
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. Se
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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1759014
Title
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 notificati
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]
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
dhcp4-o
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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1759014
Title
@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 compla
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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/175
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
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 th
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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.n
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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.laun
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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.laun
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
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 netplan.io/bionic-proposed
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]
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]
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
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
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. Se
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
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:
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:~#
>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: Co
36 matches
Mail list logo
