Skip to contentSkip to conversation

Iwd: unable to start AP with NXP 88W9098 chipset

DISCUSSION Joao Marcos Costa 2 participants 7 messages Dec 21, 2023 – Jan 24, 2024

lore
Share & tools
lore
#0 lore raw

Hello,

I hope this email finds you well.

I'm currently facing what seems to be the very same bug reported at https://lore.kernel.org/iwd/AM7PR01MB67244F63EBEAB9A65D965BEAADC69@AM7PR01MB6724.eurprd01.prod.exchangelabs.com/

As for my own context, I'm using:

- Ublox wifi module Jody-W377-00A

- IWD v1.26 (from meta-openembedded)

- Linux v6.1.68 (x86_64)

- NXP Wi-Fi driver for NXP 88W9098 chipset, from github.com/nxp-imx/mwifiex (branch=lf-6.1.55_2.2.0)

I followed the steps in https://iwd.wiki.kernel.org/ap_mode, and this is the error I get in my iwctl console:

# iwctl
NetworkConfigurationEnabled: enabled
StateDirectory: /var/lib/iwd
Version: 1.26
[iwd]# device muap0 set-property Mode ap
[iwd]# device list
Devices                                   *
--------------------------------------------------------------------------------
  Name                Address             Powered   Adapter Mode
--------------------------------------------------------------------------------
  uap0                62:09:c3:80:9b:1d   on        mwiphy0 ap
  mlan0              60:09:c3:80:9a:1d   on        mwiphy0 station
  muap0             62:09:c3:80:9b:1e   on        mwiphy1 ap
  mmlan0           60:09:c3:80:9a:1e   on        mwiphy1 station
[iwd]# ap list
                          Devices in Access Point Mode                        *
--------------------------------------------------------------------------------
  Name                Started
--------------------------------------------------------------------------------
  uap0                no
  muap0             no

[iwd]# ap muap0 start-profile testap
[iwd]# [22444.663032] wlan: Starting AP

[22444.668197] fw doesn't support 11ax
[22444.674130] CMD_RESP: cmd 0xb1 error, result=0x1
[22444.679286] IOCTL failed: 00000000ae152881 id=0x20000, sub_id=0x20001 action=1, status_code=0x1
[22444.689145] woal_cfg80211_add_beacon: start uap failed

Operation failed

My /var/lib/iwd/ap/testap.ap file is identical to the one provided in the Wiki, and as for my main.conf:

---

[General]
EnableNetworkConfiguration=true
UseDefaultInterface=true

[Network]

[Scan]
DisablePeriodicScan=true

---

I tried adding Country=FR and ControlPortOverNL80211=false, but without any success.

I also added DisableHT=true in the testap.ap file later on, but the result was the same.

However, I was able to start the Access Point using hostapd, and it worked fine.

I can provide you with my hostapd.conf, if you find it pertinent.

Since referencing the original thread, are there any updates?

Has anyone else encountered a similar issue? Even if the chipset is not precisely the same.

Please feel free to ask for logs or other unmentioned details, and thank you for your assistance.

Signature · 2 lines
Best regards,
João Marcos Costa
#1 lore raw

Hi Joao,

Quoted 11 lines · Joao Marcos Costa

Hello,

I hope this email finds you well.

I'm currently facing what seems to be the very same bug reported at https://lore.kernel.org/iwd/AM7PR01MB67244F63EBEAB9A65D965BEAADC69@AM7PR01MB6724.eurprd01.prod.exchangelabs.com/

As for my own context, I'm using:

- Ublox wifi module Jody-W377-00A

- IWD v1.26 (from meta-openembedded)

This is quite an old version, there have been many changes to AP mode since then.

Quoted 52 lines

- Linux v6.1.68 (x86_64)

- NXP Wi-Fi driver for NXP 88W9098 chipset, from github.com/nxp-imx/mwifiex (branch=lf-6.1.55_2.2.0)

