[Ns-bugs] [Bug 415] OLSR's broken dynamic behaviour?

[code@nsnam.ece.gatech.edu]

http://www.nsnam.org/bugzilla/show_bug.cgi?id=415





--- Comment #3 from Egemen <egemen.cetinkaya at gmail.com>  2008-12-01 17:45:21 EDT ---
(In reply to comment #2)
> OLSR is based on timers.  After bringing down an interface, you have to wait
> some time (6 seconds IIRC) until neighbor tuples on that interface expire and a
> new routing table is calculated.
> 
> Although I would agree a possible optimization is to force the tuple expiration
> as soon as the interface comes down.  But I am not sure NS-3 can give the OLSR
> agent any kind of notification that an interface has gone down; not without new
> core API anyway...
> 

In the test file attached, the on/off application starts at 10, and stops at 30
sec. (both for the sink and the source). The interface is being setdown at 15
sec. and from 15 sec to 30 sec there is no traffic. According to your comment
there should be traffic from 21 sec to 30 sec., which is not the case.


-- 
Configure bugmail: http://www.nsnam.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.