everyone has been very helpful so far, thank you all, hopefully i will
become knowledgeable enough to help out others.
However ... if I use the below, it DOES set up two vif's with the correct
addresses, however, they can't reach/be reached by the internet. (Only
eth3 (of dom0)->xen-br1 is external available, so it seems to me they
aren't binding to br1, but to br0.
My reason for thinking this is 1) the no external availability and 2) in
the dom0 ifconfig the vif.1 has the same MAC as br0, leading me to believe
it's bound to that MAC.
Mark wrote:
"The MAC of xenU's eth0, eth1 etc. The MAC of vifX.Y in dom0 always shows
fe:ff:ff:ff:ff."
is this true? It seems vifX.1 (bound to br1) should have MAC of br1,
vifX.0 bound to br0 should have MAC of br0. Maybe this is where I'm going
wrong.
Everything worked fine when i was using eth0/br0 as my external interface
... so i feel like the bridge binding is my only problem ...
ugh, sorry I'm having so many problems ...
On Mon, 2 May 2005, Jody Belka wrote:
On Sun, May 01, 2005 at 09:45:22PM -0700, andrew mathes wrote:
i have this in my configuration file:
vif = [ 'mac=aa:00:00:1a:%d:11' % (vmid), 'bridge=xen-br0']
vif = [ 'mac=aa:00:00:1a:%d:12' % (vmid), 'bridge=xen-br1']
the configuration files are actually python scripts, so the
2nd line there is replacing the information from the first. This is
what you actually need:
vif = [ 'mac=aa:00:00:1a:%d:11, bridge=xen-br0' % (vmid),
'mac=aa:00:00:1a:%d:12, bridge=xen-br1' % (vmid)]
J
--
Jody Belka
knew (at) pimb (dot) org
_______________________________________________
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
|