I followed the steps in https://iwd.wiki.kernel.org/ap_mode, and this is the error I get in my iwctl console:

# iwctl
NetworkConfigurationEnabled: enabled
StateDirectory: /var/lib/iwd
Version: 1.26
[iwd]# device muap0 set-property Mode ap
[iwd]# device list
Devices                                   *
-------------------------------------------------------------------------------- 

  Name                Address             Powered   Adapter Mode
--------------------------------------------------------------------------------

  uap0                62:09:c3:80:9b:1d   on        mwiphy0 ap mlan0              60:09:c3:80:9a:1d   on        mwiphy0 station muap0             62:09:c3:80:9b:1e   on        mwiphy1 ap mmlan0           60:09:c3:80:9a:1e   on        mwiphy1 station [iwd]# ap list
                          Devices in Access Point Mode                        *
--------------------------------------------------------------------------------

  Name                Started
--------------------------------------------------------------------------------

  uap0                no
  muap0             no

[iwd]# ap muap0 start-profile testap
[iwd]# [22444.663032] wlan: Starting AP

[22444.668197] fw doesn't support 11ax
[22444.674130] CMD_RESP: cmd 0xb1 error, result=0x1
[22444.679286] IOCTL failed: 00000000ae152881 id=0x20000, sub_id=0x20001 action=1, status_code=0x1
[22444.689145] woal_cfg80211_add_beacon: start uap failed

Operation failed

My /var/lib/iwd/ap/testap.ap file is identical to the one provided in the Wiki, and as for my main.conf:

---

[General]
EnableNetworkConfiguration=true
UseDefaultInterface=true

[Network]

Quoted 8 lines

[Scan]
DisablePeriodicScan=true

---

I tried adding Country=FR and ControlPortOverNL80211=false, but without any success.

I also added DisableHT=true in the testap.ap file later on, but the result was the same.

This is a more recent option. I have a feeling if you updated IWD and set DisableHT it would work.

Quoted 11 lines

However, I was able to start the Access Point using hostapd, and it worked fine.

I can provide you with my hostapd.conf, if you find it pertinent.

Since referencing the original thread, are there any updates?

Has anyone else encountered a similar issue? Even if the chipset is not precisely the same.

Please feel free to ask for logs or other unmentioned details, and thank you for your assistance.

When helping  Salahaldeen in the original thread I remember that hardware being extremely flaky. It would start sometimes and not others, and if it failed once it would need a full reboot to get it working again. Even with hostapd if I used an option it didn't like it required a full reboot to get it going again.

IIRC there was also some success on one of the interfaces but not the others. If you could provide some IWD debug logs too that would be great, and might as well show the hostapd configuration that works as well.

Thanks,

James

#2 lore raw

Hello James,

Thanks for such a quick reply!

Quoted 70 lines · James Prestwood

Hi Joao,

Quoted 11 lines · Joao Marcos Costa

Hello,

I hope this email finds you well.

I'm currently facing what seems to be the very same bug reported at https://lore.kernel.org/iwd/AM7PR01MB67244F63EBEAB9A65D965BEAADC69@AM7PR01MB6724.eurprd01.prod.exchangelabs.com/

As for my own context, I'm using:

- Ublox wifi module Jody-W377-00A

- IWD v1.26 (from meta-openembedded)

This is quite an old version, there have been many changes to AP mode since then.

Quoted 55 lines

- Linux v6.1.68 (x86_64)

- NXP Wi-Fi driver for NXP 88W9098 chipset, from github.com/nxp-imx/mwifiex (branch=lf-6.1.55_2.2.0)

I followed the steps in https://iwd.wiki.kernel.org/ap_mode, and this is the error I get in my iwctl console:

# iwctl
NetworkConfigurationEnabled: enabled
StateDirectory: /var/lib/iwd
Version: 1.26
[iwd]# device muap0 set-property Mode ap
[iwd]# device list
Devices                                   *
-------------------------------------------------------------------------------- 

  Name                Address             Powered   Adapter Mode
