2015-11-13 13:52 GMT-03:00 Gordon Messmer <gordon.messmer at gmail.com>:> On 11/13/2015 03:22 AM, Sergio Belkin wrote: > >> I'm trying to create virtualized linux bridge >> > > Well, you can't do that by putting two interfaces on the same LAN. A > bridge should be used to connect two separate LANs. > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos >But.... AFAIK, routers divide broadcast domains, and switches (and therefore bridges) divide collision domains. For example: "A bridge is a piece of software used to unite two or more network segments. A bridge behaves like a virtual network switch, working transparently (the other machines do not need to know or care about its existence). Any real devices (e.g. eth0) and virtual devices (e.g. tap0) can be connected to it." https://wiki.archlinux.org/index.php/Network_bridge If I'm wrong please correct me. -- -- Sergio Belkin LPIC-2 Certified - http://www.lpi.org
On 11/13/2015 09:15 AM, Sergio Belkin wrote:> But.... AFAIK, routers divide broadcast domains, and switches (and > therefore bridges) divide collision domains.Oh good, Cisco terminology. :) I'll be more specific than I was earlier, then. It's possible to unify two collision domains into a single broadcast domain with a router, but it's also possible to use a bridge to link collision domains to create a larger broadcast domain. Don't get hung up on that. The comparison of a Linux bridge to a switch is apt. You could, conceptually, connect two PCs to each other using a Linux bridge. You wouldn't, however, connect two ports on one switch (here, the Linux bridge) to two ports on another switch. Doing that creates a loop in your network. Linux Ethernet bridges have several uses, so it's not clear what you're really trying to do. That is, you've said that you're trying to create a virtualized Linux bridge, but a bridge is a tool, not a goal in itself. What do you expect the bridge to do when you've set it up?
2015-11-13 16:43 GMT-03:00 Gordon Messmer <gordon.messmer at gmail.com>:> On 11/13/2015 09:15 AM, Sergio Belkin wrote: > >> But.... AFAIK, routers divide broadcast domains, and switches (and >> therefore bridges) divide collision domains. >> > > Oh good, Cisco terminology. :) >Oh yeah,> > I'll be more specific than I was earlier, then. > > It's possible to unify two collision domains into a single broadcast > domain with a router, but it's also possible to use a bridge to link > collision domains to create a larger broadcast domain. Don't get hung up > on that. > > The comparison of a Linux bridge to a switch is apt. You could, > conceptually, connect two PCs to each other using a Linux bridge. You > wouldn't, however, connect two ports on one switch (here, the Linux bridge) > to two ports on another switch. Doing that creates a loop in your network. > > Linux Ethernet bridges have several uses, so it's not clear what you're > really trying to do. That is, you've said that you're trying to create a > virtualized Linux bridge, but a bridge is a tool, not a goal in itself. > What do you expect the bridge to do when you've set it up? > > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos >I'd want to connect a VM to another VM (or eventually to the host) via the "Linux bridge" so that I can demonstrate that capability in a classroom with only one laptop. -- -- Sergio Belkin LPIC-2 Certified - http://www.lpi.org