This bug is quite puzzling me. Not the bug itself, the problem is on how to fix it.

Now, RttEstimator's constructor is something like:
{
  ObjectBase::ConstructSelf (AttributeConstructionList ());
  m_currentEstimatedRtt = m_initialEstimatedRtt;
}
whereas m_initialEstimatedRtt is set by an attribute.

The problem (huge one) is this: the attribute default value is 1.0 sec, but m_currentEstimatedRtt is set to ZERO.

The calls traces are:
RttEstimator:RttEstimator(0x7ff2c1c87de0)
Initialize m_currentEstimatedRtt to 0 sec.
Initialize m_initialEstimatedRtt to 0 sec.
RttEstimator:RttMeanDeviation(0x7ff2c1c87de0)
RttEstimator:SetInitialEstimatedRtt(0x7ff2c1c87de0, +1000000000.0ns)
RttEstimator:SetMinRto(0x7ff2c1c87de0, +200000000.0ns)

Mind that I added an explicit setter and getter for InitialEstimatedRtt.

How this is possible? Top ranked guess (I'm not an attribute wizard):
- the ObjectBase::ConstructSelf (AttributeConstructionList ()) call is not doing what's supposed to do. Maybe because the TypeId is the one of the derived class ? How can we force the base class attributes to be read ?

Another solution is to use the DoStart() method, however the RttEstimator is *not* aggregated to the node, it's just built on-the-fly when a socket is created.

The only (ugly) solution I found is to add another *public* function DoStart (DoStart is protected usually) and call it explicitly when the RttEstimator is created. Of course we can call it in a different way, but the idea is still ugly, no matter how we call the function.

Any better solution ?

T.