Hi,
first of all I beg your pardon - while I'm just the one cleaning old bugs - it 
is bad that you had to wait so long.

Now lets get to your case...

This is a mix of systemd and ifup based network ocnfiguration, and in
Artful a lot of this was still in flight.

In Bionic there is a simplified frontend to networkd (or networkmanager) [1] 
netplan.
I wanted to check your case with this new way to do it.

I have 4 devices, using one as "wan" and 3 for the bridge in netplan looks like:
network:
    version: 2
    ethernets:
        wan:
            dhcp4: true
            match:
                macaddress: 52:54:00:75:f5:3e
            set-name: wan
        lan1:
            match:
                macaddress: 52:54:00:84:a1:87
            set-name: lan1
        lan2:
            match:
                macaddress: 52:54:00:f3:4f:cc
            set-name: lan2
        lan3:
            match:
                macaddress: 52:54:00:ff:11:1a
            set-name: lan3
    bridges:
        br0:
            addresses: [ 10.0.0.1/24 ]
            interfaces:
                - lan1
                - lan2
                - lan3



That will create link files like yours for renaming:
$ cat /run/systemd/network/10-netplan-wan.link 
[Match]
MACAddress=52:54:00:75:f5:3e
[Link]
Name=wan
WakeOnLan=off


But also for network configuration:
$ cat /run/systemd/network/10-netplan-wan.network 
[Match]
MACAddress=52:54:00:75:f5:3e
Name=wan
[Network]
DHCP=ipv4
[DHCP]
UseMTU=true
RouteMetric=100

Especially also the bridge:
$ cat /run/systemd/network/10-netplan-br0.network 
[Match]
Name=br0
[Network]
Address=10.0.0.1/24
$ cat /run/systemd/network/10-netplan-br0.netdev 
[NetDev]
Name=br0
Kind=bridge

And the device association to the bridge:
$ cat /run/systemd/network/10-netplan-lan2.network 
[Match]
MACAddress=52:54:00:f3:4f:cc
Name=lan2
[Network]
Bridge=br0
LinkLocalAddressing=no


That looks good to me now:
$ networkctl list
IDX LINK             TYPE               OPERATIONAL SETUP     
  1 lo               loopback           carrier     unmanaged 
  6 br0              ether              routable    configured
  7 lan3             ether              carrier     configured
  8 lan1             ether              carrier     configured
  9 wan              ether              routable    configured
 10 lan2             ether              carrier     configured

$ networkctl status
●        State: routable
       Address: 10.0.0.1 on br0
                192.168.122.229 on wan
                fe80::e831:94ff:fe76:95f9 on br0
                fe80::5054:ff:fe75:f53e on wan
       Gateway: 192.168.122.1 on wan
           DNS: 192.168.122.1

$ brctl show
bridge name     bridge id               STP enabled     interfaces
br0             8000.ea31947695f9       no              lan1
                                                        lan2
                                                        lan3

Please see [1] and man netplan for more, or feel free to write the same
in networkd rules as you already started on your own.

But mixing the systems to control devices is not really recommended as
you'd run in issues just as the one you have reported.

Therefore I'd consider this a broken config more than a bug in Ubuntu
and would mark the bug incomplete for now until further discussion/info
was provided.

[1]: https://netplan.io/

** Also affects: netplan.io (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: systemd (Ubuntu)
       Status: New => Incomplete

** Changed in: netplan.io (Ubuntu)
       Status: New => Incomplete

** Changed in: bridge-utils (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1738085

Title:
  Bridge gets created while the network interfaces are still being
  renamed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1738085/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to