Task #1444
closed
Hub Discovery test scenario
Added by Beichuan Zhang over 10 years ago.
Updated over 10 years ago.
Category:
Integration Tests
Description
Topology
B---A---R---D
A,B,D are NDN hosts.
R is an IP router and is not NDN host; R does not forward multicast packets.
Script is invoked on host A. It can control other hosts via ssh.
- On host A,
- start NFD
- start
ndn-autoconfig-server
, set FaceUri to udp4://10.63.18.1
- start
bind
to serve these records
_ndn._udp.autoconfig-test.named-data.net
=> 10.63.18.2
_ndn._udp.autoconfig-test.tmp._homehub._autoconf.named-data.net
=> 10.63.18.3
- On host B
- invoke
ndnsec-keygen /tmp/autoconfig-test | ndnsec-install-cert -
- in
/etc/resolv.conf
, set DNS Server to A's IP address on A-B link, set DNS search domain to autoconfig-test.named-data.net
(stage 2 would work, but autoconfig tool should try stage 1 first)
- start NFD
- invoke
nfd-autoconfig
- execute
nfd-status -f
,
- search output for
10.63.18.1
, fail if not found.
- search output for
10.63.18.2
, fail if found.
- search output for
10.63.18.3
, fail if found.
- stop NFD
- On host D, invoke
ndnsec-keygen /tmp/autoconfig-test | ndnsec-install-cert -
- On host D,
- in
/etc/resolv.conf
, set DNS Server to A's IP address on A-R link, set DNS search domain to autoconfig-test.named-data.net
- start NFD
- invoke
nfd-autoconfig
- execute
nfd-status -f
,
- search output for
10.63.18.1
, fail if found.
- search output for
10.63.18.2
, fail if not found.
- search output for
10.63.18.3
, fail if found.
- stop NFD
- On host D,
- in
/etc/resolv.conf
, set DNS Server to A's IP address on A-R link, set DNS search domain to autoconfig-test-none.named-data.net
- start NFD
- invoke
nfd-autoconfig
- execute
nfd-status -f
,
- search output for
10.63.18.1
, fail if found.
- search output for
10.63.18.2
, fail if found.
- search output for
10.63.18.3
, fail if not found.
- stop NFD
Files
- Status changed from New to In Progress
Do we want automated script here as in #1388?
Ultimately, every test scenario should be automated.
I need some more time to verify this tool. this is my current status:
Step 1:
ndn-autoconfig-server fails to register a FaceMgmt uri. I need more time to debug it to understand if I'm doing something wrong here.
Step 2 (After setting: search ndnsim.net):
I get the next uri: udp://spurs.cs.ucla.edu:1395, but whenever I try to connect to this uri, I get:
ERROR: Failed to create face: : Unauthorized command (code: 403)
Step 3:
Is there anyway to test it using a tmp certificate?
For step 3, just create a self-signed certificate with the "correct" name.
- % Done changed from 0 to 80
All stages passed.
I suspect that we need to set a larger timeout to ndn-autoconfig-server, what do you think?
80% represents manual tests as well as a basic script. I still need to modify the script to use the integration framework.
Hila, is it a typo about the port number returned by DNS query (1395) or is it that you're getting in the script? The port configured in DNS entry is 6363.
There is no need to modify timeout for the server. The current timeout is long enough (~4 seconds).
- Subject changed from Test Hub Discovery tool to Hub Discovery test scenario
- Description updated (diff)
Alex, it's not a typo... it's a bug. be16toh is missing. I'll fix it now.
I actually already use be16toh, but I'm taking the port number at the wrong place...
After solving #1550, I get:
Stage2:
Stage 1: Trying multicast discovery...
Timeout
Stage 2: Trying DNS query with default suffix...
about to connect to: udp://spurs.cs.ucla.edu:6363
Successfully created face: ControlParameters(FaceId: 45, Uri: udp://spurs.cs.ucla.edu:6363, )
Stage 3:
Stage3: About to query for a home router: _ndn._udp.hila.wustl.edu.ndn._homehub._autoconf.named-data.net
about to connect to: udp://momcat.arl.wustl.edu:6363
Successfully created face: ControlParameters(FaceId: 43, Uri: udp://momcat.arl.wustl.edu:6363, )
I am ready to push the changes if that looks OK.
Sorry, I can't modify the previous comment and it looks bad...
Stage2:
Stage 1: Trying multicast discovery...
Timeout Stage
2: Trying DNS query with default suffix...
about to connect to: udp://spurs.cs.ucla.edu:6363 Successfully created face: ControlParameters(FaceId: 45, Uri: udp://spurs.cs.ucla.edu:6363, )
Stage 3:
Stage3: About to query for a home router: ndn.udp.hila.wustl.edu.ndn.homehub.autoconf.named-data.net
about to connect to:
udp://momcat.arl.wustl.edu:6363 Successfully created face: ControlParameters(FaceId: 43, Uri: udp://momcat.arl.wustl.edu:6363, )
- Target version changed from v0.1 to v0.2
- Description updated (diff)
I'm correcting a mistake in the spec.
Stage 2 and 3 testing must be done on host D, because A and D cannot talk over multicast.
- Description updated (diff)
Correcting another mistake.
Host B should be configured such that Stage 1, 2, and 3 can all work, but ndn-autoconfig
tool should try stage 1 first.
upload patchset 6 verification logs
- Target version changed from v0.2 to v0.3
- Status changed from In Progress to Closed
- Start date deleted (
04/03/2014)
- % Done changed from 80 to 100
This Task is finally complete after being open for almost 3 months.
Also available in: Atom
PDF