<div dir="ltr"><div>Hi Ishita</div><div><br></div><div>Only the first Interest appeared on the wire. Other Interests are lost somewhere on the client node. It's probably some bug in UDP
multicast
implementation.</div><div>Try a different face transport type, such as Ethernet multicast or UDP unicast.</div><div><br></div><div>Yours, Junxiao</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, May 1, 2020 at 8:06 PM Ishita Dasgupta <<a href="mailto:ishita.dasgupta@gmail.com">ishita.dasgupta@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><p style="text-align:center"><font color="red"><strong>External Email</strong><br></font></p><div dir="ltr"><div style="font-family:tahoma,sans-serif">Hi Junxiao</div><div style="font-family:tahoma,sans-serif"><br></div><div style="font-family:tahoma,sans-serif">Done. Here it is.<br>Also attached the log for the failed sequence number interests.<br><br></div><div><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><font face="tahoma, sans-serif"><span style="font-size:12.8px">Regards,</span><br style="font-size:12.8px"><span style="font-size:12.8px">Ishita Dasgupta</span><br style="font-size:12.8px"></font></div></div></div></div></div></div></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, May 1, 2020 at 7:43 PM Junxiao Shi <<a href="mailto:shijunxiao@email.arizona.edu" target="_blank">shijunxiao@email.arizona.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr">Hi Ishita<div><br></div><div>The tcpdump trace is generated incorrectly. I need pcap format.<br></div><div>Use this command:</div><div><font face="monospace">sudo tcpdump -i eth1 -w 1.pcap "(ether proto 0x8624) or (tcp port 6363) or (udp port 6363) or (udp port 56363)"</font></div><div>Substitute eth1 with the network interface name between your two nodes.</div><div><br></div><div>For NFD logs, please only include the current run, and delete anything from previous runs.</div><div><br></div><div>Yours, Junxiao</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, May 1, 2020 at 7:38 PM Ishita Dasgupta <<a href="mailto:ishita.dasgupta@gmail.com" target="_blank">ishita.dasgupta@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><p style="text-align:center"><font color="red"><strong>External Email</strong><br></font></p><div dir="ltr"><div style="font-family:tahoma,sans-serif">Hi Junxiao, <br><br></div><div style="font-family:tahoma,sans-serif">Here is all of them. <br>Also, attaching the failed sequence numbers so that its easier to trace from the log. <br>Because everytime I start and stop the nfd, "<b>journalctl -u nfd</b>" logging seems to retain the prior sessions as well. Is there a way to look at the most current nfd session only?<br><br></div>
<div><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><font face="tahoma, sans-serif"><span style="font-size:12.8px">Regards,</span><br style="font-size:12.8px"><span style="font-size:12.8px">Ishita Dasgupta</span><br style="font-size:12.8px"></font></div></div></div></div></div></div></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, May 1, 2020 at 7:09 PM Junxiao Shi <<a href="mailto:shijunxiao@email.arizona.edu" target="_blank">shijunxiao@email.arizona.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Hi Ishita</div><div><br></div><div>Please reply-all with the following so that I can help you.</div><div><ul><li>tcpdump capture on the network interface between consumer and producer node</li><li>reduce NFD loglevel to</li><ul><li>default_level WARN</li><li>Forwarder DEBUG</li><li>BestRouteStrategy2 DEBUG</li><li>RibManager DEBUG</li><li>FibManager DEBUG</li></ul></ul></div><div><br></div><div><br></div><div>Yours, Junxiao</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, May 1, 2020 at 3:48 PM Ishita Dasgupta via Nfd-dev <<a href="mailto:nfd-dev@lists.cs.ucla.edu" target="_blank">nfd-dev@lists.cs.ucla.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><p style="text-align:center"><font color="red"><strong>External Email</strong><br></font></p><div dir="ltr"><div style="font-family:tahoma,sans-serif">System information: Ubuntu 18.04</div><div style="font-family:tahoma,sans-serif">GCC: 7.4.0</div><div style="font-family:tahoma,sans-serif">NFD: 0.7.0</div><div style="font-family:tahoma,sans-serif"><br></div><div style="font-family:tahoma,sans-serif">After having started nfd using systemctl, and adding routes via nfdc route add, I am trying to perform a simple ndnping test that fails after one successful interest received. Looking at the nfd logs, it seems like the consecutive interests are sent by the consumer but not received by the producer. <br>Can any body help me understand why? I have added the nfd logs(producer-nfdserver.log, consumer-nfd.log) on in this email.<br><br>Also attached is an image of the ndnping client log<br><br><br></div><div><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><font face="tahoma, sans-serif"><span style="font-size:12.8px">Regards,</span><br style="font-size:12.8px"><span style="font-size:12.8px">Ishita Dasgupta</span><br style="font-size:12.8px"></font></div></div></div></div></div></div></div></div></div></div>
</blockquote></div></div>
</blockquote></div>
</blockquote></div></div>
</blockquote></div>
</blockquote></div></div>