Recent changes to support-requests

#10 windowsize option

Martin Dummer — Sat, 11 Apr 2026 21:01:17 -0000

status: pending --> closed

#11 Switch from old PCRE to actively maintained PCRE2

Shubh — Wed, 10 Apr 2024 05:25:31 -0000

Hey Andi , Martin , i am seeing the similar issue where my pcre2 methods are not getting detected and am seeing" undefined reference to pcre2_match_data_create_from_pattern_'" issues and many others , as the original git has the pcre support https://sourceforge.net/projects/atftp/files/ . I wanted to check how do you guys have resolved this issue in here. I tried to add pcre2.h from https://github.com/php/php-src/blob/master/ext/pcre/pcre2lib/pcre2.h but it didnt worked for me

#11 Switch from old PCRE to actively maintained PCRE2

Andi — Wed, 21 Dec 2022 14:26:45 -0000

I guess this bug can now be closed.

#10 windowsize option

Andi — Wed, 21 Dec 2022 14:25:54 -0000

I guess this bug can now be closed.

#13 ATFTPD crashes when requested a non-existent file

Eduardo Barretto — Fri, 11 Nov 2022 09:19:53 -0000

By default Ubuntu compile packages with LTO enabled, which I think Debian is not yet using.
There's two course of actions, either we disable it on our Deb, or upstream can evaluate if they want to have this compile flag enabled by default and fix the issues in code (something like the mentioned fix above).

#14 atftpd runs as daemon from the shell but fails on launch by the systemd socket

l2fl2f — Fri, 11 Nov 2022 00:11:28 -0000

tried via the console directly: same problem.

#13 ATFTPD crashes when requested a non-existent file

l2fl2f — Thu, 10 Nov 2022 22:59:59 -0000

On Ubuntu 22.04: 0.7.git20210915-4 crashes unable to start any client

#14 atftpd runs as daemon from the shell but fails on launch by the systemd socket

l2fl2f — Thu, 10 Nov 2022 22:57:50 -0000

Got the same problem with Ubuntu 22.04. Need help

#13 ATFTPD crashes when requested a non-existent file

Andi — Mon, 03 Oct 2022 18:08:16 -0000

I can confirm the issue on jammy. However, as far as I can tell, it's the same code. I did not investigate it in detail, but it looks like it's a matter of compiler flags applied, which causes the issue.

atftpd runs as daemon from the shell but fails on launch by the systemd socket

Randy Rue — Mon, 03 Oct 2022 17:54:52 -0000

Hello,

I'm running the default install of atftpd as provided by apt in Ubuntu 22.

Configuration in /etc/default/atftpd is unchanged from the default except I have changed the default '--verbose=5' to '--verbose=7'

If I try to get a test file 'foo' present at /srv/tftp/foo, 'journalctl -f --unit atftpd.service' shows:

Oct 03 10:41:55 tftp systemd[1]: Started Advanced TFTP Server.
Oct 03 10:41:55 tftp atftpd[6968]: Advanced Trivial FTP server started (0.7.5)
Oct 03 10:41:55 tftp atftpd[6968]:   started by inetd
Oct 03 10:41:55 tftp atftpd[6968]:   logging level: 7
Oct 03 10:41:55 tftp atftpd[6968]:   directory: /srv/tftp/
Oct 03 10:41:55 tftp atftpd[6968]:   user: nobody.nogroup
Oct 03 10:41:55 tftp atftpd[6968]:   log file: syslog
Oct 03 10:41:55 tftp atftpd[6968]:   not forcing to listen on local interfaces.
Oct 03 10:41:55 tftp atftpd[6968]:   server timeout: 300
Oct 03 10:41:55 tftp atftpd[6968]:   tftp retry timeout: 5
Oct 03 10:41:55 tftp atftpd[6968]:   maximum number of thread: 100
Oct 03 10:41:55 tftp atftpd[6968]:   option timeout:    enabled
Oct 03 10:41:55 tftp atftpd[6968]:   option tzise:      enabled
Oct 03 10:41:55 tftp atftpd[6968]:   option blksize:    enabled
Oct 03 10:41:55 tftp atftpd[6968]:   option windowsize: enabled
Oct 03 10:41:55 tftp atftpd[6968]:   option multicast:  enabled
Oct 03 10:41:55 tftp atftpd[6968]:      address range:  239.239.239.0-255
Oct 03 10:41:55 tftp atftpd[6968]:      port range:     1758
Oct 03 10:41:55 tftp atftpd[6968]: socket may listen on any address, including broadcast
Oct 03 10:41:55 tftp atftpd[6968]: Creating new socket: :::50554
Oct 03 10:41:55 tftp atftpd[6968]: Serving foo to ::ffff:10.6.164.109:56665
Oct 03 10:41:55 tftp systemd[1]: atftpd.service: Main process exited, code=killed, status=6/ABRT
Oct 03 10:41:55 tftp systemd[1]: atftpd.service: Failed with result 'signal'.

However, if I stop the socket using systemctl and launch the binary directly from the shell, using the same arguments as in /etc/default/atftpd and adding '--daemon' to the beginning of the arguments, I can 'get' the file foo. It lands on the client and on the server 'journalctl -f | grep atftp' shows:

Oct 03 10:51:02 tftp atftpd[7016]: socket may listen on any address, including broadcast
Oct 03 10:51:02 tftp atftpd[7016]: Creating new socket: 10.6.164.61:40125
Oct 03 10:51:02 tftp atftpd[7016]: Serving foo to 10.6.164.109:51809
Oct 03 10:51:02 tftp atftpd[7016]: End of transfer
Oct 03 10:51:02 tftp atftpd[7016]: Server thread exiting

I've confirmed that the /srv/tftp directory has 0777 permissions although the results were the same when it had 0755 permissions and I'd prefer this service be read only.

Short version, I'm thinking that the socket is somehow launching the binary differently than a shell session.

Any help would be appreciated.