Apple intel wifi adapter v2 kext

# Frequently Asked Questions

# Installation

# What’s the difference between Alpha Prerelease and Latest Release

A testing version automatically compiled by GitHub actions based on the latest source code on the master branch.

Note that Alpha Prerelease Kexts are never tested; we do not guarantee their availability, usability, and stability.

NOT recommended for daily use

An official stable version. This version is usually released after new features are implemented and tested.

Recommended for daily use

# Which Kext Should I Use

Read the Installation guide for more information

# Is My Card Supported

Read the Compatibility table for more information

# Usage

# Limitation of AirportItlwm.kext

• Handoff and Universal Clipboard are the only supported Continuity features

(opens new window) .

Instant Hotspot from iPhone can be recognized but may likely fail to connect.

• Workaround: use itlwm.kext with HeliPort.

Apple Bluetooth peripherals may fail to connect.

• Workaround: use itlwm.kext with HeliPort or disable iCloud.

Unable to connect to Hidden Networks.

# How to connect to my Wi-Fi with itlwm.kext

• By HeliPort (Recommended)
• Fill in the essential information in Info.plist , located inside itlwm.kext

# How to disconnect my Wi-Fi with itlwm.kext

Use HeliPort’s Options Menu (press the Option key while opening).

# HeliPort shows itlwm not loaded

Visit our Troubleshooting guide for more info

# Nothing appears in System Preferences

Visit our Troubleshooting guide for more info

# How can I change the country code from ZZ to a specific country

Adapters that don’t report country codes (iwn, 7000 & 8000 series) can use itlwm_cc= COUNTRY_CODE

(opens new window) to specify a desired one.

# Dual-Boot with Windows

(opens new window) from Linux for more info.

# About Platform Noise

(opens new window) from Linux for more info.

# Can I use Bluetooth with Wi-Fi

2.4 GHz Yes, but it is known to cause performance issues.

(opens new window) from Linux for more info.

# Performance SUCKS

Using the latest stable version (v1.3.0) connected to 5 GHz (40 MHz), the expected maximum speed is 240 Mbps for download and 180 Mbps for upload.

Tested with 9560ac & ax201 using iperf3

Devices with single antennas are expected to have much worse results

It is already ideal for daily usage. Including watching 4K Netflix and YouTube

If you are not satisfied with its performance, consider using Ethernet or Bcrm Cards.

# Why does my adaptor turn back on after a sleep-wake cycle

By default, when the system boots, itlwm starts to initialize the Wi-Fi card and starts connecting to the Internet. This process can all be done before the system boots into user space and launches HeliPort. So, even if HeliPort has stored a property that indicates whether the card should be on/off by default and immediately adjusts itlwm’s behavior, your card has been turned on anyway before then.

Currently, there is no way to make itlwm not power on the card by default on boot. If it’s designed to be off by default and requires HeliPort to power it on, users may have to wait longer until the card is ready and it’s not friendly for users that don’t use HeliPort but rely on itlwm’s Plist.

# Features

# Is it a replacement of natively supported Broadcom Cards

# Is it a replacement of USB Wi-Fi Dongles

# Why does my adapter shows up as Ethernet in System Preferences instead of Wi-Fi

itlwm.kext uses Apple’s public IOEthernetController instead of the private IO80211Family.

Spoofing into Ethernet does not affect performance.

AirportItlwm enables the native Wi-Fi selection menu with limited continuity features.

# Does it support connecting to Hidden Wi-Fi networks

MVM Gen 2 (iwx) cards do not support connecting to Hidden Wi-Fi networks.

iwm and iwn devices:

• itlwm.kext : Yes
• AirportItlwm.kext : No

# Does it support WPA2/3-Enterprise or 802.1X

• itlwm.kext : No
• AirportItlwm.kext : Yes

# Does it support Location Services

Supported on AirportItlwm.kext

itlwm.kext reports the Wi-Fi card as an Ethernet NIC to macOS, rather than Wi-Fi. This means that Find My does not work, since it relies on Wi-Fi data (like what networks are around you). This likely means that other location services don’t work as well.

