[ndnSIM] How to use nlsr as the routing protocol with consumer and producer in ndnSIM

[Muhammad Hosain Abdollahi Sabet]

OK.

Take ndn-nlsr-simple for example. At first(0s), there is 1 entry in fib of
all nodes. At Seconds(25.0) fib size of nodes are:
node 0 = 12
node 1 = 11
node 2 = 11
node 3 = 10
node 4 = 10

I install and start a ndn::Producer application on nodes.Get(0) at
Seconds(2.0). Again at Seconds(25.0) I have:
 ​
node 0 = 13
node 1 = 11
node 2 = 11
node 3 = 10
node 4 = 10

So I guess the convergence has not happened successfully.

--
Sabet

On Mon, Feb 20, 2017 at 11:40 PM, Anil Jangam <anilj.mailing at gmail.com>
wrote:

> Hi Sabet,
>
> What I am trying to say that if you start producer before NLSR app, it may
> not find routes as NLSR would still be doing the routing table updates. It
> does not mean that it will not allow NLSR to converge. Since I have not yet
> tested this scenario myself, I thought to speculate that possibility. I do
> not know how ndnSIM scheduler would be scheduling events from two different
> ndn applications running on a given node. Let me know how it behaves once
> you try it.
>
> /anil.
>
>
> On Mon, Feb 20, 2017 at 11:41 AM, Muhammad Hosain Abdollahi Sabet <
> mhasabet at gmail.com> wrote:
>
>> Anil,
>>
>> Thanks for the clarification. So if I start a producer app after NLSR
>> initialization, nlsr will do the convergence. Why not before? I mean If I
>> start a producer app at 1s and start nlsr at 2s, the node should inform
>> other routers of the producer prefix, right?
>>
>> Thanks,
>> Sabet
>>
>>
>>
>> On Mon, Feb 20, 2017 at 11:02 PM, Anil Jangam <anilj.mailing at gmail.com>
>> wrote:
>>
>>> Hi Sabet,
>>>
>>> I did not say that -- NLSR will converge. I was suggesting it from the
>>> point in your simulation where you start the producer application e.g. if
>>> you start producer, before starting the NLSR application, it may not find
>>> the routes. Hope this clarify your doubt.
>>>
>>> /anil.
>>>
>>>
>>>
>>> On Sun, Feb 19, 2017 at 5:55 PM, Muhammad Hosain Abdollahi Sabet <
>>> mhasabet at gmail.com> wrote:
>>>
>>>> Anil,
>>>>
>>>> Why is that? I mean if I install and start a producer application on
>>>> one of the nodes in ndn-simple-nlsr, why it isn't going to converge the
>>>> routing tables? Isn't that why we expect from nlsr?
>>>>
>>>> --
>>>> Sabet
>>>>
>>>>
>>>> On Sun, Feb 12, 2017 at 9:09 PM, Anil Jangam <anilj.mailing at gmail.com>
>>>> wrote:
>>>>
>>>>> Hello Mahsa,
>>>>>
>>>>> This scenario of application is not available yet nor tested. Below
>>>>> are some some directions how it can be done.
>>>>>
>>>>> As discussed, you will have to install the producer consumer apps on
>>>>> the nodes along with NLSR and start the producer/consumer application as
>>>>> soon as you detect that routing has converged. You can start them ahead of
>>>>> routing convergence but it may not find the routes and traffic may not go
>>>>> through. Please note that the default routing must disabled when NLSR is
>>>>> active.
>>>>>
>>>>> /anil.
>>>>>
>>>>> On Feb 12, 2017 5:46 AM, "Mahsa Aghajani" <mahsa.aghajani at gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Dear ndnSIM users
>>>>>>
>>>>>> I need to run a topology consisting of a producer, a consumer
>>>>>> and a few routers. I want to use the nlsr as the routing protocol
>>>>>> in this simulation. I know I can use nlsrSIM which is ported by
>>>>>> Anil Jangam into ndnSIM recently but I do not know how exactly I can
>>>>>> do it.
>>>>>> I appreciate if anyone help me doing this.
>>>>>>
>>>>>> --
>>>>>>
>>>>>> Mahsa Aghajani
>>>>>> M.Sc. Student
>>>>>> Department of Computer Engineering
>>>>>> Sharif University of Technology
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> ndnSIM mailing list
>>>>>> ndnSIM at lists.cs.ucla.edu
>>>>>> http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim
>>>>>>
>>>>>>
>>>>> _______________________________________________
>>>>> ndnSIM mailing list
>>>>> ndnSIM at lists.cs.ucla.edu
>>>>> http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim
>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20170222/58ebb9da/attachment.html>