[Ns-bugs] [Bug 812] Assert when getting socket in RecvReply for AODV

[code@nsnam.ece.gatech.edu]

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





--- Comment #3 from Kevin Peters <kevjay at gmail.com>  2010-03-05 13:57:53 EDT ---
Thanks, I updated my ns3-7 code base with the three relevant AODV source files
from that changeset.  I no longer see any crashes.  The only problem I saw
seems to be specific to the flow monitor not knowing what the drop code is for
when a route is not found which might be because this is with ns3-7:

Unexpected drop reason code 5

Program received signal SIGSEGV, Segmentation fault.
0x6f9ad1f2 in ns3::Ipv4FlowProbe::DropLogger (this=0xbae8f8,
ipHeader=@0x228b30, ipPayload={m_ptr = 0xbc2e00},
    reason=ns3::Ipv4L3Protocol::DROP_ROUTE_ERROR, ifIndex=0) at
../src/contrib/flow-monitor/ipv4-flow-probe.cc:167
167               NS_FATAL_ERROR ("Unexpected drop reason code " << reason);


I can easily get around this be disabling the flow monitor.

As far as bug 737, there are a lot of us here using ns-3 for MANET research. 
We do not see very good packet delivery in higher node and data rate scenarios
so are very interested if this bug is related.  Do you know when there will be
a more final solution/patch or is it suggested to use the simple patch that is
already attached to this bug?

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