On 12/3/19 2:50 AM, Frank Morawietz wrote:
Many thanks Steffen and Merlin for your configuration details!
I learned a lot already and I believe that we are on the right track.
I included your suggestions into my dhpcd.conf .
According to the log output below it seems to select the correct file now.
But I still could not yet get it to work correctly.
In order to debug this I increased the tftpd verbosity level. And this is what
I now get in daemon.log when I try again:
Dec 3 11:31:34 sysadm02 dhcpd[12875]: DHCPDISCOVER from 50:9a:4c:43:c1:b7 via
ens9
Dec 3 11:31:34 sysadm02 dhcpd[12875]: DHCPOFFER on 10.250.217.16 to
50:9a:4c:43:c1:b7 via ens9
Dec 3 11:31:37 sysadm02 dhcpd[12875]: DHCPREQUEST for 10.250.217.16
(10.250.217.102) from 50:9a:4c:43:c1:b7 via ens9
Dec 3 11:31:37 sysadm02 dhcpd[12875]: DHCPACK on 10.250.217.16 to
50:9a:4c:43:c1:b7 via ens9
Dec 3 11:31:37 sysadm02 in.tftpd[13050]: RRQ from 10.250.217.16 filename
fai/syslinux64.efi
Dec 3 11:31:37 sysadm02 in.tftpd[13050]: tftpd: read: Connection refused
Dec 3 11:31:41 sysadm02 in.tftpd[13052]: RRQ from 10.250.217.16 filename
fai/syslinux64.efi
Dec 3 11:31:41 sysadm02 in.tftpd[13052]: tftp: client does not accept options
Dec 3 11:31:41 sysadm02 in.tftpd[13053]: RRQ from 10.250.217.16 filename
fai/syslinux64.efi
10.250.217.16 is the installation client.
Any idea which read failed for tftpd ?
The syslinux files all are mode 644, so they are readable. Directories are 755.
What may refuse the connection for tftpd?
The "client does not accept options" does not express a problem. This message
also appears when the install boot is successful (in legacy BIOS mode).
To clarify, this client can successfully tftp the pxelinux.0 file over
when configured for legacy BIOS mode?
I agree that the "client does not accept options" message is not an
issue as I see this also as part of the tftp connection negotiations.
I also confirmed that my files are 644 and owned by root so that is not
the issue.
This looks suspiciously like a config problem on the server
(firewall?). You can troubleshoot the issue using a tftp client on one
of your test boxes.
- install a tftp client if you do not have one already
- > tftp (to start the client from the terminal/command prompt)
- > ? (to list help)
- > connect server.name
- > verbose (to give more detailed output)
- > get fai/syslinux64.efi
this should get the file successfully. If it does not then you can look
at the logging on both sides. Also, if it does not then try "get
fai/pxelinux.0", which is the BIOS boot file and was working for you.
Not an answer but I hope this helps.
Cheers,
Merlin.
--
Merlin Hansen
Department of Computing Science
Vancouver Island University
900 Fifth Street
Nanaimo BC V9R 5S5
250-753-3245 x 2321
t...@csci.viu.ca
