Hi Guanyao, The timeout for any address location in the authenticator depends on the idle_timeout and hard_timeout field values in the Host_auth_event the address was authenticated with. The idle_timeout, if non-zero, will time out the address locations after that many seconds of inactivity. Similarly, the hard_timeout, if non-zero, denotes after how many seconds the address location should be timed out regardless of activity. If both values are 0, the address location will never time out - it must be explicitly removed through a Host_auth_event if desired so.
If you're explicitly posting Host_auth_events to authenticate address locations, then you can set the timeout values yourself. If you're using the authenticator to automatically detect and authenticate address locations, you should set the default timeout values used by the authenticator using its member methods "set_default_hard_timeout" and "set_default_idle_timeout". Natasha On Thu, Feb 4, 2010 at 10:48 AM, Guanyao Huang <[email protected]> wrote: > Hello > Sorry to bother others. > I can't understand the code of authenticator module, but I need a small > favor. > I understand that if one mac is dst address, this mac address should > first be authenticated. After a while, this mac will timeout and > expire. > My current program wants to extend this timeout session. In this > program it first sends ping packets to authenticate dst mac (by ICMP > reply), and then tcpreplay some traces. If it expires quickly later > traces can not be redirected but only broadcasted to dst mac. > So, I only want to know which variable defines this interval. I tried > a few and it works. But I still need to know which variable is the key > factor. > Thanks. > > _______________________________________________ > nox-dev mailing list > [email protected] > http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org >
_______________________________________________ nox-dev mailing list [email protected] http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
