New ath code works well as AP

Adrian Chadd adrian at freebsd.org
Mon Aug 20 16:36:05 UTC 2012


On 20 August 2012 09:31, Slawa Olhovchenkov <slw at zxy.spb.ru> wrote:

>> The main issues I see right now are very likely due to noisy
>> environments and ANI behaving poorly.
>
> How you detect noisy environments?
> (some output from athsurvey?)

Yup. Look at the channel busy statistics. YOur channel isn't busy at all.

> What level of noisy is acpetable in terms of athsurvey and in terms of
> physicaly units? (I can use Cisco Spectrum Expert for survey, but not
> simultaneously with this card).

Anything bursty, wide or narrow band, will cause issues.


> What is ANI?

Ambient/Automatic Noise Immunity. There's some code which adjusts some
PHY parameters to do with signal sizing and offset; however I may have
(more) broken it.
I need to sit down and add some further debugging and write an
inspection tool or two to figure out exactly what's going on.

> What I need to try in next time of lost traffic?

> (no messages in console in this situation, nothing about "ath0: device
> timeout" nor "ath0: bb hang detected (0x4), resetting").
>
> Do I need to enable some debug?

Well, what do you mean by "lost traffic" ? I need some more
information about that.



Adrian


More information about the freebsd-wireless mailing list