On 03/23/10 11:52 PM, Michael Hunter wrote:
> There is a mechanism in the b133 nwam that resets queue used between
> nwam and nwam-manager if one appears unresponsive. In the log you show
> we are just getting pounded with rescan requests. I wonder if the
> length of the AP list together with the scan rate is just causing us to
> fall far enough behind that one side declares the other dead
> continually?
>
> I'd be really interested in how b135 deals with this.
The log I sent is from b135 as I said in some email.
Erik
