search

OpenIntelWireless / itlwm

Intel Wi-Fi Drivers for macOS
https://OpenIntelWireless.github.io/itlwm/
GNU General Public License v2.0
6.94k stars 666 forks source link

Cannot connect to 802.11ax 5 GHz WiFi SSID with Intel AX210 #913

Closed KA2107 closed 1 year ago

KA2107 commented 1 year ago

Have You Read Our Docs Yes

Are You Reporting A Bug Yes

Environment Router: GL-iNet GL-MT3000 Beryl AX running OpenWrt 23.05-SNAPSHOT (Mediatek filogic, mt76 driver) (OR) Dynalink DL-WRX36 running OpenWrt 23.05-SNAPSHOT (Qualcomm ath11k driver)

Client: 2017 MacBook Air, macOS Ventura 13.5.2, OpenCore Legacy Patcher (OCLP) 0.6.8, Intel AX210 M.2 WiFi 6E Card using Adapter

5 GHz SSID: KSH1_5GHz 802.11ax, 20 MHz, Channel 40 or 157 or 165, Country: US Mixed WPA2-PSK (CCMP / AES) + WPA3-SAE, 802.11w (Protected Management Frames) set to OPTIONAL

2.4 SSID: KSH1_2.4GHz 802.11ax, 20 MHz, Channel 6, Country: US Mixed WPA2-PSK (CCMP / AES) + WPA3-SAE, 802.11w (Protected Management Frames) set to OPTIONAL

Description I cannot connect to 5 GHz SSID (KSH1_5GHz). I can connect to 2.4 GHz SSID (KSH1_2.4GHz).

Bug Report Archive Heliport_Diagnostic_Report.zip Log_2023-09-12_19-19-53.log

Kext Download Source AirportItlwm.kext.zip Custom built locally with 802.11ax enabled as per instructions at https://github.com/OpenIntelWireless/itlwm/issues/897#issuecomment-1625497763

KA2107 commented 1 year ago

Software Versions: CoreWLAN: 16.0 (1657) CoreWLANKit: 16.0 (1657) Menu Extra: 17.0 (1728) System Information: 15.0 (1502) IO80211 Family: 12.0 (1200.13.0) Diagnostics: 11.0 (1163) AirPort Utility: 6.3.9 (639.21)

Interfaces: en0: Card Type: Wi-Fi (0x8086, 0x24) Firmware Version: itlwm: 2.3.0 fw: 68.01d30b0c.0 MAC Address: 68:7a:64:XX:XX:XX Locale: FCC Country Code: US Supported PHY Modes: 802.11 a/b/g/n/ac/ax Supported Channels: 1 (2GHz), 2 (2GHz), 3 (2GHz), 4 (2GHz), 5 (2GHz), 6 (2GHz), 7 (2GHz), 8 (2GHz), 9 (2GHz), 10 (2GHz), 11 (2GHz), 12 (2GHz), 13 (2GHz), 36 (5GHz), 40 (5GHz), 44 (5GHz), 48 (5GHz), 52 (5GHz), 56 (5GHz), 60 (5GHz), 64 (5GHz), 100 (5GHz), 104 (5GHz), 108 (5GHz), 112 (5GHz), 116 (5GHz), 120 (5GHz), 124 (5GHz), 128 (5GHz), 132 (5GHz), 136 (5GHz), 140 (5GHz), 144 (5GHz), 149 (5GHz), 153 (5GHz), 157 (5GHz), 161 (5GHz), 165 (5GHz) Wake On Wireless: Supported AirDrop: Supported Auto Unlock: Supported Status: Connected

Current Network Information: KSH1_2.4GHz: PHY Mode: 802.11ax Channel: 6 (2GHz, 40MHz) Country Code: US Network Type: Infrastructure Security: WPA2/WPA3 Personal Signal / Noise: -33 dBm / 58 dBm Transmit Rate: 36 MCS Index: 11

KSH1_5GHz: PHY Mode: 802.11 Channel: 157 (5GHz, 20MHz) Network Type: Infrastructure Security: WPA2/WPA3 Personal Signal / Noise: -47 dBm / 58 dBm

zxystd commented 1 year ago

Hi, 11ax mode is not test pass yet, have you tried the released one? v2.3.0-alpha or v2.2.0-stable.

From the log I found that the itlwm accidentally negotiate to 80MHz channel width while you only limit to 20MHz, it maybe working fine on master version. I will also try to fix this 11ax related problem.

KA2107 commented 1 year ago

I tried AirportItlwm_v2.2.0_stable_Ventura.kext.zip and I am able to connect to the 5 GHz SSID in 802.11ac (VHT) mode.

I built git commit e66257e525b55930f4ea7f0958d6f09d945ab3cf (latest in master) (with 802.11ax enabled) AirportItlwm.kext.zip and I am NOT able to connect to 5 GHz SSID.

KA2107 commented 1 year ago

I changed the 5 GHz SSID from HE20 (802.11ax, 20 MHz) to VHT20 (802.11ac, 20 MHz) in OpenWrt config and with the AirportItlwm.kext (commit e66257e525b55930f4ea7f0958d6f09d945ab3cf, 802.11ax enabled), I am able to connect to the 5 GHz SSID.

So looks like it is 802.11ax mode that is causing the issue with 5 GHz SSID. However 802.11ax mode works with 2.4 GHz SSID.

zxystd commented 1 year ago

I tried AirportItlwm_v2.2.0_stable_Ventura.kext.zip and I am able to connect to the 5 GHz SSID in 802.11ac (VHT) mode.

I built git commit e66257e (latest in master) (with 802.11ax enabled) AirportItlwm.kext.zip and I am NOT able to connect to 5 GHz SSID.

What about the log?

KA2107 commented 1 year ago

I tried AirportItlwm_v2.2.0_stable_Ventura.kext.zip and I am able to connect to the 5 GHz SSID in 802.11ac (VHT) mode. I built git commit e66257e (latest in master) (with 802.11ax enabled) AirportItlwm.kext.zip and I am NOT able to connect to 5 GHz SSID.

What about the log?

Log_2023-09-14_15-46-12.log

zxystd commented 1 year ago 
[  544.232117]: itlwm: ieee80211_he_negotiate chan_width=80

@KA2107 are you sure you used the latest commit? it may not negotiate to 80MHz channel on the latest commit.

KA2107 commented 1 year ago 
[  544.232117]: itlwm: ieee80211_he_negotiate chan_width=80

@KA2107 are you sure you used the latest commit? it may not negotiate to 80MHz channel on the latest commit.

I re-built the kext from latest commit in master and tried again. I see in log

itlwm: ieee80211_he_negotiate chan_width=80

and

itlwm: ieee80211_he_negotiate chan_width=40

but no attempt to negotiate 20 MHz for HE (802.11ax).

Log_2023-09-14_21-21-37.log Log_2023-09-14_21-27-53.log AirportItlwm.kext.zip

zxystd commented 1 year ago

@KA2107 I see, your openwrt configuration is set to HE 20MHz but also announcing phy_cap_info[0] that support 40MHZ_80MHZ_IN_5G capability....

KA2107 commented 1 year ago

My /etc/config/wireless

config wifi-device 'radio0'
        option type 'mac80211'
        option path 'platform/18000000.wifi'
        option band '2g'
        option require_mode 'n'
        option htmode 'HE20'
        option he_bss_color '8'
        option he_su_beamformer '1'
        option he_su_beamformee '1'
        option he_mu_beamformer '1'
        option beacon_int '100'
        option country 'US'
        option country_ie '1'
        option channel '6'
        option channels '1 6 11'
        option cell_density '1'

config wifi-device 'radio1'
        option type 'mac80211'
        option path 'platform/18000000.wifi+1'
        option band '5g'
        option require_mode 'n'
        option acs_exclude_dfs '1'
        option beacon_int '100'
        option country 'US'
        option country_ie '1'
        option htmode 'HE20'
        option he_bss_color '8'
        option he_su_beamformer '1'
        option he_su_beamformee '1'
        option he_mu_beamformer '1'
        option cell_density '1'
        option channel '157'

config wifi-iface 'ksh1_2ghz'
        option device 'radio0'
        option mode 'ap'
        option key '****************'
        option ssid 'KSH1_2.4GHz'
        option encryption 'sae-mixed'
        option network 'lan_1'
        option ifname 'wlan0_2ghz'
        option disassoc_low_ack '0'
        option auth_cache '1'
        option wpa_disable_eapol_key_retries '1'
        option tdls_prohibit '1'
        option dtim_period '5'
        option multicast_to_unicast_all '1'
        option wpa_group_rekey '3600'
        option ieee80211w '1'

config wifi-iface 'ksh1_5ghz'
        option ifname 'wlan0_5ghz'
        option device 'radio1'
        option mode 'ap'
        option key '****************'
        option ssid 'KSH1_5GHz'
        option network 'lan_1'
        option disassoc_low_ack '0'
        option auth_cache '1'
        option wpa_disable_eapol_key_retries '1'
        option tdls_prohibit '1'
        option dtim_period '5'
        option sae_pwe '2'
        option doth '0'
        option encryption 'sae-mixed'
        option multicast_to_unicast_all '1'
        option wpa_group_rekey '3600'
KA2107 commented 1 year ago

I tried HE40 for 5 GHz and still could not connect Log_2023-09-14_21-27-53.log

KA2107 commented 1 year ago

HE80 works Log_2023-09-14_22-09-31.log

HE40 and HE20 do not work (previous logs).

zxystd commented 1 year ago

AirportItlwm.kext.zip @KA2107 can you try this one?

KA2107 commented 1 year ago

AirportItlwm.kext.zip @KA2107 can you try this one?

I am able to connect with this kext. However with 5 GHz SSID it is connecting in VHT20 (802.11ac) mode rather than HE20 (802.11ax) mode. With 2.4 GHz SSID it is connecting in HT20 (802.11n) mode. Are you sure 802.11ax is enabled in this kext? Log_2023-09-14_23-44-03.log

zxystd commented 1 year ago

well, I forgot to enable it. AirportItlwm.kext.zip

KA2107 commented 1 year ago

well, I forgot to enable it. AirportItlwm.kext.zip

I could not connect to either 2.4 GHz or 5 GHz (both HE20) with this kext. Log_2023-09-15_10-28-38.log Log_2023-09-15_10-40-32.log

Ophelie22 commented 1 year ago

Software Versions: CoreWLAN: 16.0 (1657) CoreWLANKit: 16.0 (1657) Menu Extra: 17.0 (1728) System Information: 15.0 (1502) IO80211 Family: 12.0 (1200.13.0) Diagnostics: 11.0 (1163) AirPort Utility: 6.3.9 (639.21)

Interfaces: en0: Card Type: Wi-Fi (0x8086, 0x24) Firmware Version: itlwm: 2.3.0 fw: 68.01d30b0c.0 MAC Address: 68:7a:64:XX:XX:XX Locale: FCC Country Code: US Supported PHY Modes: 802.11 a/b/g/n/ac/ax Supported Channels: 1 (2GHz), 2 (2GHz), 3 (2GHz), 4 (2GHz), 5 (2GHz), 6 (2GHz), 7 (2GHz), 8 (2GHz), 9 (2GHz), 10 (2GHz), 11 (2GHz), 12 (2GHz), 13 (2GHz), 36 (5GHz), 40 (5GHz), 44 (5GHz), 48 (5GHz), 52 (5GHz), 56 (5GHz), 60 (5GHz), 64 (5GHz), 100 (5GHz), 104 (5GHz), 108 (5GHz), 112 (5GHz), 116 (5GHz), 120 (5GHz), 124 (5GHz), 128 (5GHz), 132 (5GHz), 136 (5GHz), 140 (5GHz), 144 (5GHz), 149 (5GHz), 153 (5GHz), 157 (5GHz), 161 (5GHz), 165 (5GHz) Wake On Wireless: Supported AirDrop: Supported Auto Unlock: Supported Status: Connected

Current Network Information: KSH1_2.4GHz: PHY Mode: 802.11ax Channel: 6 (2GHz, 40MHz) Country Code: US Network Type: Infrastructure Security: WPA2/WPA3 Personal Signal / Noise: -33 dBm / 58 dBm Transmit Rate: 36 MCS Index: 11

