Received-SPF: pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Subject: Re: Any reason AID is not in the NL80211_STA_INFO enumeration?
To:     Johannes Berg <johannes@sipsolutions.net>,
        "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
References: <5E4B39B2.8050905@candelatech.com>
 <3fcaaf0ba9ed726c863f9f1e7c5d61c08ca40795.camel@sipsolutions.net>
From:   Ben Greear <greearb@candelatech.com>
Message-ID: <29006a9e-4de2-1733-1a8a-a5aae686fd42@candelatech.com>
Date:   Fri, 28 Feb 2020 07:26:40 -0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <3fcaaf0ba9ed726c863f9f1e7c5d61c08ca40795.camel@sipsolutions.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-wireless-owner@vger.kernel.org
Precedence: bulk


On 02/28/2020 02:06 AM, Johannes Berg wrote:
> On Mon, 2020-02-17 at 17:11 -0800, Ben Greear wrote:
>> To sniff /AX stations, it is helpful to know their AID.  So, any problems
>> with adding it to 'iw station dump' output?
>
> No, no problem at all. I guess it was just never added because it
> originally comes from userspace (hostapd), and so didn't really need to
> be sent back. But yeah, we have trivial infrastructure to send it back,
> so sure, why not.

Ok, thanks for the response.

 From looking at debugfs for a station device, there is the netdev AID:

cat /debug/ieee80211/wiphy0/netdev\:wlan0/aid
1

And there is a peer AID:

cat /debug/ieee80211/wiphy0/netdev\:wlan0/stations/04\:f0\:21\:c2\:fd\:b0/aid
0

For sniffing AX, I'd need to use '1' here as far as I can tell.  Maybe for station
devices the peer is always zero?  And for AP devices, the peer IDs are what is useful
and the netdev AID is not?


Thanks,
Ben

>
> johannes
>

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com