Project

General

Profile

Actions

Task #1296

closed

Task #1294: autoconfig: discover NDN router

HUB discovery producer

Added by Junxiao Shi over 10 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Normal
Category:
Tools
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
3.00 h

Description

Implement a producer app that publishes Data for NDN HUB discovery procedure.


Related issues 2 (0 open2 closed)

Blocked by NFD - Task #1193: HUB discovery procedureClosedAlex Afanasyev01/31/2014

Actions
Blocks NFD - Task #1295: HUB discovery clientClosedHila Ben Abraham

Actions
Actions #1

Updated by Hila Ben Abraham over 10 years ago

  • Status changed from New to In Progress
Actions #2

Updated by Hila Ben Abraham over 10 years ago

Just making sure... this producer responds only to the first stage of the protocol. Stages 2 & 3 should be answered by the DNS server (task #1297?)

Also, can you please elaborate on the data response? ("The value of this block is the URI for the HUB, preferably a UDP tunnel").

Actions #3

Updated by Alex Afanasyev over 10 years ago

The published value should be just a string, containing face URI. Like

udp://hostname.domain

or

udp://192.168.2.1:6363

You don't need to parse or configure these URIs. They should be directly configured by the node operator (e.g., as a command-line argument).

Actions #4

Updated by Junxiao Shi over 10 years ago

Payload is not "just a string". It’s a FaceMgmt URI wrapped in Uri TLV-BLOCK.

Having a TLV-BLOCK is useful, because additional fields may be added in the future.

The tool doesn’t need to construct the FaceUri by itself. It could read it from a command line argument.

Actions #5

Updated by Hila Ben Abraham over 10 years ago

  • % Done changed from 0 to 90

I'm having problems testing the program since the producer fails to connect to the daemon. nfd daemon crashes and according to the gdb bt, it's the sign method that throws the exception. Can it be that there is something wrong with my certificates?

users-MacBook-Pro:NFD user$ ndnsec-ls-identity -C
* /tmp/hila
  +->* /tmp/hila/ksk-1394415714
       +->* /tmp/hila/KEY/ksk-1394415714/ID-CERT/%FD%FF%FF%FF%FF%D1%86?%0A
Actions #6

Updated by Junxiao Shi over 10 years ago

  1. configure ndn-cpp-dev with flag --without-osx-keychain
  2. recompile and install ndn-cpp-dev
  3. rm -rf $HOME/.ndnx
  4. ndnsec-keygen - | ndnsec-install-cert -
  5. export NFD=1

If you are unsure whether it's a problem with your producer, test with ndn-tlv-ping first.

Actions #7

Updated by Hila Ben Abraham over 10 years ago

Thank you.

Still having the same problem. ndnpingserver results in the same nfd crash (used to work before). I will try to debug it now to see if I can find a problem with my set up.

Actions #8

Updated by Junxiao Shi over 10 years ago

Producer crashing is similar to Bug #1351, which is fixed now. Is your producer still causing NFD crash?

Actions #9

Updated by Hila Ben Abraham over 10 years ago

I'll have to go back and test it on my mac. (I switched to use my ubuntu vm because of this crash)

Actions #10

Updated by Hila Ben Abraham over 10 years ago

  • Status changed from In Progress to Code review
  • % Done changed from 90 to 100
Actions #11

Updated by Hila Ben Abraham over 10 years ago

  • Status changed from Code review to Closed
Actions

Also available in: Atom PDF