[Nfd-dev] Drop Packets NFD - XBee Face

[Junxiao Shi]

Hi Oscar

The TX  fragment the Interest Packets as:
>
>
> 100[30]={81[8]=FFFFFFFFFFFFFFFF,82[1]=00,83[1]=05,80[12]=05310721080A636C69636B69}
>
> 100[30]={81[8]=0000000000000000,82[1]=01,83[1]=05,80[12]=646569610813746573746669}
>
> 100[30]={81[8]=0000000000000001,82[1]=02,83[1]=05,80[12]=6C655F6F726967696E616C5F}
>
> 100[30]={81[8]=0000000000000002,82[1]=03,83[1]=05,80[12]=31090212000A046287BE9A0C}
> 100[21]={81[8]=0000000000000003,82[1]=04,83[1]=05,80[3]=020FA0}
>

This is a correctly encoded NDN Interest (packet format v0.2) in five
NDNLPv2 fragments. I can interpret the L3 packet as:
0531 Interest
  0721 Name
    080A636C69636B6964656961 GenericNameComponent clickideia
    08137465737466696C655F6F726967696E616C5F31 GenericNameComponent
testfime_original_1
  0902 Selectors
    1200 MustBeFresh
  0A046287BE9A Nonce
  0C020FA0 InterestLifetime 4000ms



> The RX is Dropping the packets as show below:
>
> XBee RX Message:
> 100[30]={81[8]=FFFFFFFFFFFFFFFF,82[1]=00,83[1]=05,80[12]=05310721080A636C69636B69}
>

This line is correct.

1558009398.386278 TRACE: [nfd.XBeeTransport]
> [id=256,local=xbee://,remote=xbee://[xbee]] Received: 82 bytes
>

The "82 bytes" is problematic, as we can see there are only 32 bytes in the
NDNLPv2 frame.


> Wire Type = 49
>

I don't know where does this number come from, but this is likely the
problem because it also appears in GenericLinkService's error message.


> TLV LpPacket = 100
>

This is the correct type and is what should be passed to the LinkService.

1558009398.386386 WARNING: [nfd.GenericLinkService]
> [id=256,local=xbee://,remote=xbee://[xbee]] packet parse error
> (unrecognized TLV-TYPE 49): DROP
>

Yours, Junxiao
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20190517/67695d27/attachment.html>