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
<[email protected] <mailto:[email protected]>> 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
> [email protected] <mailto:[email protected]>
> http://lists.xensource.com/mailman/listinfo/xen-api
_______________________________________________
xen-api mailing list
[email protected] <mailto:[email protected]>
http://lists.xensource.com/mailman/listinfo/xen-api
_______________________________________________
xen-api mailing list
[email protected]
http://lists.xensource.com/mailman/listinfo/xen-api