KSH1_5GHz: PHY Mode: 802.11 Channel: 157 (5GHz, 20MHz) Network Type: Infrastructure Security: WPA2/WPA3 Personal Signal / Noise: -47 dBm / 58 dBm

Ophelie22 commented 1 year ago

I have the same configuration, ans since i pu th the ventura i can connect to internet , with wifi et bluetothh is onluuy work with ethernet . What i have to do? Do you have a tuto that show it on youtube or something like this?

almajthob commented 1 year ago

"Hi there, I have a question that's a bit unrelated, but I'm hoping you can help. I recently installed macOS Ventura 13.4 on my Surface Pro 7, and I'm experiencing issues connecting it to my iPhone 12 5G hotspot. 4G work fine with me I just wanted to know if it's possible to update macOS Ventura to version 13.5.1 after installed macOS Ventura 13.4 on the Surface Pro 7. Thanks in advance for your assistance!"

zxystd commented 1 year ago

@KA2107 AirportItlwm.kext.zip

almajthob commented 1 year ago

i think its better than the old one work for me 80%

KA2107 commented 1 year ago

@KA2107 AirportItlwm.kext.zip

@zxystd Thank you for this kext. I am able to connect to both 2.4 GHz SSID (HE20, Channel 6) and 5 GHz SSID (HE20, Channel 165). Log_2023-09-18_11-36-45.log

zxystd commented 1 year ago

@KA2107 Thank you, how about other modes?

KA2107 commented 1 year ago

@KA2107 Thank you, how about other modes?

I tried the following modes:

2.4 GHz, SSID: KSH1_2.4GHz, Channel 6 HT20 (802.11n, 20 MHz) HE20 (802.11ax, 20 MHz)

5 GHz, SSID: KSH1_5GHz, Channel 40 HT20 (802.11n, 20 MHz) HT40 (802.11n, 40 MHz) VHT20 (802.11ac, 20 MHz) VHT40 (802.11ac, 40 MHz) VHT80 (802.11ac, 80 MHz) HE20 (802.11ax, 20 MHz) HE40 (802.11ax, 40 MHz) HE80 (802.11ax, 80 MHz)

5 GHz, SSID: KSH1_5GHz, Channel 157 HT20 (802.11n, 20 MHz) HT40 (802.11n, 40 MHz) VHT20 (802.11ac, 20 MHz) VHT40 (802.11ac, 40 MHz) VHT80 (802.11ac, 80 MHz) HE20 (802.11ax, 20 MHz) HE40 (802.11ax, 40 MHz) HE80 (802.11ax, 80 MHz)

5 GHz, SSID: KSH1_5GHz, Channel 165 HE20 (802.11ax, 20 MHz)

I did not try 5 GHz VHT160 (80211ac, 160 MHz) or HE160 (80211ax, 160 MHz) modes.

All the modes: Country: US (USA) Mixed WPA2-PSK (CCMP / AES) + WPA3-SAE, 802.11w (Protected Management Frames) set to OPTIONAL

I was able to connect in all the modes. There was a minor hiccup while changing from 5 GHz, Channel 40, VHT40 => VHT80 where the macOS did not auto-connect. I had to manually turn off and on the WiFi and then it auto-connected immediately.

Log_2023-09-20_21-11-27.log

almajthob commented 1 year ago

I still have a problem connecting to the Wi-Fi hotspot on my iPhone 12. Is there anything I can do to show you where the error is? macOS Ventura 13.4 on Surface Pro 7

KA2107 commented 1 year ago

I still have a problem connecting to the Wi-Fi hotspot on my iPhone 12. Is there anything I can do to show you where the error is?

@almajthob I am not a dev but you can collect logs by following the instructions at https://openintelwireless.github.io/itlwm/Troubleshooting.html#runtime-logs. I followed the "Manually Collecting Logs" section, not the "Via HeliPort" section.

Also there's this info in the FAQ regarding iPhone Hotspot https://openintelwireless.github.io/itlwm/FAQ.html#usage