--------------------------------------------------------------------------------

  uap0                62:09:c3:80:9b:1d   on        mwiphy0 ap mlan0              60:09:c3:80:9a:1d   on        mwiphy0 station muap0             62:09:c3:80:9b:1e   on        mwiphy1 ap mmlan0           60:09:c3:80:9a:1e   on        mwiphy1 station [iwd]# ap list
                          Devices in Access Point Mode                        *
--------------------------------------------------------------------------------

  Name                Started
--------------------------------------------------------------------------------

  uap0                no
  muap0             no

[iwd]# ap muap0 start-profile testap
[iwd]# [22444.663032] wlan: Starting AP

[22444.668197] fw doesn't support 11ax
[22444.674130] CMD_RESP: cmd 0xb1 error, result=0x1
[22444.679286] IOCTL failed: 00000000ae152881 id=0x20000, sub_id=0x20001 action=1, status_code=0x1
[22444.689145] woal_cfg80211_add_beacon: start uap failed

Operation failed

My /var/lib/iwd/ap/testap.ap file is identical to the one provided in the Wiki, and as for my main.conf:

---

[General]
EnableNetworkConfiguration=true
UseDefaultInterface=true

[Network]

[Scan]
DisablePeriodicScan=true

Quoted 6 lines
Quoted 5 lines

---

I tried adding Country=FR and ControlPortOverNL80211=false, but without any success.

I also added DisableHT=true in the testap.ap file later on, but the result was the same.

This is a more recent option. I have a feeling if you updated IWD and set DisableHT it would work.

I updated it to v2.9 and indeed it works. For documentation's sake:

This is my /etc/iwd/main.conf:

   [General]
   EnableNetworkConfiguration=true
   Country=FR
   UseDefaultInterface=true

   [Network]

   [Scan]
   DisablePeriodicScan=true

and this is my /var/lib/iwd/ap/test.ap:

   [General]
   DisableHT=true
   Channel=10

   [Security]
   Passphrase=password123

   [IPv4]
   Address=192.168.250.1
   Gateway=192.168.250.1
   Netmask=255.255.255.0
   DNSList=8.8.8.8

Quoted 7 lines
Quoted 7 lines

However, I was able to start the Access Point using hostapd, and it worked fine.

I can provide you with my hostapd.conf, if you find it pertinent.

Since referencing the original thread, are there any updates?

Quoted 7 lines
Quoted 3 lines

Has anyone else encountered a similar issue? Even if the chipset is not precisely the same.

Please feel free to ask for logs or other unmentioned details, and thank you for your assistance.

When helping  Salahaldeen in the original thread I remember that hardware being extremely flaky. It would start sometimes and not others, and if it failed once it would need a full reboot to get it working again. Even with hostapd if I used an option it didn't like it required a full reboot to get it going again.

IIRC there was also some success on one of the interfaces but not the others. If you could provide some IWD debug logs too that would be great, and might as well show the hostapd configuration that works as well.

I kept trying with muap0 interface, which worked fine.

Just in case, here's my hostapd.conf:

   # the interface used by the AP
   interface=muap0
   # "g" simply means 2.4GHz band
   hw_mode=g
   # the channel to use
   channel=10
   # limit the frequencies used to those allowed in the country
   ieee80211d=1
   # the country code
   country_code=FR
   # 802.11n support
   ieee80211n=1
   # QoS support, also required for full speed on 802.11n/ac/ax
   wmm_enabled=1
   # the name of the AP
   ssid=test

   # 1=wpa, 2=wep, 3=both
   auth_algs=1
   # WPA2 only
   wpa=2
   wpa_key_mgmt=WPA-PSK
   rsn_pairwise=CCMP
   wpa_passphrase=password123

Quoted 4 lines

Thanks,

James

Thanks once more. I hope this will be of help to other users.

Signature · 2 lines
Best regards,
João Marcos Costa
#3 lore raw

Hello James,

Quoted 4 lines · Joao Marcos Costa

