Problem accessing the Wapt server on the client side

[Regis]

Hello,

I'm testing a Windows deployment via WAPT on a VirtualBox 7.2.4 environment.

As a reminder, I installed WAPT version 2.6 on Rocky 10.

I configured the DHCP server; here is the dhcpd.conf file:

..............................................................................................................................................................................

subnet 172.16.1.0 netmask 255.255.255.0 {
range 172.16.1.120 172.16.1.180;
option routers 0.0.0.0;
option subnet-mask 255.255.255.0;
option broadcast-address 172.16.1.255;
next-server 172.16.1.100; # TFTP server
# If not iPXE
if not exists user-class {
# If legacy BIOS
if (option vendor-class-identifier = "PXEClient:Arch:00000") {
filename "boot/pxeboot.n12";
} else {
filename "efi/boot/bootmgfw.efi";
}
}
# If iPXE
else if option user-class = "iPXE" {
# If legacy BIOS
if (option vendor-class-identifier = "PXEClient:Arch:00000") {
filename "http://172.16.1.100/api/v3/baseipxe?uef ... &keymap=fr";
} else {
filename "http://172.16.1.100/api/v3/baseipxe?keymap=fr";
}
}
..............................................................................................................................................................................

Testing this command on the client side works fine:

...............................................................................................................................................................................
cd ~
tftp 172.16.1.100;
binary
get snponly.efi
quit
ls -l snponly.efi
..............................................................................................................................................................................

When I then test the Windows deployment after adding the Windows ISO and an answer file, I find that the rest doesn't work. The client correctly obtains an IP address, but it stops at the TFTP connection
with error messages:

.......................... .................................................................................................................................
client mac addr: 08 00 27 5c b2 0c ..................
client ip: 172.16.1.140 mask: 255.255.255.0 dhcp ip: 172.16.1.110
TFTP
pxe-t01: file not found
pxe-e3b: tftp error - file not found
pxe-m0f:Exiting Intel pxe rom
..................................................................................................................................................................

I can get an IP address, but the TFTP connection is stuck; I don't understand why.

I'm wondering what I'm missing, whether I enable UEFI or not in the client-side BIOS.


Thanks in advance for your help.

[sfonteneau]

Hello,

the last time I tested with VirtualBox the tests were inconclusive:

In fact, VirtualBox includes its own IPXE https://ipxe.org/err/3c0920

But only in this IPXE provided by VirtualBox, HTTP booting has been disabled (I don't know why...).

So you end up directly at:

`if option user-class = "iPXE" {
http://172.16.1.100/api/v3/baseipxe?keymap=fr"`.

But this doesn't work because HTTP boot is disabled... (thanks VirtualBox).

One solution is to do something similar to fog and compile your own IPXE with:

`/opt/wapt/waptserver

. Then, in your DHCP configuration, set `

filename "snponly_custom.efi";`

instead of `file http:

`filename "http://172.16.1.100/api/v3/baseipxe?uef ... &keymap=fr";`.


I'll test it here to see if it works.


Otherwise, you can boot without IPXE:

simply specify

`efi/boot/bootmgfw.efi`

as the filename.

[Regis]

Hello,

I ran the command:

/opt/wapt/waptserver/scripts/compile_ipxe.sh I got:
.......................................................................................................................................................................................................

install git gcc gcc-c++ make zlib-devel binutils-devel xz-devel
custom ipxe
compile legacy ipxe
compile uefi ipxe
compile snponly.efi
..........................................................................................................................................................................................

And when in /etc/dhcpd.conf I add or remove:
..................................................................................................................................................................................................

If iPXE
else if option user-class = "iPXE" {
If legacy BIOS
if (option vendor-class-identifier = "PXEClient:Arch:00000") {
filename "undionly_custom.kpxe";
} else {
filename "ipxe_custom.efi";
.
;

,

no files are loading. I don't understand it at all

Sincerely

[Regis]

When I test TFTP, it takes too long. I wonder if the problem is there:

tftp wapt.iplesp.upmc.fr
tftp> binary
tftp> get bootmgfw.efi
Transfer timed out.

When I test the TFTP server status:

systemctl status wapttftpserver
● wapttftpserver.service - WAPT/WADS TFTP Server startup script
Loaded: loaded (/usr/lib/systemd/system/wapttftpserver.service; enabled; preset: disabled)
Active: active (running) since Wed 2026-03-04 16:53:53 CET; 4 min 33 s ago
.....................................................................................................................................................................

Mar 04 16:53:53 srvwapt3 waptserver[2108]: 20260304 15535335 ! info tftp server running on 0.0.0.0:69 serving files in /var/www/wads/pxe

..............................................................................................................................................................................

When I run `ls -al /var/www/wads/pxe`, it fails even though the files are in /var/www/html/wads/pxe.

It's very unclear and difficult to understand.

[sfonteneau]

Like this?

Code: Select all

tftp 127.0.0.1
tftp>  binary
tftp> get efi/boot/bootmgfw.efi
tftp> quit

[Regis]

Even when running:

tftp 127.0.0.1
tftp> binary
tftp> get efi/boot/bootmgfw.efi
tftp> quit,

it takes a very, very long time, which isn't normal. And the command:
ss -tulnp gives:

udp UNCONN 8448 0 0.0.0.0:69 0.0.0.0:* users:(("wapttftpserver.",pid=256906,fd=3))

The port isn't listening, which is strange.

[sfonteneau]

There have been issues with older versions of wapt on wapttftpserver.

Can you tell us your (full) version?

[Regis]

Adding Tranquil IT repository:

`cat > /etc/yum.repos.d/wapt.repo <
[wapt]
name=WAPT Server Repo
baseurl=https://wapt.tranquil.it/redhat10/wapt-2.6/
enabled=1
gpgcheck=1
EOF`

So I installed version wapt-2.6

[sfonteneau]

What gives?

cat /opt/wapt/version-full

[Regis]

The result is:

2.6.1.17705-092e11fc