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] Network Stup Problem

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Network Stup Problem
From: Matthias Henze <lists@xxxxxxxxxxxxxx>
Date: Mon, 12 Nov 2007 15:49:52 +0100
Delivery-date: Mon, 12 Nov 2007 08:15:55 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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: KNode/0.10.5
Hi,

I want to setup a server at 1&1 with XEN on Debian Etch AMD 64. Basic setup
and setting up domU's is no problem. What i want you can see here:

http://www.mhcsoftware.de/xen.png

Every eth0 should get it's own official IP. For this i have 3 IP's which are
routed to my switchport. Routing at 1&1 is a bit tricky. With a normal
server eth0 gets it's IP with 255.255.255.255 as netmask and the the
following is required for gateway config:

route add -net 10.255.255.1 netmask 255.255.255.255 dev eth0
route add default gw 10.255.255.1

After this "the world" is reachable. Dom0 is configured like this an
reachable. Then I've setup on bridge and connect one domU to it and did the
same setup with a different official IP. Then I Tried to test this with a
ping and traced the packets. With my setup the problem is, that the packets
are send out and the echo reply comes back to the bridge but never reaches
eth0 of the domU because of it's mac address. Eth0 of the domU is connected
to vif0.1 of br0 but the mac the packets are sent to is the real mac of the
hardware and this is bound to vif0.0 of br0.

How can i get this working ? I'm stuck.

TIA
matthias


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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Network Stup Problem, Matthias Henze <=