To fix it with cloud-init we need to create an override-file for netplan
like this:
/etc/netplan/99-critical-dhcp.yaml
network:
version: 2
ethernets:
ens2:
dhcp4: true
critical: true
--
You received this bug notification because you are a member of Ubuntu
The problem I had was not related to netplan, networkd or dhcp client of any
kind.
I had both my ISP links connected to a VLAN switch DLink DGS-1100-08 and
multiplexed to a single Linux router interface with different VLAN numbers.
On Linux side, vlan.NNN interfaces were configured to separate
Hi All,
I know the issue is closed. However, I am observing this issue. I am on
a network where the DHCP lease time out occurs every 24 hours and
whenever that happens my network gets restarted. Due to this I am
loosing some of my IP route entries which in turn causes failures to my
application.
netwokrd backend documentation:
https://www.freedesktop.org/software/systemd/man/systemd.network.html#CriticalConnection=
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Yes, the critical connection is the option to use in this case.
You may also check the leases themselves in /run/systemd/netif/leases
and check if the T1/T2/Lifetime are sensible, with each subsequent one
higher than the prior. And if not, contact your ISP support to correct
those.
** Changed
ok, I installed netplan.io 0.37.1 from Ubuntu Cosmic and set 'critical: true'
for my ISP connection
will check how it will be going after that.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
6 matches
Mail list logo
