On Mon, Oct 30, 2006 at 09:53:52AM -0300, Tiago Cruz wrote: > Please, > > Some fedora-guy help me with this bridge configuration, because I'm > making some wrong (the bridge on debian usually works for me): > > # btctl show > bridge name bridge id STP enabled interfaces > xenbr0 8000.00137255e4c6 no eth0 > peth0 > vif0.0 > > The problem start when I 'up' the xenbr0 interface... :-( You shouldn't have to ifup the xenbr0 interface at all. There is also no need to created sysconfig/network-scripts/ifcfg-xenbr0 either. Just setup a normal 'ifcfg-eth0' configuration for networking in exactly the same way that you would for bare-metal. When the box comes up, eth0 gets configured as normal. Then, when 'xend' starts it creates the xenbr0 device automatically and makes eth0 part of the bridge & copies across the IP address config that eth0 had to the bridge. You should never have to configure anything on the bridge directly - should be all automatic. Regards, Dan. > > Thanks a lot! > > > On Fri, 2006-10-27 at 19:25 -0300, Tiago Cruz wrote: > > Hello again fedora-guys! > > > > I'm getting one strange problem with FC5 running on XEN 3.0.3 x64, and I > > suspect of my bridge configuration (I never did this before on fedora): > > > > File sysconfig/network-scripts/ifcfg-eth0: > > DEVICE=eth0 > > TYPE=Ethernet > > BRIDGE=xenbr0 > > ONBOOT=yes > > > > File sysconfig/network-scripts/ifcfg-xenbr0: > > DEVICE=xenbr0 > > TYPE=BRIDGE > > BOOTPROTO=dhcp > > ONBOOT=yes > > > > Is it correct this bridge configuration? > > > > Because I have a lot of messages on my console, like this (dmesg): > > > > printk2: 2 messages suppressed > > vif0.0: "received packet with own address as source address" > > printk2: 4775 messages suppressed > > vif0.0: "received packet with own address as source address" > > printk2: 165845 messages suppressed > > vif0.0: "received packet with own address as source address" > > printk2: 186540 messages suppressed > > xenbr0: port 3(eth0) entering disabled state > > xenbr0: port 1(vif0.0) entering disabled state > > device eth0 left promiscuous mode > > audit(1161983401.126:10): dev=eth0 prom=0 old_prom=256 auid=4294967295 > > xenbr0: port 3(eth0) entering disabled state > > > > And the worst part: The MRTG point to my machine with XEN running one > > absurd volume of output data sent (normal is around 6 MB/s) and when XEN > > is working we get 80 MB/s until my DRAC is alive... after this, the > > machine crash, DRAC stop to reply, swith stop do work together... > > > > Anyone knows whats happening now? ;) > > > > Many thanks for any comments! > > Tiago Cruz > > > > -- > > Fedora-xen mailing list > > Fedora-xen@xxxxxxxxxx > > https://www.redhat.com/mailman/listinfo/fedora-xen > > > -- > > Tiago Cruz > Depto. de Sistemas > Fone:(11) 3065-9840 > tiagocruz@xxxxxxxxx > www.ig.com.br > > > -- > Fedora-xen mailing list > Fedora-xen@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/fedora-xen -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| -- Fedora-xen mailing list Fedora-xen@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-xen
