[Ndn-interest] Fwd: Wireshark and NDN
shijunxiao at email.arizona.edu
Fri Feb 27 11:27:03 PST 2015
---------- Forwarded message ----------
From: Anil Jangam <anilj.mailing at gmail.com>
Date: Fri, Feb 27, 2015 at 12:22 PM
Subject: Re: [Ndn-interest] Wireshark and NDN
To: Junxiao Shi <shijunxiao at email.arizona.edu>
Perfect! Nice tut..
On Fri, Feb 27, 2015 at 10:45 AM, Junxiao Shi <shijunxiao at email.arizona.edu>
> Hi Anil
> Did you setup a Route for /name/data prefix toward a non-local udp4 or
> tcp4 face?
> ndndump is only able to capture NDN-TLV traffic over IPv4-UDP or IPv4-TCP
> If traffic is over IPv6 tunnels or WebSocket or UNIX faces, ndndump won't
> see them.
> See this tutorial on how to setup routes:
> Yours, Junxiao
> On Fri, Feb 27, 2015 at 11:31 AM, Anil Jangam <anilj.mailing at gmail.com>
>> Hi Junxiao,
>> Thanks for reply. I started ndndump as follows. by default it monitors
>> the eth0 (which is correct interface).
>> sudo ndndump -v
>> ndndump: listening on eth0
>> ndndump: pcap_filter = (ether proto 0x8624) || (tcp port 6363) || (udp
>> port 6363)
>> Later, I am doing a ndnping from same host for some random name prefix to
>> test the dump utility, but I do not see any activity.
>> ndnping ndn:/name/data
>> === Pinging ndn:/name/data ===
>> Timeout From ndn:/name/data - Ping Reference = 8667669
>> Timeout From ndn:/name/data - Ping Reference = 8667670
>> Timeout From ndn:/name/data - Ping Reference = 8667671
>> I am not sure what I am missing. Can you please comment? My larger goal
>> is to get the ChronoChat application running on my testbed.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ndn-interest