[Mini-NDN] About minindn nlsr running error

Alexander Wilhelm Lane (awlane) awlane at memphis.edu
Tue Apr 2 09:11:34 PDT 2024


Good morning,
I believe this is an issue with the nfdc helper code not handling the returned output for "face-updated" which is not treated as a failure internally in nfdc, we had observed this prior and noted it did not seem to be causing issues. I will try and push an update ASAP as I believe this has caused confusion multiple times and I was able to find the apparent cause. However, I am reasonably confident that you are safe to ignore it until then.

-Alex Lane

________________________________
From: Àîâø•Ó Yitong LI <yitongli at hkust-gz.edu.cn>
Sent: Monday, April 1, 2024 8:17 PM
To: mini-ndn at lists.cs.ucla.edu <mini-ndn at lists.cs.ucla.edu>
Subject: [Mini-NDN] About minindn nlsr running error

Hi all,

I met an error when building an example to run nlsr on minindn. At last nlsr indeed converges. But there¡¯re two faces fail to register before. I¡¯ve attached the log below.

caster at ubuntu:~/Downloads$ sudo python3 mini-ndn/mini-ndn/examples/nlsr/pingall.py
Using topology file /usr/local/etc/mini-ndn/default-topology.conf
*** Creating network
*** Adding controller
*** Adding hosts:
a b c d
*** Adding switches:

*** Adding links:
(10ms delay) (10ms delay) (a, b) (10ms delay) (10ms delay) (a, c) (10ms delay) (10ms delay) (b, d)
*** Configuring hosts
a b c d
*** Starting controller
c0
*** Starting 0 switches

[c] Face register failed: face-updated id=260 local=udp4://10.0.0.6:6363 remote=udp4://10.0.0.5:6363 persistency=permanent reliability=off congestion-marking=on congestion-marking-interval=100ms default-congestion-threshold=65536B mtu=8800
[d] Face register failed: face-updated id=260 local=udp4://10.0.0.10:6363 remote=udp4://10.0.0.9:6363 persistency=permanent reliability=off congestion-marking=on congestion-marking-interval=100ms default-congestion-threshold=65536B mtu=8800
Waiting 60 seconds for convergence...
...done
NLSR has converged successfully.
Staring ping server on prefix /ndn/a-site/a
Staring ping server on prefix /ndn/b-site/b
Staring ping server on prefix /ndn/c-site/c
Staring ping server on prefix /ndn/d-site/d
Each node will ping 4 node(s)
Scheduling ping(s) from a for /ndn/b-site/b
Scheduling ping(s) from a for /ndn/c-site/c
Scheduling ping(s) from a for /ndn/d-site/d
Scheduling ping(s) from b for /ndn/c-site/c
Scheduling ping(s) from b for /ndn/d-site/d
Scheduling ping(s) from b for /ndn/a-site/a
Scheduling ping(s) from c for /ndn/d-site/d
Scheduling ping(s) from c for /ndn/a-site/a
Scheduling ping(s) from c for /ndn/b-site/b
Scheduling ping(s) from d for /ndn/a-site/a
Scheduling ping(s) from d for /ndn/b-site/b
Scheduling ping(s) from d for /ndn/c-site/c
*** Starting CLI:
mini-ndn> a echo "hello"
hello
mini-ndn>


Many thanks,
Caster
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20240402/5a4eb0fe/attachment.htm>


More information about the Mini-NDN mailing list