[Nfd-dev] additional data between ethernet header and ndn header

[Junxiao Shi]

Hi Salvatore

The payload of the first packet in the pcap
is 50:37:51:08:00:00:00:00:00:00:00:11:54:2b:05:29:07:21:08:10:70:34:73:6f:66:74:77:61:72:65:73:77:69:74:63:68:08:0d:73:61:79:68:65:6c:6c:6f:77:6f:72:6c:64:0a:04:10:f2:e0:8f.
This appears to be NDNLPv1-TLV
<http://redmine.named-data.net/projects/nfd/wiki/NDNLP-TLV> protocol, and
can be interpreted as:

50 37 // NdnlpData
   51 08 // NdnlpSequence
      00 00 00 00 00 00 00 11
   54 2b // NdnlpPayload
      05 29 // Interest
         07 21 // Name
            08 10 // NameComponent
               70 34 73 6f 66 74 77 61 72 65 73 77 69 74 63 68
            08 0d // NameComponent
               73 61 79 68 65 6c 6c 6f 77 6f 72 6c 64
         0a 04 // Nonce
            10 f2 e0 8f

Neither ndndump nor NDN dissector for Wireshark supports NDNLPv1-TLV.
In latest NFD, NDNLPv1-TLV is deprecated and replaced by NDNLPv2
<http://redmine.named-data.net/projects/nfd/wiki/NDNLPv2>, which will be
supported by NDN dissector for Wireshark in #3197
<http://redmine.named-data.net/issues/3197>.

Yours, Junxiao

On Mon, Dec 14, 2015 at 3:52 PM, Salvatore Signorello <
salvatore.signorello at uni.lu> wrote:

> Hi Alex,
>
> the pcap is in attach. I'm not using the latest version of the software
> tools and daemon, so if you either don't see the issue or are not able to
> reproduce it. I'll likely update the ndn software suite before asking you
> for more support.
>
> Thanks,
> Salvatore
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20151215/d90f3814/attachment.html>