NFD

I need a couple of clarifications:

1. Step 2 requires best-route while step 3 requires best-route v1. Does nfd support both? I thought that best-route2 is what we refer as the current best-route strategy, so what is best-route v1?
2. Whenever the procedure requires setting the link delay - can I assume a specific interface is used (such as eth0/1) or should I add it as a configurable parameter (such as in multi-host.conf)?

Answer to note-6:

NFD supports both best-route and best-route v1. To select best-route v1: nfdc set-strategy /namespace /localhost/nfd/strategy/best-route/%FD%01.

You can neither hard-code a specific interface nor add it as a configuration parameter.
Instead, parse the output of ip addr with awk or sed or grep, and find which interface has $IP4_B1.
The script should be able to handle the situation when $IP4_B1 is a proper prefix of an IP on another interface; for example: "eth1 10.0.0.1; eth2=10.0.0.11; $IP4_B1=10.0.0.1", the script should not find eth2.

I used PyNDN2 to implement the script that sends and retransmits Interests as required in steps: 6,7,10,12.

Do not add dependency on PyNDN. PyNDN code is not reviewed by NFD developers.

Instead, use ndn-cxx for the consumer program.

OK. What would be the appropriate way to build the consumer? Can I add it as the initial test step? Or should I support it as part of the 'install_helpers' step?

OK. What would be the appropriate way to build the consumer? Can I add it as the initial test step? Or should I support it as part of the 'install_helpers' step?

Talk to Eric. He's doing something similar in #1942.

After discussing it with Eric we suggest one of the following options:

1. Adding new apps to a new 'tools' directory, possibly under install_helpers, 
   and supporting a single build system that builds all apps during the initialization phase.

2. Having each test support its own consumer/producer apps as part of the test run.

I personally think the first choice is preferred, but open to hear other suggestions.
Any thoughts?

I prefer the first option in note-13.
For simplicity:

• use a Makefile
• keep each program to a single cpp file when feasible
• in each program source code, insert a comment to indicate which test case(s) uses this program

The above rules should appear in tools/README.

Note that infoedit should not be treated in the same way; #3387 is still valid.

Two tests fail according to the results attached in note-16.

* test_remote_register
* test_nack

First, is test_remote_register expected to fail?

Second, test_nack fails on stage #10 since there is no nack coming back (both Interests timeout). Since it is working on my environment, I wonder whether there is a restriction on configuring delays on Emulab. I don't see any error for those commands so I assume it is something else.
Is it possible to run NFD in higher severity log to check the problem?

is test_remote_register expected to fail?

#3825

Is it possible to run NFD in higher severity log to check the problem?

You may invoke infoedit to edit NFD configuration file and increase log levels. You may even invoke tcpdump to save traffic trace.