[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] Routing problem in bridged setup


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Pepe Barbe <elventear@xxxxxxxxx>
  • Date: Fri, 9 May 2008 12:17:27 -0500
  • Delivery-date: Fri, 09 May 2008 10:18:43 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:content-type:content-transfer-encoding:mime-version:subject:date:x-mailer; b=gHXMIG3JVx2mdQFpGLJq19AE4L5l1VE14gkamcDy60ptd2J1HOJ3apkp0zaW3oyy4mxxWW/6svWAqd6PzbUFGquRMPTpbWxp2N9TUkhPnjh/sO76C4xnsDzpv+9EhgWb8ncsM4tpTA0LNbnEb2j32PKiH9hodvOaZqVctyzGW10=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hello,

I am having some routing troubles with my Xen setup.

I have two domUs, one running as a firewall and another running as a dmz:

The dom0 has the following:
- eth0 bridge (10.0.0.3/24)

The domU-firewall has the following:
- Direct passthrough PCI NIC (Public Internet)
- Virtual NIC connected to the eth0 bridge on dom0 (10.0.0.1/24)
- Bridge called brdmz for the dmz zone (10.0.2.1/24)

The domU-dmz has the following:
- Virtual NIC connected to the brdmz in domU-firewall (10.0.2.2/24)

So far can I can make the domU-firewall and domU-dmz talk to each other without problem. Using IPTables/NAT on domU-firewall I can route to the public internet from dom0/Local Lan and from the domU-dmz. But I can't communicate from the domU-dmz to local lan and viceversa. I've made sure that there are no IPTables rules blocking this kind of traffic, so all I am left is with the possiblity of a routing problem: domU-firewall not forwarding packets from the local lan to the dmz bridge for some reason.

Anyone has any idea of what could I do to troubleshoot this problem?

Thanks,
Pepe

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.