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

[Xen-users] Xen 3.0 and a virtual net (brouter with masq) (Repost in pla

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Xen 3.0 and a virtual net (brouter with masq) (Repost in plaintext)
From: Arjen Runsink <arjen@xxxxxxxxxxx>
Date: Sat, 04 Mar 2006 10:20:54 +0100
Delivery-date: Sat, 04 Mar 2006 09:22:12 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5 (Windows/20051201)
Hi All,

My previous post accidentally made it it to this list as a HTML text. This was unintentional. In the hope someone can still point me in the right direction for this I am reposting my question


I am trying to create the following configuration:

dom0:

  |---eth2 Masquerading interface to OUTSIDE
  |
  |---eth0 LAN:10.0.1.1/24
  |
  |---eth1 WLAN:10.0.2.1/24
  |
  |---xenbr0 DMZ:10.0.3.1/24
         |
         |-- vifX.0 -- eth0 of domU:10.0.3.2


I would like to do it this way because I will not be using xen all the time on this machine.

I created a network-virtual script which sets up the xenbr0 bridge and gives it an IP, analogues to how a brouting setup would be.

The vif-bridge script is unchanged and used when a domU is started to attach it's vif to it.

users on the LAN and WLAN are allowed to reach the DMZ and OUTSIDE
domU in the DMZ is allowed to reach OUTSIDE.

This all works, except for one thing. the domU does not react to incoming packages for it.

When I ping from a host on the LAN and run tcpdump on eth0 in the domU, I can see the icmp packages coming in like expected. But the domU just will not reply to them.

iptables were flushed etc.
no messages in dmesg or /var/log/messages on the domU

So maybe someone on this list might have an idea what setting might be the cause here?

BB, Arjen

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

<Prev in Thread] Current Thread [Next in Thread>