[ndnSIM] Help with Retransmission Timeout (RTO) / Scheduling of requests

Adhy Satya adhysatya820 at gmail.com
Sat Jun 16 18:21:04 PDT 2018


Just an update! I ran the same scenarios multiple times, and in some cases
it fetches all contents without retransmissions. Though for (about) every 7
simulations, one is able to fetch all contents, the others fetch the 7
contents out of 10 that I mentioned before.
Can this be related to the NS-3 randomization of simulation seeds?

To this point, I don't know what I'm doing wrong or don't know how to
bypass this issue.


On Thu, Jun 14, 2018 at 3:15 PM, Adhy Satya <adhysatya820 at gmail.com> wrote:

> Hi all,
> With my custom fw-strategy working, I'm now working on my application,
> which uses directional antennas to send an Interest request to one node and
> if that Interest times out, it turns the antenna and sends it to another
> node.
> I'm observing some weird behavior and with the RTO. I'm using
> Config::SetDefault ("ns3::ndn::RttEstimator::MaxRTO", TimeValue (Seconds
> (rto_Time)));
> to set the MaxRTO.
> I'm using ndnSIM 2.5 and ConsumerCbr.
> Test #1
> 1 Consumer, 1 Interest/s, requesting 10 Contents, MaxRTO is set to 4s,
> simulation duration 600 seconds.
> Result: consumer only fetches 7 contents (last content is fetched at 14
> seconds).
> Test #2
> Same as before, but removed MaxRTO limit.
> Result: Consumer only fetches 3 contents and RTO is 64 s.
> I understand that the RTO doubles every time an Interest is sent and a
> data packet doesn't come back (i.e., doubles every time it expires).
> So setting the MaxRTO to a low value in this case would prevent the
> consumer from scheduling packets for a distant time in the future, right?
> What am I missing here?
> Thank you again!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20180616/88334301/attachment.html>

More information about the ndnSIM mailing list