[network-manager] Duplicated IP addresses appear on service re-start

Bug #1811347 reported by Alfonso Sanchez-Beato on 2019-01-11
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
snappy-hwe-snaps
High
Alfonso Sanchez-Beato

Bug Description

When re-starting the network-manager service, in some cases duplicated IP addresses appear in the managed interfaces. This happens because apparently NM is ignoring the old DHCP leases, and sends always a "DHCP discover" package. Some DHCP servers assign a new IP when that happens, and NM does not remove the old address.

The right thing to do would be to send a "DHCP request" containing the old lease. This is actually what I see happening on bionic desktop. In that case, the DHCP server can either acknowledge the old address or assign a new one.

The specified behaviour when a discover is received in the DHCP server is to consider that the leases previously assigned to the sending MAC are not in use anymore. This can lead to problems if the server decides to assign those addresses to other devices. Also, we have the additional problem of NM setting the old lease as the primary address.

Related branches

Changed in snappy-hwe-snaps:
status: New → Confirmed
importance: Undecided → High
Changed in snappy-hwe-snaps:
assignee: nobody → Alfonso Sanchez-Beato (alfonsosanchezbeato)
Changed in snappy-hwe-snaps:
status: Confirmed → Fix Committed
Changed in snappy-hwe-snaps:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers