Activating Wireless AP mode

Platform & Software

  • Board: Jetson Orin NX 16GB

  • JetPack: 5.6 / L4T R35.6

  • OS: Ubuntu 20.04

  • WiFi chip: Intel Wireless 8265/8275 (lspci → 0001:01:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78))

  • Kernel driver: iwlwifi

  • NetworkManager: 1.22.10

  • wpa_supplicant: v2.9


Problem

Attempting to create a WiFi hotspot/access point via NetworkManager fails immediately and consistently. The SSID never becomes visible to any scanning device. This occurs whether using the nmcli device wifi hotspot shorthand or a manually constructed connection with mode ap + ipv4.method shared.

This is needed for field robotics use — the Jetson needs to act as a WiFi AP with no infrastructure network present.


Command and Error

$ sudo nmcli device wifi hotspot ifname wlan0 ssid WEED_ROBOT password weedrobot
Error: Connection activation failed: (11) 802.1X supplicant took too long to authenticate.

Root Cause Identified in Logs

journalctl -u wpa_supplicant shows the actual failure happening 3 seconds into the 25-second NM timeout:

wlan0: CTRL-EVENT-DISCONNECTED bssid=... reason=3 locally_generated=1
Note: nl80211 driver interface is not designed to be used with ap_scan=2; this can result in connection failures
wlan0: Failed to start AP functionality

journalctl -u NetworkManager confirms NM successfully builds the AP config and passes it to wpa_supplicant, but then times out:

Config: added 'ssid' value 'WEED_ROBOT'
Config: added 'mode' value '2'
Config: added 'frequency' value '2412'
Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
...
device (wlan0): Hotspot network creation took too long, failing activation
device (wlan0): state change: config -> failed (reason 'supplicant-timeout')

NM is passing ap_scan=2 to wpa_supplicant when activating AP mode. The iwlwifi/nl80211 driver rejects this immediately. NM then times out after 25 seconds and surfaces the misleading 802.1X error message.


What I’ve Already Verified

iw list confirms AP mode is supported:

Supported interface modes:
    * AP
    * AP/VLAN
Supported commands:
    * start_ap
Valid interface combinations:
    * #{ managed } <= 1, #{ AP, P2P-client, P2P-GO } <= 1, #{ P2P-device } <= 1, total <= 3, #channels <= 2

rfkill list all — no soft or hard blocks:

1: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no

No ap_scan override anywhere in /etc/wpa_supplicant/ or /etc/NetworkManager/ (only an unrelated reference in functions.sh for wired 802.1X).

No global /etc/wpa_supplicant/wpa_supplicant.conf exists.

wpa_supplicant is running in userspace socket mode (-u -s), not with a config file.


Things Tried That Did Not Help

  • nmcli device wifi hotspot one-liner

  • Manually creating connection: nmcli con add type wifi ifname wlan0 mode ap ipv4.method shared wifi-sec.key-mgmt wpa-psk ...

  • Adding /etc/NetworkManager/conf.d/wifi-ap.conf with [device] wifi.backend=wpa_supplicant

  • Restarting both NetworkManager and wpa_supplicant before attempting


Questions

  1. Is NetworkManager 1.22.10 on Ubuntu 20.04 known to incorrectly pass ap_scan=2 to wpa_supplicant when configuring AP mode for an nl80211 driver (iwlwifi)?

  2. Is there a supported configuration to force ap_scan=1 for AP mode, or a patch/backport available for NM 1.22.10?

  3. Is upgrading to JetPack 6 (Ubuntu 22.04, NM 1.36+) the expected resolution, or is there a workaround on JetPack 5?

  4. Has anyone successfully run AP mode on an Intel 8265 with iwlwifi on JetPack 5?

Hi,
A user shares a method for rtl8822ce:
Slow wi-fi on orin nano devkit (RTL8822CE 802.11ac) - #13 by DaneLLL

May check the steps and see if it can be applied to 8265.

Thanks for the suggestion. Unfortunately iwd fails to start on this system as well. Running /usr/libexec/iwd directly reveals the root cause:

No HMAC(SHA1) support found
No HMAC(MD5) support found
No CMAC(AES) support found
No HMAC(SHA256) support not found
No HMAC(SHA512) support found, certain TLS connections might fail
No Diffie-Hellman support found, WPS will not be available
The following options are missing in the kernel:
        CONFIG_CRYPTO_USER_API_HASH
        CONFIG_KEY_DH_OPERATIONS
        CONFIG_CRYPTO_MD5
        CONFIG_CRYPTO_SHA256
        CONFIG_CRYPTO_AES
        CONFIG_CRYPTO_CMAC
        CONFIG_CRYPTO_USER_API_HASH
        CONFIG_CRYPTO_HMAC
        CONFIG_CRYPTO_SHA512

The crypto modules do exist as loadable .ko files in /lib/modules/$(uname -r)/kernel/crypto/ (md5.ko, sha3_generic.ko, etc.), but iwd requires them compiled into the kernel via CONFIG_ options rather than as loadable modules. The NVIDIA Tegra kernel shipped with JetPack 5.6 / L4T R35.6 was not built with these userspace crypto API flags enabled.

So the situation on JetPack 5 / Ubuntu 20.04 appears to be:

  • wpa_supplicant backend: fails because NM passes ap_scan=2 which iwlwifi/nl80211 explicitly rejects

  • iwd backend: fails because the Tegra kernel is missing required CONFIG_CRYPTO_* options

Both paths fail at the kernel level. Is there a known workaround for AP mode on JetPack 5 with iwlwifi short of recompiling the Tegra kernel or upgrading to JetPack 6? Any guidance appreciated.