<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta content="text/html; charset=UTF-8">
<style type="text/css" style="">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:#000000; font-family:Calibri,Arial,Helvetica,sans-serif">
<p>Yes, NLSR uses transport from client.conf to find NFD socket.</p>
<p><br>
</p>
<p>Ashlesh</p>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> Ndn-interest <ndn-interest-bounces@lists.cs.ucla.edu> on behalf of Dehart, John <jdd@wustl.edu><br>
<b>Sent:</b> Friday, December 2, 2016 10:42:44 AM<br>
<b>To:</b> Lan Wang (lanwang)<br>
<b>Cc:</b> ndn-interest@lists.cs.ucla.edu<br>
<b>Subject:</b> Re: [Ndn-interest] Launching several instances of nlsr</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText"><br>
Lan,<br>
<br>
Just out of curiosity, how does NLSR communicate with NFD?<br>
Does it use ‘transport’ from client.conf (via ndn-cxx library) to find the nfd socket<br>
like other NFD clients?<br>
<br>
John<br>
<br>
> On Dec 2, 2016, at 9:48 AM, Lan Wang (lanwang) <lanwang@memphis.edu> wrote:<br>
> <br>
> Why do you want to run multiple instances of NLSR on one node without mini-NDN?
<br>
> <br>
> Lan<br>
> <br>
>> On Dec 2, 2016, at 9:41 AM, Matteo Bertolino <Matteo.Bertolino@eurecom.fr> wrote:<br>
>> <br>
>> Dear Cesar,<br>
>> thanks for the answer. Actually I did it, with linux namespaces.<br>
>> I am convinced that nlsr is the problem, because I compared two FIB in this topology: node1, node2 both attached to nodeGW.<br>
>> <br>
>> FIB of node1 in MINI: (just first line)<br>
>> /ndn/NLSR/sync nexthops={faceid=257 (cost=0), faceid=260 (cost=10)}<br>
>> <br>
>> FIB of node1 without MINI: (just first line)<br>
>> /ndn/NLSR/sync nexthops={faceid=263 (cost=0), faceid=265 (cost=0), faceid=266 (cost=0), faceid=264 (cost=10), faceid=267 (cost=10), faceid=268 (cost=10)}<br>
>> <br>
>> 6 entries vs 2. Then the NLSR instances are actually "together"!<br>
>> <br>
>> <br>
>> Quoting "César A. Bernardini" <mesarpe@gmail.com>:<br>
>> <br>
>>> I don't remember the parameters of nslr . Maybe the thing you could try is<br>
>>> to create tap devices in Linux and attach the app to this fake interfaces.<br>
>>> I remember I did this three years ago.<br>
>>> <br>
>>> Bests,<br>
>>> <br>
>>> On Dec 2, 2016 15:40, "Matteo Bertolino" <Matteo.Bertolino@eurecom.fr><br>
>>> wrote:<br>
>>> <br>
>>>> Good morning, I need to perform a complicate question.<br>
>>>> I would like to launch several NDN nodes in different processes (i.e. 3<br>
>>>> processes) on the same machine. Exactly the same behaviour of mini-ndn, but<br>
>>>> without.<br>
>>>> Then, about the NFD I had no problem:<br>
>>>> 1- Open three terminals.<br>
>>>> 2- On each terminal, change the HOME environment variable.<br>
>>>> 3- Put on the new home a new nfd.conf, changing the socket name (nfd.sock,<br>
>>>> nfd1.sock, nfd2.sock), the port numbers, and repeat in the<br>
>>>> client.config.sample.<br>
>>>> 4- On each terminal, launch nfd --config ~/nfd.conf &<br>
>>>> <br>
>>>> It works well. The problem arrives with NLSR.<br>
>>>> In each HOME, I put a different version of nlsr.conf, where I changed the<br>
>>>> names and the ip of the neighborhoods.<br>
>>>> Then I run on each node nlsr -d -f ~/nlsr.conf<br>
>>>> <br>
>>>> And here I noticed a strange thing: all the output, nlsr related,<br>
>>>> converges in one terminal. So I started to think that actually there are<br>
>>>> not 3 separated nlsr instances despite the three different processes.<br>
>>>> If I try to do nlsrc advertise /prefix , it tells me "success in<br>
>>>> advertisement", but no FIBS are actually updated. This demonstrate that the<br>
>>>> three instances are actually one.<br>
>>>> <br>
>>>> But, however, mini obtains a perfect separation. I tried to replicate<br>
>>>> exactly the same steps in nlsr.py, but I have no success. In your opinion,<br>
>>>> what do I forgot ? Thanks<br>
>>>> <br>
>>>> ------------------------------------------------------------<br>
>>>> -------------------<br>
>>>> This message was sent using EURECOM Webmail: <a href="http://webmail.eurecom.fr">
http://webmail.eurecom.fr</a><br>
>>>> <br>
>>>> <br>
>>>> _______________________________________________<br>
>>>> Ndn-interest mailing list<br>
>>>> Ndn-interest@lists.cs.ucla.edu<br>
>>>> <a href="http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest">http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest</a><br>
>>>> <br>
>>> <br>
>> <br>
>> <br>
>> <br>
>> -------------------------------------------------------------------------------<br>
>> This message was sent using EURECOM Webmail: <a href="http://webmail.eurecom.fr">
http://webmail.eurecom.fr</a><br>
>> <br>
>> <br>
>> _______________________________________________<br>
>> Ndn-interest mailing list<br>
>> Ndn-interest@lists.cs.ucla.edu<br>
>> <a href="http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest">http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest</a><br>
> <br>
> <br>
> _______________________________________________<br>
> Ndn-interest mailing list<br>
> Ndn-interest@lists.cs.ucla.edu<br>
> <a href="http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest">http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest</a><br>
<br>
<br>
_______________________________________________<br>
Ndn-interest mailing list<br>
Ndn-interest@lists.cs.ucla.edu<br>
<a href="http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest">http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest</a><br>
</div>
</span></font>
</body>
</html>