<div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small;color:rgb(12,52,61)">Hello ndnSIM team,<br><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small;color:rgb(12,52,61)">It seems that I should run a socket-based application, such as the "ChronoSync", on UAN nodes.<br>I am following this link: <a href="https://github.com/spirosmastorakis/scenario-ChronoSync" target="_blank">https://github.com/<wbr>spirosmastorakis/scenario-<wbr>ChronoSync</a><br><br>While running the "./waf", this error comes up!<br>Vostro1310:~/ndnSIM2.1/scenario-ChronoSync$ ./waf<br>Waf: Entering directory `/home/narguess/ndnSIM2.1/scenario-ChronoSync/build'<br>[13/13] Linking build/chronosync-simple<br>/usr/local/lib/libns3-dev-emu-optimized.so: undefined reference to `ns3::LogComponent::LogComponent(std::string const&, ns3::LogLevel)'<br>collect2: error: ld returned 1 exit status<br><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small;color:rgb(12,52,61)">Regards,<br></div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small;color:rgb(12,52,61)">Narges<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Sep 10, 2017 at 12:04 AM, Narges Mehran <span dir="ltr"><<a href="mailto:narges.mehran@gmail.com" target="_blank">narges.mehran@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small;color:rgb(12,52,61)">Hello team,<br><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small;color:rgb(12,52,61)">Thanks a lot Spyros and<span name="Junxiao Shi" class="m_4674874838942533482gmail-gD"> Junxiao</span>,<br><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small;color:rgb(12,52,61)">I did what you had recommended; however, the limitation in sending to a specific node didn't solve the problem either.<br></div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small;color:rgb(12,52,61)">Although the producer does receive the Interest, it does not give the packet to the application layer to start producing the Data!<br><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small;color:rgb(12,52,61)">Any idea how to get closer to the solution?<br><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small;color:rgb(12,52,61)">Regards,<br></div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small;color:rgb(12,52,61)">Narges<br><br></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Aug 5, 2017 at 5:15 AM, Spyridon (Spyros) Mastorakis <span dir="ltr"><<a href="mailto:mastorakis@cs.ucla.edu" target="_blank">mastorakis@cs.ucla.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Hi,<div><br></div><div>I am not aware of the specifics of the UAN device model, but you could take a look here:</div><div><br></div><div><a href="https://github.com/4th-ndn-hackathon/ndnSIM-Mobile-Simulation-Package/blob/master/model/ndn-net-device-transport.cpp#L88" target="_blank">https://github.com/4th-ndn-hac<wbr>kathon/ndnSIM-Mobile-Simulatio<wbr>n-Package/blob/master/model/<wbr>ndn-net-device-transport.cpp#<wbr>L88</a></div><div><br></div><div>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. </div><div><br></div><div>Again, I do not know the specifics of the UAN device model, but the issue might be something similar to that.</div><div><br></div><div>Hope that this helps,</div><div><br><div>
<div><div><div><span style="float:none;display:inline!important">Spyridon (Spyros) Mastorakis</span><br><span style="float:none;display:inline!important">Personal Website: </span><a href="http://cs.ucla.edu/~mastorakis/" target="_blank">http://cs.ucla.edu/~m<wbr>astorakis/</a><br><span style="float:none;display:inline!important">Internet Research Laboratory</span><br><span style="float:none;display:inline!important">Computer Science Department</span><br><span style="float:none;display:inline!important">UCLA</span></div></div></div>
</div><div><div class="m_4674874838942533482h5">
<br><div><blockquote type="cite"><div>On Aug 4, 2017, at 2:16 AM, Oleg Surnin <<a href="mailto:o.surnin@innopolis.ru" target="_blank">o.surnin@innopolis.ru</a>> wrote:</div><br class="m_4674874838942533482m_8220818987033169073Apple-interchange-newline"><div>
<div text="#000000" bgcolor="#FFFFFF"><p>Thanks for your replies.</p><p>I added manually faces to the FIB. Packets still not forwarding.
<br>
</p><p>Also I'm noticed that p2p network devices have a MAC address in
FIB(<a>netdev://[00:00:...:0d]258</a><wbr>), but UAN devices that I added
don't have them (<a>netdev://256</a>). Maybe this is a problem?<br>
</p>
<br>
<div class="m_4674874838942533482m_8220818987033169073moz-cite-prefix">On 08/03/2017 10:38 PM, Narges Mehran
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr"><img class="m_4674874838942533482m_8220818987033169073mailtrack-img" alt="" style="display:flex" src="https://mailtrack.io/trace/mail/00e9db8067944ecb1b70f786f14c4f6fb18845d0.png?u=1311299" height="0" width="0">
<div>Hello Junxiao,</div>
<div><br>
</div>
<div>Thanks a million for your responses.</div>
<div><br>
</div>
<div>Oleg is right. Actually, I have checked it with other
versions. Also, in a paper named: "<span style="font-size:12.8px">A Named-Data Networking Approach to
Underwater Monitoring Systems</span><span style="color:inherit;font-size:inherit">", 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.</span></div>
<div><span style="color:inherit;font-size:inherit">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.</span></div>
<div><span style="color:inherit;font-size:inherit"><br>
</span></div>
<div><span style="color:inherit;font-size:inherit">Regards, </span></div>
<div><span style="color:inherit;font-size:inherit">Narges</span></div>
<div><br>
</div>
<div style="display:inline"> </div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Aug 3, 2017 at 5:38 PM, Junxiao
Shi <span dir="ltr"><<a href="mailto:shijunxiao@email.arizona.edu" target="_blank">shijunxiao@email.arizona.edu</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="m_4674874838942533482m_8220818987033169073HOEnZb">
<div class="m_4674874838942533482m_8220818987033169073h5">
<div><br>
<div class="gmail_quote">
<div>On Thu, Aug 3, 2017 at 00:40 Junxiao Shi <<a href="mailto:shijunxiao@email.arizona.edu" target="_blank">shijunxiao@email.arizona.edu</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div dir="auto">Hi Oleg</div>
<div dir="auto"><br>
</div>
<div dir="auto">FibHelper::AddRoute in ndnSIM
2.3 only recognizes PointToPointNetDevice, and
does not support UAN. <a href="https://github.com/named-data-ndnSIM/ndnSIM/blob/ndnSIM-2.3/helper/ndn-fib-helper.cpp#L137" target="_blank">https://github.com/named-data-<wbr>ndnSIM/ndnSIM/blob/ndnSIM-2.3/<wbr>helper/ndn-fib-helper.cpp#L137</a></div>
<div dir="auto">You may manipulate the FIB
directly. Look at FibHelper code to get an
idea about how to do that.</div>
<div dir="auto"><br>
</div>
<div dir="auto">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.</div>
<div dir="auto">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.</div>
<div dir="auto"><br>
</div>
<div dir="auto">Yours, Junxiao</div>
</div>
<div><br>
<div class="gmail_quote">
<div>On Wed, Aug 2, 2017 at 22:49 Oleg Surnin
<<a href="mailto:o.surnin@innopolis.ru" target="_blank">o.surnin@innopolis.ru</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I have the same
problem as a Narges. The first part of the
code looks<br>
very similar. But I'm using the ndnSIM 2.3.
In my case the packets<br>
didn't transfered between nodes.<br>
<br>
The code is here: <a href="https://pastebin.com/iVNz5cnX" rel="noreferrer" target="_blank">https://pastebin.com/iVNz5cnX</a><br>
<br>
I'm tried to setup FIB manually by<br>
<br>
ndn::FibHelper::AddRoute(nc.Ge<wbr>t(1),
"/prefix", nc.Get(0), 1);<br>
<br>
but have an error: "Cannot add route: Node#
1 and Node# 0 are not<br>
connected"<br>
<br>
<br>
</blockquote>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div></blockquote></div><br></div></blockquote></div><br></div></div></div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>