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-api

Re: [Xen-API] dual nic host

To: Chris Percol <chris.percol@xxxxxxxxx>
Subject: Re: [Xen-API] dual nic host
From: George Shuklin <george.shuklin@xxxxxxxxx>
Date: Thu, 25 Aug 2011 22:58:38 +0400
Cc: xen-api@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 25 Aug 2011 12:04:15 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type; bh=Q1PdxRQe286QLMfRJ4VP7QBoqWoJYq19ftTtGeg3hX8=; b=NIh7sGMdg6dEdUec+EBk2RxGEZbMBN+htO9ogRvjPL8QM8iTRNHAAgyq53hgL6ES+a v+cOkr/+PjH6l0Djym4JSWgH6POUF8rtfBO6TOScyR6/DnbfjDO/OFwjYKciGbSAHZwO 5z8zexW8VzJewxyyb7ynfjj4UiTYDANPWbinA=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <CAGwLQT2Sxmbd0Y0FJFR6fNd9vWtsfgVpXAbhLS+q4-JX9S+tBA@xxxxxxxxxxxxxx>
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
References: <CAGwLQT0VaieirDe8azFAo=19gz0Qqu=vMYDgWNQ4h4kwugJPhg@xxxxxxxxxxxxxx> <1314279624.31001.1.camel@mabase> <CAGwLQT2Sxmbd0Y0FJFR6fNd9vWtsfgVpXAbhLS+q4-JX9S+tBA@xxxxxxxxxxxxxx>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.18) Gecko/20110626 Icedove/3.1.11
Well, if you do really wish to connect hosts (to be exactly, dom0) to different networks, then create a separate vif's. This can sounds strange, but you can create vifs and connect them to requited networks. Control domain is same domain as normal virtual machines, so you can connect vifs/vbds to them.

'physical' network interfaces (pifs) are used only for bridging.

On 25.08.2011 22:07, Chris Percol wrote:
Thanks, but in another environment we have a similar setup and I am struggling to see why this scenario is a problem?

In the other environment we have a host with one nic connected to a switch then router/gateway, 10.10.0.1. Another nic in the same host is connected to a separate switch which is connected to a san with a gateway of 172.16.0.1. Both nics have addresses on their respective networks and the host can happily talk to either network .

However, in the new environment we are working on we can not get xenbr1 on a 192.168.100.0 network to talk to the gateway on the same network, 192.168.100.1. The xenbr0 connected to separate physical network of 192.168.1.0 has no problem  talking to the 192.168.1.1 gateway and clients.

I tried adding a route for the 192.168.100.1 which was added to the route table but still no joy.

Can anyone shed any light?

Thanks,

Chris

On Thu, Aug 25, 2011 at 2:40 PM, George Shuklin <george.shuklin@xxxxxxxxx> wrote:
I think this is a task for router.

If you are asking about direct interconnetion between networks on host,
this is possible, but not supported.


В Чт., 25/08/2011 в 11:50 +0100, Chris Percol пишет:
> Hi,
>
>
> I have a dual nic host running xcp 1 rc3 with each nic connected to a
> separate physical network/broadband connection, xenbr0 and xenbr1.
>
>
> How do I go about enabling a workstation to ping xenbr1, which is on
> the same physical network, when the host's gateway is being set by
> xenbr0?
>
>
> Here's my current setup...
>
>
> xenbr0, 192.168.100.3, gateway 192.168.100.1
> xenbr1, 192.168.1.3, (gateway 192.168.1.1)
>
>
> Many thanks,
>
>
> Chris
>
>
>
>
> _______________________________________________
> xen-api mailing list
> xen-api@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/mailman/listinfo/xen-api



_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api

_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api
<Prev in Thread] Current Thread [Next in Thread>