WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] multiple vif's/bridges

Might be worth checking all the MAC addresses (the VIFS at both "ends" (the 
dom0 vif devices and the domU eth devices).  Might as well check the "eth" 
devices in dom0.

Can you post those MAC addresses, plus your domain configs where they are set.  
If you get clashes in the MAC addresses, all sorts of weird behaviour can 
happen!

Cheers,
Mark

On Wednesday 04 May 2005 09:49, Mark Doll wrote:
> andrew mathes schrieb:
> > all i can think of now is it's a routing issue- here is my route -n on
> > dom0:
> >
> > 10.1.1.0        0.0.0.0         255.255.255.0   U     0      0        0
> > xen-br1
> > 0.0.0.0         10.1.1.254      0.0.0.0         UG    0      0        0
> > xen-br1
> >
> > and from domU:
> >
> > Destination     Gateway         Genmask         Flags Metric Ref    Use
> > Iface
> > 10.1.1.0        0.0.0.0         255.255.255.0   U     0      0        0
> > eth1
> > 0.0.0.0         10.1.1.254      0.0.0.0         UG    0      0        0
> > eth1
>
> OK, network 10.1.1.0/24 with router 10.1.1.254 via eth3 (xen-br3). Both
> dom0 and domU are simple hosts and don't route. Fine.
>
> > ifconfig output looks good, as well as brctl, everything looks bound
> > correctly, although i'm still confused why vifX.1 while bound to xen-br1
> > doesn't get it's mac address ... seems odd to me
>
> My vifX.Y always have fe:ff:ff:ff:ff:ff. Do you mean, while vifX.1 does
> not get the configured MAC your vifX.0 does?
>
> > well, that's all the output i can do, and if there's nothing wrong in
> > these routes ... i'm stumped, one network card for me i guess =/
>
> One last idea. I don't remember: Have you tried xen-br0 on eth3 and it
> worked? If not, are your eth0 and eth3 NICs different hardware
> models/use different device drivers? Maybe it's a NIC driver or hardware
> problem. Maybe setting the NIC in promicious mode might help "ip l s
> eth3 promisc on" or "ifconfig eth3 promisc". Maybe the driver is
> incompatible with the bridging code.
>
> Mark.
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users