Feb 16 07:06:37 localhost in.tftpd[13156]: tftpd: read(ack): No route to host

Issues related to configuring your network
DANNDP
Posts: 22
Joined: 2009/11/26 21:24:53
Contact:

Feb 16 07:06:37 localhost in.tftpd[13156]: tftpd: read(ack): No route to host

Postby DANNDP » 2010/02/16 20:04:47

Hello my friends,

Today i saw a weird message in /var/log/messages into my centos 4.8 system:

Feb 16 07:06:37 localhost in.tftpd[13156]: tftpd: read(ack): No route to host
Feb 16 07:06:49 localhost in.tftpd[13176]: tftpd: read(ack): No route to host
Feb 16 07:06:57 localhost in.tftpd[13172]: tftpd: read(ack): No route to host

What could be happening here? when i make a service tftpd satus it says unrecognized service, i have a tftp service up to provisioning some ip phones...

Thanks in advance

Regards

pschaff
Retired Moderator
Posts: 18276
Joined: 2006/12/13 20:15:34
Location: Tidewater, Virginia, North America
Contact:

Feb 16 07:06:37 localhost in.tftpd[13156]: tftpd: read(ack):

Postby pschaff » 2010/02/16 21:38:21

DANNDP wrote:
... when i make a service tftpd s[t]atus it says unrecognized service


That's because the tftp server you are using works through xinetd and not as a service of its own. Is the tftp service working for the clients? Have you tried temporarily disabling the firewall?

DANNDP
Posts: 22
Joined: 2009/11/26 21:24:53
Contact:

Re: Feb 16 07:06:37 localhost in.tftpd[13156]: tftpd: read(ack): No route to host

Postby DANNDP » 2010/02/16 21:52:57

yes, it is working for the clients, that's why i'm courious about this messages:

Re: Feb 16 07:06:37 localhost in.tftpd[13156]: tftpd: read(ack): No route to host

The firewall of my server is off

pschaff
Retired Moderator
Posts: 18276
Joined: 2006/12/13 20:15:34
Location: Tidewater, Virginia, North America
Contact:

Re: Feb 16 07:06:37 localhost in.tftpd[13156]: tftpd: read(ack): No route to host

Postby pschaff » 2010/02/16 22:08:12

Googling

Code: Select all

localhost in.tftpd read ack No route to host
it appears that the clients are not responding to the ACK from the server. It is suggested that the problem is on the client side. If things are working I'd be prone to let well enough alone, particularly as you are relaxed enough to run your server without a firewall.