ifconfig txpower and ni->ni_txpower are disconnected?

[Adrian Chadd]

[punting to -wireless, as we should really have an open discussion
about this kind of thing]

On 29 May 2012 12:04, Monthadar Al Jaberi <monthadar at gmail.com> wrote:
> Hi
>
> I have been testing the txpower power thing abit, and I noticed
> something. Thought I hear what you think before I patch. I have tested
> with Witness/Invariants and didnt get any warning messages.

Ok, good. Let's just do a final review of what's going on with that
code path before we commit it.

> The thing is this:
>
> ifconfig wlan0 txpower controls global txpower. Its the device limit.
>
> ifconfig wlan0 statxpower controls txpower for frames associated to a node.
>
> But I am missing a txpower that controls boradcast frames. Would you
> see it logical if I implement something like
>
> ifconfig wlan0 statxpower FF:FF:FF:FF:FF:FF ??
>
>
> for now beacons are sent with max txpower, which I can change by
> ifconfig txpower. But I want to control broadcast message

Right. So this is where things get a bit "special".

Is this global or per-vap? Ie, do you want to be able to set the TX
power for multicast and beacon traffic per-VAP or just per-interface?


I think I'm at the point where I'd better just implement per-packet
TPC on the 11n chips so we at least have something to test with.



Adrian