How to tell distance vector to advertise a route to its neighbors?

[Gitopolis]

Maybe it's a lack of documentation, but I don't understand how to propagate a route to other routers in the network.
This is what I do:

• start the daemons
  router 1:

  sudo ndnd daemon router1.yml
  

  router2:

  sudo ndnd daemon router2.yml
  

• both routers have an empty list of neighbors now, so I add them
  router1:

  ndnd dv link-create udp://<ip4>:6363
  ndnd dv link-create udp://[<ip6>]:6363
  

  router2 already have router1 as a neighbor from previous command, so there's no need to add it
• start pingserver on router1

  ndnd pingserver /ndn/qwe
  

• at this point I expect /ndn/qwe route to appear on router2's route list, but it is not there, and the pings from router2 to /ndn/qwe timeouted.

router1 route table:

prefix=/localhost/nlsr nexthop=3 origin=nlsr cost=0 flags={child-inherit} expires=never
prefix=/ndn/router1/32=DV nexthop=3 origin=nlsr cost=0 flags={child-inherit} expires=never
prefix=/ndn/32=DV/32=PFS nexthop=3 origin=nlsr cost=0 flags={child-inherit} expires=never
prefix=/ndn/32=DV/32=PFS nexthop=6 origin=nlsr cost=0 flags={child-inherit} expires=never
prefix=/ndn/qwe/ping nexthop=7 origin=app cost=0 flags={child-inherit} expires=never
prefix=/ndn/router2/32=DV nexthop=6 origin=nlsr cost=1 flags={child-inherit} expires=never
prefix=/ndn/router2/32=DV/KEY nexthop=6 origin=nlsr cost=0 flags={child-inherit} expires=never
prefix=/localhop/ndn/router2/32=DV nexthop=6 origin=nlsr cost=0 flags={child-inherit} expires=never
prefix=/localhop/ndn/router1/32=DV/32=ADV nexthop=3 origin=nlsr cost=0 flags={child-inherit} expires=never
prefix=/localhop/ndn/32=DV/32=ADS nexthop=3 origin=nlsr cost=0 flags={child-inherit} expires=never
prefix=/localhop/ndn/32=DV/32=ADS/32=PSV nexthop=6 origin=nlsr cost=0 flags={child-inherit} expires=never
prefix=/localhop/ndn/32=DV/32=ADS/32=ACT nexthop=6 origin=app cost=0 flags={child-inherit} expires=never

router2 route table:

prefix=/localhost/nlsr nexthop=3 origin=nlsr cost=0 flags={child-inherit} expires=never
prefix=/ndn/router1/32=DV nexthop=4 origin=nlsr cost=1 flags={child-inherit} expires=never
prefix=/ndn/router1/32=DV/KEY nexthop=4 origin=nlsr cost=0 flags={child-inherit} expires=never
prefix=/ndn/router2/32=DV nexthop=3 origin=nlsr cost=0 flags={child-inherit} expires=never
prefix=/ndn/32=DV/32=PFS nexthop=3 origin=nlsr cost=0 flags={child-inherit} expires=never
prefix=/ndn/32=DV/32=PFS nexthop=4 origin=nlsr cost=0 flags={child-inherit} expires=never
prefix=/localhop/ndn/router1/32=DV nexthop=4 origin=nlsr cost=0 flags={child-inherit} expires=never
prefix=/localhop/ndn/router2/32=DV/32=ADV nexthop=3 origin=nlsr cost=0 flags={child-inherit} expires=never
prefix=/localhop/ndn/32=DV/32=ADS nexthop=3 origin=nlsr cost=0 flags={child-inherit} expires=never
prefix=/localhop/ndn/32=DV/32=ADS/32=ACT nexthop=7 origin=app cost=0 flags={child-inherit} expires=never
prefix=/localhop/ndn/32=DV/32=ADS/32=PSV nexthop=4 origin=nlsr cost=0 flags={child-inherit} expires=never

If I start pingserver on /ndn/32=DV/32=PFS/qwe instead of /ndn/qwe, then I receive interest and data, so default multicast strategy works. But how to advertise the routes?

[pulsejet]

You need to specify the --expose flag to pingserver (available with v1.5.2)

ndnd pingserver --expose /my/prefix

Internally, this uses the client origin for the prefix registration, which is propagated to global routing.

[Gitopolis]

Thank you! I see that you can register the route by sending a specific interest to a management face. I wonder where I can read more about this.
I might want to have a separate unix socket for management, so I guess I'll have to send this command myself. Just want to understand this system better.

[pulsejet]

NDNd implements the NFD management protocol. See section 6 at https://irl.cs.ucla.edu/data/files/techreports/ndn0021-10.pdf
Every "command" is a signed interest prefixed with /localhost/nfd
I'm not sure where the spec is maybe @yoursunny can help

I might want to have a separate unix socket for management

I'm not against this idea but it may be unnecessary. The demultiplexing is already done using the name prefix mentioned above, and only local faces are allowed to do this.

[Pesa]

Spec: https://redmine.named-data.net/projects/nfd/wiki/Management

[Pesa]

NDNd implements the NFD management protocol. See section 6 at https://irl.cs.ucla.edu/data/files/techreports/ndn0021-10.pdf

Latest version: https://named-data.gitlab.io/TR-NDN-0021-NFD-dev-guide/ndn-0021-nfd-guide.pdf

[Gitopolis]

Thank you all for the useful links, I think I understand it a little bit better now. I still have a question though: Is it possible to tell ndnd router to readvertise every new route (maybe with some specific prefix) that appears locally? Doing it explicitly from an application itself, or from some external manager feels a bit clunky