All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz at gmail.com>
To: iwd at lists.01.org
Subject: Re: iwd access point mode
Date: Fri, 08 Oct 2021 09:45:14 -0500	[thread overview]
Message-ID: <e5efb7a7-8c5d-2955-5e1c-441f4da5fbce@gmail.com> (raw)
In-Reply-To: CAOf5uwk5RkWEOuOsWTyFynQRsnWBHx8nByOzew283YHNanQQTg@mail.gmail.com

[-- Attachment #1: Type: text/plain, Size: 1551 bytes --]

Hi Michael,

On 10/7/21 2:48 PM, Michael Nazzareno Trimarchi wrote:
> HI all
> 
> I'm playing with iwd. Looking at iwmon I can see virtual device
> discovered by iwd when they are created.
> 
> iw phy phy0 interface add wlan1 __ap
> 
> iwctl still report wlan0
> 

Right.  Since most people want to use iwd + hostapd for such tethering cases, we 
made the decision to simply ignore any new devices created outside iwd after a 
wiphy has been initialized.

You can get around this by creating the sta + ap devices first, then starting 
iwd.  You'll need to set UseDefaultInterface=true in /etc/iwd/main.conf.  See 
'man 5 iwd.config' for more details.

>   I was able to create wifi connection and access point mode using
> wpa_supplicant and NetworkManager. My idea
> is was experimenting iwd
> 
> iwctl device list still report only wlan1. The idea behind is to
> control ap+sta interface. Any feedback?
> 

Teaching iwd to create STA + AP interfaces when it initializes an adapter is on 
the TODO list.  We already do this with P2P, but not STA + AP.  This should be 
fairly easy to do, but we have been busy with other tasks.  Patches are always 
welcome!

Our (preliminary) thinking on this was to add a main.conf entry that tells iwd 
how it should manage wiphys by default.  Something like: "sta-only", "sta+p2p", 
"sta+ap".  Based on the configured setting, iwd would then create the interfaces 
automagically (assuming hardware/driver supports it,  falling back to "sta-only" 
if not).

Regards,
-Denis

             reply	other threads:[~2021-10-08 14:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-08 14:45 Denis Kenzior [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-10-08 18:53 iwd access point mode Michael Nazzareno Trimarchi
2021-10-08 18:25 Denis Kenzior
2021-10-08 16:40 Michael Nazzareno Trimarchi
2021-10-08 15:50 Denis Kenzior
2021-10-08 15:23 Michael Nazzareno Trimarchi
2021-10-08 15:19 Denis Kenzior
2021-10-07 19:48 Michael Nazzareno Trimarchi

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=e5efb7a7-8c5d-2955-5e1c-441f4da5fbce@gmail.com \
    --to=unknown@example.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.