[ns] agent timeout in Mobile IP module NS2.34

Mário Augusto marioeaugusto at gmail.com
Wed Jan 5 09:39:06 PST 2011


Hi people,

I was analyzing Mobile IP module from NS2.34 and RFC 2002 (which describes
Mobile IP). The lifetime field sent within Advertisement messages informs
"The maximum length of time that the Advertisement is considered valid in
the absence of further Advertisements" (such as described in RFC 2002,
section 2.1).
The problem is, in the recv() function (void MIPMHAgent::recv(Packet* p,
Handler *) within mip-reg.cc), the expire_time_ for that Foreign Agent is
set to: beacon_ +  Scheduler::instance().clock(), and this expire_time_ is
used in the timeout() function to verify whether that Foreign Agent is timed
out.
My question is: the expire_time_ value shouldn't be set to: miph->lifetime_
+ Scheduler::instance().clock()?
If I change ad_lifetime_ to 10 (Agent/MIPBS set ad_lifetime_ 10) rather than
default 2, into the ns-default.tcl, my AP still expires in 1 second rather
than 10 seconds.

Best regards,

Mario Ezequiel
University of Sao Paulo - Brazil


More information about the Ns-users mailing list