search for: perfmanc

On 11/12/2015 10:42 AM, Sergio Belkin wrote: > DEVICE=enp0s3 > #HWADDR=08:00:27:AB:1D:E6 > BOOTPROTO=none > ONBOOT=yes > NM_CONTROLLED=no > BRIDGE=br0 > DEVICE=enp0s8 > HWADDR=08:00:27:A3:98:E6 > BOOTPROTO=none > ONBOOT=yes > NM_CONTROLLED=no > BRIDGE=br0 Do you have those two devices connected to the same LAN? > I've disabled NetworkManager, but

2015-11-12 16:51 GMT-03:00 Gordon Messmer <gordon.messmer at gmail.com>: > On 11/12/2015 10:42 AM, Sergio Belkin wrote: > >> DEVICE=enp0s3 >> #HWADDR=08:00:27:AB:1D:E6 >> BOOTPROTO=none >> ONBOOT=yes >> NM_CONTROLLED=no >> BRIDGE=br0 >> > > DEVICE=enp0s8 >> HWADDR=08:00:27:A3:98:E6 >> BOOTPROTO=none >> ONBOOT=yes

Am 12.11.2015 um 19:42 schrieb Sergio Belkin: > [root at localhost ~]# uname -a > Linux localhost 3.10.0-123.el7.x86_64 #1 SMP Mon Jun 30 12:09:22 UTC 2014 > x86_64 x86_64 x86_64 GNU/Linux First of all: yum update to current! Alexander

On 11/12/2015 10:42 AM, Sergio Belkin wrote: > DEVICE=enp0s8 > HWADDR=08:00:27:A3:98:E6 > BOOTPROTO=none > ONBOOT=yes > NM_CONTROLLED=no > BRIDGE=br0 > DEVICE=lo > TYPE=loopback > IPADDR=127.0.0.1 > NETMASK=255.0.0.0 > NETWORK=127.0.0.0 > ... I hope thats two seperate files, ifcfg-enp0s8 and ifcfg-lo ... otherwise, why is a bridged physical interface configured

----- Original Message ----- | Hi, | | I've created a bridge using 2 interfaces and have a lot of messages as | follows: | | nov 12 15:30:22 localhost kernel: br0: received packet on enp0s3 with own | address as source address | nov 12 15:30:22 localhost kernel: br0: received packet on enp0s3 with own | address as source address | | And the operating systems is extremely slow | |

On 11/12/2015 07:42 PM, Sergio Belkin wrote: > I've created a bridge using 2 interfaces and have a lot of messages as > follows: > > nov 12 15:30:22 localhost kernel: br0: received packet on enp0s3 with own > address as source address > nov 12 15:30:22 localhost kernel: br0: received packet on enp0s3 with own > address as source address sounds like a loop. What says

2015-11-12 15:56 GMT-03:00 Ulf Volmer <u.volmer at u-v.de>: > On 11/12/2015 07:42 PM, Sergio Belkin wrote: > > I've created a bridge using 2 interfaces and have a lot of messages as >> follows: >> >> nov 12 15:30:22 localhost kernel: br0: received packet on enp0s3 with own >> address as source address >> nov 12 15:30:22 localhost kernel: br0:

On 11/13/2015 12:57 PM, Sergio Belkin wrote: > When I enable stp: > > [root at localhost ~]# brctl show br0 > bridge name bridge id STP enabled interfaces > br0 8000.080027a398e6 yes enp0s3 > enp0s8 As Gordon said, i recommend to remove one of the physical interfaces

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.

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

On 11/14/2015 09:20 AM, Sergio Belkin wrote: > 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. You don't actually need to attach *any* ethernet interfaces to do that. If you create a bridge with no Ethernet slaves, and then create two VMs,

----- Original Message ----- | On 11/14/2015 09:20 AM, Sergio Belkin wrote: | > 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. If the purpose of this is to demonstrate VMs you just want to bridge the physical interface so that the guest can

On 11/14/2015 09:20 AM, Sergio Belkin wrote: > > 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. The libvirt wiki covers this here [0]. These instructions create a bridge (br0), connect the physical ethernet interface to that bridge, then you can

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

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.

2015-11-14 16:43 GMT-03:00 Gordon Messmer <gordon.messmer at gmail.com>: > On 11/14/2015 09:20 AM, Sergio Belkin wrote: > >> 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. >> > > You don't actually need to

2015-11-12 18:07 GMT-03:00 James A. Peltier <jpeltier at sfu.ca>: > ----- Original Message ----- > | Hi, > | > | I've created a bridge using 2 interfaces and have a lot of messages as > | follows: > | > | nov 12 15:30:22 localhost kernel: br0: received packet on enp0s3 with own > | address as source address > | nov 12 15:30:22 localhost kernel: br0: received

Hi, I've created a bridge using 2 interfaces and have a lot of messages as follows: nov 12 15:30:22 localhost kernel: br0: received packet on enp0s3 with own address as source address nov 12 15:30:22 localhost kernel: br0: received packet on enp0s3 with own address as source address And the operating systems is extremely slow Interfaces files : [root at localhost ~]# cat