[Mini-NDN] Failed to add a route towards the advertised content prefix

[JIACHENG HOU]

Hi Saurab,

Thanks for your reply!

Yes, it works well in small network topology. In the network topology that contains 50 nodes, sleep 10 minutes is enough for all nodes to add the route.

I will try the dummy key chain patch to see whether it can work well with a larger network topology.

Best wishes,
Jiacheng
________________________________
From: Saurab Dulal (sdulal) <sdulal at memphis.edu>
Sent: Friday, June 18, 2021 2:08 PM
To: mini-ndn at lists.cs.ucla.edu; JIACHENG HOU
Subject: Re: Failed to add a route towards the advertised content prefix

Hi Jiacheng,

First thing, you dont need this _ hyperbolic-state=off  radius=0.0 angle 0.0  if you are not using hyperbolic routing. Your topology can just look like

....................
[nodes]
a:
b:
..

[links]
a:b delay=10ms

.....................

Second, to speed up the routing convergence process, try the dummy key chain patch<https://gerrit.named-data.net/c/mini-ndn/+/6175>, you can install it by running this command: "./install -p".

Make sure you pull the latest Mini-NDN, we have recently merged a few patches related to topology and experiment.

If you are seeing no routes, then it's highly likely the route computation was not completed by the time your experiment started. After you advertise the producer prefix, make sure you sleep enough. Are you getting good results with small topologies?

Best,

Saurab

________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of JIACHENG HOU via Mini-NDN <mini-ndn at lists.cs.ucla.edu>
Sent: Friday, June 18, 2021 12:21 AM
To: mini-ndn at lists.cs.ucla.edu <mini-ndn at lists.cs.ucla.edu>
Subject: [Mini-NDN] Failed to add a route towards the advertised content prefix

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and trust the content is safe.


Hi Mini-ndn team,



I run Mini-NDN with a customized tree topology which contains 65 nodes. All nodes in the network have “hyperbolic-state=off radius=0.0 angle=0.0”. The screenshot below shows part of the nodes in the topology.

[A picture containing text, window, keyboard  Description automatically generated]



In the network, the root node is the producer and it uses nlsrc to advertise the content prefix. After the root node advertises the content prefix, I waited around 20 minutes to make sure all nodes in the network create a route towards the prefix. After that, the leaf node starts requesting the content. However, there are usually 2 or 3 ndn nodes that are unable to add a route towards the prefix. I checked the nfd log and it shows "NoRoute" for the content prefix.



I am thinking about why this happens and is there a way to solve it?



Besides, I checked the memory usage and it shows there is still available memory space.



Thank you very much for your help.



Best wishes,

Jiacheng


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20210618/b1139537/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 101357 bytes
Desc: image001.png
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20210618/b1139537/attachment-0001.png>