This bug was filed to address *port* priority, not the bridge priority. As mentioned, systemd (networkd) lacks a per-port priority setting;
it should mirror path-cost which takes an interface and value, then the interfaces have a [Bridge] section which has the value. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1668347 Title: Unable to set bridge_portpriority with networkd Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Zesty: Fix Released Bug description: [Impact] * Netplan uses systemd-netword provider to configure all sorts of networking settings * However, unlike ifupdown, released versions of systemd do not support setting bridgeport priority, aka `brctl setportprio <bridge> <port> <priority>` * This prevents full migration from ifupdown to netplan/systemd-networkd for projects like MAAS that do need to configure equal cost; yet differential priority bridge ports. * This is proposal to cherrypick this functionality which essentially accepts one more key in the .network units; and send those values via netlink. [Test Case] * networkd-test.py is executed as part of autopkgtests that configures a bridge, and sets various valid bridge port priorities and verifies from sysfs that those were correctly set by systemd. * Alternativey create a bridge .link unit, and specify .network unit for a bridge port and use Priority=4 setting in the [Bridge] section in the said unit to modify bridge port priority. [Regression Potential] * This is an upstream cherrypick of functionality that will be included in 234 release. However, since MAAS and netplan target stable releases, I would like to cherrypick this functionality all the way back to xenial. This almost a feature, rather than a bugfix, but it is so small and accompanied by regression testsuite that it is almost a tiny bugfix. [Other Info] * Original request to support this feature. 1. root@ubuntu:/run/systemd/network# lsb_release -rd Description: Ubuntu Zesty Zapus (development branch) Release: 17.04 2. root@ubuntu:/run/systemd/network# apt-cache policy systemd systemd: Installed: 232-18ubuntu1 Candidate: 232-18ubuntu1 Version table: *** 232-18ubuntu1 500 500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages 100 /var/lib/dpkg/status 3. Using a networkd config like this: # cat 10-netplan-eth1.network [Match] MACAddress=52:54:00:12:34:02 Name=eth1 [Network] Bridge=br0 LinkLocalAddressing=no IPv6AcceptRA=no [Bridge] Cost=50 Priority=28 % cat /sys/class/net/br0/brif/eth1/priority 28 4. % cat /sys/class/net/br0/brif/eth1/priority 32 When using ifupdown and /etc/network/interfaces to configure a bridge users are able to specify a bridge port priority: auto br0 iface br0 inet static address 192.168.1.1 bridge_ports eth1 eth2 bridge_portprio eth1 28 bridge_portprio eth2 14 Which results in the bridge hook scripts running: brctl setportprio br0 eth1 28 which is visible via: /sys/class/net/br0/brif/eth2/priority Note, networkd does not mention PortPriority under netdev Bridge section, however, PathCost is mentioned. It appears networkd is missing an implementation. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-18ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8 Uname: Linux 4.10.0-8-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 Date: Mon Feb 27 17:11:32 2017 Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-8-generic root=UUID=900c1e3f-f682-4455-949c-ebdbf60ac6f5 ro console=ttyS0 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.1-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-zesty dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.1-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-zesty:cvnQEMU:ct1:cvrpc-i440fx-zesty: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-zesty dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1668347/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
