[Mini-NDN] (no subject)

Ashlesh Gawande (agawande) agawande at memphis.edu
Tue May 30 09:26:02 PDT 2017


Okay so for some reason NFD dies on the nodes. So the NLSR on the node where NFD did not die report the WARN because it can't get updates from the other nodes.


What do you see in the NFD logs:

/tmp/<node-name>/<node-name>.log

?


Ashlesh

________________________________
From: Liang zhu <liangzhu0194 at gmail.com>
Sent: Tuesday, May 30, 2017 11:22:32 AM
To: Ashlesh Gawande (agawande)
Subject: Re: [Mini-NDN] (no subject)


Hi,Ashlesh

If I build the four host connection "d-a-b-c", compile and run.

[nodes]

c: _ hyperbolic-state=off radius=4.0 angle=4.0 network=/ndn router=/%C1.Router/cs/host site=/edu/site nlsr-log-level=INFO max-faces-per-prefix=3 nfd-log-level=INFO

a: _ hyperbolic-state=off radius=2.0 angle=2.0 network=/ndn router=/%C1.Router/cs/host site=/edu/site nlsr-log-level=INFO max-faces-per-prefix=3 nfd-log-level=INFO

b: _ hyperbolic-state=off radius=3.0 angle=3.0 network=/ndn router=/%C1.Router/cs/host site=/edu/site nlsr-log-level=INFO max-faces-per-prefix=3 nfd-log-level=INFO

d: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn router=/%C1.Router/cs/host site=/edu/site nlsr-log-level=INFO max-faces-per-prefix=3 nfd-log-level=INFO

[switches]

[links]

b:c bw=120 loss=12 delay=12ms

a:b bw=200 loss=10 delay=20ms

a:d bw=100 loss=10 delay=10ms

The NLSR log has the following problem:

20170531001057730 WARN: [RoutingTableCalculator] Cost between [0][3] and [3][0] are not the same (0 != 10). Correcting to cost: 0

20170531001110090 FATAL: [NlsrRunner] ERROR: error while receiving data from socket (End of file)

20170531001110090 FATAL: [NlsrRunner] ERROR: error while receiving data from socket (End of file)

Your,Liang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20170530/2c42af69/attachment-0001.html>


More information about the Mini-NDN mailing list