> have you considered tcp wrappers ? Thanks for your input.
In my opinion, installation in legacy mode shouldn't work either if something like tcp wrappers or a firewall would hinder the installation in UEFI mode. IP addresses and ports would be the same. Some additional information: I picked the boot files from the local syslinux installation: - /usr/lib/syslinux/modules/efi32/syslinux.c32 --> syslinux32.efi - /usr/lib/syslinux/modules/efi64/syslinux.c32 --> syslinux64.efi - /usr/lib/syslinux/modules/bios/ldlinux.c32 --> ldlinux.c32 - /usr/lib/syslinux/modules/efi32/ldlinux.e32 --> ldlinux.e32 - /usr/lib/syslinux/modules/efi64/ldlinux.e64 --> ldlinux.e64 All boot files are in /srv/tftp/fai/ , with modified names where necessary. In comparison, the DHCP + TFTP logs of a working installation in legacy BIOS mode look like this: Dec 3 14:38:44 sysadm02 dhcpd[12875]: DHCPDISCOVER from 50:9a:4c:43:c1:b7 via ens9 Dec 3 14:38:44 sysadm02 dhcpd[12875]: DHCPOFFER on 10.250.217.16 to 50:9a:4c:43:c1:b7 via ens9 Dec 3 14:38:48 sysadm02 dhcpd[12875]: DHCPREQUEST for 10.250.217.16 (10.250.217.102) from 50:9a:4c:43:c1:b7 via ens9 Dec 3 14:38:48 sysadm02 dhcpd[12875]: DHCPACK on 10.250.217.16 to 50:9a:4c:43:c1:b7 via ens9 Dec 3 14:38:48 sysadm02 in.tftpd[14209]: RRQ from 10.250.217.16 filename fai/pxelinux.0 Dec 3 14:38:48 sysadm02 in.tftpd[14209]: tftp: client does not accept options Dec 3 14:38:48 sysadm02 in.tftpd[14210]: RRQ from 10.250.217.16 filename fai/pxelinux.0 Dec 3 14:38:48 sysadm02 in.tftpd[14211]: RRQ from 10.250.217.16 filename fai/ldlinux.c32 Dec 3 14:38:48 sysadm02 in.tftpd[14212]: RRQ from 10.250.217.16 filename fai/pxelinux.cfg/44454c4c-3200-1056-8052-c 3c04f314c32 Dec 3 14:38:48 sysadm02 in.tftpd[14212]: sending NAK (1, File not found) to 10.250.217.16 Dec 3 14:38:48 sysadm02 in.tftpd[14213]: RRQ from 10.250.217.16 filename fai/pxelinux.cfg/01-50-9a-4c-43-c1-b7 Dec 3 14:38:48 sysadm02 in.tftpd[14213]: sending NAK (1, File not found) to 10.250.217.16 Dec 3 14:38:48 sysadm02 in.tftpd[14214]: RRQ from 10.250.217.16 filename fai/pxelinux.cfg/0AFAD910 Dec 3 14:38:48 sysadm02 in.tftpd[14215]: RRQ from 10.250.217.16 filename fai/vmlinuz-4.9.0-9-amd64 Dec 3 14:38:49 sysadm02 in.tftpd[14216]: RRQ from 10.250.217.16 filename fai/initrd.img-4.9.0-9-amd64 So it looks like the UEFI tftp connection refused error happened where ldlinux should be transferred. Is there anything else I could examine to diagnose further? 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.
