TFTP client timed out

Support
#1

Foreman is installed on virtual machine in oVirt, operating system CentOS 7.
I am creating a new host, I choose the created operating system and run virtual machine.
VM gets ip from dhcp server, download pxelinux.0 file in /var/lib/tftpboot, but then the following happens(screen)

%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202019-07-02%2018-00-56
Снимок экрана от 2019-07-02 18-00-56.png719×401 7.35 KB

pxelinux.cfg/{mac}:

Blockquote

This file was deployed via ‘Kickstart default PXELinux’ template

DEFAULT menu
MENU TITLE Booting into OS installer (ESC to stop)
TIMEOUT 100
ONTIMEOUT installer

LABEL installer
MENU LABEL Kickstart default PXELinux
KERNEL boot/centos-mirror-qVbSBrznIWMc-vmlinuz
APPEND initrd=boot/centos-mirror-qVbSBrznIWMc-initrd.img ks=http://foreman.dc.rk/unattended/provision?token=64ac896a-33fb-43a2-addf-c54b0c9d0105 network ksdevice=bootif ks.device=bootif BOOTIF=00-00-02-01-00-00-d8 kssendmac ks.sendmac inst.ks.sendmac
IPAPPEND 2

tcpdump: https://pastebin.com/VNwagyQa

Can you help me? Thanks

#2

/var/log/message:

Jul 2 18:08:37 foreman in.tftpd[22241]: RRQ from 172.17.10.83 filename pxelinux.cfg/01-00-02-01-00-00-d8 [259/1995]
Jul 2 18:08:37 foreman in.tftpd[22242]: RRQ from 172.17.10.83 filename pxelinux.cfg/01-00-02-01-00-00-d8
Jul 2 18:08:37 foreman in.tftpd[22243]: RRQ from 172.17.10.83 filename pxelinux.cfg/01-00-02-01-00-00-d8
Jul 2 18:08:37 foreman in.tftpd[22244]: RRQ from 172.17.10.83 filename pxelinux.cfg/01-00-02-01-00-00-d8
Jul 2 18:08:37 foreman in.tftpd[22245]: RRQ from 172.17.10.83 filename pxelinux.cfg/01-00-02-01-00-00-d8
Jul 2 18:08:37 foreman in.tftpd[22246]: RRQ from 172.17.10.83 filename pxelinux.cfg/01-00-02-01-00-00-d8
Jul 2 18:08:38 foreman in.tftpd[22247]: RRQ from 172.17.10.83 filename pxelinux.cfg/01-00-02-01-00-00-d8
Jul 2 18:08:38 foreman in.tftpd[22248]: RRQ from 172.17.10.83 filename pxelinux.cfg/01-00-02-01-00-00-d8
Jul 2 18:08:38 foreman in.tftpd[22249]: RRQ from 172.17.10.83 filename pxelinux.cfg/01-00-02-01-00-00-d8
Jul 2 18:08:39 foreman in.tftpd[22250]: RRQ from 172.17.10.83 filename pxelinux.cfg/01-00-02-01-00-00-d8
Jul 2 18:08:39 foreman in.tftpd[22251]: RRQ from 172.17.10.83 filename pxelinux.cfg/01-00-02-01-00-00-d8
Jul 2 18:08:40 foreman in.tftpd[22252]: RRQ from 172.17.10.83 filename pxelinux.cfg/01-00-02-01-00-00-d8
Jul 2 18:08:41 foreman in.tftpd[22255]: RRQ from 172.17.10.83 filename pxelinux.cfg/01-00-02-01-00-00-d8
Jul 2 18:08:42 foreman in.tftpd[22256]: RRQ from 172.17.10.83 filename pxelinux.cfg/01-00-02-01-00-00-d8
Jul 2 18:08:43 foreman in.tftpd[22241]: Client 172.17.10.83 timed out
Jul 2 18:08:43 foreman in.tftpd[22242]: Client 172.17.10.83 timed out
Jul 2 18:08:43 foreman in.tftpd[22243]: Client 172.17.10.83 timed out
Jul 2 18:08:43 foreman in.tftpd[22244]: Client 172.17.10.83 timed out
Jul 2 18:08:43 foreman in.tftpd[22257]: RRQ from 172.17.10.83 filename pxelinux.cfg/01-00-02-01-00-00-d8
Jul 2 18:08:43 foreman in.tftpd[22245]: Client 172.17.10.83 timed out
Jul 2 18:08:43 foreman in.tftpd[22246]: Client 172.17.10.83 timed out
Jul 2 18:08:44 foreman in.tftpd[22247]: Client 172.17.10.83 timed out
Jul 2 18:08:44 foreman in.tftpd[22248]: Client 172.17.10.83 timed out
Jul 2 18:08:44 foreman in.tftpd[22249]: Client 172.17.10.83 timed out
Jul 2 18:08:45 foreman in.tftpd[22258]: RRQ from 172.17.10.83 filename pxelinux.cfg/01-00-02-01-00-00-d8
Jul 2 18:08:45 foreman in.tftpd[22250]: Client 172.17.10.83 timed out
Jul 2 18:08:45 foreman in.tftpd[22251]: Client 172.17.10.83 timed out
Jul 2 18:08:46 foreman in.tftpd[22252]: Client 172.17.10.83 timed out
Jul 2 18:08:46 foreman in.tftpd[22261]: RRQ from 172.17.10.83 filename pxelinux.cfg/01-00-02-01-00-00-d8
Jul 2 18:08:47 foreman in.tftpd[22255]: Client 172.17.10.83 timed out
Jul 2 18:08:48 foreman in.tftpd[22256]: Client 172.17.10.83 timed out
Jul 2 18:08:48 foreman in.tftpd[22262]: RRQ from 172.17.10.83 filename pxelinux.cfg/01-00-02-01-00-00-d8
Jul 2 18:08:49 foreman in.tftpd[22257]: Client 172.17.10.83 timed out
Jul 2 18:08:51 foreman in.tftpd[22258]: Client 172.17.10.83 timed out

#3

auto provision working in foreman subnet(172.17.0.0/24), but in other subnet(172.17.10.0/24) is not working. With what it can be connected?

#4

If i enter in iPXE CLI(Ctrl+B) and manual booting i get the following:

%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202019-07-10%2012-05-22
Снимок экрана от 2019-07-10 12-05-22.png721×398 4.63 KB

%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202019-07-10%2012-06-36
%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202019-07-10%2012-07-29
%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202019-07-10%2012-07-47
Снимок экрана от 2019-07-10 12-07-47.png715×393 6.92 KB

Why autoprovision not download this pxelinux.cfg files?

#5

Hey, TFTP is a UDP based protocol and it’s stateless therefore you need to open up your firewall properly. Also if there is a NAT you need a special module to have that working.

And I don’t understand the iPXE problem then.