public inbox for iwd@lists.linux.dev
 help / color / mirror / Atom feed
From: James Prestwood <prestwoj@gmail.com>
To: James Hanley <jhanley@dgtlrift.com>, iwd@lists.linux.dev
Subject: Re: Exposing bssid information
Date: Sat, 15 Feb 2025 12:29:47 -0800	[thread overview]
Message-ID: <97112988-3681-4192-abb2-9a9ee6d9552d@gmail.com> (raw)
In-Reply-To: <CAF++6AMG1Jj8cWS0rmSgLPZqCAgRU1o1wgrUaBsOvhGJvrtzYQ@mail.gmail.com>

Hi Jim,

On 2/15/25 12:10 PM, James Hanley wrote:
> Hi,
> I’m looking to access (and/or expose) via dbus scanned information on
> bssid. Specifically, information as follows:
>
> {
>    "wifiAccessPoints": [
>   {
>    "macAddress": "f0:d5:bf:fd:12:ae",
>    "signalStrength": -43,
>    "signalToNoiseRatio": 0,
>    "channel": 11,
>    "age": 0
> },
> {
>    "macAddress": "3c:37:86:5d:75:d4",
>    "signalStrength": -35,
>    "signalToNoiseRatio": 0
> },
> {
>    "macAddress": "30:86:2d:c4:29:d0",
>    "signalStrength": -35,
>    "signalToNoiseRatio": 0
> }
>   ]
> }
>
> This would be for geolocation services such as skyhook or google
> https://developers.google.com/maps/documentation/geolocation/requests-geolocation
> to allow a device to estimate its location. It seems that what is
> exposed is ESSID information with the strongest AP, or does is this
> information already exposed in iwd and which module/interface should
> be used? If not exposed, which model would be the most appropriate to
> add this to - scan, station, or another - and what interface for dbus
> should the method be exposed through?

Take a look at the ExtendedServiceSet property [1] on the network 
objects. This contains a list of BasicServiceSet object [2] paths. At 
the moment the BasicServiceSet objects only contain the BSSID as this 
was all I really needed for the affinity functionality, but I'm not 
opposed to additional info being added such as signal strength/channel 
etc. If you need any pointers for this let me know, but it should be 
relatively straight forward to add extra properties in the interface 
setup [3].

iwctl also supports showing the BSS object paths/properties via:

"station wlan0 get-bsses"

[1] 
https://git.kernel.org/pub/scm/network/wireless/iwd.git/tree/doc/network-api.txt#n54
[2] 
https://git.kernel.org/pub/scm/network/wireless/iwd.git/tree/doc/basic-service-set.txt
[3] 
https://git.kernel.org/pub/scm/network/wireless/iwd.git/tree/src/network.c#n2196
>
> -Jim
>

  reply	other threads:[~2025-02-15 20:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-15 20:10 Exposing bssid information James Hanley
2025-02-15 20:29 ` James Prestwood [this message]
2025-02-19 20:42   ` James Hanley
2025-02-19 20:53     ` Denis Kenzior
2025-02-19 21:08     ` James Prestwood

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=97112988-3681-4192-abb2-9a9ee6d9552d@gmail.com \
    --to=prestwoj@gmail.com \
    --cc=iwd@lists.linux.dev \
    --cc=jhanley@dgtlrift.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox