Date: Sun, 10 Jul 2011 18:43:54 +0200 From: "C. P. Ghost" <cpghost@cordula.ws> To: freebsd-questions@freebsd.org Subject: Re: tftp - bad checksum error? can't transfer file Message-ID: <CADGWnjWXbtYeOYAdBuZ9D5xThjBnjDCPJqfqY%2BRbbU_JiEvFHQ@mail.gmail.com> In-Reply-To: <20110708110005.GD34870@mech-cluster241.men.bris.ac.uk> References: <20110707224435.GA27624@mech-cluster241.men.bris.ac.uk> <CADGWnjXwK=OrKCtYPSi=ziGZ5ZKEeSsPb=_MrtbSmQTBro9nyw@mail.gmail.com> <20110708110005.GD34870@mech-cluster241.men.bris.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jul 8, 2011 at 1:00 PM, Anton Shterenlikht <mexas@bristol.ac.uk> 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/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADGWnjWXbtYeOYAdBuZ9D5xThjBnjDCPJqfqY%2BRbbU_JiEvFHQ>