- Instant Hotspot from iPhone can be recognized but the hotspot must be enabled directly on the iPhone first, see itlwm #749

zxystd commented 1 year ago

@KA2107 Thank you very much for helping with the testing!

KA2107 commented 1 year ago

@zxystd Thank you for developing itlwm.

KA2107 commented 1 year ago

With the release of OCLP 1.0.0, I upgraded to macOS Sonoma in my 2017 Macbook Air.

Since the AirportItlwm build for Sonoma is still in development, is not yet (somewhat) stable and lacks 802.11ax, I shifted to itlwm.kext (with 802.11ax enabled, locally built from latest git).

I tried connecting using Heliport. I see the macbook show up as connected in my router connected devices page, but there's no IP address assigned in macOS Sonoma.

Heliport Diagnostics Report bugreport_34780.zip

Heliport Screenshot Heliport

Notice in the above screenshot

IP Address is "Unknown" and Router is 127.0.0.1 (localhost).

macOS Network Settings Window macOS_Network_Settings

Looks like either Heliport is not attached to the "Ethernet" network device in macOS settings. (OR) DHCP is not working.

Not sure if this is an issue in itlwm, Heliport or macOS Sonoma itself.

zxystd commented 1 year ago

will be there after Chinese National holiday.

zxystd commented 1 year ago

no issue on the driver from the log, please check your password. and try to clean and reconnect by Heliport

---Original--- From: "Keshav @.> Date: Tue, Oct 3, 2023 10:09 AM To: @.>; Cc: @.**@.>; Subject: Re: [OpenIntelWireless/itlwm] Cannot connect to 802.11ax 5 GHz WiFiSSID with Intel AX210 (Issue #913)

I upgraded to Sonoma and therefore shifted to itlwm.kext (with 802.11ax enabled, locally built from latest git). I tried connecting using Heliport. I see the macbook show up as connected in my router connected devices page, but there's no IP address assigned in macOS Sonoma. Not sure if this is an issue in itlwm, Heliport or macOS Sonoma itself.

Heliport Diagnostics Report bugreport_34780.zip

Any idea how to get itlwm

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

KA2107 commented 1 year ago

@zxystd Thank you for responding during your holiday time. No need to rush. Enjoy your vacation.

Just giving my updates below: I tried removing Heliport using AppCleaner (in order to delete the preferences files as well) and after a reboot, re-installing Heliport. Still did not work.

I also tried directly adding the SSID and password in the Info.plist inside the itlwm.kext. The behavior is similar to trying to connect using Heliport.

In both cases, the device is associated with router, but the en0 interface does not have IP address (neither IPv4 nor IPv6) assigned, and the en0 status shows as "inactive". Not sure what that means.

I tried Airportitlwm kext attached at https://github.com/OpenIntelWireless/itlwm/issues/883#issuecomment-1670749680 and my Macbook got stuck at boot. It did not boot to login screen. Not sure if default OCLP config (for Broadcom card) is messing with Airportitlwm kext.

I have replaced the Intel AX210 card with the Broadcom card that originally came with the Macbook. I think I will wait for Airportitlwm for Sonoma to stabilize before trying the AX210 card again.

zxystd commented 1 year ago

Just giving my updates below: I tried removing Heliport using AppCleaner (in order to delete the preferences files as well) and after a reboot, re-installing Heliport. Still did not work.

Passwords are stored in KeyChain.

I also tried directly adding the SSID and password in the Info.plist inside the itlwm.kext. The behavior is similar to trying to connect using Heliport.

If you try this way, you can close Heliport, it should work after reboot.

In both cases, the device is associated with router, but the en0 interface does not have IP address (neither IPv4 nor IPv6) assigned, and the en0 status shows as "inactive". Not sure what that means.

inactive means the network interface is not 'UP', which also means the itlwm.kext not really connected to the router.

I tried Airportitlwm kext attached at #883 (comment) and my Macbook got stuck at boot. It did not boot to login screen. Not sure if default OCLP config (for Broadcom card) is messing with Airportitlwm kext.

Airportitlwm uses the native OS dependencies like the native wifi driver, different to the OCLP patches(reactive old drivers/libraries from old systems).

