netplan assigns local-link addresses when local-link is diabled

Bug #2043629 reported by LnxGnome
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Netplan
Triaged
Medium
Unassigned

Bug Description

netplan will assign an ipv4 address by default, even if link-local is set to an empty set (link-local: [ ]) to disable it.

The comments in the source suggest that if no address is specified, then link-local should be enabled, and the code does not check it link-local is disabled.

This is faulty logic as you may have stacked interface (example: Physical<VLAN<bridge) where I only want the top (Bridge) to have an address assigned, and neither the Physical or VLAN should be assigned any address. As it is, netplan will would enable link-local for all the lower interfaces that do not have addresses assigned.

Tags: link-local
Revision history for this message
LnxGnome (lnxgnome) wrote :
Revision history for this message
Lukas Märdian (slyon) wrote :

Thank you very much for your analysis and the patch provided. It sounds reasonable at first glance.

Would you mind transforming your patch into a pull-request at https://github.com/canonical/netplan/pulls for easier review and iteration?

Revision history for this message
LnxGnome (lnxgnome) wrote :

Can do. Will add creating a pull to my tasks.

Lukas Märdian (slyon)
Changed in netplan:
status: New → In Progress
LnxGnome (lnxgnome)
description: updated
Revision history for this message
LnxGnome (lnxgnome) wrote (last edit ):

I found my patch isn't quite complete, or maybe it's another issue, as I'm still getting multiple IPv6 addresses on Bridge interfaces. I'll update here when I sort that out.

Lukas Märdian (slyon)
Changed in netplan:
status: In Progress → Triaged
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.