Hello James,

Thanks for such a quick reply!

[...]

Quoted 29 lines

I updated it to v2.9 and indeed it works. For documentation's sake:

This is my /etc/iwd/main.conf:

   [General]
   EnableNetworkConfiguration=true
   Country=FR
   UseDefaultInterface=true

   [Network]

   [Scan]
   DisablePeriodicScan=true

and this is my /var/lib/iwd/ap/test.ap:

   [General]
   DisableHT=true
   Channel=10

   [Security]
   Passphrase=password123

   [IPv4]
   Address=192.168.250.1
   Gateway=192.168.250.1
   Netmask=255.255.255.0
   DNSList=8.8.8.8

[...]

Quoted 26 lines
Quoted 3 lines

When helping  Salahaldeen in the original thread I remember that hardware being extremely flaky. It would start sometimes and not others, and if it failed once it would need a full reboot to get it working again. Even with hostapd if I used an option it didn't like it required a full reboot to get it going again.

IIRC there was also some success on one of the interfaces but not the others. If you could provide some IWD debug logs too that would be great, and might as well show the hostapd configuration that works as well.

I kept trying with muap0 interface, which worked fine.

Just in case, here's my hostapd.conf:

   # the interface used by the AP
   interface=muap0
   # "g" simply means 2.4GHz band
   hw_mode=g
   # the channel to use
   channel=10
   # limit the frequencies used to those allowed in the country
   ieee80211d=1
   # the country code
   country_code=FR
   # 802.11n support
   ieee80211n=1
   # QoS support, also required for full speed on 802.11n/ac/ax
   wmm_enabled=1
   # the name of the AP
   ssid=test
Quoted 7 lines

   # 1=wpa, 2=wep, 3=both
   auth_algs=1
   # WPA2 only
   wpa=2
   wpa_key_mgmt=WPA-PSK
   rsn_pairwise=CCMP
   wpa_passphrase=password123

Would you remember if you faced performance issues with this hardware/driver?

I'm using iwd v2.9 with the same main.conf and *.ap (except for the IP addresses) as before, and this is what I get with iperf3:

iperf3 -c 10.0.24.1
Connecting to host 10.0.24.1, port 5201
[  5] local 10.0.24.102 port 46170 connected to 10.0.24.1 port 5201 [ ID] Interval           Transfer     Bitrate         Retr  Cwnd [  5]   0.00-1.00   sec   768 KBytes  6.29 Mbits/sec    0   45.2 KBytes [  5]   1.00-2.00   sec   512 KBytes  4.19 Mbits/sec    0   46.7 KBytes [  5]   2.00-3.00   sec   640 KBytes  5.24 Mbits/sec    0   49.5 KBytes [  5]   3.00-4.00   sec   384 KBytes  3.14 Mbits/sec    0   53.7 KBytes [  5]   4.00-5.00   sec   384 KBytes  3.15 Mbits/sec    0   53.7 KBytes [  5]   5.00-6.00   sec   512 KBytes  4.19 Mbits/sec    0   53.7 KBytes [  5]   6.00-7.00   sec   256 KBytes  2.10 Mbits/sec    0   53.7 KBytes [  5]   7.00-8.00   sec   512 KBytes  4.19 Mbits/sec    0   53.7 KBytes [  5]   8.00-9.00   sec   512 KBytes  4.19 Mbits/sec    0   53.7 KBytes [  5]   9.00-10.00  sec   768 KBytes  6.29 Mbits/sec    0   74.9 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec  5.12 MBytes  4.30 Mbits/sec 0             sender [  5]   0.00-10.05  sec  4.77 MBytes  3.98 Mbits/sec                  receiver

iperf Done.

On the other hand, with hostapd (using the same hostapd.conf as before), I'm getting considerably better results:

