The first important thing to know is that Fedora uses the directory /var/lib/tftpboot rather than the old and venerable /tftpboot. This should be invisible to clients, but rarpd needs to be informed.
The Sun 3/280 gets its IP address from rarpd, then converts it into
a filename that it tries to fetch via tftp.
In our case that filename is C0A8001E (for 192.168.0.30).
You stop and start tftpd using:
systemctl status tftp.service systemctl stop tftp.serviceWhen I stop it, I get the warning:
Stopping 'tftp.service', but its triggering units are still active: tftp.socketI give it some file (any file) in the following way:
cd /var/lib/tftpboot cp /etc/hosts C0A8001ESo far the Sun has been unable to get this file via tftp, although wireshark shows me the requests asking for it. Wireshark sees broadcast requests aimed at port 69.
I see the following running before I stop the service:
ps -alx | grep tftp 4 0 187297 1 20 0 2836 1788 do_sel Ss ? 0:00 /usr/sbin/in.tftpd -s /var/lib/tftpbootI try running it by hand to see if I can get it to be verbose and give me more information:
cd /usr/sbin ./in.tftpd -L -v -vNot matter what I do, tftpd will not stay running in the foreground giving me information.
May 16 18:18:13 trona systemd[1]: Started tftp.service - Tftp Server. May 16 18:18:14 trona in.tftpd[193249]: connect: Invalid argument May 16 18:19:17 trona in.tftpd[193303]: connect: Invalid argument May 16 18:19:17 trona in.tftpd[193304]: connect: Invalid argument May 16 18:20:21 trona in.tftpd[193350]: connect: Invalid argument May 16 18:21:25 trona in.tftpd[193390]: connect: Invalid argument May 16 18:22:29 trona in.tftpd[193434]: connect: Invalid argument May 16 18:23:33 trona in.tftpd[193474]: var/lib/tftpboot: No such file or directoryJust for starters, why has it stripped the leading "/" from the directory path?
I did launch a special rarpd with the "-e" switch by hand, and I will need to find a way to get that into the Fedora service scripts.
Tom's Computer Info / tom@mmto.org