<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Mar 7, 2014 at 6:06 AM, Robie Basak <span dir="ltr"><<a href="mailto:robie.basak@ubuntu.com" target="_blank">robie.basak@ubuntu.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class="">On Thu, Mar 06, 2014 at 05:36:57PM -0500, Asif Iqbal wrote:<br>
> Any suggestion on how to troubleshoot this?<br>
<br>
</div>Try tcpdump, to see what is actually not going out or not arriving.<br>
</blockquote></div><div class="gmail_extra"><br></div><div class="gmail_extra"><br></div><div class="gmail_extra">ubuntu client (192.168.0.248) tries few times and then times out</div><div class="gmail_extra"><br></div><div class="gmail_extra">
~$ tftp 192.168.0.15</div><div class="gmail_extra">tftp> get file</div><div class="gmail_extra">Transfer timed out.</div><div class="gmail_extra"><br></div><div class="gmail_extra">tftp> </div><div><br></div><div>tcpdump on ubuntu client (192.168.0.248)</div>
<div><br></div><div><div>12:33:32.086503 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 44)</div><div> 192.168.0.248.59695 > 192.168.0.15.69: [bad udp cksum c46c!] 16 RRQ "file" netascii</div>
<div>12:33:37.086528 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 44)</div><div> 192.168.0.248.59695 > 192.168.0.15.69: [bad udp cksum c46c!] 16 RRQ "file" netascii</div><div>12:33:42.086548 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 44)</div>
<div> 192.168.0.248.59695 > 192.168.0.15.69: [bad udp cksum c46c!] 16 RRQ "file" netascii</div><div>12:33:47.086569 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 44)</div><div> 192.168.0.248.59695 > 192.168.0.15.69: [bad udp cksum c46c!] 16 RRQ "file" netascii</div>
<div>12:33:52.086587 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 44)</div><div> 192.168.0.248.59695 > 192.168.0.15.69: [bad udp cksum c46c!] 16 RRQ "file" netascii</div></div>
<div>
<br></div><div>tcpdump on ubuntu tftp server (192.168.0.15)</div><div><br></div><div><div>12:33:37.086694 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 44)</div><div> 192.168.0.248.59695 > 192.168.0.15.69: [udp sum ok] 16 RRQ "file" netascii</div>
<div>12:33:42.086684 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 44)</div><div> 192.168.0.248.59695 > 192.168.0.15.69: [udp sum ok] 16 RRQ "file" netascii</div><div>12:33:47.086739 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 44)</div>
<div> 192.168.0.248.59695 > 192.168.0.15.69: [udp sum ok] 16 RRQ "file" netascii</div><div>12:33:52.086761 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 44)</div><div> 192.168.0.248.59695 > 192.168.0.15.69: [udp sum ok] 16 RRQ "file" netascii</div>
</div><div><br></div><div><br></div><div>centos client works right away when pulling the file from ubuntu tftpd server</div><div><br></div><div><div>[vagrant@centos65 ~]$ tftp 192.168.0.15</div><div>tftp> get file</div>
<div>tftp></div></div><div><br></div><div>tcpdump from centos client (192.168.0.71)</div><div><br></div><div><div>17:42:16.398838 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 44)</div><div> 192.168.0.71.36536 > 192.168.0.15.tftp: [bad udp cksum e242!] 16 RRQ "file" netascii</div>
</div><div><br></div><div>tcpdump from ubuntu tftpd server (192.168.0.15)</div><div><div><br></div><div>12:42:17.931861 IP (tos 0x0, ttl 50, id 0, offset 0, flags [none], proto UDP (17), length 44)</div><div> 192.168.0.71.36536 > 192.168.0.15.69: [udp sum ok] 16 RRQ "file" netascii</div>
<div><br></div></div><div><br></div><div>-- <br></div><div><br></div>Asif Iqbal<br>PGP Key: 0xE62693C5 KeyServer: <a href="http://pgp.mit.edu">pgp.mit.edu</a><br>A: Because it messes up the order in which people normally read text.<br>
Q: Why is top-posting such a bad thing?<br><br>
</div></div>