I am trying to set up tftp server on my workstation to manage some switches.
I have done the following:
dnf install tftp tftp-server firewall-cmd --add-service=tftp --permanent firewall-cmd --reload systemctl start tftp
I can get files from a local terminal window with:
tftp localhost -cv file
I had problems with put until I saw that the file had to preexist. I did that with touch file on my system.
From a F24 notebook on the same subnet as the one running tftp server, though I cannot get the file. I get:
Transfer timed out.
I also tried:
firewall-cmd --add-port=69/udp --permanent
but no different.
I don't see anything in the tftp.service file to indicate anything there.
What am I missing?
thanks
On 1/23/19 12:50 PM, Robert Moskowitz wrote:
I can get files from a local terminal window with:
tftp localhost -cv file
I had problems with put until I saw that the file had to preexist. I did that with touch file on my system.
From a F24 notebook on the same subnet as the one running tftp server, though I cannot get the file. I get:
Transfer timed out.
I also tried:
firewall-cmd --add-port=69/udp --permanent
but no different.
I don't see anything in the tftp.service file to indicate anything there.
What am I missing?
IIRC, tftp (like non-passive FTP) is one of those ancient, firewall- unfriendly protocols. I think that the server actually initiates the connection to the client for the actual transfer.
For a quick test, you'll need to adjust the firewall rules (or disable it altogether) on the *client*. Note that this shouldn't be an issue for your switches, as they won't be blocking the transfer traffic.
HTH
On 1/23/19 3:27 PM, Ian Pilcher wrote:
On 1/23/19 12:50 PM, Robert Moskowitz wrote:
I can get files from a local terminal window with:
tftp localhost -cv file
I had problems with put until I saw that the file had to preexist. I did that with touch file on my system.
From a F24 notebook on the same subnet as the one running tftp server, though I cannot get the file. I get:
Transfer timed out.
I also tried:
firewall-cmd --add-port=69/udp --permanent
but no different.
I don't see anything in the tftp.service file to indicate anything there.
What am I missing?
IIRC, tftp (like non-passive FTP) is one of those ancient, firewall- unfriendly protocols. I think that the server actually initiates the connection to the client for the actual transfer.
For a quick test, you'll need to adjust the firewall rules (or disable it altogether) on the *client*. Note that this shouldn't be an issue for your switches, as they won't be blocking the transfer traffic.
Humph.
Well setting the firewall on the client did not seem to make a difference, but I went over the the switch and that is working. Now that I know all the permissions that need to be set...
thanks
-
Ian Pilcher -
Robert Moskowitz