[Mini-NDN] Issues with NACKs

[Andre]

Hi


I forgot to mention the NLSR sleep though I did try a few different 
values for it, between 40 and 200 seconds. Going lower than that did 
make it worse, but in that range it does not make much difference.


Testing a bit further now, it seems that the probability of getting a 
NACK increased over time, pretty much all hosts got the data in the 
first few transmissions and then started getting more and more NACKs.


I tested some producer-consumer pairs in the CLI after the script had 
run, and there does not seem to be an issue with connectivity between 
the hosts, even in the cases where there were NACKs. Is there another 
way to test it, or is this method right?


I attached the .conf topology file I'm using to the email as well as the 
debug logs for NFD and NLSR for all nodes. There is also this graph that 
represents the topology.



Best regards,

André Dexheimer Carneiro



On 03/02/2021 02:29, Saurab Dulal (sdulal) wrote:
> Hi Andre,
>
> First, let's try by increasing sleep time after starting NLSR. 
> Depending upon the size of the topology, NLSR requires enough time for 
> route computation and convergence otherwise it's possible to get many 
> noRoutes nacks.
>
> Additionally, check if the routes (from consumer to the producer) are 
> properly set up or not via Mini-NDN CLI.
>
> If the above step doesn't work, please send here NLSR and NFD debugs 
> log files and the topology that you are using.
>
> Saurab,
>
> ------------------------------------------------------------------------
> *From:* Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of 
> Andre via Mini-NDN <mini-ndn at lists.cs.ucla.edu>
> *Sent:* Tuesday, February 2, 2021 7:03 PM
> *To:* mini-ndn at lists.cs.ucla.edu <mini-ndn at lists.cs.ucla.edu>
> *Subject:* [Mini-NDN] Issues with NACKs
> 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.
>
>
> Hello everybody,
>
>
> I've been experimenting with some custom topologies with a bunch of
> producer-consumer pairs. However I've been getting a lot o NACKs when
> transmitting data.
>
> These producer/consumer programs are the same as those in the
> ndn-cxx/examples directory with some slight modifications only to log
> results in a custom format. They are instantiated in a python script,
> based on the one in examples/mnndn.py, which sets everything up and runs
> MiniNDN.
>
> Here are some details of the issue:
>
> 1. I still get data through, though in a small proportion in relation to
> the NACKs, and it is not related to any specific links or hosts in the
> topology.
>
> 2. It is not specific to my setup, which was created using the
> Vagrantfile in the last few commits on the named-data/mini-ndn
> repository, since I got similar results in different computers.
>
> 3. It not a hardware limitation, since I've tried running it with up to
> 16GB o RAM and 12 CPU cores.
>
> 4. It is not caused by the lack of the nlsrc advertise command. In fact,
> I'm currently using the default filters pre-advertised in nslrc
> (/ndn/<host_name>-site/<host_name>/).
>
> 5. It is currently working on my laptop, where I can run the simulations
> and get 0 NACKs (as I should). However, running the exact same code and
> configuration on another installation, which was set up in the same way,
> yields a 10-1 proportion of DATAs-NACKs.
>
>
> I've tried using debug level logs for NFD and NLSRC, but I could not get
> anywhere with those since they are pretty confusing and don't seem to
> lead me anywhere (some tips would be appreciated).
>
>
> My hope is that there is something missing (like a command or
> configuration not done by the install.sh script) in my setup or code, or
> that there is a specific configuration to the VM that I do not have.
>
>
> Best regards,
>
> André Dexheimer Carneiro
>
>
> _______________________________________________
> Mini-NDN mailing list
> Mini-NDN at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/mini-ndn
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20210204/20f6bff5/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kjhlhpgnjpplpfhe.png
Type: image/png
Size: 167122 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20210204/20f6bff5/attachment-0001.png>
-------------- next part --------------
[nodes]
h0: _ radius=106.066017 angle=0.785398
h1: _ radius=72.622311 angle=0.668289
h2: _ radius=70.178344 angle=0.998603
h3: _ radius=56.080300 angle=0.873775
h4: _ radius=62.609903 angle=0.463648
h5: _ radius=63.529521 angle=0.491809
h6: _ radius=79.075913 angle=0.165149
h7: _ radius=77.129761 angle=0.235545
h8: _ radius=61.522354 angle=0.130403
h9: _ radius=94.540996 angle=1.168682
d0: _ radius=46.270941 angle=0.108271
d1: _ radius=71.021124 angle=1.401018
d2: _ radius=108.300508 angle=0.739678
d3: _ radius=32.802439 angle=0.915101
d4: _ radius=92.179173 angle=0.497615
d5: _ radius=129.957685 angle=0.878028
d6: _ radius=58.077534 angle=0.051678
d7: _ radius=91.241438 angle=1.405648
d8: _ radius=105.118980 angle=0.974878
d9: _ radius=138.621788 angle=0.764993
s0: _ radius=55.901699 angle=1.107149
s1: _ radius=37.854986 angle=1.357858
s2: _ radius=52.497619 angle=0.704494
s3: _ radius=32.984845 angle=0.244979
s4: _ radius=101.390335 angle=1.311465
s5: _ radius=56.727418 angle=0.860258
s6: _ radius=111.072049 angle=0.753562
s7: _ radius=102.449988 angle=0.674741
s8: _ radius=72.470684 angle=1.082462
s9: _ radius=18.788294 angle=1.130954
v0: _ radius=77.025970 angle=0.515926
v1: _ radius=77.103826 angle=0.757882
v2: _ radius=87.965902 angle=1.422468
v3: _ radius=125.495020 angle=0.712083
v4: _ radius=17.464249 angle=1.158386
v5: _ radius=10.000000 angle=0.927295
v6: _ radius=48.332184 angle=1.144169
v7: _ radius=101.257099 angle=0.609917
v8: _ radius=63.600314 angle=0.640356
v9: _ radius=113.216607 angle=0.822881
[links]
h0:d2 delay=10ms bw=10
h0:s6 delay=10ms bw=10
h0:v9 delay=10ms bw=10
h1:v1 delay=10ms bw=10
h1:v8 delay=10ms bw=10
h1:v0 delay=10ms bw=10
h2:s8 delay=10ms bw=10
h2:s0 delay=10ms bw=10
h2:s5 delay=10ms bw=10
h3:s5 delay=10ms bw=10
h3:s2 delay=10ms bw=10
h3:s0 delay=10ms bw=10
h4:h5 delay=10ms bw=10
h4:v8 delay=10ms bw=10
h4:v0 delay=10ms bw=10
h5:v8 delay=10ms bw=10
h5:v0 delay=10ms bw=10
h6:h7 delay=10ms bw=10
h6:h8 delay=10ms bw=10
h6:d6 delay=10ms bw=10
h7:h8 delay=10ms bw=10
h7:h4 delay=10ms bw=10
h8:d6 delay=10ms bw=10
h8:d0 delay=10ms bw=10
h9:s4 delay=10ms bw=10
h9:d8 delay=10ms bw=10
h9:d7 delay=10ms bw=10
d0:d6 delay=10ms bw=10
d0:s3 delay=10ms bw=10
d1:v2 delay=10ms bw=10
d1:d7 delay=10ms bw=10
d1:s8 delay=10ms bw=10
d2:s6 delay=10ms bw=10
d2:s7 delay=10ms bw=10
d3:s9 delay=10ms bw=10
d3:s1 delay=10ms bw=10
d3:v4 delay=10ms bw=10
d4:v7 delay=10ms bw=10
d4:v0 delay=10ms bw=10
d4:s7 delay=10ms bw=10
d5:d9 delay=10ms bw=10
d5:v9 delay=10ms bw=10
d5:v3 delay=10ms bw=10
d7:v2 delay=10ms bw=10
d7:s4 delay=10ms bw=10
d8:v9 delay=10ms bw=10
d8:h0 delay=10ms bw=10
d9:v3 delay=10ms bw=10
d9:v9 delay=10ms bw=10
s0:v6 delay=10ms bw=10
s0:s5 delay=10ms bw=10
s1:v6 delay=10ms bw=10
s1:s9 delay=10ms bw=10
s2:s5 delay=10ms bw=10
s2:v8 delay=10ms bw=10
s3:d3 delay=10ms bw=10
s3:s9 delay=10ms bw=10
s4:v2 delay=10ms bw=10
s6:v9 delay=10ms bw=10
s7:v7 delay=10ms bw=10
s7:s6 delay=10ms bw=10
s8:s0 delay=10ms bw=10
s8:h3 delay=10ms bw=10
s9:v4 delay=10ms bw=10
s9:v5 delay=10ms bw=10
v1:v8 delay=10ms bw=10
v1:v0 delay=10ms bw=10
v3:s6 delay=10ms bw=10
v3:d2 delay=10ms bw=10
v4:v5 delay=10ms bw=10
v5:d3 delay=10ms bw=10
v6:h3 delay=10ms bw=10
v7:d2 delay=10ms bw=10
v9:d2 delay=10ms bw=10
-------------- next part --------------
A non-text attachment was scrubbed...
Name: logs.zip
Type: application/zip
Size: 19587877 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20210204/20f6bff5/attachment-0001.zip>