<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Mar 7, 2014 at 12:45 PM, Asif Iqbal <span dir="ltr"><<a href="mailto:vadud3@gmail.com" target="_blank">vadud3@gmail.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 dir="ltr"><br><div class="gmail_extra"><div><div class="h5">
<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>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></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 class=""><div><br></div></div></div></div></blockquote><div><br></div><div><br></div><div>I realized tcpdump only port 69 will miss all the other tftp related traffic. Here is a better snapshot of tcpdump </div>
<div>from ubuntu client and ubuntu server during tftp. tftp is still timing out.</div><div><br></div><div>ubuntu client is 192.168.0.94 and ubuntu server is 192.168.0.15 (sanitized)</div><div><br></div><div>tcdump on ubuntu client</div>
<div><div>$ sudo tcpdump -nnieth0 host 192.168.0.15 and not port 22</div><div>tcpdump: verbose output suppressed, use -v or -vv for full protocol decode</div><div>listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes</div>
<div><br></div><div>11:22:05.145882 ARP, Request who-has 192.168.0.15 (ff:ff:ff:ff:ff:ff) tell 192.168.0.112, length 46<br></div><div>11:22:07.200985 IP 192.168.0.94.40554 > 192.168.0.15.69: 16 RRQ "file" netascii</div>
<div>11:22:07.205970 IP 192.168.0.15.43112 > 192.168.0.94.40554: UDP, length 38</div><div>11:22:12.201170 IP 192.168.0.94.40554 > 192.168.0.15.69: 16 RRQ "file" netascii</div><div>11:22:12.206110 IP 192.168.0.15.50574 > 192.168.0.94.40554: UDP, length 38</div>
<div>11:22:12.206254 IP 192.168.0.15.43112 > 192.168.0.94.40554: UDP, length 38</div><div>11:22:17.201323 IP 192.168.0.94.40554 > 192.168.0.15.69: 16 RRQ "file" netascii</div><div>11:22:17.206211 IP 192.168.0.15.41961 > 192.168.0.94.40554: UDP, length 38</div>
<div>11:22:17.206489 IP 192.168.0.15.50574 > 192.168.0.94.40554: UDP, length 38</div><div>11:22:17.206607 IP 192.168.0.15.43112 > 192.168.0.94.40554: UDP, length 38</div><div>11:22:22.201477 IP 192.168.0.94.40554 > 192.168.0.15.69: 16 RRQ "file" netascii</div>
<div>11:22:22.206360 IP 192.168.0.15.59041 > 192.168.0.94.40554: UDP, length 38</div><div>11:22:22.206977 IP 192.168.0.15.41961 > 192.168.0.94.40554: UDP, length 38</div><div>11:22:22.207016 IP 192.168.0.15.43112 > 192.168.0.94.40554: UDP, length 38</div>
<div>11:22:22.207206 IP 192.168.0.15.50574 > 192.168.0.94.40554: UDP, length 38</div><div>11:22:27.201625 IP 192.168.0.94.40554 > 192.168.0.15.69: 16 RRQ "file" netascii</div><div>11:22:27.206519 IP 192.168.0.15.38812 > 192.168.0.94.40554: UDP, length 38</div>
<div>11:22:27.206644 IP 192.168.0.15.59041 > 192.168.0.94.40554: UDP, length 38</div><div>11:22:27.206757 ARP, Request who-has 192.168.0.15 tell 192.168.0.94, length 28</div><div>11:22:27.206978 ARP, Reply 192.168.0.15 is-at ac:16:2d:79:64:ec, length 46</div>
<div>11:22:27.207263 IP 192.168.0.15.41961 > 192.168.0.94.40554: UDP, length 38</div><div>11:22:27.207302 IP 192.168.0.15.43112 > 192.168.0.94.40554: UDP, length 38</div><div>11:22:27.207549 IP 192.168.0.15.50574 > 192.168.0.94.40554: UDP, length 38</div>
<div>11:22:32.206854 IP 192.168.0.15.38812 > 192.168.0.94.40554: UDP, length 38</div><div>11:22:32.207260 IP 192.168.0.15.59041 > 192.168.0.94.40554: UDP, length 38</div><div>11:22:32.207533 IP 192.168.0.15.41961 > 192.168.0.94.40554: UDP, length 38</div>
<div>11:22:32.207780 IP 192.168.0.15.50574 > 192.168.0.94.40554: UDP, length 38</div></div><div><br></div><div>tcpdump on the ubuntu server</div><div><br></div><div><div>$ sudo tcpdump -nnieth0 host 192.168.0.94 and not port 22</div>
<div>tcpdump: verbose output suppressed, use -v or -vv for full protocol decode<br></div><div>listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes</div><div><br></div><div>11:19:36.013763 IP 192.168.0.94.40554 > 192.168.0.15.69: 16 RRQ "file" netascii<br>
</div><div>11:19:36.018476 IP 192.168.0.15.43112 > 192.168.0.94.40554: UDP, length 38</div><div>11:19:36.891384 IP 192.168.0.94.17500 > 255.255.255.255.17500: UDP, length 155</div><div>11:19:36.891991 IP 192.168.0.94.17500 > 192.168.0.255.17500: UDP, length 155</div>
<div>11:19:41.013686 IP 192.168.0.94.40554 > 192.168.0.15.69: 16 RRQ "file" netascii</div><div>11:19:41.018380 IP 192.168.0.15.50574 > 192.168.0.94.40554: UDP, length 38</div><div>11:19:41.018526 IP 192.168.0.15.43112 > 192.168.0.94.40554: UDP, length 38</div>
<div>11:19:46.013625 IP 192.168.0.94.40554 > 192.168.0.15.69: 16 RRQ "file" netascii</div><div>11:19:46.018241 IP 192.168.0.15.41961 > 192.168.0.94.40554: UDP, length 38</div><div>11:19:46.018483 IP 192.168.0.15.50574 > 192.168.0.94.40554: UDP, length 38</div>
<div>11:19:46.018649 IP 192.168.0.15.43112 > 192.168.0.94.40554: UDP, length 38</div><div>11:19:51.013542 IP 192.168.0.94.40554 > 192.168.0.15.69: 16 RRQ "file" netascii</div><div>11:19:51.018153 IP 192.168.0.15.59041 > 192.168.0.94.40554: UDP, length 38</div>
<div>11:19:51.018778 IP 192.168.0.15.41961 > 192.168.0.94.40554: UDP, length 38</div><div>11:19:51.018821 IP 192.168.0.15.43112 > 192.168.0.94.40554: UDP, length 38</div><div>11:19:51.019003 IP 192.168.0.15.50574 > 192.168.0.94.40554: UDP, length 38</div>
<div>11:19:56.013443 IP 192.168.0.94.40554 > 192.168.0.15.69: 16 RRQ "file" netascii</div><div>11:19:56.018067 IP 192.168.0.15.38812 > 192.168.0.94.40554: UDP, length 38</div><div>11:19:56.018211 IP 192.168.0.15.59041 > 192.168.0.94.40554: UDP, length 38</div>
<div>11:19:56.018531 ARP, Request who-has 192.168.0.15 tell 192.168.0.94, length 46</div><div>11:19:56.018554 ARP, Reply 192.168.0.15 is-at ac:16:2d:79:64:ec, length 28</div><div>11:19:56.018825 IP 192.168.0.15.41961 > 192.168.0.94.40554: UDP, length 38</div>
<div>11:19:56.018873 IP 192.168.0.15.43112 > 192.168.0.94.40554: UDP, length 38</div><div>11:19:56.019056 IP 192.168.0.15.50574 > 192.168.0.94.40554: UDP, length 38</div><div>11:20:01.018171 IP 192.168.0.15.38812 > 192.168.0.94.40554: UDP, length 38</div>
<div>11:20:01.018582 IP 192.168.0.15.59041 > 192.168.0.94.40554: UDP, length 38</div><div>11:20:01.018861 IP 192.168.0.15.41961 > 192.168.0.94.40554: UDP, length 38</div><div>11:20:01.019108 IP 192.168.0.15.50574 > 192.168.0.94.40554: UDP, length 38</div>
</div><div><br></div><div><br></div><div> </div><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 dir="ltr">
<div class="gmail_extra"><div class=""><div></div><div>-- <br></div><div><br></div>Asif Iqbal<br>PGP Key: 0xE62693C5 KeyServer: <a href="http://pgp.mit.edu" target="_blank">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></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>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>