[Ns-bugs] [Bug 406] GlobalRouteManager behaviour after Ipv4 interface SetDown and SetUp procedure

code@nsnam.ece.gatech.edu code at nsnam.ece.gatech.edu
Tue Nov 11 11:21:07 PST 2008


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


Mathieu Lacage <mathieu.lacage at sophia.inria.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mathieu.lacage at sophia.inria.
                   |                            |fr




--- Comment #3 from Mathieu Lacage <mathieu.lacage at sophia.inria.fr>  2008-11-11 14:21:06 EDT ---
(In reply to comment #2)
> Yes, global routing only works in the pre-simulation stage at present.  I will
> try to provide some kind of workaround for you later tonight.  
> 
> For the longer-term cleaner fix, in general, if we want to support calling
> PopulateRoutingTables() at any time in the simulation, we need to be able to
> keep track of the routes that were previously injected, so they could be
> removed.  One way would be to tag each route somehow so the routes iterated
> could be examined for the tag.  Another way would be to store these routes in a
> dedicated global routing object that is distinct from the static routing
> ("manual" routing) object that users may want to hand-enter default routes, and
> to call Flush() on this routing object.  Right now, those routes are mixed
> together in Ipv4StaticRouting so we do not want to just delete every route we
> find in that object.

Erm, the behavior I was expecting was that PopulateRoutingTables would reset
the routing tables of all nodes it is invoked on. i.e., it would empty the
forwarding tables before filling them.


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


More information about the Ns-bugs mailing list