Connecting to host 192.168.0.1, port 5201
[  5] local 192.168.0.2 port 44490 connected to 192.168.0.1 port 5201 [ ID] Interval           Transfer     Bitrate         Retr  Cwnd [  5]   0.00-1.00   sec  12.1 MBytes   102 Mbits/sec    0    447 KBytes [  5]   1.00-2.00   sec  9.12 MBytes  76.5 Mbits/sec    0    472 KBytes [  5]   2.00-3.00   sec  9.50 MBytes  79.8 Mbits/sec    0    551 KBytes [  5]   3.00-4.00   sec  9.75 MBytes  81.7 Mbits/sec    0    611 KBytes [  5]   4.00-5.00   sec  10.4 MBytes  87.0 Mbits/sec    0    626 KBytes [  5]   5.00-6.00   sec  10.1 MBytes  85.0 Mbits/sec    0    626 KBytes [  5]   6.00-7.00   sec  11.5 MBytes  96.5 Mbits/sec    0    626 KBytes [  5]   7.00-8.00   sec  10.1 MBytes  84.9 Mbits/sec    0    626 KBytes [  5]   8.00-9.00   sec  12.8 MBytes   107 Mbits/sec    0    701 KBytes [  5]   9.00-10.00  sec  11.6 MBytes  97.4 Mbits/sec    0    747 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec   107 MBytes  89.7 Mbits/sec 0             sender [  5]   0.00-10.02  sec   104 MBytes  86.9 Mbits/sec                  receiver

iperf Done.

I tried removing 'DisableHT', but that raises some issues on the driver:

| CMD_RESP: cmd 0xb0 error, result=0x1
| IOCTL failed: 000000006106683e id=0x20000, sub_id=0x2000c action=1, status_code=0x1

or:

No matching method found
Failed to retrieve I[  610.756333] Block woal_cfg80211_set_power_mgmt in abnormal driver state WD dbus objects, quitting...

Could you please give me some insights on why we need DisableHT for it to work?

Would you have any suggestions on how to approach this performance gap?

Thanks once more!

Signature · 2 lines
Best regards,
João Marcos Costa
#4 lore raw

Hi Joao,

Quoted 134 lines · Joao Marcos Costa

Hello James,

Quoted 4 lines · Joao Marcos Costa

Hello James,

Thanks for such a quick reply!

[...]

Quoted 29 lines

I updated it to v2.9 and indeed it works. For documentation's sake:

This is my /etc/iwd/main.conf:

   [General]
   EnableNetworkConfiguration=true
   Country=FR
   UseDefaultInterface=true

   [Network]

   [Scan]
   DisablePeriodicScan=true

and this is my /var/lib/iwd/ap/test.ap:

   [General]
   DisableHT=true
   Channel=10

   [Security]
   Passphrase=password123

   [IPv4]
   Address=192.168.250.1
   Gateway=192.168.250.1
   Netmask=255.255.255.0
   DNSList=8.8.8.8

[...]

Quoted 26 lines
Quoted 3 lines

When helping  Salahaldeen in the original thread I remember that hardware being extremely flaky. It would start sometimes and not others, and if it failed once it would need a full reboot to get it working again. Even with hostapd if I used an option it didn't like it required a full reboot to get it going again.

IIRC there was also some success on one of the interfaces but not the others. If you could provide some IWD debug logs too that would be great, and might as well show the hostapd configuration that works as well.

I kept trying with muap0 interface, which worked fine.

Just in case, here's my hostapd.conf:

   # the interface used by the AP
   interface=muap0
   # "g" simply means 2.4GHz band
   hw_mode=g
   # the channel to use
   channel=10
   # limit the frequencies used to those allowed in the country
   ieee80211d=1
   # the country code
   country_code=FR
   # 802.11n support
   ieee80211n=1
   # QoS support, also required for full speed on 802.11n/ac/ax
   wmm_enabled=1
   # the name of the AP
   ssid=test
Quoted 7 lines

   # 1=wpa, 2=wep, 3=both
   auth_algs=1
   # WPA2 only
   wpa=2
   wpa_key_mgmt=WPA-PSK
   rsn_pairwise=CCMP
   wpa_passphrase=password123

