TFTP time out error

Installing, Configuring, Troubleshooting server daemons such as Web and Mail
bagodonut1
Posts: 1
Joined: 2011/09/16 18:18:41

TFTP time out error

Postby bagodonut1 » 2011/09/16 18:44:41

Hi

I am currently running CentOS 5.6 and trying to install and configure TFTP.

/etc/xinetd.d/tftp

Code: Select all

# default: off
# description: The tftp server serves files using the trivial file transfer
#       protocol.  The tftp protocol is often used to boot diskless
#       workstations, download configuration files to network-aware printers,
#       and to start the installation process for some operating systems.
service tftp
{
        disable         = no
        socket_type     = dgram
        protocol        = udp
        wait            = yes
        user            = root
        server          = /usr/sbin/in.tftpd
        server_args     = -s /tftpboot
        per_source      = 11
        cps             = 100 2
        flags           = IPv4
}
[Moderator edit: Added code tags to preserve formatting.]

Started it /sbin/service xinetd start

When I try to TFTP from a client, I get a timeout. Reading through forums on the web someone mentioned testing it locally via tftp localhost. This times out as well.

I shutdown IPTables and SELinux.

Any assistance would be greatly appreciated.

Thanks

kyrunner
Posts: 30
Joined: 2011/09/26 16:34:22
Contact:

Re: TFTP time out error

Postby kyrunner » 2011/09/28 14:28:57

I was having the same issue until I opened the tftp port ACCEPT udp -- anywhere anywhere state NEW udp dpt:tftp

But from your thread you say you have the firewall off and SELinux off. I'm sure you checked that tftp service is running.

Are you able to ping the server from the client.

charlesgmoore
Posts: 15
Joined: 2011/09/08 18:41:56

Re: TFTP time out error

Postby charlesgmoore » 2011/09/30 14:32:16

You should make sure to restart xinetd

service xinetd restart

then do a

netstat -a |grep tftp

make sure tftp is listening

gerald_clark
Posts: 10642
Joined: 2005/08/05 15:19:54
Location: Northern Illinois, USA

TFTP time out error

Postby gerald_clark » 2011/09/30 14:48:15

xinetd services don't listen on the ports.
Xinetd launches them only when a connection is attempted.

charlesgmoore
Posts: 15
Joined: 2011/09/08 18:41:56

Re: TFTP time out error

Postby charlesgmoore » 2011/09/30 14:51:15

I apologize, you are correct.

User avatar
TrevorH
Forum Moderator
Posts: 21199
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: TFTP time out error

Postby TrevorH » 2011/09/30 15:22:30

xinetd services don't listen on the ports.


Yes they do. Xinetd listens to the port and spawns the correct server for the port and passes the socket over to it.

Code: Select all

# chkconfig --list | grep tftp
        tftp:           on
# netstat -antup | grep 69
udp        0      0 0.0.0.0:69                  0.0.0.0:*                               3164/xinetd

gerald_clark
Posts: 10642
Joined: 2005/08/05 15:19:54
Location: Northern Illinois, USA

Re: TFTP time out error

Postby gerald_clark » 2011/09/30 15:35:45

That is what I said.
Netstat will not show a connection to tftp unless there is a current connection.
Tftp does not listen. Xinetd does.

User avatar
TrevorH
Forum Moderator
Posts: 21199
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: TFTP time out error

Postby TrevorH » 2011/09/30 15:58:27

Sorry, I read your comment as meaning that nothing listened on the port and then magic happened when a connection was attempted :-)

But the command listed above by charlesgmoore would still have worked to show the listener

Code: Select all

# netstat -a | grep tftp
udp        0      0 *:tftp

gerald_clark
Posts: 10642
Joined: 2005/08/05 15:19:54
Location: Northern Illinois, USA

Re: TFTP time out error

Postby gerald_clark » 2011/09/30 16:06:49

You are correct.

Now, are there any hints in the logs?

charlesgmoore
Posts: 15
Joined: 2011/09/08 18:41:56

Re: TFTP time out error

Postby charlesgmoore » 2011/09/30 18:35:01

maybe a tail -f /var/log/gmessages and see if anything pops up when you reboot the tftp device.

or

do a tcpdump for port 69 and see if the device is even hitting the box.