[Nfd-dev] Enable Incoming Face Indication feature

[Nick Gordon]

I've just checked in the current NFD head (6daf2a39f54dfc1a85e9cb80535afb2239e4972a) and I only see four places where I think this tag is 
used, and all are in the forwarder:


daemon/fw/forwarder.cpp:81

daemon/fw/forwarder.cpp:201

daemon/fw/forwarder.cpp:275

daemon/fw/forwarder.cpp:386


It doesn't look like you should have to enable anything, particularly. Additionally, the commit adding this feature was in 2015, so there 
should be no way that you don't have it, regardless of what you're using. Generally, it looks like NFD will set that field all the time. 
It's not clear what your problem is.


-Nick


On 10/25/17 13:55, Muktadir R Chowdhury (mrchwdhr) wrote:
>
> 	
> This sender failed our fraud detection checks and may not be who they appear to be. Learn about spoofing <http://aka.ms/LearnAboutSpoofing>
> 	Feedback <http://aka.ms/SafetyTipsFeedback>
>
> Hi all,
>
> I am trying to use CertificateFetcherDirectFetch 
> (https://github.com/named-data/ndn-cxx/blob/master/src/security/v2/certificate-fetcher-direct-fetch.hpp)
>
> which is using IncomingFaceId of the data to sent certificate-interest.
> My question is how to enable IncomingFaceId feature (https://redmine.named-data.net/projects/nfd/wiki/NDNLPv2) in nfd?
>
> Muktadir
>
>
> _______________________________________________
> Nfd-dev mailing list
> Nfd-dev at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20171026/52a7e4fe/attachment.html>