This bug was fixed in the package systemd - 242-7ubuntu3.2

systemd (242-7ubuntu3.2) eoan; urgency=medium

  [ Dan Streetman ]
  * d/extra/dhclient-enter-resolved-hook:
    - Replace use of bash-only &> with > and 2> (LP: #1849608)
  * d/p/lp1849658-resolved-set-stream-type-during-DnsStream-creation.patch:
    - Fix bug in refcounting TCP stream types (LP: #1849658)
  * d/extra/dhclient-enter-resolved-hook: cleanup temp $newstate file

  [ Rafael David Tinoco ]
  * Add support to KeepConfiguration= fixing behaviour for HA (LP: #1815101)
    - d/p/lp1815101-01-networkd-add-support-to-keep-configuration.patch
    - d/p/lp1815101-02-networkd-stop-clients-when-networkd-shuts-down.patch
    - d/p/lp1815101-03-network-add-KeepConfiguration-dhcp-on-stop.patch
    - d/p/lp1815101-05-man-add-documentation-about-KeepConfiguration.patch

systemd (242-7ubuntu3.1) eoan; urgency=medium

  [ Balint Reczey ]
  * Fix shutdown and related actions from the login screen (LP: #1847896)
  * debian/gbp.conf: Set debian-branch to ubuntu-eoan
    File: debian/gbp.conf

  [ Dan Streetman ]
  * Fix bogus routes after DHCP lease change (LP: #1831787)
  * Set src address for dhcp 'classless' routes (LP: #1835581)
  * Allows cache=no-negative option to be set, ignoring negative answers to
    be cached (LP: #1668771)

 -- Dan Streetman <>  Fri, 01 Nov 2019 16:33:08

** Changed in: systemd (Ubuntu Eoan)
       Status: Fix Committed => Fix Released

You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.

  Bogus routes after DHCP lease change

Status in netplan:
Status in systemd:
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Disco:
  In Progress
Status in systemd source package in Eoan:
  Fix Released

Bug description:

  networkd does not remove old route(s) after DHCP address change

  [test case]

  on a system using networkd, that is connected to a network where you
  can control the addresses that the DHCP server provides, setup system
  with networkd to get address via DHCP, e.g.



  (re)start networkd or reboot, so the system gets an ipv4 DHCP address, and 
corresponding route to the gateway.

  Then on the dhcp server, change the subnet to a different subnet.  On the 
client, once its renews its DHCP address, the server will provide a new address 
in the new subnet, and the client will add a new default route to the new 
gateway address.  However, the old default route to the old gateway address 
isn't removed.

  Note this also happens without changing the entire subnet, but is more
  subtle as shown in the original description.

  [regression potential]

  this affects how networkd handles routes, so has the potential to
  leave a system with partial or incorrect networking, or no networking
  at all.  Any regression would most likely occur during networkd
  (re)start or during renewal of a DHCP lease, or when an interface is
  brought up.

  [other info]

  original description:

  Netplan config:

    version: 2
    renderer: networkd
        dhcp4: no
        dhcp4: no
        dhcp4: yes
          - eno4

  On initial boot, machine got IP address:

  May 03 13:09:41 ceph2 systemd-networkd[29349]: br0: Configured
  May 03 13:09:41 ceph2 systemd-networkd[29349]: br0: DHCPv4 address via

  At one point, DHCP server reserver this IP address and client
  eventually picked up new IP address:

  May 03 15:01:12 ceph2 systemd-networkd[1137]: br0: DHCPv4 address via

  This resulted in IP addresses:

  # ip -o a
  1: lo    inet scope host lo\       valid_lft forever 
preferred_lft forever
  1: lo    inet6 ::1/128 scope host \       valid_lft forever preferred_lft 
  2: eno1np0    inet brd scope global eno1np0\       
valid_lft forever preferred_lft forever
  2: eno1np0    inet6 fe80::b226:28ff:fe53:56be/64 scope link \       valid_lft 
forever preferred_lft forever
  6: br0    inet brd scope global dynamic br0\       
valid_lft 503sec preferred_lft 503sec
  6: br0    inet6 fe80::b8d7:5eff:fe6b:62a/64 scope link \       valid_lft 
forever preferred_lft forever

  So far, everything is fine. But, the routes on the machine are bogus:

  # ip r
  default via dev br0 proto dhcp src metric 100
  default via dev br0 proto dhcp src metric 100 dev br0 proto kernel scope link src dev br0 proto dhcp scope link src metric 100 dev br0 proto dhcp scope link src metric 100 dev eno1np0 proto kernel scope link src

  routes with src should have been removed when lease was
  renewed. I'm not sure if this is a bug in netplan or systemd. This is
  18.04, systemd 37-3ubuntu10.21, netplan 0.40.1~18.04.4.

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to