Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 14 Aug 2000 13:20:58 +0200
From:      Francesco Casadei <fcasadei@inwind.it>
To:        freebsd-stable mailing list <freebsd-stable@freebsd.org>
Subject:   tftpd broken?
Message-ID:  <20000814132058.A2789@goku.kasby>

next in thread | raw e-mail | index | archive | help
   I'm trying to boot an old 486 DX2-50 from network using etherboot,
BOOTP and TFTP.

Here's what I see on the 486:

Loading ROM image....
ROM segment 0x1000 length 0x4000 reloc 0x9800
Boot from (N)etwork or from (L)ocal? N
Etherboot/32 version 4.6.1 (GPL) for [NE*000]
Probing...[NE*000]
NE1000 base 0x0300, addr 00:00:02:02:67:67
Searching for server (BOOTP)...
Me: 192.168.0.2, Server: 192.168.0.1, Gateway 192.168.0.1
Loading /kernel.gohan <sleep>
<sleep>
<sleep>
...etc etc

   I suppose that etherboot is ok since the bootstrap and NIC probe
work. I have an Artisoft RoadRunner 2000/SI (without BOOTROM, I'm
using a floppy image) with the following settings: I/O base 0x300,
IRQ 15, Mode NE-2000, IOCS16 Normal.

   I suppose too that bootpd is porperly configured since the client
gets his IP and the server IP. Here's the output of tcpdump:

tcpdump: listening on ed0
12:46:18.771661 0.0.0.0.0 > 255.255.255.255.bootps:  (request)
xid:0xec50c00 [|bootp]
12:46:18.772239 goku.bootps > gohan.bootpc:  xid:0xec50c00 Y:gohan
S:goku sname "goku.kasby"[|bootp]
12:46:18.777329 arp who-has goku tell gohan
12:46:18.777386 arp reply goku is-at 0:c0:26:f1:d5:80

   I think that tftpd is broken or not properly configured. The 486
hangs while loading the kernel with tftp. Here's what tcpdump says:

12:46:18.777837 gohan.wizard > goku.tftp:  35 RRQ "/kernel.gohan"
12:46:18.777904 goku > gohan: icmp: goku udp port tftp unreachable

   At the root console I receive the following message:

Aug 14 12:42:08 goku inetd[117]: tftp/udp server failing (looping),
service terminated
Aug 14 12:42:08 goku inetd[117]: tftp/udp server failing (looping),
service terminated

   Seems like the client connect to the tftp server and the server
dies, then the client reconnect and the server dies and so on...until
inetd terminate the tftp service.
   Here's the relevant lines in inetd.conf:

tftp  dgram  udp  wait  nobody  /usr/libexec/tftpd  tftpd  /tftpboot
bootps  dgram  udp  wait  root  /usr/libexec/bootpd  bootpd -t 2

   I've tried to start the tftp server manually and here's what I
got:

root> /usr/libexec/tftpd /tftpboot
Aug 14 13:16:51 goku tftpd[2821]: recvfrom: Socket operation on
non-socket
Aug 14 13:16:51 goku tftpd[2821]: recvfrom: Socket operation on
non-socket

   tftpd simpy don't want to start! What's wrong?


		Francesco Casadei


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000814132058.A2789>