Hi Shannon,
On Mon, May 19, 2008 at 4:54 PM, Shannon <slafferty@xxxxxxxxxxx> wrote:
> 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. :)
>
Sounds like you just need to use a custom network script.
Below are a couple good links that explain it pretty well.
The basic idea is that you will use your custom script to call the proper
network scripts and setup the right netdevs, vifs, and bridges with those
scripts. Then you will connect your guest to the proper bridge.
http://wiki.xensource.com/xenwiki/XenNetworking#head-7b845eda5e0154fecb98165adbd774f6168119d1
http://lists.centos.org/pipermail/centos-virt/2007-December/000119.html
Let us know if you have any problems making the scripts after taking a
look at those links.
Cheers,
Todd
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home