# Does it support Apple’s Continuity Framework (Airdrop, HandOff)

Only Handoff and Universal Clipboard works with AirportItlwm, other features are not supported.

# Can I use it to create a Personal Hotspot

# Can I monitor Upload and Download speed

Yes, this feature was added since v1.2.0

# Does it support 40/80/160 MHz

HT40 (40 MHz) support was added since v1.3.0

VHT80 & VHT160 support was implemented since v2.0.0

# Does it support 802.11AC and 802.11AX

Yes, 802.11AC and 802.11AX support was implemented since v2.0.0

# Design

# Why not port code directly from Linux but OpenBSD

The amount of code from Linux is enormous. It will likely take forever to finish such a project with our current manpower.

Источник

AppleIntelWifi

Releases

Debug

Release

Why this kext?

Well, we’re working on a full implementation with IOKit. This means that macOS will handle all WPA2 handshaking, key management, and the rest. This significantly reduces the amount of work that we have to do, and is a massive plus for the security (and I’m generally uncomfortable writing any crypto code, as that is far from my expertise). As well, it should be measurably more performant, due to avoiding a second 802.11 stack. In fact, the majority of wireless kexts (including the realtek USB adapters) implement dual 802.11 stacks, and are often a mess to debug and fiddle with when things go wrong, with homebrewed implementation of WPA. Approaching wireless devices via this method requires either a massive department staffed with cryptographers, wireless experts, and potentially linux kernel developers, or entails a duct taped job where you merely strap IEEE80211 from OpenBSD to your driver, and call it a day. I’m simply not satisfied with the latter, and sadly do not have a department at a billion dollar company, and frankly, I’m sick of having a dongle strapped to my laptop.

Will AirDrop ever be supported?

It is definitely possible with all of the discoveries that I have made, however, I’m uncertain entirely on whether or not I want to subject myself to the pain and torture that implementing AWDL will cause. It is a possibility.

What devices are supported?

Unfortunately, due to a massive architectural change (and a lack of development devices), AX-series devices are unsupported. However, all 802.11 AC devices are planned to be supported (316x, 7xxx, 8xxx, 9xxx).

I found a bug! How can I report it?

Run the logging script, and create a new issue on the repo with your log file attached.

I’d like to help! How can I help?

We’re crowd-sourcing testing to the community. We’ve found it to be significantly effective in determining compatibility with wireless devices, and I would love to continue that trend as much as we can. If you have Xcode installed, and can run a simple shell scripts, please upload your log file to the repo here. There are a significant number of devices which have been unaccounted for, as well as some devices having unknown compatibility. A sample size of n=500 is bounds better then a sample size of n=5.
In addition, if you are technically minded and don’t mind reading and writing C/C++, I am ALWAYS accepting of pull requests and contributions. This is not a one-man effort, and my C++ knowledge is only so vast. We have adopted the Google coding style to the entire repo, and request that you format and lint your code before submitting a PR.

Copyright В© 2020 IntelWifi for MacOS authors. All rights reserved.

Источник

v2.1.0-alpha

Disclaimer:

This alpha version is for testing only.
It is not ready for daily use and we do not guarantee its usability.
If you discovered an issue and you do not have debugging skills, please check with the Gitter Chat Room in advance before opening an Issue.

The latest five updates are:

• 3e1d25a iwn: Fix initial connection on HT40.
• 1008cb4 iwn: fix calib_to timeout object leak.
• 307f2c7 Intel doesn’t support 80+80 channel on 11ac mode, so just fallback to 20mhz like Linux.
• efbd073 iwx: convert reading index into real ring index, we are not using the queue max size as actual ring length on gen3 devices.
• 0bd8a85 iwn: add Centrino Wireless-N 6150 card id.

Assets

v2.0.0 stable

This version brings performance to the next level:

• iwm/iwx: Add support for 802.11AC
• iwm/iwx: Add support for VHT160 (160MHz)
• Add support for LDPC and STBC
• Improve RA rate scaling algorithm to support HT, VHT, and HE throughput
• AirportItlwm: Add support for macOS Monterey
• AirportItlwm: Add support for overriding Country Code by Airport (starting from macOS Mojave)

