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

[code@nsnam.ece.gatech.edu]

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

           Summary: GlobalRouteManager behaviour after Ipv4 interface
                    SetDown and SetUp procedure
           Product: ns-3
           Version: ns-3.2
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Keywords: bug
          Severity: major
          Priority: P2
         Component: routing
        AssignedTo: ns-bugs at isi.edu
        ReportedBy: egemen.cetinkaya at gmail.com
   Estimated Hours: 0.0


Created an attachment (id=297)
 --> (http://www.nsnam.org/bugzilla/attachment.cgi?id=297)
Ipv4 SetDown procedure

I am trying to simulate a scenario which brings down a PointToPoint link
between a node pair. The topology consists of three nodes, no loop, and using
GlobalRoute manager to route OnOff traffic. 

Ipv4::SetUp procedure was already implemented. We came up with the patch
(attached as interface_down_patch) to access Ipv4 objects from the simulation.
Both SetUp and SetDown seems working.

The problem is when the Ipv4 interface was brought up after the scheduled time,
by examining the logs, it looks like the intermediate node does not know how to
route the packets:

1800000000ns Ipv4L3Protocol:SendRealOut(): No route to host.  Drop

In the attached 3nodesonly.cc file, when we schedule to setdown the i1i2
interface, and brought it up, intermediate node (node 1) is not able to forward
the packets. Basically the packets stopped in the trace file.

We already discussed this problem in the following post:

http://groups.google.com/group/ns-3-users/browse_thread/thread/91499a40f22b025e


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