Hi Steven.
Le 21/12/2021 à 17:16, Steven Spencer via rocky a écrit :
Does the client have a `firewalld` rule as well?
I had this already in mind but expected there is no firewall on the client. Anyway I did check on the client:
sudo systemctl stop firewalld.service
tftp myserver.mydomain.local -m binary -c get file1.txt /dev/stdout Hello File 1
sudo systemctl start firewalld.service
tftp myserver.mydomain.local -m binary -c get file1.txt /dev/stdout Transfer timed out.
So obviously the firewall on the client is the problem. Oh man, so easy :-( Thanks for the solution.
I' m only wondering what the "status" indicates in case the firewall rules are active:
tftp myserver.mydomain.local tftp> status Connected to myserver.mydomain.local. Mode: netascii Verbose: off Tracing: off Literal: off Rexmt-interval: 5 seconds, Max-timeout: 25 seconds
Maybe the message "Connected to myserver.mydomain.local." is a bit misleading and therefore I didn't follow the idea with a firewall in the way.
Regards,
Meikel