Priority: User Override > Firmware LOC > Airport Override
Adapters that don’t provide Country Codes will now accept them from airportd

Contributors

Assets

v1.3.0 stable

This version brings significant speed and stability improvements

• Implement Tx Aggregation with A-MPDU and A-MSDU
• Add HT40 (40MHz) support to iwn (#516), iwm, and iwx devices
• Switch to the RA algorithm for rate selection (Credit Christian Ehrhardt and Stefan Sperling)
• Implement channel width changing between 20MHz and 40MHz
• Force disable ASPM to prevent devices being in unsupported states
• Correctly configure Tx QoS for iwx devices to eliminate stuttering when uploading
• Partially implement Airport SSID nodes cache age to optimize user experience
• Add retries if BSS association fails
• Decrypting multicast frames will no longer generate failures on iwx devices

Assets

v1.2.0 stable

• Use Apple RSN Supplicant for authentication. AirportItlwm now supports connecting to WPA/2 Enterprise networks. Credit @usr-sse2 (#311) (#349)
• Partially support Apple Watch Unlock (Not tested)
• Switch to MacKernelSDK
• Bug fixes for iwm and iwx
• IO80211Family headers update and bug fixes
• Support AWDL service initialization (no further services available)
• Add support for country code
  • Adapters that don’t report country codes (iwn, 7000 & 8000 series) can use itlwm_cc= COUNTRY_CODE to select them
• Support monitoring download speed
• Add support for iwn devices. Credit @pigworlds (#399) (#411) (#404) (#424)
• Change itlwm dependencies version to fit 10.9 and above
• Change AirportItlwm match strategy to fix random kernel panic when system boots
• Sync openbsd net80211 (#453)
• Bug fixes for the MIRA algorithm. Credit @pigworlds (#465) (#466)
• Correct iwx sending traffic ids, improved performance
• Fix SSID disappering in Heliport when itlwm is associating
• Use kprintf instead of IOLog to avoid missing interruptions while associating

Assets

v1.1.0 stable

itlwm

1. Merged itlwmx to itlwm, itlwmx is now deprecated.
2. Compressed firmware files, reduced itlwm size to 9.9 MB.
3. Resolved an issue that causes the system to become unresponsive when uploading with P2P software.

A single itlwm.kext supports all the previously supported devices.

itlwm still needs to be used with Heliport and provides support for 10.12 and above systems.

AirportItlwm Beta

1. Supports all itlwm-supported devices.
2. Supports native Wi-Fi selection and switching with WPA/WPA2/Unencrypted Wi-Fi Networks.
3. Supports Location Services.
4. Handoff and Universal Clipboard perfectly supported. (#292 (comment))

Known Issues and limitations

• Handoff and Universal Clipboard are the only supported Continuity features.
• Instant HotSpot from iPhone can be recognized but may likely fail to connect. Workaround: use itlwm.kext with HeliPort.
• Apple Bluetooth peripherals may fail to connect. Workaround: use itlwm.kext with HeliPort or disable iCloud.

Bootloader Compatibility

Note:
OpenCore requires 0.6.1 or higher. Please read OpenCore’s Official Document for more details.

Set SecureBootModel to Default to make sure IO80211Family loads properly.

Workaround for Users with Prelinked Kernel without ImmutableKernel

• Force IO80211Family to load. 「Supports OpenCore and Clover(not tested)」 (Read the Kernel — Force section in OpenCore’s manual for more info)
• Load AirportItlwm from Terminal (Continuity features may not work)
• Extract IO80211Family from the system, insert AirportItlwm as a Plugin, and load the bundle with a bootloader.
• Or disable SIP and install AirportItlwm into /Library/Extensions (Take your own risk)

The latter two methods are not recommended, hence details are not provided.

境内加速下载链接：
Download boosted URL for China:

Источник

Apple intel wifi adapter v2 kext

Please note: this project is now unsupported. Please go to itlwm if you would like a supported kext.

This is a kext which aims to provide support for Intel wireless devices on MacOS. It is intended to provide similar support with MacOS as a native AirPort device (via the IO80211Controller private IOKit class).

This kext does not function yet. Do NOT install this into Clover, or /S/L/E. You WILL ruin your system.

Card Name	PCI ID	Supported	Planned Support	Relevant Threads
Intel(R) Dual Band Wireless AC 3160	8086:08B4, 8086:0B83	No (LMAC scanning)	Yes
Intel(R) Dual Band Wireless AC 3165	8086:3165, 8086:3166	No (LMAC scanning)	Yes	device-logs#6
Intel(R) Dual Band Wireless AC 3168	8086:24FB	Unknown (CNVi card)	Unknown	device-logs#8
Intel(R) Dual Band Wireless AC 4165	8086:24F5, 8086:24F6	Unknown (similar to 8xxx series)	Unknown
Intel(R) Dual Band Wireless AC 7260	8086:08B1	Yes (confirmed)	Yes
Intel(R) Dual Band Wireless N 7260	8086:08B2	Unconfirmed	Unknown
Intel(R) Dual Band Wireless AC 7265	8086:095A, 8086:095B	Unconfirmed	Unknown	device-logs#12
Intel(R) Wireless N 7265	8086:095A, 8086:095B	Unconfirmed	Unknown
Intel(R) Dual Band Wireless AC 8260	8086:24F3	Yes (confirmed)	Yes	device-logs#7 device-logs#11 device-logs#13
Intel(R) Dual Band Wireless AC 8265	8086:24F3, 8086:24FD	Yes (confirmed)	Yes	device-logs#9
Intel(R) Dual Band Wireless AC 8275	8086:24FD	Yes (confirmed)	Yes
Intel(R) Dual Band Wireless-AC 9162	Unknown	Unknown (CNVi card)	Unknown
Intel(R) Dual Band Wireless-AC 9260	8086:2526, 8086:0000 8086:0010, 8086:0014 8086:0018, 8086:0210 8086:0214, 8086:4010 8086:8014, 8086:a014	Support varies	Yes
Killer (R) Wireless-AC 1550 Wireless Network Adapter (9260NGW)	8086:2526, 1a56:1550	Unknown (rebrand)	Unknown
Intel(R) Dual Band Wireless-AC 9270	8086:1410, 8086:1610	Unknown	Unknown
Intel(R) Dual Band Wireless-AC 9461	8086:0060, 8086:0064 8086:0260, 8086:0264	Unknown (CNVi card?)	Unknown
Intel(R) Dual Band Wireless-AC 9462	8086:00a0, 8086:00a4 8086:02a0, 8086:02a4 8086:40a4, 8086:42a4	Unknown (CNVi card?)	Unknown	device-logs#14
Intel(R) Dual Band Wireless-AC 9560	8086:0030, 8086:0034 8086:0038, 8086:003c 8086:0230, 8086:0234 8086:0238, 8086:023c 8086:2030, 8086:2034 8086:4030, 8086:4034 8086:4234	Mixed results (some are CNVi, some are PCIe)	Yes	device-logs#1
Killer(R) Wireless-AC 1550s Wireless Network Adapter	1a56:1551	Unknown (rebrand)	Unknown
Killer(R) Wireless-AC 1550i Wireless Network Adapter	1a56:1552	Unknown (rebrand)	Unknown
Intel(R) Dual Band Wireless-AC 19560	8086:1030	Unknown (gigabit card?)	Unknown

If your card is not listed here (or does not have an open issue), please open an issue here: https://github.com/AppleIntelWifi/device-logs

NOTE: AX-series cards are currently NOT supported, and are very likely to never be supported.

Apple for making macOS, and all of the glorious awful APIs that I use

@zxystd for writing the initial base code for this kext

Intel for the cheap wireless devices

@acidanthera for the CI configuration

@comex for this amazing gist which contains several structs I didn’t want to RE

@rpeshkov for paving the way initially with IntelWifi/Black80211

About

Kext providing initial support for Intel wireless devices

Источник