Talk:Network bridge

Merge duplicate effort in other articles

The following articles/sections should be moved here and merged:

1. Bridge with netctl
2. Xen#Creation_of_a_network_bridge
3. QEMU#Creating_bridge_manually

axper (talk) 16:42, 8 July 2014 (UTC)

"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.

Twofive0 (talk) 18:52, 12 August 2014 (UTC)

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?

Lindhe (talk) 15:00, 18 January 2018 (UTC)

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.

CorruptComputer (talk) 03:30, 9 August 2019 (UTC)

I was surprised there weren't any openvSwitch article. I am a total noob using openvSwitch but an just about to try it out integrating libvirt. If you still is up to the task I would appreciate it. I do wonder though if it should be it's own page or not though... --Damme (talk) 21:41, 22 June 2021 (UTC)

I've started a draft for Open vSwitch at User:Damme/Open vSwitch since it's my first attempt at creating a new page I could use some help formatting and making it more clear before I move it to a new page. --Damme (talk) 19:02, 27 June 2021 (UTC)

Instructions style comment on the section, With NetworkManager

regarding Network_bridge#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:

Before:

# nmcli connection show                                                                                ~
NAME                UUID                 TYPE      DEVICE 
Wired connection 1  [yet another value]  ethernet  eno1

After

# 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  --  

I propose,

1) adding `connection show` as the first step

2) rewording `Connection` as:

$ nmcli connection down connection_name

Good?

Xtian (talk) 17:44, 23 April 2021 (UTC)

Bridge with firewall

I use a bridge for a host-only network with QEMU / KVM.

After a lot of struggle I found out that my setup didn't work out because my firewall blocked the bridge.

I added a line to my nftables.conf and everything was fine:

iifname "br0" accept comment "allow from bridge br0"

I thought it would be a good idea to mention this.

I'm not sure if this is more related to QEMU or the network bridge article.

Any suggestions? FreakingOut (talk) 20:53, 22 January 2024 (UTC)

I added a troubleshooting section about this yesterday precisely because I didn't see any mentions about dealing with the firewall in the main article, which would have helped immensely.

I'd say add it here and link to it in the QEMU article. Feel free to rephrase the troubleshooting subsection, since they deal with a similar thing, but bear in mind that your config and the one on that section do different things, I think (in/out vs in only) Eudes (talk) 15:12, 23 January 2024 (UTC)

This is already described on the QEMU page: QEMU#Internal networking. — Lahwaacz (talk) 11:35, 28 January 2024 (UTC)