From owner-freebsd-questions@FreeBSD.ORG Sun Jul 10 16:43:55 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6EF71106566B for ; Sun, 10 Jul 2011 16:43:55 +0000 (UTC) (envelope-from cpghost@cordula.ws) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 31DA38FC12 for ; Sun, 10 Jul 2011 16:43:55 +0000 (UTC) Received: by mail-vw0-f54.google.com with SMTP id 18so3135628vws.13 for ; Sun, 10 Jul 2011 09:43:55 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.73.164 with SMTP id m4mr4645882vdv.157.1310316234136; Sun, 10 Jul 2011 09:43:54 -0700 (PDT) Received: by 10.220.167.197 with HTTP; Sun, 10 Jul 2011 09:43:54 -0700 (PDT) X-Originating-IP: [93.221.166.60] In-Reply-To: <20110708110005.GD34870@mech-cluster241.men.bris.ac.uk> References: <20110707224435.GA27624@mech-cluster241.men.bris.ac.uk> <20110708110005.GD34870@mech-cluster241.men.bris.ac.uk> Date: Sun, 10 Jul 2011 18:43:54 +0200 Message-ID: From: "C. P. Ghost" To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: tftp - bad checksum error? can't transfer file X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Jul 2011 16:43:55 -0000 On Fri, Jul 8, 2011 at 1:00 PM, Anton Shterenlikht wrote: >> I've had some trouble netbooting / jumpstaring recently with a similar >> pattern (using RARP/BOOTP/TFTP/NFS). It turned out to be a dying >> port on the switch whose errors were masked by TCP in day to day >> use, but alas were too frequent for UDP. > > I just have a direct ethernet connection > between my FreeBSD laptop with bootpd/tftpd > servers (one ethernet port only) and a node > which I want to boot (also a single ethernet > port). Is there way for me to check whether > either of these ports are "dying"? > Any further diagnostics I can do? Just push a lot of data (/dev/zero, /dev/urandom, ...) over this connection, via ssh or something like that, and monitor the error rates in "netstat -in" on both ends. Look at Ierrs, Idrop and Oerrs columns. If one of those ports are dying, or if your cable isn't properly shielded, you'll notice immediately. > Many thanks > Anton -cpghost. -- Cordula's Web. http://www.cordula.ws/