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

Re: [Xen-users] dom0 networking problem

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] dom0 networking problem
From: Jens Fiedler <jens.fiedler@xxxxxxxxxxxxxxxxxxx>
Date: Thu, 05 Oct 2006 18:22:07 +0200
Delivery-date: Thu, 05 Oct 2006 09:21:15 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <45250C72.1040604@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>
References: <4523F8F1.5050905@xxxxxxxxxxxxxxxxxxx> <4524127E.3090501@xxxxxxx> <45250C72.1040604@xxxxxxxxxxxxxxxxxxx>
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
Jens Fiedler wrote:

John Smith wrote:

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
Cheers,
-Jens


Jens,

it smells like a switch with autolearning.
I would try it with a hub _in stead_ of the switch.

Sincerely,

Jan.


Hi,

The ARP response passes the switch, the hub was placed behind the switch in order to check wheter the switch drops the ARP response. It does not, I can see the ARP responses using a 3rd machine (sniffer in the fig.) connected to that hub. So the switch is not the point of
failure.

   <---------------------ARP request----------------
   ----------------------ARP response---->
+-------+                                     +-------------+
|target |     +--------+       +-----+        | xen machine |
|machine|-----| switch |-------| hub |--------|peth0        |
+-------|     +--------+       +-----+        +-------------+
                                 |
                             +--------+
                             | sniffer|
                             +--------+

Additionally, when I look at the packet counters using 'ifconfig', the counters for TX and RX go up, although tcpdump does not show any incoming ARP response on peth0. So the ARP responses are received by the interface, but get dropped before coming to tcpdump or xenbr0. peth0 counters for errors are 0. In tcpdump for peth0 I can see the outgoing ARP requests. The only incoming packets I see are broadcasts from other machines (router adv, other machines' ARP reqs for different IP addresses, not related to the xen box)

Still clueless,
   -Jens

I "solved" the problem ...
The xen machine has 4 ethernet devices:
04:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 11) 08:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 11) 0b:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06) 0b:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06)

The problem vanished when switching from the Broadcom interface (eth0) to an Intel interface (eth2) as the physical device. I'm now running with peth2 on the xenbr0 bridge and it runs fine. I'm not a kernel guru, but seems that the driver for the broadcom nic (bnx2) has some bug.

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>