tftp - bad checksum error? can't transfer file
mexas at bristol.ac.uk
Fri Jul 8 11:00:51 UTC 2011
On Fri, Jul 08, 2011 at 12:05:37PM +0200, C. P. Ghost wrote:
> On Fri, Jul 8, 2011 at 12:44 AM, Anton Shterenlikht <mexas at bristol.ac.uk> wrote:
> > I'm trying to troubleshoot tftpd(8).
> > ? ?192.168.232.10.15388 > buzi.tftp: [no cksum] ?25 RRQ "/bsd.rd.IP32" octet (
> > o
> > 23:25:21.024160 IP (tos 0x0, ttl 64, id 56, offset 0, flags [none], proto UDP (1
> > 7), length 30, bad cksum 0 (->293a)!)
> > ? ?buzi.19330 > 192.168.232.10.15388: [udp sum ok] UDP, length 2
> > 23:25:51.013759 IP (tos 0x0, ttl 255, id 256, offset 0, flags [none], proto UDP
> > (17), length 53)
> 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?
Room 2.6, Queen's Building
Mech Eng Dept
University Walk, Bristol BS8 1TR, UK
Tel: +44 (0)117 331 5944
Fax: +44 (0)117 929 4423
More information about the freebsd-questions