[Nfd-dev] [EXT] IncomingFaceIdTag is null

Shi, Junxiao - (shijunxiao) shijunxiao at arizona.edu
Thu May 21 09:19:10 PDT 2026


Hi Guangyu

ndn6-facemon has IncomingFaceId usage:
https://github.com/yoursunny/ndn6-tools/blob/af7d60160bad1608040ca75b54c24c48e4519f4a/facemon.md
https://github.com/yoursunny/ndn6-tools/blob/af7d60160bad1608040ca75b54c24c48e4519f4a/facemon.cpp

You can try this program to see whether your NFD build supports IncomingFaceId.
You can compare your code to this program to see whether any step is missing.

Yours, Junxiao
________________________________
From: Nfd-dev <nfd-dev-bounces at lists.cs.ucla.edu> on behalf of 郝广宇 <haoguangyu at chorustek.com>
Sent: Wednesday, May 20, 2026 1:18 PM
To: nfd-dev <nfd-dev at lists.cs.ucla.edu>
Subject: [EXT] [Nfd-dev] IncomingFaceIdTag is null


External Email

________________________________
Dear team,
Below, egw and igw implement intranet/extranet access penetration by creating a TCP link between  egw and igw NFD. Now we encounter a problem: igw always gets faceid as 0 when calling `interest.getTag<ndn::lp::IncomingFaceIdTag>`. Therefore, we cannot obtain the faceid of the TCP link between egw and igw from the interest packet. We want to know why `ndn::lp::IncomingFaceIdTag` is not working. We have confirmed that the interest packet is received via the TCP link. Could it be that support for `IncomingFaceIdTag` is disabled in the compilation of NFD or ndn-cxx, or is there another reason? We need this feature to work. Thank you very much!

BR.
GuangYu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20260521/51e01e6b/attachment.htm>


More information about the Nfd-dev mailing list