#1791: 1 second "freeze" every 2 minutes
------------------------------------+---------------------------------------
      Reporter:  [EMAIL PROTECTED]  |       Owner:        
          Type:  defect             |      Status:  closed
      Priority:  major              |   Milestone:        
     Component:  madwifi: driver    |     Version:        
    Resolution:  invalid            |    Keywords:        
Patch_attached:  0                  |  
------------------------------------+---------------------------------------
Changes (by mrenzmann):

  * status:  new => closed
  * resolution:  => invalid

Comment:

 Replying to [comment:4 [EMAIL PROTECTED]:
 > No answer to my question? Strange...

 IDLE in the context mentioned above is the value of the nodes' current
 "inactivity timer" counter. The purpose of this counter is explained in
 net80211/ieee80211_node.h,
 [source:madwifi/trunk/net80211/[EMAIL PROTECTED] lines 47 ff]:

 {{{
 #!blockquote
 For inactivity processing each node has a timeout
 set in its ni_inact field that is decremented on each timeout
 and the node is reclaimed when the counter goes to zero.  We
 use different inactivity timeout values depending on whether
 the node is associated and authorized (either by 802.1x or
 open/shared key authentication) or associated but yet to be
 authorized.  The latter timeout is shorter to more aggressively
 reclaim nodes that leave part way through the 802.1x exchange.
 }}}

 As far as I could find out in a quick review of the source, the counter is
 decreased while a node shows no activity and is reset when the node
 becomes active again. Once the value goes below a certain threshold the AP
 actively probes the node (see
 [source:madwifi/trunk/net80211/[EMAIL PROTECTED] here]). If the
 node still shows no activity and the counter reaches zero it will be
 considered "dead" (see above).

 The different values used for this counter in different states can be
 changed via {{{iwpriv}}} (inact_init, inact_auth, inact; see
 [wiki:UserDocs/UsersGuide#inact_init-SetInactivityPeriodforINITState
 here]).

 Hope this helps.

 > '''Please close this bug as invalid.'''

 Thanks, done.

-- 
Ticket URL: <https://madwifi.org/ticket/1791#comment:5>
madwifi.org <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Madwifi-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/madwifi-tickets

Reply via email to