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
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
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 t
** 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 supp
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
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
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
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
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]
@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
13 matches
Mail list logo
