• Problems with tftp & tftpd on Ubuntu 22, upgraded from 18

    From Java Jive@21:1/5 to All on Fri May 16 13:03:13 2025
    XPost: alt.os.linux

    As per title, I can get neither tftp or tftpd - at least I think
    neither but it's difficult to be sure - to work under Ubuntu 22. After
    some initial difficulties, I decided to uninstall and reinstall. Upon reinstallation, I received a warning that the file '/etc/inetd.conf' did
    not exist so I uninstalled them both again, 'touch'ed to create an empty '/etc/inetd.conf', and then reinstalled again, this time without undue warnings. The two config files now read as follows ...

    user@Computer:/home$ cat /etc/inetd.conf
    tftp dgram udp wait nobody /usr/sbin/tcpd /usr/sbin/in.tftpd /srv/tftp

    user@Computer:/home$ cat /etc/xinetd.d/tftp
    service tftp
    {
    protocol = udp
    port = 69
    socket_type = dgram
    wait = yes
    user = nobody
    server = /usr/sbin/in.tftpd
    server_args = /home/tftpboot
    disable = no
    }

    ... and, to be sure the firewall isn't the problem, ...

    user@Computer:/home$ sudo ufw status
    Status: inactive

    ... then ...

    user@Computer:/home$ sudo service xinetd restart

    ... and syslog looks alright to my eyes at least ...

    user@Computer:/home$ tail -50 /var/log/syslog
    [...]
    May 16 11:37:41 Computer systemd[1]: Stopping LSB: Starts or stops the
    xinetd daemon....
    May 16 11:37:41 Computer xinetd[1925]: * Stopping internet superserver
    xinetd
    May 16 11:37:41 Computer xinetd[1909]: Exiting...
    May 16 11:37:41 Computer xinetd[1925]: ...done.
    May 16 11:37:41 Computer systemd[1]: xinetd.service: Deactivated
    successfully.
    May 16 11:37:41 Computer systemd[1]: Stopped LSB: Starts or stops the
    xinetd daemon..
    May 16 11:37:41 Computer systemd[1]: Starting LSB: Starts or stops the
    xinetd daemon....
    May 16 11:37:41 Computer xinetd[1933]: * Starting internet superserver
    xinetd
    May 16 11:37:41 Computer xinetd[1933]: ...done.
    May 16 11:37:41 Computer systemd[1]: Started LSB: Starts or stops the
    xinetd daemon..
    May 16 11:37:42 Computer xinetd[1945]: Reading included configuration
    file: /etc/xinetd.d/chargen [file=/etc/xinetd.conf] [line=14]
    May 16 11:37:42 Computer xinetd[1945]: Reading included configuration
    file: /etc/xinetd.d/chargen-udp [file=/etc/xinetd.d/chargen-udp] [line=28]
    May 16 11:37:42 Computer xinetd[1945]: Reading included configuration
    file: /etc/xinetd.d/daytime [file=/etc/xinetd.d/daytime] [line=14]
    May 16 11:37:42 Computer xinetd[1945]: Reading included configuration
    file: /etc/xinetd.d/daytime-udp [file=/etc/xinetd.d/daytime-udp] [line=26]
    May 16 11:37:42 Computer xinetd[1945]: Reading included configuration
    file: /etc/xinetd.d/discard [file=/etc/xinetd.d/discard] [line=14]
    May 16 11:37:42 Computer xinetd[1945]: Reading included configuration
    file: /etc/xinetd.d/discard-udp [file=/etc/xinetd.d/discard-udp] [line=25]
    May 16 11:37:42 Computer xinetd[1945]: Reading included configuration
    file: /etc/xinetd.d/echo [file=/etc/xinetd.d/echo] [line=14]
    May 16 11:37:42 Computer xinetd[1945]: Reading included configuration
    file: /etc/xinetd.d/echo-udp [file=/etc/xinetd.d/echo-udp] [line=26]
    May 16 11:37:42 Computer xinetd[1945]: Reading included configuration
    file: /etc/xinetd.d/servers [file=/etc/xinetd.d/servers] [line=14]
    May 16 11:37:42 Computer xinetd[1945]: Reading included configuration
    file: /etc/xinetd.d/services [file=/etc/xinetd.d/services] [line=13]
    May 16 11:37:42 Computer xinetd[1945]: Reading included configuration
    file: /etc/xinetd.d/tftp [file=/etc/xinetd.d/tftp] [line=13]
    May 16 11:37:42 Computer xinetd[1945]: Reading included configuration
    file: /etc/xinetd.d/time [file=/etc/xinetd.d/time] [line=11]
    May 16 11:37:42 Computer xinetd[1945]: Reading included configuration
    file: /etc/xinetd.d/time-udp [file=/etc/xinetd.d/time-udp] [line=28]
    May 16 11:37:42 Computer xinetd[1945]: added service tftp [file=/etc/inetd.conf] [line=1]
    May 16 11:37:42 Computer xinetd[1945]: 2.3.15.3 started with libwrap
    loadavg labeled-networking options compiled in.
    May 16 11:37:42 Computer xinetd[1945]: Started working: 2 available services

    ... but no listener is found on port 69 ...

    user@Computer:/home$ netstat -na | grep LIST | grep 69
    unix 2 [ ACC ] STREAM LISTENING 9169 /var/run/samba/nmbd/unexpected

    ... and generally there is no evidence of any tftp service actually
    running, for example ...

    user@Computer:/home$ ps -aux | grep -v grep | grep tftp
    user@Computer:/home$ systemctl list-units --no-pager | grep tftp user@Computer:/home$ sudo service --status-all | grep tftp

    ... all find nothing. Unsurprisingly therefore, when I try to set up a
    test, nothing works ...

    user@Computer:/home$ sudo echo "This is a TFTP test from $(hostname)" > /home/tftpboot/test.txt
    user@Computer:/home$ sudo chown nobody:nogroup /home/tftpboot/test.txt user@Computer:/home$ ll /home/tftpboot/test.txt
    -rw-r--r-- 1 nobody nogroup 36 2025-05-15 21:43 /home/tftpboot/test.txt user@Computer:/home$ cat /home/tftpboot/test.txt
    This is a TFTP test from Computer
    user@Computer:/home$ tftp localhost
    tftp> get test.txt
    tftp: test.txt: Permission denied
    tftp> q

    Using 127.0.0.1 instead of localhost suffers the same fate, as does an
    attempt to get a similar test text file from one of the Zyxel NSA221
    NASs, as does an attempt for a non-existent file or a non-existent
    server, so the error given could mean almost any type of failure and I
    don't know whether I have one problem with the client on the Ubuntu PC,
    or two problems with the service on each machine, PC and NAS, or all
    three. I was going to install the windows TFTP client to test with
    that, but for some reason or other that failed, and there's nothing in
    the event logs to suggest why, so for the moment I'm stuck.

    BTW, in case it's relevant, IPv6 is disabled on this PC:

    user@Computer:/home$ ip a
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
    group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
    valid_lft forever preferred_lft forever
    2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state
    UP group default qlen 1000
    link/ether ec:f4:bb:1f:5c:55 brd ff:ff:ff:ff:ff:ff
    altname enp0s25
    inet 192.168.1.[anonymised]/24 brd 192.168.1.255 scope global
    dynamic noprefixroute eno1
    valid_lft 81052sec preferred_lft 81052sec
    3: wlp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
    state DOWN group default qlen 1000
    link/ether ac:7b:a1:dd:6f:03 brd ff:ff:ff:ff:ff:ff

    Any helpful ideas?

    --

    Fake news kills!

    I may be contacted via the contact address given on my website:
    www.macfh.co.uk

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Theo@21:1/5 to Java Jive on Fri May 16 13:36:11 2025
    XPost: alt.os.linux

    In uk.comp.os.linux Java Jive <java@evij.com.invalid> wrote:
    As per title, I can get neither tftp or tftpd - at least I think
    neither but it's difficult to be sure - to work under Ubuntu 22. After
    some initial difficulties, I decided to uninstall and reinstall. Upon reinstallation, I received a warning that the file '/etc/inetd.conf' did
    not exist so I uninstalled them both again, 'touch'ed to create an empty '/etc/inetd.conf', and then reinstalled again, this time without undue warnings. The two config files now read as follows ...
    [snip]
    May 16 11:37:42 Computer xinetd[1945]: added service tftp [file=/etc/inetd.conf] [line=1]
    May 16 11:37:42 Computer xinetd[1945]: 2.3.15.3 started with libwrap
    loadavg labeled-networking options compiled in.
    May 16 11:37:42 Computer xinetd[1945]: Started working: 2 available services

    OK, so xinetd is running and has seen your tftp config file.

    ... but no listener is found on port 69 ...

    user@Computer:/home$ netstat -na | grep LIST | grep 69
    unix 2 [ ACC ] STREAM LISTENING 9169 /var/run/samba/nmbd/unexpected

    It's udp so it won't have a LISTEN state. I would expect a line similar to:

    udp 0 0 0.0.0.0:69 0.0.0.0:*

    ... and generally there is no evidence of any tftp service actually
    running, for example ...

    There is no tftp service. xinetd is doing the listening. When it sees an incoming connection it starts the in.tftpd binary and hands the file
    descriptor (I think) over to it. So every incoming connection starts a new in.tftpd instance. Until that happens in.tftpd isn't running.

    user@Computer:/home$ ps -aux | grep -v grep | grep tftp
    user@Computer:/home$ systemctl list-units --no-pager | grep tftp user@Computer:/home$ sudo service --status-all | grep tftp

    ... all find nothing. Unsurprisingly therefore, when I try to set up a
    test, nothing works ...

    Do ps/etc show that xinetd is running?
    Does 'ss -lp' show xinetd listening on any sockets?

    user@Computer:/home$ sudo echo "This is a TFTP test from $(hostname)" > /home/tftpboot/test.txt
    user@Computer:/home$ sudo chown nobody:nogroup /home/tftpboot/test.txt user@Computer:/home$ ll /home/tftpboot/test.txt
    -rw-r--r-- 1 nobody nogroup 36 2025-05-15 21:43 /home/tftpboot/test.txt user@Computer:/home$ cat /home/tftpboot/test.txt
    This is a TFTP test from Computer
    user@Computer:/home$ tftp localhost
    tftp> get test.txt
    tftp: test.txt: Permission denied
    tftp> q

    Assuming this is tftp-hpa, you could try 'status', 'verbose' and 'trace' commands to give more logs.

    It will however do this behaviour even to a nonexistent tftp server:

    $ tftp example.com
    tftp> verbose
    Verbose mode on.
    tftp> status
    Connected to example.com.
    Mode: netascii Verbose: on Tracing: off Literal: off
    Rexmt-interval: 5 seconds, Max-timeout: 25 seconds
    tftp> trace
    Packet tracing on.
    tftp> get nonexistent.txt
    getting from example.com:nonexistent.txt to nonexistent.txt [netascii]
    sent RRQ <file=nonexistent.txt, mode=netascii>
    sent RRQ <file=nonexistent.txt, mode=netascii>
    sent RRQ <file=nonexistent.txt, mode=netascii>
    ^C

    Using 127.0.0.1 instead of localhost suffers the same fate, as does an attempt to get a similar test text file from one of the Zyxel NSA221
    NASs, as does an attempt for a non-existent file or a non-existent
    server, so the error given could mean almost any type of failure and I
    don't know whether I have one problem with the client on the Ubuntu PC,
    or two problems with the service on each machine, PC and NAS, or all
    three. I was going to install the windows TFTP client to test with
    that, but for some reason or other that failed, and there's nothing in
    the event logs to suggest why, so for the moment I'm stuck.

    I think you can tell xinetd to log incoming connections, ie times it started
    up in.tftpd - it may already do that. Check logs.

    Last time I set up tftp and had troubles it turned out it was ufw blocking connections, but it seems you don't have ufw enabled. But I would guess a similar networking cause.

    Theo

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Java Jive@21:1/5 to Theo on Fri May 16 17:39:49 2025
    XPost: alt.os.linux

    On 2025-05-16 13:36, Theo wrote:

    In uk.comp.os.linux Java Jive <java@evij.com.invalid> wrote:

    As per title, I can get neither tftp or tftpd - at least I think
    neither but it's difficult to be sure - to work under Ubuntu 22. After
    some initial difficulties, I decided to uninstall and reinstall. Upon
    reinstallation, I received a warning that the file '/etc/inetd.conf' did
    not exist so I uninstalled them both again, 'touch'ed to create an empty
    '/etc/inetd.conf', and then reinstalled again, this time without undue
    warnings. The two config files now read as follows ...
    [snip]
    May 16 11:37:42 Computer xinetd[1945]: added service tftp
    [file=/etc/inetd.conf] [line=1]
    May 16 11:37:42 Computer xinetd[1945]: 2.3.15.3 started with libwrap
    loadavg labeled-networking options compiled in.
    May 16 11:37:42 Computer xinetd[1945]: Started working: 2 available services

    OK, so xinetd is running and has seen your tftp config file.

    ... but no listener is found on port 69 ...

    user@Computer:/home$ netstat -na | grep LIST | grep 69
    unix 2 [ ACC ] STREAM LISTENING 9169
    /var/run/samba/nmbd/unexpected

    It's udp so it won't have a LISTEN state. I would expect a line similar to:

    udp 0 0 0.0.0.0:69 0.0.0.0:*

    There's no such line.

    Do ps/etc show that xinetd is running?

    Yes xinetd is running ...

    user@Computer:/home$ ps -aux | grep -v grep | grep xinetd
    root 1061 0.0 0.0 9796 2564 ? Ss 16:47 0:00 /usr/sbin/xinetd -pidfile /run/xinetd.pid -stayalive -inetd_compat
    -inetd_ipv6

    ... but ...

    Does 'ss -lp' show xinetd listening on any sockets?

    ... that finds nothing ...

    user@Computer:/home$ ss -lp | grep xinetd
    user@Computer:/home$

    user@Computer:/home$ sudo echo "This is a TFTP test from $(hostname)" >
    /home/tftpboot/test.txt
    user@Computer:/home$ sudo chown nobody:nogroup /home/tftpboot/test.txt
    user@Computer:/home$ ll /home/tftpboot/test.txt
    -rw-r--r-- 1 nobody nogroup 36 2025-05-15 21:43 /home/tftpboot/test.txt
    user@Computer:/home$ cat /home/tftpboot/test.txt
    This is a TFTP test from Computer
    user@Computer:/home$ tftp localhost
    tftp> get test.txt
    tftp: test.txt: Permission denied
    tftp> q

    Assuming this is tftp-hpa,

    No its straight tftp, as in ...

    user@Computer:/home$ apt search tftp
    [...]
    tftp/jammy,now 0.17-23ubuntu1 amd64 [installed]
    Trivial file transfer protocol client
    [...]
    tftpd/jammy,now 0.17-23ubuntu1 amd64 [installed]
    Trivial file transfer protocol server
    [...]

    It will however do this behaviour even to a nonexistent tftp server:

    Yes, the error messages are useless for determining what is going wrong.

    I think you can tell xinetd to log incoming connections, ie times it started up in.tftpd - it may already do that. Check logs.

    That's odd, I've not changed anything since this morning, except that I
    shut down the PC when I went out for a walk, but the behaviour has
    changed slightly since then:

    user@Computer:/home$ tftp localhost
    tftp> get test.txt
    Transfer timed out.

    tftp> q

    ... resulting in a 0-length file in my home folder, and now when I check syslog, whereas previously it had been unhelpfully free of anything
    relevant, now I see the following 5 times ...

    May 16 17:17:09 Computer xinetd[1991]: execv( /usr/sbin/tcpd ) failed:
    No such file or directory (errno = 2)

    ... and indeed the following doesn't find tcpd anywhere at all on the
    system partition:

    user@Computer:/home$ sudo find / -xdev -name tcpd

    --

    Fake news kills!

    I may be contacted via the contact address given on my website:
    www.macfh.co.uk

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Theo@21:1/5 to Java Jive on Fri May 16 20:15:01 2025
    XPost: alt.os.linux

    In uk.comp.os.linux Java Jive <java@evij.com.invalid> wrote:
    That's odd, I've not changed anything since this morning, except that I
    shut down the PC when I went out for a walk, but the behaviour has
    changed slightly since then:

    user@Computer:/home$ tftp localhost
    tftp> get test.txt
    Transfer timed out.

    tftp> q

    ... resulting in a 0-length file in my home folder, and now when I check syslog, whereas previously it had been unhelpfully free of anything
    relevant, now I see the following 5 times ...

    May 16 17:17:09 Computer xinetd[1991]: execv( /usr/sbin/tcpd ) failed:
    No such file or directory (errno = 2)

    ... and indeed the following doesn't find tcpd anywhere at all on the
    system partition:

    user@Computer:/home$ sudo find / -xdev -name tcpd


    So it looks like you've configured tftpd in both inetd.conf and xinetd.conf, and the one in inetd.conf has taken priority but isn't working. According
    to the man page the inetd.conf format has the following fields, tab or space separated, one service per line:

    service name
    socket type
    protocol[,sndbuf=size][,rcvbuf=size]
    wait/nowait[.max]
    user[.group] or user[:group]
    server program
    server program arguments

    It looks like you're trying to run a server command:
    "/usr/sbin/tcpd /usr/sbin/in.tftpd /srv/tftp"

    tcpd was a very old way to do access control, ie allow/deny certain hosts. Nowadays you'd do that in the firewall. That's probably why you don't have that binary.

    Also that command is setting the root of your TFTP files to be /srv/tftp and
    I think you want it to be /home/tftpboot

    I think you need to remove one or other of the inetd.conf and xinetd.conf as otherwise you're trying to start the service twice. Try deleting the inetd.conf line, rebooting and trying again?

    Theo

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Java Jive@21:1/5 to Theo on Fri May 16 20:51:11 2025
    XPost: alt.os.linux

    On 2025-05-16 20:15, Theo wrote:
    In uk.comp.os.linux Java Jive <java@evij.com.invalid> wrote:
    That's odd, I've not changed anything since this morning, except that I
    shut down the PC when I went out for a walk, but the behaviour has
    changed slightly since then:

    user@Computer:/home$ tftp localhost
    tftp> get test.txt
    Transfer timed out.

    tftp> q

    ... resulting in a 0-length file in my home folder, and now when I check
    syslog, whereas previously it had been unhelpfully free of anything
    relevant, now I see the following 5 times ...

    May 16 17:17:09 Computer xinetd[1991]: execv( /usr/sbin/tcpd ) failed:
    No such file or directory (errno = 2)

    ... and indeed the following doesn't find tcpd anywhere at all on the
    system partition:

    user@Computer:/home$ sudo find / -xdev -name tcpd


    So it looks like you've configured tftpd in both inetd.conf and xinetd.conf, and the one in inetd.conf has taken priority but isn't working. According
    to the man page the inetd.conf format has the following fields, tab or space separated, one service per line:

    service name
    socket type
    protocol[,sndbuf=size][,rcvbuf=size]
    wait/nowait[.max]
    user[.group] or user[:group]
    server program
    server program arguments

    It looks like you're trying to run a server command:
    "/usr/sbin/tcpd /usr/sbin/in.tftpd /srv/tftp"

    tcpd was a very old way to do access control, ie allow/deny certain hosts. Nowadays you'd do that in the firewall. That's probably why you don't have that binary.

    Also that command is setting the root of your TFTP files to be /srv/tftp and I think you want it to be /home/tftpboot

    I think you need to remove one or other of the inetd.conf and xinetd.conf as otherwise you're trying to start the service twice. Try deleting the inetd.conf line, rebooting and trying again?

    Well, that's how it was originally, no /etc/inetd.conf file, but nothing
    was working then either. However, your comments are interesting,
    because this is covered by an associated document ...

    /usr/share/doc/xinetd/README.Debian

    ... which states that where both are configured, xinetd will take
    priority ...

    README.Debian for xinetd
    ========================

    xinetd in debian is supposed to work with -inetd_compat enabled (you can
    tweak that in /etc/default/xinetd).

    Package maintainers that support xinetd in addition to inetd, will drop
    files in /etc/xinetd.d/<service> _and_ add entries in /etc/inetd.conf,
    enabling them using update-inetd.

    If both an xinetd service configuration id and an entry in
    /etc/inetd.conf match, the xinetd one will hide the inetd.conf one, even
    if disabled. This trick is built to simplify the logic in update-inetd,
    and let the administrators only touch xinetd configuration and don't
    have /etc/inetd.conf mess with that they changed behind their back.

    -- Pierre Habouzit <madcoder@debian.org> Wed, 28 Nov 2007 11:55:48 +0100s

    ... although I think the problem section is "If both an xinetd service configuration id and an entry in /etc/inetd.conf match", so I tried what
    you suggested.

    First I commented out the line in /etc/inetd.conf and rebooted, but
    still got 'Permission denied' when trying to get the test file. Next I
    renamed the file and rebooted, with exactly the same result.

    However, in both cases, the 5 lines in syslog are now not generated, in
    fact now nothing at all appears in syslog as a result of the failed
    attempt. I guess that perhaps that may be considered as an improvement,
    but unfortunately the service is still not working.

    --

    Fake news kills!

    I may be contacted via the contact address given on my website:
    www.macfh.co.uk

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Java Jive@21:1/5 to Java Jive on Fri May 16 20:22:52 2025
    XPost: alt.os.linux

    On 2025-05-16 17:39, Java Jive wrote:

    That's odd, I've not changed anything since this morning, except that I
    shut down the PC when I went out for a walk, but the behaviour has
    changed slightly since then:

    user@Computer:/home$ tftp localhost
    tftp> get test.txt
    Transfer timed out.

    tftp> q

    ... resulting in a 0-length file in my home folder, and now when I check syslog, whereas previously it had been unhelpfully free of anything
    relevant, now I see the following 5 times ...

    May 16 17:17:09 Computer xinetd[1991]: execv( /usr/sbin/tcpd ) failed:
    No such file or directory (errno = 2)

    ... and indeed the following doesn't find tcpd anywhere at all on the
    system partition:

    user@Computer:/home$ sudo find / -xdev -name tcpd

    And also I've now been able to get the test file from the NSA221's tftp service. So now we have that both the NSA221's tftp service and the
    Ubuntu client are working, leaving the problem just with the Ubuntu 22
    service.

    However, I wish I could work out what has changed since this morning.

    --

    Fake news kills!

    I may be contacted via the contact address given on my website:
    www.macfh.co.uk

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Java Jive@21:1/5 to Java Jive on Fri May 16 22:12:29 2025
    XPost: alt.os.linux

    On 2025-05-16 20:51, Java Jive wrote:

    First I commented out the line in /etc/inetd.conf and rebooted, but
    still got 'Permission denied' when trying to get the test file.  Next I renamed the file and rebooted, with exactly the same result.

    However, in both cases, the 5 lines in syslog are now not generated, in
    fact now nothing at all appears in syslog as a result of the failed attempt.  I guess that perhaps that may be considered as an improvement,
    but unfortunately the service is still not working.

    Addendum. Editing /etc/inetd.conf to read ...

    user@Computer:/home$ cat /etc/inetd.conf
    tftp dgram udp wait nobody /usr/sbin/in.tftpd /srv/tftp

    ... has the same effect as renaming the file or commenting out the line, nothing in syslog, but still 'Permission denied'. However, expanding on
    this, realising that it was necessary to give the correct parameters to
    to in.tftpd, the following works:

    user@Computer:/home$ cat /etc/inetd.conf
    tftp dgram udp wait nobody /usr/sbin/in.tftpd -s /home/tftpboot
    user@Computer:/home$ tftp localhost
    tftp> get test.txt
    Received 37 bytes in 0.0 seconds
    tftp> q
    user@Computer:/home$ cat test.txt
    This is a TFTP test from Computer
    user@Computer:/home$ tail -50 /var/log/syslog
    [...]
    May 16 22:04:55 Computer tftpd[2245]: tftpd: trying to get file: test.txt
    May 16 22:04:55 Computer tftpd[2245]: tftpd: serving file from
    /home/tftpboot

    Thanks very much for your help, which was instrumental in setting on the
    right track.

    --

    Fake news kills!

    I may be contacted via the contact address given on my website:
    www.macfh.co.uk

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Theo@21:1/5 to Java Jive on Sun May 18 11:55:05 2025
    XPost: alt.os.linux

    In uk.comp.os.linux Java Jive <java@evij.com.invalid> wrote:

    ... has the same effect as renaming the file or commenting out the line, nothing in syslog, but still 'Permission denied'. However, expanding on this, realising that it was necessary to give the correct parameters to
    to in.tftpd, the following works:

    user@Computer:/home$ cat /etc/inetd.conf
    tftp dgram udp wait nobody /usr/sbin/in.tftpd -s /home/tftpboot
    [...]

    Thanks very much for your help, which was instrumental in setting on the right track.

    Glad you got it sorted. I noticed on my travels that one of the 'helpful'
    web pages on setting up tftpd:
    https://linuxlink.timesys.com/docs/linux_tftp

    tells you to configure it to use tcpd even though it doesn't tell you to install tcpd (which it turns out is still available as a package in Ubuntu).
    So that's setting you up to fail. And there may be config differences
    between the different versions of tftpd as to whether you need '-s' when telling it the root location.

    They don't feel like AI slop but seems like a bit of cargo-culting about how
    to configure things in all these 'helpful' pages.

    Theo

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)