NetworkManager and networkd different bridged outcome

Bug #1844754 reported by Trevor Rabie
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Netplan
New
Undecided
Unassigned

Bug Description

The following config:

network:
  version: 2
  renderer: networkd
  ethernets:
    enp0s31f6:
      dhcp4: no
  bridges:
    npbr0:
      interfaces:
        - enp0s31f6
      dhcp4: yes

produces the following expected outcome:

npbr0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
        inet 192.168.1.64 netmask 255.255.255.0 broadcast 192.168.1.255

enp0s31f6: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
        ether 70:85:c2:72:83:25 txqueuelen 1000 (Ethernet)
        RX packets 12244805 bytes 11369274561 (11.3 GB)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 24490862 bytes 31660043085 (31.6 GB)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
        device interrupt 16 memory 0xdf100000-df120000

HOWEVER, changing the renderer to NetworkManager does not correctly bind enp0s31f6 to the bridge npbr0. enp0s31f6 is allocated the IP of 192.168.1.64 and not the bridge.

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.