Quote:
Originally Posted by stukov
wlandebug looks exactly like the magic wand that will help me identifying the problem, however the man page doesn't mention where the debug output is shown...
|
It is outputed by kernel on console.
You could also enable
ath(4) special debug options available in driver itself.
Note that such ath debug options are documented only in ath source and are mostly used by developers.
But enable first one by one so you dont get lost in forest of console messages.
You could also sniff WLAN packets with another device while carrier get lost. But understanding
such captured output is another story ....