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] dom0 networking problem

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] dom0 networking problem
From: Jens Fiedler <jens.fiedler@xxxxxxxxxxxxxxxxxxx>
Date: Wed, 04 Oct 2006 20:09:53 +0200
Delivery-date: Wed, 04 Oct 2006 11:08:26 -0700
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: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20060607 Debian/1.7.12-1.2
Hello,

I'm new to xen and happily managed to boot into dom0 with default settings so far. xend is not started automatically, but as soon as I do, networking is broken.
Here is what happens
the bridge is started by /etc/xen/scripts/network-bridge .
It gets the two interfaces peth0 (former eth0) and vif0.0, which connects
to eth0 (former veth0).
eth0 has IP address 10.147.160.15 (ok)
the MAC addess has also moved to eth0 (as it should)
Now, when I ping 10.147.160.11 (an existing system in the network), it does'nt work.
When I do this ping without the xen networking stuff, it works perfectly.
I've tracked down the problem by attaching tcpdump to each interface and found out that ARP requests leave the xen system, get into the target machine, which generates the ARP response. The ARP response is then sent over the network (one single switch), passes the switch (checked using a hub after it), but does not show up in the
tcpdump for peth0, xenbr0, vif0.0 and eth0. causing ping to fail due to ARP.

I digged in the archive and found that people reported this problem before, but I was'nt
able to find a solution yet. Any clues ?

Cheers,
   -Jens

--
Dipl.-Inform. Jens Fiedler
FhI FOKUS, Competence Center for NGNI
Tel.: +49 30 3463 7270
jens.fiedler@xxxxxxxxxxxxxxxxxxx

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

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