#487: iwconfig athX txpower X say "operation not supported" when card is not
connected/nothing is connected to card
-----------------------------------+----------------------------------------
Reporter: anonymous | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: madwifi: 802.11 stack | Version: trunk
Keywords: iwconfig , txpower | Patch_attached: 0
-----------------------------------+----------------------------------------
during testing my startup scripts adopted to madwifi-ng, i have noticed ,
that when i use iwconfig athX txpower Y - where X in my tests e <0,5> , Y
e <1,14> - it doesn't set desired txpower and instead of it throw error
message - "SET failed on device ath1 ; Operation not supported." . After
some further tests, i have noticed, that this doesn't happen in cases,
where athX is in sta mode and it is already connected to some ap or when
athX is in ap mode and some other card is connected to it. If this had't
been fulfilled , it happened everytime , regardless of ifconfig up/down of
the card, regardless of svn checkout - tried on 1482, 1460 and 1451 ,
regardless of wireless tools, regardless of kernel version etc. . So i
guess it is madwifi issue and report it here. Reproduced by me on 3
diferent boxes and also reproduced by p0g0 during discussions on IRC. This
is not very big issue, but, in some cases, it could bring ppl troubles -
aka, when box which acts and hotspot somewhere is suddenly restarted ,
proper txpower limit is not set if some client card is not connected to it
in time when startup script is setting txpower.
Dirty workaround : as in old good times and prism25 based z626 and etc. ,
let cron set the txpower max every 5-10minutes or stuff
--
Ticket URL: <http://madwifi.org/ticket/487>
MadWifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
