iwd.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: KeithG <ys3al35l@gmail.com>
To: James Prestwood <prestwoj@gmail.com>
Cc: iwd@lists.linux.dev
Subject: Re: iwd ap mode changed?
Date: Tue, 9 May 2023 23:52:24 -0500	[thread overview]
Message-ID: <CAG17S_OvMmYKJP==2bn-XoCtkUDC7b+sMRk+woeSN9Q_GR9PTw@mail.gmail.com> (raw)
In-Reply-To: <152dff569b6fba0baadd7ac14673cf2a67c42eb4.camel@gmail.com>

On Thu, Mar 2, 2023 at 10:15 AM James Prestwood <prestwoj@gmail.com> wrote:
>
> Hi Keith,
>
> On Tue, 2023-02-28 at 21:26 -0600, KeithG wrote:
> > I am playing with ap mode and I previously used this page to set it
> > up:
> > https://iwd.wiki.kernel.org/ap_mode
> > Now, when I use iwd 2.3, I get
> > "Operation failed"
> > when I use the iwctl ap start or start-profile command.
> > when I revert to version 1.28, it starts to work again.  Is there a
> > changed parameter in the main.conf or something that I do not have
> > set
> > right?
>
> Indeed AP mode has changed in recent releases to support HT. The logic
> now tries to pick the highest channel width possible, and in theory
> enable higher throughput.
>
> But perhaps some hardware doesn't like this, or the logic is wrong. For
> the time being you can set this in the AP profile (with upstream IWD).
>
> [General]
> DisableHT=true
>
> But if you could also send an iwmon/debug log of the problem I can take
> a look. Make sure you start iwmon before IWD starts so I can see the
> advertised hardware capabilities.
>
> Thanks,
> James
>
> >
> > Keith
> >
>
James,

I am finally back on this. I have switched OSes. I was on Arch and am
now on RPiOS.
I built and installed iwd/ell for this os but on the same hardware
(Rpi 3B+) and am having the same problem:
root@runeaudio(rw):~# cat /etc/iwd/main.conf
[General]
EnableNetworkConfiguration=true
UseDefaultInterface=true
DisableHT=true
root@runeaudio(rw):~# cat /var/lib/iwd/ap/RuneAudioAP.ap
[Security]
Passphrase=RuneAudio
[IPv4]
Address=192.168.5.1
Gateway=192.168.5.1
Netmask=255.255.255.0
DNSList=192.168.5.1
root@runeaudio(rw):~# iwctl device list
                                    Devices
--------------------------------------------------------------------------------
  Name                  Address               Powered     Adapter     Mode
--------------------------------------------------------------------------------
  wlan0                 b8:27:eb:xx:xx:xx    on          phy0        ap
root@runeaudio(rw):~# iwctl ap wlan0 start-profile RuneAudioAP
Operation failed
When I try to start iwmon, I also get an error:
root@runeaudio(rw):~# iwmon
Wireless monitor ver 2.4
Failed to create monitor interface nlmon: Unknown error -95

In the journal, I get this when I try to start in AP mode:
May 09 23:47:03 runeaudio iwd[1747]: Could not register frame watch
type 0000: -114
May 09 23:47:03 runeaudio iwd[1747]: Could not register frame watch
type 0020: -114
May 09 23:47:03 runeaudio iwd[1747]: Could not register frame watch
type 0040: -114
May 09 23:47:03 runeaudio iwd[1747]: Could not register frame watch
type 00a0: -114
May 09 23:47:03 runeaudio iwd[1747]: Could not register frame watch
type 00b0: -114
May 09 23:47:03 runeaudio iwd[1747]: Could not register frame watch
type 00c0: -114
May 09 23:47:03 runeaudio iwd[1747]: START_AP failed: -52

