AW: AW: PXE boot with UEFI

[Frank Morawietz]

> To clarify, this client can successfully tftp the pxelinux.0 file over
> when configured for legacy BIOS mode?

Yes, exactly. This works.

> This looks suspiciously like a config problem on the server
> (firewall?).

The client is connected via direct cross link TP cable to the server and the firewall is configured to accept anything from that interface.
To eliminate mistakes in the firewall configuration or bugs, I also tried with the firewall stopped. Same result on the client.

Corresponding complete log on server during this time:

Dec  5 14:21:06 sysadm02 systemd[1]: Stopping nftables...
Dec  5 14:21:06 sysadm02 systemd[1]: Stopped nftables.
Dec  5 14:22:23 sysadm02 dhcpd[12875]: DHCPDISCOVER from 50:9a:4c:43:c1:b7 via ens9
Dec  5 14:22:23 sysadm02 dhcpd[12875]: DHCPOFFER on 10.250.217.16 to 50:9a:4c:43:c1:b7 via ens9
Dec  5 14:22:27 sysadm02 dhcpd[12875]: DHCPREQUEST for 10.250.217.16 (10.250.217.102) from 50:9a:4c:43:c1:b7 via ens9
Dec  5 14:22:27 sysadm02 dhcpd[12875]: DHCPACK on 10.250.217.16 to 50:9a:4c:43:c1:b7 via ens9
Dec  5 14:22:27 sysadm02 in.tftpd[26988]: RRQ from 10.250.217.16 filename fai/syslinux64.efi
Dec  5 14:22:27 sysadm02 in.tftpd[26988]: tftp: client does not accept options
Dec  5 14:22:27 sysadm02 in.tftpd[26989]: RRQ from 10.250.217.16 filename fai/syslinux64.efi
Dec  5 14:22:49 sysadm02 systemd[1]: Starting nftables...
Dec  5 14:22:49 sysadm02 systemd[1]: Started nftables.

The connection refused message is missing, but it just ends after second try with syslinux64.efi .

With the firewall enabled again, it looks exactly the same:

Dec  5 14:22:49 sysadm02 systemd[1]: Starting nftables...
Dec  5 14:22:49 sysadm02 systemd[1]: Started nftables.
Dec  5 14:26:05 sysadm02 dhcpd[12875]: DHCPDISCOVER from 50:9a:4c:43:c1:b7 via ens9
Dec  5 14:26:05 sysadm02 dhcpd[12875]: DHCPOFFER on 10.250.217.16 to 50:9a:4c:43:c1:b7 via ens9
Dec  5 14:26:09 sysadm02 dhcpd[12875]: DHCPREQUEST for 10.250.217.16 (10.250.217.102) from 50:9a:4c:43:c1:b7 via ens9
Dec  5 14:26:09 sysadm02 dhcpd[12875]: DHCPACK on 10.250.217.16 to 50:9a:4c:43:c1:b7 via ens9
Dec  5 14:26:09 sysadm02 in.tftpd[27017]: RRQ from 10.250.217.16 filename fai/syslinux64.efi
Dec  5 14:26:09 sysadm02 in.tftpd[27017]: tftp: client does not accept options
Dec  5 14:26:09 sysadm02 in.tftpd[27018]: RRQ from 10.250.217.16 filename fai/syslinux64.efi

Connection refused seems to be gone. But PXE boot still does not work.
Note that the log is complete, no lines were omitted.

> You can troubleshoot the issue using a tftp client on one
> of your test boxes.

Nice idea! I booted the client into Knoppix, installed the  tftp-hpa  client and tested.
I could successfully get every single file from the server in /srv/tftp/fai/ .
Worked without any issue and on server side no refused nor any other error.

So it does not seem to be a problem with the tftp server, right?

Regards,
Frank
--
Frank Morawietz


This message and any attachment are confidential and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, you must not copy this message or attachment or disclose the contents to any other person. If you have received this transmission in error, please notify the sender immediately and delete the message and any attachment from your system. Merck KGaA, Darmstadt, Germany and any of its subsidiaries do not accept liability for any omissions or errors in this message which may arise as a result of E-Mail-transmission or for damages resulting from any unauthorized changes of the content of this message and any attachment thereto. Merck KGaA, Darmstadt, Germany and any of its subsidiaries do not guarantee that this message is free of viruses and does not accept liability for any damages caused by any virus transmitted therewith.



Click http://www.merckgroup.com/disclaimer to access the German, French, Spanish and Portuguese versions of this disclaimer.