[support] UMIP: Config option InitialBindackTimeoutFirstReg ?

Romain KUNTZ kuntz at lsiit.u-strasbg.fr
Thu May 7 20:56:18 JST 2009


Hi Mattias,

On 2009/04/30, at 17:32, Mattias Blomqvist wrote:
> The configuration option InitialBindackTimeoutFirstReg does not seem
> to work. Regardless of what I set it to in the configuration file, it
> is set to 1.5 seconds at start.
> I can see that there is an implementation of it in the configuration
> parsing. But I'm unable find out why it doesn't work.
> Is it supposed to work?
> What about InitialBindackTimeoutReReg ? It has the same problem.

By looking quickly at the code, I'd say this is supposed to work.  
Could you send the mip6d log of the MN? Especially, are these values  
correctly displayed in the debug (there are printed at startup)? That  
would help to know if it is a problem from the parser or later in the  
code.

> I really need to set this value higher and it would be good to not
> have to modify the source to do it.
>
> Wouldn't it be a good idea to also have the initial_solicit_timer_ts
> configurable?

INITIAL_SOLICIT_TIMER is a protocol constant defined by the MobileIPv6  
specification. This is I guess the reason why it is not configurable.  
However it seems that the specification does not forbid the use of  
another value, so this could be made configurable too.

Cheers,
romain


More information about the Support mailing list