|
Could you please use the brctl command and send the output of the command to verify that the bridges are set up correctly?
-Nick
>>> On Fri, Jun 27, 2008 at 1:56 AM, Stephan Seitz <s.seitz@xxxxxxxxxxxx> wrote:
Hi there,
I'm trying to use different bridges like shown below:
| default gateway |
-----------------
|
-----------------
| switch ext |
-----------------
| peth0 | peth1
-----------------------------------------
| eth0(bridge) eth1(bridge) |
| dom0/ | | | | | | \dom0unused|
| vif vif vif vif vif vif |
| domU dU dU dU dU dU |
| vif vif vif vif vif vif |
| | | | | | | |
| dom0\ | | | | | | |
| eth2(bridge)------------ |
-----------------------------------------
| peth2
-------------------
| switch int | no default route
-------------------
My attempt is to have sets of domUs bridge-connected via different
NICs to "ext". I'm trying to avoid bonding peth0 and peth1 do have
all domUs bridged via bond0, as this needs switch configuration
with physical presence at the datecenter (I would like to have an
off-site alternative).
The eth0 and eth2 bridges are working like expected. My problem is
eth1. I first tried a bridge with no dom0 connection, I don't think
it's possible at all(?). Having eth1 configured with another dom0 IP
seems to work for dom0, but even if I configure a completele eth1 for
a completely different range (default gateway is aware of a handful
of independent subnets) the traffic "seems" to leave peth0 instead of
peth1. I didn't investigate into this as my primary goal is not dom0
connection. My tests with domUs bridged on eth1 shows only outgoing
traffic. domUs connected via eth0 are working as expected.
Any suggestions?
Thanks in advance!
Stephan
This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR.
|
