NFD

I don't think is a problem of a missing name field the wire encode. I call the name "prefix", and it's corresponding member variable (m_prefix) is indeed added.

I'm playing around with the nfd-status tool itself and I think that's where the problem lies. In afterFetchFibEnumerationInfo() (~ line 206, I have some debugging additions), the code uses a Block constructor with its length verification disabled. Enabling length verification results in the constructor failing due to a mismatch of the buffer length (49 bytes) with the TLV length (19 bytes). My understanding of this constructor is that it's trying to convert the entire result buffer into a single block. Is that correct?

The result is successfully parsed if I use the Block(uint8_t*, max size) constructor instead and nfd-status runs without issue.

Here's the output. I think there's a different, but related, problem:

$ NFD=1 nfdc create udp4://10.0.0.10
Face creation succeeded: ForwardingEntry(FaceID: 3, Uri: udp4://10.0.0.10)
$ NFD=1 nfdc add-nexthop /example 3
Nexthop insertion succeeded: ForwardingEntry(Prefix: /example, FaceID: 3, Cost: 0, Strategy: /, )
$ NFD=1 nfd-status -b
FIB:
  /example nexthops={faceid=3 (cost=0)}
  /example nexthops={faceid=3 (cost=0)}
  /example nexthops={faceid=3 (cost=0)}

Steve DiBenedetto wrote:

I don't think is a problem of a missing name field the wire encode. I call the name "prefix", and it's corresponding member variable (m_prefix) is indeed added.

I'm playing around with the nfd-status tool itself and I think that's where the problem lies. In afterFetchFibEnumerationInfo() (~ line 206, I have some debugging additions), the code uses a Block constructor with its length verification disabled. Enabling length verification results in the constructor failing due to a mismatch of the buffer length (49 bytes) with the TLV length (19 bytes). My understanding of this constructor is that it's trying to convert the entire result buffer into a single block. Is that correct?

The result is successfully parsed if I use the Block(uint8_t*, max size) constructor instead and nfd-status runs without issue.

I'll check nfd-status. The constructor must use the current version (this one is thread-safe). There could be more bugs in this constructor...

Corrected my debugging use of the Block(uint8_t*, max size) constructor and I now get (what I think is) the correct output:

FIB:
  /example nexthops={faceid=3 (cost=0)}
  /localhost/nfd nexthops={faceid=1 (cost=0)}