when IWD starts, I get this in the journal:
May 09 23:37:17 runeaudio iwd[1747]: No Diffie-Hellman support found,
WPS will not be available
May 09 23:37:17 runeaudio iwd[1747]: The following options are missing
in the kernel:
May 09 23:37:17 runeaudio iwd[1747]:         CONFIG_KEY_DH_OPERATIONS
May 09 23:37:17 runeaudio iwd[1747]: Wireless daemon version 2.4
May 09 23:37:17 runeaudio iwd[1747]: Loaded configuration from
/etc/iwd/main.conf
May 09 23:37:17 runeaudio iwd[1747]: Wiphy: 0, Name: phy0
May 09 23:37:17 runeaudio iwd[1747]:         Permanent Address:
b8:27:eb:52:cc:d0
May 09 23:37:17 runeaudio iwd[1747]:         2.4Ghz Band:
May 09 23:37:17 runeaudio iwd[1747]:                 Bitrates (non-HT):
May 09 23:37:17 runeaudio iwd[1747]:                          1.0 Mbps
May 09 23:37:17 runeaudio iwd[1747]:                          2.0 Mbps
May 09 23:37:17 runeaudio iwd[1747]:                          5.5 Mbps
May 09 23:37:17 runeaudio iwd[1747]:                         11.0 Mbps
May 09 23:37:17 runeaudio iwd[1747]:                          6.0 Mbps
May 09 23:37:17 runeaudio iwd[1747]:                          9.0 Mbps
May 09 23:37:17 runeaudio iwd[1747]:                         12.0 Mbps
May 09 23:37:17 runeaudio iwd[1747]:                         18.0 Mbps
May 09 23:37:17 runeaudio iwd[1747]:                         24.0 Mbps
May 09 23:37:17 runeaudio iwd[1747]:                         36.0 Mbps
May 09 23:37:17 runeaudio iwd[1747]:                         48.0 Mbps
May 09 23:37:17 runeaudio iwd[1747]:                         54.0 Mbps
May 09 23:37:17 runeaudio iwd[1747]:                 HT Capabilities:
May 09 23:37:17 runeaudio iwd[1747]:                         HT40
May 09 23:37:17 runeaudio iwd[1747]:                         Short GI for 20Mhz
May 09 23:37:17 runeaudio iwd[1747]:                 HT RX MCS indexes:
May 09 23:37:17 runeaudio iwd[1747]:                         0-7
May 09 23:37:17 runeaudio iwd[1747]:         5Ghz Band:
May 09 23:37:17 runeaudio iwd[1747]:                 Bitrates (non-HT):
May 09 23:37:17 runeaudio iwd[1747]:                          6.0 Mbps
May 09 23:37:17 runeaudio iwd[1747]:                          9.0 Mbps
May 09 23:37:17 runeaudio iwd[1747]:                         12.0 Mbps
May 09 23:37:17 runeaudio iwd[1747]:                         18.0 Mbps
May 09 23:37:17 runeaudio iwd[1747]:                         24.0 Mbps
May 09 23:37:17 runeaudio iwd[1747]:                         36.0 Mbps
May 09 23:37:17 runeaudio iwd[1747]:                         48.0 Mbps
May 09 23:37:17 runeaudio iwd[1747]:                         54.0 Mbps
May 09 23:37:17 runeaudio iwd[1747]:                 HT Capabilities:
May 09 23:37:17 runeaudio iwd[1747]:                         HT40
May 09 23:37:17 runeaudio iwd[1747]:                         Short GI for 20Mhz
May 09 23:37:17 runeaudio iwd[1747]:                         Short GI for 40Mhz
May 09 23:37:17 runeaudio iwd[1747]:                 HT RX MCS indexes:
May 09 23:37:17 runeaudio iwd[1747]:                         0-7
May 09 23:37:17 runeaudio iwd[1747]:                 VHT Capabilities:
May 09 23:37:17 runeaudio iwd[1747]:                         Short GI for 80Mhz
May 09 23:37:17 runeaudio iwd[1747]:                         Max RX
MCS: 0-9 for NSS: 1
May 09 23:37:17 runeaudio iwd[1747]:                         Max TX
MCS: 0-9 for NSS: 1
May 09 23:37:17 runeaudio iwd[1747]:         Ciphers: BIP-CMAC-128 CCMP-128 TKIP
May 09 23:37:17 runeaudio iwd[1747]:         Supported iftypes: ad-hoc
station ap p2p-client p2p-go p2p-device
May 09 23:37:17 runeaudio iwd[1747]: Wiphy phy0 will only use the
default interface
May 09 23:37:17 runeaudio iwd[1747]: Could not register frame watch
type 00b0: -22


Keith

  reply	other threads:[~2023-05-10  4:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-01  3:26 iwd ap mode changed? KeithG
2023-03-02 16:15 ` James Prestwood
2023-05-10  4:52   ` KeithG [this message]
2023-05-10 15:02     ` 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='CAG17S_OvMmYKJP==2bn-XoCtkUDC7b+sMRk+woeSN9Q_GR9PTw@mail.gmail.com' \
    --to=ys3al35l@gmail.com \
    --cc=iwd@lists.linux.dev \
    --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;
as well as URLs for NNTP newsgroup(s).