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

Mon Dec 1 04:35:07 PST 2008

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

Gustavo J. A. M. Carneiro <gjcarneiro at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |gjcarneiro at gmail.com

--- Comment #2 from Gustavo J. A. M. Carneiro <gjcarneiro at gmail.com>  2008-12-01 07:35:06 EDT ---
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...

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