Bridging in plasma-nm
To elaborate on why I added a note on not being able to add a bridge from the plasma-nm KCM, I verified this with a look through the UI, as well as a cursory glance at the code for creating a connection (https://github.com/KDE/plasma-nm/blob/8d18894fd9b236fca548e8f6235c0ae18e060e1d/kcm/kcm.cpp#L260-L367) showing no capabilities of creating a virtual connection.
Merge duplicate effort in other articles
The following articles/sections should be moved here and merged:
"With bridge-utils" Section Breaks Existing Connection
Executing the commands in the "With bridge-utils" section broke my existing network configuration. I got around the issue by using netctl instead but even then, only by starting the bridge first. In this case, netctl starts the bound interfaces automatically when the bridge is started. I would like to suggest a clarification of this on the Bridge with netctl page and perhaps a re-work of command examples on Network bridge.
Is a bridge really like a switch?
I had read elsewhere that a bridge is like a hub, but the introductory section of this article says it's like a network switch. What's the case? Does it duplicate all packets to all hosts like a hub, or is it clever about it with arp tables etc. like a switch?
- I don't know for certain that the bridge described works identically to the physical piece of network equipment known as a "bridge", but a switch is basically defined as a multiport network bridge, and a hub is a multiport repeater. --Magotchi (talk) 15:09, 18 January 2018 (UTC)
Adding Open vSwitch?
Would it be beneficial to add Open vSwitch to this article? I don't have any problem working on it, but I was wondering what others thought about this.
Instructions style comment on the section, With NetworkManager
I found this line confusing:
$ nmcli connection down Connection
Arguments and values with the same name are confusing. More so here, because the term is used in the preceding paragraphs referring to "new bridged connection", "Connections window", etc., and without reference to the use I've cited here.
Fortunately, there is another command which labels the value, and it's use demonstrates progress with the instructions:
# nmcli connection show ~ NAME UUID TYPE DEVICE Wired connection 1 [yet another value] ethernet eno1
# nmcli connection show ~ NAME UUID TYPE DEVICE bridge-br0 [some value] bridge br0 bridge-slave-eno1 [another value] ethernet eno1 Wired connection 1 [yet another value] ethernet --
1) adding `connection show` as the first step
2) rewording `Connection` as:
$ nmcli connection down connection_name