I am doing yet another variation on diskless clients using Red Hat 9, tftp-hpa
0.34, and pxelinux. The client's Ethernet card is Intel 1000/100/10.
My clients are booting OK, except that some new traffic has been occurring.
Here is what gets logged on the server:
Feb 25 00:34:20 localhost dhcpd: DHCPACK on 192.168.1.101 to 00:07:e9:0f:e9:d3
via eth0
Feb 25 08:34:20 localhost in.tftpd[4499]: tftp: client does not accept options
Feb 25 08:34:44 localhost in.tftpd[4510]: tftpd: read: Connection refused
Feb 25 08:34:45 localhost in.tftpd[4511]: tftpd: read: Connection refused
Feb 25 00:34:48 localhost rpc.mountd: authenticated mount request from
192.168.1.101:640 for /tftpboot/common_files/redhat/usr
(/tftpboot/common_files)
<additional nfs mounts omitted to save space here in this post>
Feb 25 08:34:56 localhost in.tftpd[4504]: tftpd: read: Connection refused
Feb 25 08:34:57 localhost in.tftpd[4506]: tftpd: read: Connection refused
I know about the "client does not accept options" business, but I was
not
getting the "Connection refused" warnings before and I am trying to
understand just who could be trying to read what over tftp at this point in
the boot process.
Any suggestions as to what this might be? I suppose that I could play with the
tftp-hpa source code to provide more information. I'm sorry if this is a
stupid question.
Thanks for all help
James
