Task #1409
closedInterest loop test scenario
Description
Topology:
->A---->B--
| |
-----C<----
It's okay to have A,B,C on same Ethernet switch and in same IP subnet, but multicast must be disabled. The tunnels will have this logical topology.
All are NDN nodes.
Script is invoked on host A. Script should control other hosts over ssh.
Arguments: strategy under test.
Steps:
- Start NFD on A,B,C.
- On host A, create UDP face to host B, and add nexthop for
ndn:/test-loop
toward this face.
On host B, create UDP face to host C, and add nexthop forndn:/test-loop
toward this face.
On host C, create UDP face to host A, and add nexthop forndn:/test-loop
toward this face. - On every host, set strategy of
ndn:/test-loop
to strategy under test. - On host A, execute ndn-traffic-client to send 100 Interests to
ndn:/test-loop/A/<random>
. - On every host, execute nfd-status to see face counters.
Fail if NInInterests or NOutInterests counter of a UDP face is greater than 200.
Script can assume integrated test suite is cloned to all hosts, necessary programs are installed and accessible in $PATH, and current user can ssh to other hosts and has sudo privilege.
Updated by Yi Huang over 10 years ago
- Status changed from New to In Progress
- Assignee set to Yi Huang
Updated by Yi Huang over 10 years ago
On step 5, do you mean "nInInterests" or something else?
Updated by Yi Huang over 10 years ago
To find out the counter for the udp face, should I look at the nInInterests and nOutInterests? I think these are for the whole NFD. what does the counters following each face mean? Can you help me how to interpret this:
counters={in={0i 0d} out={6i 0d}}
Or should I look at the two values counting interests for NFD?
Updated by Yi Huang over 10 years ago
- Status changed from In Progress to Code review
- % Done changed from 0 to 90
Updated by Yi Huang over 10 years ago
- Status changed from Code review to Closed
- % Done changed from 90 to 100