public inbox for iwd@lists.linux.dev
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: James Hanley <jhanley@dgtlrift.com>,
	James Prestwood <prestwoj@gmail.com>
Cc: iwd@lists.linux.dev
Subject: Re: Exposing bssid information
Date: Wed, 19 Feb 2025 14:53:59 -0600	[thread overview]
Message-ID: <d4ae8e61-96ab-41bd-8e24-daf9a316eae0@gmail.com> (raw)
In-Reply-To: <CAF++6AMYxXJZg_im3z_4PDgUj0tr7t4Ag0KFetoTu-SKuYcYVQ@mail.gmail.com>

Hi James,

On 2/19/25 2:42 PM, James Hanley wrote:
> Thanks - this is really helpful for direction. I was going to
> initially brute force load all the attributes into a new interface,
> but it seems the preferred course from your suggestion is to gather
> the ESSID information and query each node individually for the BSSID
> information and populate that method with the associated details?
> 
> One point that I'm stumbling on in testing the pristine codebase is
> accessing the ExtendedServiceSet property:
> test-wifi/test# dbus-send --system --type=method_call --print-reply
> --dest=net.connman.iwd /net/connman/iwd/0/2/53-elided-53_psk
> net.connman.iwd.Network.ExtendedServiceSet
> Error org.freedesktop.DBus.Error.NotFound: No matching method found
> 

You are trying to invoke a method.  ExtendedServiceSet is a property.

> When I query for the available interfaces and methods, I am able to see:
> test-wifi/test# dbus-send --system --type=method_call --print-reply
> --dest=net.connman.iwd /net/connman/iwd/0/2/53-elided-53_psk
> org.freedesktop.DBus.Introspectable.Introspect
> method return time=1739996534.609643 sender=:1.1090 ->
> destination=:1.1474 serial=2631 reply_serial=2
>     string "<!DOCTYPE node PUBLIC "-//freedesktop//DTD D-BUS Object
> Introspection 1.0//EN"
> "http://www.freedesktop.org/standards/dbus/1.0/introspect.dtd">
> <node>
>          <interface name="org.freedesktop.DBus.Introspectable">
>                  <method name="Introspect">
>                          <arg name="xml" type="s" direction="out"/>
>                  </method>
>          </interface>
>          <interface name="net.connman.iwd.Network">
>                  <method name="Connect">
>                  </method>
>                  <property name="Name" type="s" access="read"/>
>                  <property name="Connected" type="b" access="read"/>
>                  <property name="Device" type="o" access="read"/>
>                  <property name="Type" type="s" access="read"/>
>                  <property name="KnownNetwork" type="o" access="read"/>
>                  <property name="ExtendedServiceSet" type="ao" access="read"/>

^^^

>          </interface>
>          <interface name="org.freedesktop.DBus.Properties">
>                  <method name="Get">
>                          <arg name="interface_name" type="s" direction="in"/>
>                          <arg name="property_name" type="s" direction="in"/>
>                          <arg name="value" type="v" direction="out"/>

Use this or the GetAll method to query properties.

>                  </method>
>                  <method name="Set">
>                          <arg name="interface_name" type="s" direction="in"/>
>                          <arg name="property_name" type="s" direction="in"/>
>                          <arg name="value" type="v" direction="in"/>
>                  </method>
>                  <method name="GetAll">
>                          <arg name="interface_name" type="s" direction="in"/>
>                          <arg name="props" type="a{sv}" direction="out"/>
>                  </method>
>                  <signal name="PropertiesChanged">
>                          <arg name="interface_name" type="s"/>
>                          <arg name="changed_properties" type="a{sv}"/>
>                          <arg name="invalidated_properties" type="as"/>
>                  </signal>
>          </interface>
>          <node name="d8-elided-95"/>
>          <node name="d8-elided-55"/>
>          <node name="d8-elided-15"/>
>          <node name="d8-elided-95"/>
>          <node name="d8-elided-55"/>
>          <node name="d8-elided-95"/>
> </node>
> "
> 
> Is there something I'm missing in attempting to access this detail
> from dbus-send?  Ultimately this is only for testing, but I do plan on
> using the DBusConnection c-api and getting it right with dbus-send
> will help me in defining the code flow.

Try qdbus-viewer or d-feet.  Nicer to use than dbus-send.

> 
> -Jim

Regards,
-Denis

  reply	other threads:[~2025-02-19 20:54 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
2025-02-19 20:42   ` James Hanley
2025-02-19 20:53     ` Denis Kenzior [this message]
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=d4ae8e61-96ab-41bd-8e24-daf9a316eae0@gmail.com \
    --to=denkenz@gmail.com \
    --cc=iwd@lists.linux.dev \
    --cc=jhanley@dgtlrift.com \
    --cc=prestwoj@gmail.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