[ndnSIM] problem with an underwater node while running, the NDN layer!

[Narges Mehran]

Hello ndnSIM team,

It seems that I should run a socket-based application, such as the
"ChronoSync", on UAN nodes.
I am following this link: https://github.com/spirosmastorakis/scenario-
ChronoSync

While running the "./waf", this error comes up!
Vostro1310:~/ndnSIM2.1/scenario-ChronoSync$ ./waf
Waf: Entering directory `/home/narguess/ndnSIM2.1/scenario-ChronoSync/build'
[13/13] Linking build/chronosync-simple
/usr/local/lib/libns3-dev-emu-optimized.so: undefined reference to
`ns3::LogComponent::LogComponent(std::string const&, ns3::LogLevel)'
collect2: error: ld returned 1 exit status

Regards,
Narges

On Sun, Sep 10, 2017 at 12:04 AM, Narges Mehran <narges.mehran at gmail.com>
wrote:

> Hello team,
>
> Thanks a lot Spyros and Junxiao,
>
> I did what you had recommended; however, the limitation in sending to a
> specific node didn't solve the problem either.
> Although the producer does receive the Interest, it does not give the
> packet to the application layer to start producing the Data!
>
> Any idea how to get closer to the solution?
>
> Regards,
> Narges
>
>
> On Sat, Aug 5, 2017 at 5:15 AM, Spyridon (Spyros) Mastorakis <
> mastorakis at cs.ucla.edu> wrote:
>
>> Hi,
>>
>> I am not aware of the specifics of the UAN device model, but you could
>> take a look here:
>>
>> https://github.com/4th-ndn-hackathon/ndnSIM-Mobile-Simulatio
>> n-Package/blob/master/model/ndn-net-device-transport.cpp#L88
>>
>> This is a project of the latest NDN hackathon and in this specific piece
>> of code we have changed the doSend method of the net device transport to
>> support unicast association with a Wifi access point.
>>
>> Again, I do not know the specifics of the UAN device model, but the issue
>> might be something similar to that.
>>
>> Hope that this helps,
>>
>> Spyridon (Spyros) Mastorakis
>> Personal Website: http://cs.ucla.edu/~mastorakis/
>> Internet Research Laboratory
>> Computer Science Department
>> UCLA
>>
>> On Aug 4, 2017, at 2:16 AM, Oleg Surnin <o.surnin at innopolis.ru> wrote:
>>
>> Thanks for your replies.
>>
>> I added manually faces to the FIB. Packets still not forwarding.
>>
>> Also I'm noticed that p2p network devices have a MAC address in FIB(
>> netdev://[00:00:...:0d]258), but UAN devices that I added don't have
>> them (netdev://256). Maybe this is a problem?
>>
>> On 08/03/2017 10:38 PM, Narges Mehran wrote:
>>
>> Hello Junxiao,
>>
>> Thanks a million for your responses.
>>
>> Oleg is right. Actually, I have checked it with other versions. Also, in
>> a paper named: "A Named-Data Networking Approach to Underwater
>> Monitoring Systems", the application of NDN layer has been exploited
>> with the newer version of ndnSIM; however, it seems that the authors of
>> this paper are so busy to guide us.
>> Anyway, ndnSIM is OK with the WiFi protocols and I have tested it myself.
>> But with the underwater acoustic protocols, it seems that the structures do
>> not agree with each other properly. U R right. I should go through the
>> routing to see if it is working truly.
>>
>> Regards,
>> Narges
>>
>>
>> On Thu, Aug 3, 2017 at 5:38 PM, Junxiao Shi <shijunxiao at email.arizona.edu
>> > wrote:
>>
>>>
>>> On Thu, Aug 3, 2017 at 00:40 Junxiao Shi <shijunxiao at email.arizona.edu>
>>> wrote:
>>>
>>>> Hi Oleg
>>>>
>>>> FibHelper::AddRoute in ndnSIM 2.3 only recognizes
>>>> PointToPointNetDevice, and does not support UAN.
>>>> https://github.com/named-data-ndnSIM/ndnSIM/blob/ndnSIM-2.3/
>>>> helper/ndn-fib-helper.cpp#L137
>>>> You may manipulate the FIB directly. Look at FibHelper code to get an
>>>> idea about how to do that.
>>>>
>>>> I guess the reason FibHelper::AddRoute(node, prefix, nexthopNode,
>>>> metric) being limited to PointToPointNetDevice is that, ndnSIM is incapable
>>>> of unicasting over a broadcast or ad hoc wireless face. It would be
>>>> semantically incorrect if this FibHelper::AddRoute overload causes a node
>>>> to broadcast Interests onto a channel where nexthopNode and potentislly
>>>> other nodes are present.
>>>> However, it would be nice for this overload to install a route to the
>>>> broadcast face if the underlying channel only contains {node, nexthopNode},
>>>> which exactly fulfills your use case. I suggest reporting an issue with
>>>> Tracker=Feature on ndnSIM Redmine site.
>>>>
>>>> Yours, Junxiao
>>>>
>>>> On Wed, Aug 2, 2017 at 22:49 Oleg Surnin <o.surnin at innopolis.ru> wrote:
>>>>
>>>>> I have the same problem as a Narges. The first part of the code looks
>>>>> very similar. But I'm using the ndnSIM 2.3. In my case the packets
>>>>> didn't transfered between nodes.
>>>>>
>>>>> The code is here: https://pastebin.com/iVNz5cnX
>>>>>
>>>>> I'm tried to setup FIB manually by
>>>>>
>>>>> ndn::FibHelper::AddRoute(nc.Get(1), "/prefix", nc.Get(0), 1);
>>>>>
>>>>> but have an error:  "Cannot add route: Node# 1 and Node# 0 are not
>>>>> connected"
>>>>>
>>>>>
>>>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20170911/9b07e5fe/attachment.html>