Bug #1842

Amahi Netboot for F21

Added by bigfoot65 over 6 years ago. Updated over 6 years ago.

Target version:
Start date:
Due date:
% Done:



There is a file missing which prevents amahi-netboot from working correctly.

In F19, xinetd was installed by default in the OS. Along with that, there was a file in /etc/xinetd.d/tftp:

# default: off
# description: The tftp server serves files using the trivial file transfer \
#       protocol.  The tftp protocol is often used to boot diskless \
#       workstations, download configuration files to network-aware printers, \
#       and to start the installation process for some operating systems.
service tftp
        socket_type             = dgram
        protocol                = udp
        wait                    = yes
        user                    = root
        server                  = /usr/sbin/in.tftpd
        server_args             = -s /var/lib/tftpboot
        disable = no
        per_source              = 11
        cps                     = 100 2
        flags                   = IPv4

In F21, xinetd is not installed by default in the OS. It now a dependency of amahi-netboot, but that does not solve the problem. The /etc/xinetd.d/tftp file is absent in F21 install of xinetd for some reason. May be an OS bug.

To test the theory, I manually installed /etc/xinetd.d/tftp file after amahi-netboot was installed. Next I installed Clonezilla and using another client performed a network boot to the software. Upon selecting Easy option in Clonezilla, the app loaded and performed as designed.

Recommend we add /etc/xinetd.d/tftp and it's contents to the amahi-netboot app. Once done and tested, this bug can be closed.


#1 Updated by bigfoot65 over 6 years ago

  • Status changed from Assigned to Feedback

Added the file to the Amahi netboot application. It will remove itself upon application uninstall.

Testing now and will report results.

#2 Updated by bigfoot65 over 6 years ago

Tested netboot with Clonezilla. For some reason, it's not working. When trying to netboot from my laptop, it does not find the DHCP server and exits to the local OS installed on the machine.

Verified files match what Fedora 19 used.

Does amahi-netboot need more current syslinux files? They appear to be the same as the Fedora 19 version in size.

All other config files appear to match what worked in Fedora 19.

#3 Updated by cpg over 6 years ago

"does not work" is not debuggable :-)

describe the error, maybe find some log files with details or something.

#4 Updated by bigfoot65 over 6 years ago

What I meant was when I network boot my laptop, it starts looking for DHCP. Then it times out.

There are no logs to view for the client obviously. I did check for logs on the server but did not see any for xinetd or tftp.

I will keep looking around in case they are in an odd place.

#5 Updated by bigfoot65 over 6 years ago

The error on the laptop says "No boot filename received".

That comes after it tries to assign a DHCP address and fails I believe. It works fine for me on Fedora 19 so I don't understand what is missing.

#6 Updated by cpg over 6 years ago

so far, i see /etc/xinetd.d/tftp.rpmsave which is not a good sign, but it may be because my installation was not 100% clean.

it could be that this file (/etc/xinetd.d/tftp.dgram is the proper name) is not created properly by either our rpms or the app.

i think xinet is still picking up that file despite the unconventional name, but i did not get to test yet.

#7 Updated by cpg over 6 years ago

please look for errors in /var/log/messages or better: journalctl -xu xinetd.service

#8 Updated by bigfoot65 over 6 years ago

Think I found the problem.

The following line is commented out in /etc/dnsmasq.conf:


Once I uncommented that line, it got to the PXE boot menu. Still having problems with Clonezilla working, but that is likely another issue. Investigating it now.

It appears dnsmasq.conf in Fedora 21 is a little different than Fedora 19.

As for the journal of xinet.service I see the following error:

unexpected signal: 18 (Continued) in signal pipe

Not sure what that means.

#9 Updated by bigfoot65 over 6 years ago

BTW, the signal error was before I made the change to dnsmasq.conf. It does not appear to have occurred since.

#10 Updated by cpg over 6 years ago

see the bottom lines for conf-dir

# Include all files in /etc/dnsmasq.d except RPM backup files

so, the dnsmasq files are read (otherwise, no Amahi settings would work!)

#11 Updated by bigfoot65 over 6 years ago

That makes sense. Guess I didn't understand that line, but now I do.

Maybe it's my laptop client that is the problem here. It's running Windows 10.

I will try a different client and see how things work.

Also available in: Atom