[Nfd-dev] Help with NFD FATAL errors

Junxiao Shi shijunxiao at email.arizona.edu
Thu Feb 21 06:34:42 PST 2019


Hi John

It’s caused by malformed packets, plus missing error handling somewhere in
the programs.
Next step: run tcpdump and wait for crash, then inspect each packet
arriving within 100ms of the crash.

Yours, Junxiao

On Thu, Feb 21, 2019 at 09:18 Dehart, John <jdd at wustl.edu> wrote:

>
> I have a node on the NDN Testbed that is getting NFD FATAL errors.
> Here are a couple from last night:
>
> nfd.log.1:Feb 19 23:22:49 vnetlab nfd[1100]: 1550618569.594084 FATAL:
> [nfd.Main] unrecognized TLV-TYPE 240
>
> ——
>
>
> nfd.log.1:Feb 21 00:27:19 vnetlab nfd[16979]: 1550708838.808549 FATAL:
> [nfd.Main] TLV-LENGTH of sub-element of type 21 exceeds TLV-VALUE boundary
> of parent block
>
>
> Any suggestions on what to look for?
>
> John
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20190221/a0b3e186/attachment.html>


More information about the Nfd-dev mailing list