** Changed in: systemd (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726912
Title:
fails to keep dhcplease
To manage notifications about this bug go to:
I can confirm this works in Bionic so close away
thanks,
-jon
On Tue, Apr 17, 2018, 4:11 PM Mathieu Trudel-Lapierre
wrote:
> This would be a systemd-networkd bug, which I suspect might have already
> been fixed too. Reassigning to systemd.
>
> ** Package changed: nplan (Ubuntu) => systemd (Ubun
This would be a systemd-networkd bug, which I suspect might have already
been fixed too. Reassigning to systemd.
** Package changed: nplan (Ubuntu) => systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
this is actually upstream bug
https://github.com/systemd/systemd/issues/6593 related to setting MTU.
If this isn't patched before 18.04 release please, please, please revert
to ifupdown as default
** Bug watch added: github.com/systemd/systemd/issues #6593
https://github.com/systemd/systemd/is
I have verified this is reproducible on other systems with ixgbe based
add in cards.
igb (1G) cards seem to behave properly as do a random assortment of
onboard devices and virtio devices inside VMs.
Based on a pseudo random selection of my available gear it does seem
hardware specific but this i
this is happening on a system using 10G Intel NIC:
05:00.0 Ethernet controller: Intel Corporation Ethernet Controller 10-Gigabit
X540-AT2 (rev 01)
root@host:~# ethtool enp129s0f0
Settings for enp129s0f0:
Supported ports: [ FIBRE ]
Supported link modes: 1baseT/Full
S