KA2107 commented 1 year ago

@zxystd I connected back the Intel AX210 WiFi card in my Macbook Air and got it working with itlwm.kext in macOS Sonoma 14.0 with OCLP 1.0.1 . Turns out 802.11w setting in the AP / router was the culprit.

WPA2-PSK (CCMP / AES) and WPA3-SAE Mixed Mode with 802.11w OPTIONAL ==>> itlwm.kext does not connect, en0 is in "inactive" state.

WPA2-PSK (CCMP / AES) only with 802.11w OPTIONAL ==>> itlwm.kext does not connect, en0 "inactive"

WPA2-PSK (CCMP / AES) only with 802.11w DISABLED ==>> itlwm.kext connects to 5 GHz WiFi in 802.11ax mode (Channel 40, HE40), en0 has both IPv4 and IPv6 addresses.

I haven't tried 2.4 GHz SSID with itlwm.kext, but I guess the behavior will be same as with 5 GHz SSID.

KA2107 commented 1 year ago

@zxystd Thank you for updating the git repo with macOS Sonoma support.

I built both AirportItlwm.kext (for Sonoma) and itlwm.kext (both with 802.11ax enabled) from https://github.com/OpenIntelWireless/itlwm/commit/ff1138b026d3198beb9a716f73efe4f4a86ed68b using Xcode.

I am able to connect to 802.11ax 5 GHz HE40 SSID using itlwm.kext + Heliport.

However when I switched to AirportItlwm.kext, the kext loads but the macOS Sonoma's native wifi menu does not show any networks. macOS "System Settings", under "Network" shows the AX210 wifi card as "Not connected". I have attached the kext I built and the log.

Log_2023-10-18_19-46-40.log

AirportItlwm.kext.zip

I also tried AirportItlwm-Sonoma-v2.3.0-DEBUG-alpha-ff1138b.zip. Same behavior as the attached AirportItlwm.kext.zip.

zxystd commented 1 year ago

@KA2107 Are you sure you don't have patched the Sonoma with OCLP?

KA2107 commented 1 year ago

@KA2107 Are you sure you don't have patched the Sonoma with OCLP?

I have modified the OCLP's EFI config.plist to disable Broadcom WiFi related kexts and settings (I set the corresponding kexts' "Enabled" field to "false" in the config and also disabled IOSkywalkFamily downgrade).

config_sonoma_AirportItlwm.plist.zip

Is there anything in the log file that shows why AirportItlwm.kext is not working?

zxystd commented 1 year ago

@KA2107 AirportItlwm is working, but the OCLP replaced userspace frameworks and binaries(token from Ventura), you should not only disabled the kexts loading.

KA2107 commented 1 year ago

@KA2107 AirportItlwm is working, but the OCLP replaced userspace frameworks and binaries(token from Ventura), you should not only disabled the kexts loading.

@zxystd Your reply gave me an idea and I used AirportItlwm.kext (Ventura) instead of AirportItlwm.kext (Sonoma), and I am able to connect to both 802.11ax WPA2-PSK (AES / CCMP) (my wifi) and 802.11ac WPA2-Enterprise (wifi provided by ISP for guests) (both 5 GHz).

My setup:

I have attached the OCLP plist files and kexts (802.11ax enabled) files for Sonoma (both itlwm.kext and AirportItlwm.kext). For those how have actual Apple Macs, with OCLP patched Sonoma system, you need to use AirportItlwm.kext (Ventura) version, NOT AirportItlwm.kext (Sonoma) version. Use AirportItlwm.kext (Sonoma) version if you are using normal OpenCore in a Hackintosh.

Please note my plist files contain the Itlwm / AirportItlwm specific boot-args "itlwm_cc=US -noht40". Please change the country code ("US" in my case) to match your country and also keep / remove "-noht40" as needed.

OCLP_plist_files.zip

itlwm.kext.zip

AirportItlwm_Ventura.kext.zip

AirportItlwm_Sonoma.kext.zip

KA2107 commented 1 year ago

Now that AirportItlwm.kext is working in my system, I will close this issue.

Looking forward to 802.11w and WPA3 next.

@zxystd Thank you so much for your work.