You are not logged in.
Hi. There is a difference in behavior between tnftp installed from the extra repository and tnftp6 installed from the AUR, whose cause I find mysterious. Unlike tnftp6, tnftp can only connect to LAN ftp servers whose ip starts with 192.168* or 127*, but can't connect to Internet-based ftp servers such as ftp.freebsd.org. For example, the command
tnftp -a ftp.freebsd.org
produces the message
tnftp: Can't connect to `96.47.72.116:21': Network is unreachable
. But if I uninstall tnftp and install tnftp6 from the AUR, then I'll have no problem accessing LAN-based and Internet-based ftp servers with it. Why is that? The version of tnftp and tnftp6 is the same. tnftp6 supports ipv6, but it's irrelevant in this case.
Last edited by Oleg_NYC (2023-08-12 13:04:25)
Offline
ip a; ip r; ip r get 96.47.72.116
Can you "tnftp -6 -a ftp.freebsd.org"?
Offline
If I execute that command with tnftp6, it produces the message "Network is unreachable", but the -4 option allows me to connect to the server. With tnftp, neither the -4 nor the -6 option allows me to connect to the server.
Offline
AUR has "--with-socks=no"
You could try to build the repo package w/ that difference, https://wiki.archlinux.org/title/Arch_b … ILD_source
Offline
So, there is a possibility that if I use the --with-socks=no option to rebuild tnftp from the extra repository, I will be able to connect to ftp servers that are not on my LAN? Yes, I might rebuild this, but if --with-socks=yes (I don't even understand the meaning of this option) removes a lot of functionality from the "extra" tnftp package, why was it built like that in the first place?
Offline
It doesn't. https://www.inet.no/dante/
systemctl status sockd
I found this interesting comment:
https://slackbuilds.org/repository/14.2/network/tnftp/
It's not possible to build a single tnftp binary with both IPv6 andSOCKS5 support.
It's from 2020, but you could try
--disable-ipv6
and keep socks.
No idea whether the tnftp in the repos is maybe misconfigured itr (trying to use both)
Offline
You mentioned sockd. sockd.service is inactive. The official PKGBUILD for the "extra" tnftp sources has both ipv6 and socks enabled, so I kept socks enabled and disabled ipv6. After building it, I was unable to connect to ftp servers with internet ips. I re-enabled ipv6 and disabled socks and was able to connect to servers with Internet ips. Then I disabled both ipv6 and socks and was able to connect to servers with internet ips. I always used the -4 option. What do these results mean? Does it mean there is something wrong with the official PKGBUILD or does it mean there is something wrong on my end?
Offline
idk what the idea behing the tnftp package is, but you'll probably *need* a socks tunnel with that configuration, what makes it probably useless to connect some random public ftp server.
You can file a bug against the package to inquire the intent. I can confirm that it won't work the way you desire w/ its current config.
If you're just looking for an cli ftp, there's ftp in inetutils.
Offline
Thanks for the info. I opened a bug report and will mark this topic as solved.
Offline