iwd.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: James Prestwood <prestwoj@gmail.com>
To: "clement.legoffic@kelio.com" <clement.legoffic@kelio.com>,
	"iwd@lists.linux.dev" <iwd@lists.linux.dev>
Subject: Re: Enable access-point feature
Date: Wed, 24 May 2023 07:11:50 -0700	[thread overview]
Message-ID: <fcc1f156-95d3-d66f-af64-1cce5db653b6@gmail.com> (raw)
In-Reply-To: <cfee44d1ada44a0c85ab52bfcfba80c6@kelio.com>



On 5/24/23 12:14 AM, clement.legoffic@kelio.com wrote:
> Hello,
> 
> I develop a simple software to discuss with iwd using DBus to do simple task such as Connect/Disconnect/Scan/Enable AP
> The fact is that, the iwd version brings by package manager is 1.26 and I cannot get the Access Point API.
> So I have tried to compile a more recent version of IWD (the one tagged 2.4)  and the access point API doesn't appear too.
> I didn't find any information if it is a feature only available using --enable-FEATURE
> In the documentation it is said that it is an experimental feature, but I don't know how to activate it.

AP mode has been around since 2017, I think even within the first public 
release (0.1).

> 
> So how to get this API available ?

Starting an AP requires you set the adapter mode to AP which is done 
using the "Mode" property on the Device interface. After that an 
AccessPoint DBus interface should appear. Doing it with iwctl:

$ iwctl device <wlan> set-property Mode ap
$ iwctl ap <wlan> start MySSID secret123

Thanks,
James

> 
> Thanks,
> 
> Clément
> 
> 
> 
> Ce message et toutes les pieces jointes (ci-apres le "message") sont etablis a l'intention exclusive de ses destinataires.
> Si vous recevez ce message par erreur, merci de le detruire et d'en avertir immediatement l'expediteur par e-mail.
> Toute utilisation de ce message non conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. Les communications sur Internet n'etant pas securisees, l'expediteur informe qu'il ne peut accepter aucune responsabilite quant au contenu de ce message.
> This mail message and attachments (the "message") are solely intended for the addresses. It is confidential in nature.
> If you receive this message in error, please delete it and immediately notify the sender by e-mail.
> Any use other than its intended purpose, dissemination or disclosure, either whole or partial, is prohibited except if formal approval is granted. As communication on the Internet is not secure, the sender does not accept responsibility for the content of this message.
> 

      reply	other threads:[~2023-05-24 14:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-24  7:14 Enable access-point feature clement.legoffic
2023-05-24 14:11 ` James Prestwood [this message]

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=fcc1f156-95d3-d66f-af64-1cce5db653b6@gmail.com \
    --to=prestwoj@gmail.com \
    --cc=clement.legoffic@kelio.com \
    --cc=iwd@lists.linux.dev \
    /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;
as well as URLs for NNTP newsgroup(s).