[Nfd-dev] Troubleshooting interest path

[Davide Pesavento]

Oh I see... I misunderstood your question then. I am not aware of any
traceroute-like tools for NDN.

Thanks,
Davide

On Thu, Sep 8, 2016 at 3:54 PM, Burke, Jeff <jburke at remap.ucla.edu> wrote:

> Hi Davide,
>
>
>
> Yes, but doesn’t this approach require:
>
>
>
> 1) pcap access on each (potential) node in the path (I have this on some
> but not all)
>
> 2) capturing potentially a lot of traffic (if on, say, a testbed node and
> I did have access)
>
> 3) then having to gather all capture records from the various hosts and
> filter on names/nonces
>
>
>
> That’s what I meant by manually instrumenting each node, which I can do
> for some nodes, but not the testbed nodes. It also seems to require a lot
> of instrumentation and post-gathering/-filtering (and access) effort that
> grows quickly as the number of nodes increase.   I guess what I’m looking
> for is whether anyone has returned to work on something that looks a little
> more like traceroute in its usage?
>
>
>
> Thanks,
>
> Jeff
>
>
>
>
>
> *From: *Davide Pesavento <davide.pesavento at lip6.fr>
> *Date: *Thursday, September 8, 2016 at 2:33 AM
> *To: *Jeff Burke <jburke at remap.ucla.edu>
> *Cc: *"nfd-dev at lists.cs.ucla.edu" <nfd-dev at lists.cs.ucla.edu>
> *Subject: *Re: [Nfd-dev] Troubleshooting interest path
>
>
>
> On Thu, Sep 8, 2016 at 7:23 AM, Burke, Jeff <jburke at remap.ucla.edu> wrote:
>
> I doubt my problem is complicated.  But in trying to figure out why this
> doesn’t work, I am curious what the state-of-the-art is for tracing
> Interest/Data exchange?  If I want to see whether an Interest expressed by
> Consumer hits the Repo, is my only solution to watch the logs in NFD2 (or
> for anything potentially in the path, in a larger example), keep track of
> which face Repo corresponds to and see if things are forwarded?     Repo-ng
> doesn’t seem to say/log much itself.. but more generally the question here
> is about whether there are techniques to do Interest/Data packet tracing
> without manually- or custom- instrumenting each potential node in the
> path(s).
>
>
>
>
>
> Hi Jeff,
>
>
>
> You can use ndndump, or you can capture a trace in pcap format and then
> read it with Wireshark + the NDN dissector. Both are available in the
> ndn-tools repository.
>
>
>
> Thanks,
>
> Davide
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20160908/2da75a28/attachment.html>