* iwd ap mode changed?
@ 2023-03-01 3:26 KeithG
2023-03-02 16:15 ` James Prestwood
0 siblings, 1 reply; 4+ messages in thread
From: KeithG @ 2023-03-01 3:26 UTC (permalink / raw)
To: iwd
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?
Keith
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: iwd ap mode changed?
2023-03-01 3:26 iwd ap mode changed? KeithG
@ 2023-03-02 16:15 ` James Prestwood
2023-05-10 4:52 ` KeithG
0 siblings, 1 reply; 4+ messages in thread
From: James Prestwood @ 2023-03-02 16:15 UTC (permalink / raw)
To: KeithG, iwd
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
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: iwd ap mode changed?
2023-03-02 16:15 ` James Prestwood
@ 2023-05-10 4:52 ` KeithG
2023-05-10 15:02 ` James Prestwood
0 siblings, 1 reply; 4+ messages in thread
From: KeithG @ 2023-05-10 4:52 UTC (permalink / raw)
To: James Prestwood; +Cc: iwd
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: iwd ap mode changed?
2023-05-10 4:52 ` KeithG
@ 2023-05-10 15:02 ` James Prestwood
0 siblings, 0 replies; 4+ messages in thread
From: James Prestwood @ 2023-05-10 15:02 UTC (permalink / raw)
To: KeithG; +Cc: iwd
Hi Keith,
On 5/9/23 9:52 PM, KeithG wrote:
> 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
Ah, DisableHT should be in the AP profile, not main.conf.
> 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
This is either a permission issue (sudo iwmon) or a module problem
(modprobe nlmon).
>
> 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
"Invalid exchange", that's a new one...
Try putting DisableHT in the AP profile and hopefully it lets you start it.
On this same topic I have a feeling drivers that I don't use or didn't
test on have issues with setting the channel width. Prior to adding HT
we let the driver decide, now we set it explicitly. Maybe HT needs to be
an opt-in rather than opt-out...
Thanks,
James
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2023-05-10 15:02 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-03-01 3:26 iwd ap mode changed? KeithG
2023-03-02 16:15 ` James Prestwood
2023-05-10 4:52 ` KeithG
2023-05-10 15:02 ` James Prestwood
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).