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

[Xen-users] Specific vif-route or vif-bridge in DomU config file?

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Specific vif-route or vif-bridge in DomU config file?
From: Shannon <slafferty@xxxxxxxxxxx>
Date: Mon, 19 May 2008 16:54:24 -0400
Delivery-date: Mon, 19 May 2008 13:54:57 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.14 (Windows/20080421)
Is there any way to specific on the vif = [] line of a DomU config if an interface should be routed or bridged?

Have a situation that I believe calls for wanting to use both methods at the same time. (Bridging for almost everything, but routing for a few special use case DomUs)... I thought I saw mention in a man file someplace that this could be specified, but no ideal where I saw it now...

Basically, we have a physical box with two ethernet ports, one goes to our internal private LAN, the other connects to the outside world.. want to fullfill three needs:

- Every DomU needs to be able to access the private network that hangs off eth0, but doesn't need to be accessible FROM the private network (bridging at use). - Every DomU needs to be able to access the internet (hanging off Dom0's eth1), and *some* need to be accessible from the rest of the internet (routing at play). - Every DomU needs to be able to communicate with *each other*, freely, on the 192.168.x.x network that was created by libvirtd (or where-ever that was started)..

The first two I have working fine, using vif-route network-route, and some manual manipulation of the routing tables on the DomUs... the last one is driving me insane, as traffic from one DomU to another is showing up (for instance, in nfs, and even tcpdumps) as coming from the Dom0's IP address instead... If I use brctl manually and add the appropriate vif#.0 to the bridge, it works okay, but if I can't automate it, it's not going to work out. (ie: having to run brctl every time a DomU is restarted != fun).

If I switch xend-config over to bridging, I can make the third thing work, but lose the first two. :( So I'm wondering if there's any way to specify in more detail how a specific vif should be built? Or am I chasing this in entirely the wrong direction? I'm assuming someone out there has wanted to do something similar before, I just can't seem to find mention anywhere online of *how* anyone has accomplished it. :)

- Shannon

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

<Prev in Thread] Current Thread [Next in Thread>