[Mini-NDN] [Ndn-interest] Launching several instances of nlsr

[Ashlesh Gawande (agawande)]

Mininet provides virtual ethernet pairs in networked namespaces. So each node provided by Mininet have a network stack. That is why NLSR can be configured with IPs of neighboring nodes.


You can create your own network namespaces, but why not use Mininet?

If you want to anyway - I would suggest to see how exactly Mininet does it.


Do these NLSR have the same log file, what does the neighbor section look like?


Ashlesh

________________________________
From: Ndn-interest <ndn-interest-bounces at lists.cs.ucla.edu> on behalf of Lan Wang (lanwang) <lanwang at memphis.edu>
Sent: Friday, December 2, 2016 9:48:03 AM
To: Matteo Bertolino
Cc: ndn-interest at lists.cs.ucla.edu
Subject: Re: [Ndn-interest] Launching several instances of nlsr

Why do you want to run multiple instances of NLSR on one node without mini-NDN?

Lan

> On Dec 2, 2016, at 9:41 AM, Matteo Bertolino <Matteo.Bertolino at eurecom.fr> wrote:
>
> Dear Cesar,
> thanks for the answer. Actually I did it, with linux namespaces.
> I am convinced that nlsr is the problem, because I compared two FIB in this topology: node1, node2 both attached to nodeGW.
>
> FIB of node1 in MINI: (just first line)
> /ndn/NLSR/sync nexthops={faceid=257 (cost=0), faceid=260 (cost=10)}
>
> FIB of node1 without MINI: (just first line)
> /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)}
>
> 6 entries vs 2. Then the NLSR instances are actually "together"!
>
>
> Quoting "César A. Bernardini" <mesarpe at gmail.com>:
>
>> I don't remember the parameters of nslr . Maybe the thing you could try is
>> to create tap devices in Linux and attach the app to this fake interfaces.
>> I remember I did this three years ago.
>>
>> Bests,
>>
>> On Dec 2, 2016 15:40, "Matteo Bertolino" <Matteo.Bertolino at eurecom.fr>
>> wrote:
>>
>>> Good morning, I need to perform a complicate question.
>>> I would like to launch several NDN nodes in different processes (i.e. 3
>>> processes) on the same machine. Exactly the same behaviour of mini-ndn, but
>>> without.
>>> Then, about the NFD I had no problem:
>>> 1- Open three terminals.
>>> 2- On each terminal, change the HOME environment variable.
>>> 3- Put on the new home a new nfd.conf, changing the socket name (nfd.sock,
>>> nfd1.sock, nfd2.sock), the port numbers, and repeat in the
>>> client.config.sample.
>>> 4- On each terminal, launch nfd --config ~/nfd.conf &
>>>
>>> It works well. The problem arrives with NLSR.
>>> In each HOME, I put a different version of nlsr.conf, where I changed the
>>> names and the ip of the neighborhoods.
>>> Then I run on each node nlsr -d -f  ~/nlsr.conf
>>>
>>> And here I noticed a strange thing: all the output, nlsr related,
>>> converges in one terminal. So I started to think that actually there are
>>> not 3 separated nlsr instances despite the three different processes.
>>> If I try to do nlsrc advertise /prefix , it tells me "success in
>>> advertisement", but no FIBS are actually updated. This demonstrate that the
>>> three instances are actually one.
>>>
>>> But, however, mini obtains a perfect separation. I tried to replicate
>>> exactly the same steps in nlsr.py, but I have no success. In your opinion,
>>> what do I forgot ? Thanks
>>>
>>> ------------------------------------------------------------
>>> -------------------
>>> This message was sent using EURECOM Webmail: http://webmail.eurecom.fr
>>>
>>>
>>> _______________________________________________
>>> Ndn-interest mailing list
>>> Ndn-interest at lists.cs.ucla.edu
>>> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest
>>>
>>
>
>
>
> -------------------------------------------------------------------------------
> This message was sent using EURECOM Webmail: http://webmail.eurecom.fr
>
>
> _______________________________________________
> Ndn-interest mailing list
> Ndn-interest at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest


_______________________________________________
Ndn-interest mailing list
Ndn-interest at lists.cs.ucla.edu
http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161202/c55e6c48/attachment-0001.html>