Date: Thu, 01 Jun 2006 10:14:26 -0600 From: Scott Long <scottl@samsco.org> To: Danny Braniss <danny@cs.huji.ac.il> Cc: freebsd-hackers@freebsd.org Subject: Re: iSCSI/sendto(...) Message-ID: <447F1262.6020805@samsco.org> In-Reply-To: <E1Fll7X-0008Fd-8P@cs1.cs.huji.ac.il> References: <E1Fll7X-0008Fd-8P@cs1.cs.huji.ac.il>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?447F1262.6020805>