tftp timeout for ubuntu and debian client, but not for centos client

[Asif Iqbal]

On Fri, Mar 7, 2014 at 6:06 AM, Robie Basak <robie.basak at ubuntu.com> wrote:

> On Thu, Mar 06, 2014 at 05:36:57PM -0500, Asif Iqbal wrote:
> > Any suggestion on how to troubleshoot this?
>
> Try tcpdump, to see what is actually not going out or not arriving.
>


ubuntu client (192.168.0.248) tries few times and then times out

~$ tftp 192.168.0.15
tftp> get file
Transfer timed out.

tftp>

tcpdump on ubuntu client (192.168.0.248)

12:33:32.086503 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP
(17), length 44)
    192.168.0.248.59695 > 192.168.0.15.69: [bad udp cksum c46c!]  16 RRQ
"file" netascii
12:33:37.086528 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP
(17), length 44)
    192.168.0.248.59695 > 192.168.0.15.69: [bad udp cksum c46c!]  16 RRQ
"file" netascii
12:33:42.086548 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP
(17), length 44)
    192.168.0.248.59695 > 192.168.0.15.69: [bad udp cksum c46c!]  16 RRQ
"file" netascii
12:33:47.086569 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP
(17), length 44)
    192.168.0.248.59695 > 192.168.0.15.69: [bad udp cksum c46c!]  16 RRQ
"file" netascii
12:33:52.086587 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP
(17), length 44)
    192.168.0.248.59695 > 192.168.0.15.69: [bad udp cksum c46c!]  16 RRQ
"file" netascii

tcpdump on ubuntu tftp server (192.168.0.15)

12:33:37.086694 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP
(17), length 44)
    192.168.0.248.59695 > 192.168.0.15.69: [udp sum ok]  16 RRQ "file"
netascii
12:33:42.086684 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP
(17), length 44)
    192.168.0.248.59695 > 192.168.0.15.69: [udp sum ok]  16 RRQ "file"
netascii
12:33:47.086739 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP
(17), length 44)
    192.168.0.248.59695 > 192.168.0.15.69: [udp sum ok]  16 RRQ "file"
netascii
12:33:52.086761 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP
(17), length 44)
    192.168.0.248.59695 > 192.168.0.15.69: [udp sum ok]  16 RRQ "file"
netascii


centos client works right away when pulling the file from ubuntu tftpd
server

[vagrant at centos65 ~]$ tftp 192.168.0.15
tftp> get file
tftp>

tcpdump from centos client (192.168.0.71)

17:42:16.398838 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP
(17), length 44)
    192.168.0.71.36536 > 192.168.0.15.tftp: [bad udp cksum e242!]  16 RRQ
"file" netascii

tcpdump from ubuntu tftpd server (192.168.0.15)

12:42:17.931861 IP (tos 0x0, ttl 50, id 0, offset 0, flags [none], proto
UDP (17), length 44)
    192.168.0.71.36536 > 192.168.0.15.69: [udp sum ok]  16 RRQ "file"
netascii


-- 

Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-server/attachments/20140307/6763d6fb/attachment.html>