Networking and servers • nmcli, Network Manager CLI, has naming problem.

Pi OS desktop updated today on Pi 4. I created an eth0 wlan1 bridge using nmcli. Tested the steps so they could be in a config script.

When nmcli created bridge br0, nmcli said it created bridge-br0. I then entered the commands to configure the bridge and switch it on. The enslave commands required the name br0 and refused to recognize bridge-br0. The up command refused to recognize br0 and worked only when I used bridge-br0. nmcli appears to be a long way from finished.

I ended up putting both both versions of the up command in my script on the basis they might fix the up command to use our name for the bridge, not the NM internal name.

The enslave command is more dangerous. It happily lets you add the same device multiple times with different names. You cannot add both versions of the command in the hope that just one works. If the command is changed to accept both names, you will end up with the one device added twice.

I do not know if there is an easy way for a script to run the following command then only run the second command if the first one fails.
nmcli con up br0
nmcli con up bridge-br0

Statistics: Posted by peterlite — Sun Jun 16, 2024 7:34 am

---