Would you remember if you faced performance issues with this hardware/driver?

I'm using iwd v2.9 with the same main.conf and *.ap (except for the IP addresses) as before, and this is what I get with iperf3:

iperf3 -c 10.0.24.1
Connecting to host 10.0.24.1, port 5201
[  5] local 10.0.24.102 port 46170 connected to 10.0.24.1 port 5201 [ ID] Interval           Transfer     Bitrate         Retr  Cwnd [  5]   0.00-1.00   sec   768 KBytes  6.29 Mbits/sec    0   45.2 KBytes [  5]   1.00-2.00   sec   512 KBytes  4.19 Mbits/sec    0   46.7 KBytes [  5]   2.00-3.00   sec   640 KBytes  5.24 Mbits/sec    0   49.5 KBytes [  5]   3.00-4.00   sec   384 KBytes  3.14 Mbits/sec    0   53.7 KBytes [  5]   4.00-5.00   sec   384 KBytes  3.15 Mbits/sec    0   53.7 KBytes [  5]   5.00-6.00   sec   512 KBytes  4.19 Mbits/sec    0   53.7 KBytes [  5]   6.00-7.00   sec   256 KBytes  2.10 Mbits/sec    0   53.7 KBytes [  5]   7.00-8.00   sec   512 KBytes  4.19 Mbits/sec    0   53.7 KBytes [  5]   8.00-9.00   sec   512 KBytes  4.19 Mbits/sec    0   53.7 KBytes [  5]   9.00-10.00  sec   768 KBytes  6.29 Mbits/sec    0   74.9 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec  5.12 MBytes  4.30 Mbits/sec 0 sender
[  5]   0.00-10.05  sec  4.77 MBytes  3.98 Mbits/sec                  receiver

iperf Done.

On the other hand, with hostapd (using the same hostapd.conf as before), I'm getting considerably better results:

Connecting to host 192.168.0.1, port 5201
[  5] local 192.168.0.2 port 44490 connected to 192.168.0.1 port 5201 [ ID] Interval           Transfer     Bitrate         Retr  Cwnd [  5]   0.00-1.00   sec  12.1 MBytes   102 Mbits/sec    0    447 KBytes [  5]   1.00-2.00   sec  9.12 MBytes  76.5 Mbits/sec    0    472 KBytes [  5]   2.00-3.00   sec  9.50 MBytes  79.8 Mbits/sec    0    551 KBytes [  5]   3.00-4.00   sec  9.75 MBytes  81.7 Mbits/sec    0    611 KBytes [  5]   4.00-5.00   sec  10.4 MBytes  87.0 Mbits/sec    0    626 KBytes [  5]   5.00-6.00   sec  10.1 MBytes  85.0 Mbits/sec    0    626 KBytes [  5]   6.00-7.00   sec  11.5 MBytes  96.5 Mbits/sec    0    626 KBytes [  5]   7.00-8.00   sec  10.1 MBytes  84.9 Mbits/sec    0    626 KBytes [  5]   8.00-9.00   sec  12.8 MBytes   107 Mbits/sec    0    701 KBytes [  5]   9.00-10.00  sec  11.6 MBytes  97.4 Mbits/sec    0    747 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec   107 MBytes  89.7 Mbits/sec 0 sender
[  5]   0.00-10.02  sec   104 MBytes  86.9 Mbits/sec                  receiver

iperf Done.

I tried removing 'DisableHT', but that raises some issues on the driver:

| CMD_RESP: cmd 0xb0 error, result=0x1
| IOCTL failed: 000000006106683e id=0x20000, sub_id=0x2000c action=1, status_code=0x1

or:

Quoted 8 lines

No matching method found
Failed to retrieve I[  610.756333] Block woal_cfg80211_set_power_mgmt in abnormal driver state WD dbus objects, quitting...

Could you please give me some insights on why we need DisableHT for it to work?

Would you have any suggestions on how to approach this performance gap?

