[Nfd-dev] [EXT] ndnping error report

Ishita Dasgupta ishita.dasgupta at gmail.com
Fri May 1 17:05:10 PDT 2020


Hi Junxiao

Done. Here it is.
Also attached the log for the failed sequence number interests.

Regards,
Ishita Dasgupta

On Fri, May 1, 2020 at 7:43 PM Junxiao Shi <shijunxiao at email.arizona.edu>
wrote:

> Hi Ishita
>
> The tcpdump trace is generated incorrectly. I need pcap format.
> Use this command:
> sudo tcpdump -i eth1 -w 1.pcap "(ether proto 0x8624) or (tcp port 6363) or
> (udp port 6363) or (udp port 56363)"
> Substitute eth1 with the network interface name between your two nodes.
>
> For NFD logs, please only include the current run, and delete anything
> from previous runs.
>
> Yours, Junxiao
>
> On Fri, May 1, 2020 at 7:38 PM Ishita Dasgupta <ishita.dasgupta at gmail.com>
> wrote:
>
>> *External Email*
>> Hi Junxiao,
>>
>> Here is all of them.
>> Also, attaching the failed sequence numbers so that its easier to trace
>> from the log.
>> Because everytime I start and stop the nfd, "*journalctl -u nfd*"
>> logging seems to retain the prior sessions as well. Is there a way to look
>> at the most current nfd session only?
>>
>> Regards,
>> Ishita Dasgupta
>>
>> On Fri, May 1, 2020 at 7:09 PM Junxiao Shi <shijunxiao at email.arizona.edu>
>> wrote:
>>
>>> Hi Ishita
>>>
>>> Please reply-all with the following so that I can help you.
>>>
>>>    - tcpdump capture on the network interface between consumer and
>>>    producer node
>>>    - reduce NFD loglevel to
>>>       - default_level WARN
>>>       - Forwarder DEBUG
>>>       - BestRouteStrategy2 DEBUG
>>>       - RibManager DEBUG
>>>       - FibManager DEBUG
>>>
>>>
>>>
>>> Yours, Junxiao
>>>
>>> On Fri, May 1, 2020 at 3:48 PM Ishita Dasgupta via Nfd-dev <
>>> nfd-dev at lists.cs.ucla.edu> wrote:
>>>
>>>> *External Email*
>>>> System information: Ubuntu 18.04
>>>> GCC: 7.4.0
>>>> NFD: 0.7.0
>>>>
>>>> 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.
>>>> Can any body help me understand why? I have added the nfd
>>>> logs(producer-nfdserver.log, consumer-nfd.log) on in this email.
>>>>
>>>> Also attached is an image of the ndnping client log
>>>>
>>>>
>>>> Regards,
>>>> Ishita Dasgupta
>>>>
>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20200501/1d7818c3/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 1.pcap
Type: application/octet-stream
Size: 283 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20200501/1d7818c3/attachment-0003.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nfdclient.log
Type: application/octet-stream
Size: 94905 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20200501/1d7818c3/attachment-0004.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nfdservers.log
Type: application/octet-stream
Size: 89948 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20200501/1d7818c3/attachment-0005.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sequencenumbers.png
Type: image/png
Size: 269567 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20200501/1d7818c3/attachment-0001.png>


More information about the Nfd-dev mailing list