[Nfd-dev] How to avoid Duplicate nonce generation on retrasnmitted interests

[Lan Wang (lanwang)]

Ishita,

In your experiment, does the Interest with the same nonce come from the same face?  If the duplicate nonce comes from the same face, NFD should not generate a NACK duplicate according to the design mentioned in https://redmine.named-data.net/issues/3888/).  You may want to report it on Redmine and continue discussion there.

Regarding  https://redmine.named-data.net/issues/3888/, I think there is more work on that issue.  Now that the ad hoc face has been implemented, we are observing the problem mentioned in Junxiao’s note #8 in our experiments.  This needs to be fixed.

Lan

On Aug 8, 2019, at 5:09 PM, Ishita Dasgupta via Nfd-dev <nfd-dev at lists.cs.ucla.edu<mailto:nfd-dev at lists.cs.ucla.edu>> wrote:

Hi All,

I am running NDN on top of NFD 0.6.2
On the consumer end, I have the same interface drop packets/connection with NACK duplicate messages. On further investigation, I figured that some of the interests with interrupted connections generate "same" nonce for same interest packets (probably retransmitted) and whenever that happens, the connection over NFD completely drops.
I came across this conversation thread<https://redmine.named-data.net/issues/3888/> and found that this was a design flaw that was corrected in v0.6 but I still came across this in 0.6.2

I was wondering if I could talk to someone regarding the issue and my workaround it.

Regards,
Ishita Dasgupta

_______________________________________________
Nfd-dev mailing list
Nfd-dev at lists.cs.ucla.edu<mailto: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/20190809/7d621e70/attachment.html>