From owner-freebsd-hackers@FreeBSD.ORG Thu Jun 1 16:14:47 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6A09216A782 for ; Thu, 1 Jun 2006 16:14:47 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD7C243D46 for ; Thu, 1 Jun 2006 16:14:46 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [10.10.3.185] ([69.15.205.254]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k51GEWCF008013; Thu, 1 Jun 2006 10:14:39 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <447F1262.6020805@samsco.org> Date: Thu, 01 Jun 2006 10:14:26 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060206 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Danny Braniss References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=3.8 tests=none autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: freebsd-hackers@freebsd.org Subject: Re: iSCSI/sendto(...) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jun 2006 16:14:47 -0000 Danny Braniss wrote: >>Danny Braniss wrote: >> >> >>>Hi, >>> on a fairly new 6.1-stable, and probably before, once in a >>>blue moon, sendto return error 64 (EHOSTDOWN?). but the packet seems to have >>>been received by the target, since i get a response, and further more, >>>everything keeps on working. >>> >>>what is error 64? >>> >>>danny >>> >>> >> >>EHOSTDOWN comes from the ARP layer of the IP stack, and would be >>consistent with the host either getting no arp response or rejected >>responses from the target. It would be useful to run tcpdump+ethereal >>on your connection to see what is really going on. >> > > too much traffic, and would be like looking for a needle in a haystack. > (i can't reproduce this at will) > the question is, if it was an error, how come the packet did go out. > need more proof for the above statement - working on it. > > danny > > > > I find that ethereal does a great job of associating packets and making it easy to sort through mountains of data. It's not so good at actually collecting the packets, so I run tcpdump in raw collection mode and then feed the output to ethereal for analysis. Having tcpdump generate a circular ring of files that are at most 20MB works best. Scott