[ndnSIM] ndnSIM

Alex Afanasyev alexander.afanasyev at ucla.edu
Wed Oct 9 00:47:03 PDT 2013


1. You may want to check NS-3 documentation on tracing: http://www.nsnam.org/docs/manual/html/tracing.html

You don't need to do anything special with m_receiveDatas, but you would need to implement your own callback and then use one of the forms of TraceConnect to connect callback to the right "trace source".  You can use ndn::L3RateTracer (and its base class ndn::L2Tracer) as an example for that.

2. You can definitely can inherit from ndn::Limit class, but the question is where exactly you want to enable this limit.  Are you planning to do it as part of the forwarding strategy?

3. I have a similar question as in 2.  Where exactly you want to detect?  If you implement your own consumer, then you will be able to detect congestion of the whole path.  Is it what you're expecting?


On Oct 8, 2013, at 12:22 PM, "lakerskb.8" <lakerskb.8 at 163.com> wrote:

> Dear friend:
> Hi,I am a new user of ndnSIM and I want to use it to do some experiment about congestion control. I have read the document file and source code for a few days but I am still not sure where to start. I have some questions, hope you can help me to solve.
> 1. I am confused about the trace source of ndnSIM. Take the image below as an example. <截图1.png>
> If there is a callback function somewhere binds m_receivedDatas, or should I implement it myself?
> 2. If I want to control the sending rate of interest packet, can I inherit ns3::ndn::limit class?
> 3, If I want to detect the congestion based on interest sending rate,can I inherit ns3::ndn::consumer(just like the ConsumerWindow class)?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20131009/00d3d1ca/attachment.html>

More information about the ndnSIM mailing list