Prior to me adding HT (high throughput) IWD's AP mode was just using basic rates, so very slow. I added HT support, but apparently not all drivers were happy about it. So DisableHT removes the extra stuff that allows it to work with this specific driver, but at the cost of performance.

I'm not really in a position to devote a lot of time to AP mode at the moment. I know we've gotten a lot of inquiries about it recently but to be completely honest if your intent is to run a full fledged access point hostapd is really the tool to use. I'd love to get IWD up to the same level of quality and support as hostapd but its a massive undertaking. Not only that but out of tree driver support is something very hard to get right. Hostapd has been around long enough and is the de-factor software for APs that hardware vendors have added their quirks here and there, IWD doesn't have that luxury.

Thanks,

James

Quoted 4 lines

Thanks once more!

#5 lore raw

Hi James,

On 1/19/24 18:44, James Prestwood wrote:

[...]

Quoted 8 lines

Prior to me adding HT (high throughput) IWD's AP mode was just using basic rates, so very slow. I added HT support, but apparently not all drivers were happy about it. So DisableHT removes the extra stuff that allows it to work with this specific driver, but at the cost of performance.

I'm not really in a position to devote a lot of time to AP mode at the moment. I know we've gotten a lot of inquiries about it recently but to be completely honest if your intent is to run a full fledged access point hostapd is really the tool to use. I'd love to get IWD up to the same level of quality and support as hostapd but its a massive undertaking. Not only that but out of tree driver support is something very hard to get right. Hostapd has been around long enough and is the de-factor software for APs that hardware vendors have added their quirks here and there, IWD doesn't have that luxury.

Thanks,

James

Thanks for this insight. I'll keep DisableHT for my tests, then.

However, there's still something I don't quite understand. I'm trying to set up this AP:

[General]
DisableHT=true
Channel=36

[Security]
Passphrase=***********

[IPv4]
Address=10.0.5.1
Gateway=10.0.5.1
Netmask=255.255.255.0
IPRange=10.0.5.100,10.0.5.110

but I keep getting this error:

# iwctl ap muap0 start-profile smarc5GHz
Argument type is wrong

AFAIK, 5GHz band supports up to Channel=37. Is this supported by iwd?

Thanks!

Signature · 2 lines
Best regards,
João Marcos Costa
#6 lore raw

Hi Joao,

Quoted 33 lines · Joao Marcos Costa

Hi James,

On 1/19/24 18:44, James Prestwood wrote:

[...]

Quoted 8 lines

Prior to me adding HT (high throughput) IWD's AP mode was just using basic rates, so very slow. I added HT support, but apparently not all drivers were happy about it. So DisableHT removes the extra stuff that allows it to work with this specific driver, but at the cost of performance.

I'm not really in a position to devote a lot of time to AP mode at the moment. I know we've gotten a lot of inquiries about it recently but to be completely honest if your intent is to run a full fledged access point hostapd is really the tool to use. I'd love to get IWD up to the same level of quality and support as hostapd but its a massive undertaking. Not only that but out of tree driver support is something very hard to get right. Hostapd has been around long enough and is the de-factor software for APs that hardware vendors have added their quirks here and there, IWD doesn't have that luxury.

Thanks,

James

Thanks for this insight. I'll keep DisableHT for my tests, then.

However, there's still something I don't quite understand. I'm trying to set up this AP:

[General]
DisableHT=true
Channel=36

[Security]
Passphrase=***********

[IPv4]
Address=10.0.5.1
Gateway=10.0.5.1
Netmask=255.255.255.0
IPRange=10.0.5.100,10.0.5.110

Quoted 6 lines

but I keep getting this error:

# iwctl ap muap0 start-profile smarc5GHz
Argument type is wrong

AFAIK, 5GHz band supports up to Channel=37. Is this supported by iwd?

Could be a regulatory domain issue. Try setting:

[General]

Country=<alpha2>

For whatever country your in:

https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2

Quoted 5 lines

Thanks!