To be able to use tethering in macOS, you will need to install the HoRNDIS driver, which enables RNDIS devices to be usable under macOS.
HoRNDIS Driver
Unfortunately, the former developer of the driver had abandoned the project and it hasn’t been updated since 2018. Now it’s maintained by another developer from the community, which created a new version of the driver, which works under macOS 11 and 12, Intel and M1 processors.
The original version of HoRNDIS works with macOS up to 10.14 (Mojave). macOS 10.15 requires another version od HoRNDIS, which is prepared for new way of loading kernel extentions. macOS 11 and above have to use notarized version of HoRNDIS, which allows the usage of driver with SIP enabled.
Please find below the instructions for installing the HoRNDIS driver, depending on your version of macOS:
macOS 10.14 (Mojave) and below
Just install the driver from here: Release HoRNDIS 9.2 · jwise/HoRNDIS and it should work out of the box.
macOS 10.15 (Catalina)
To be able to install the driver in Catalina, you have to use a modified version of the driver: https://github.com/jwise/HoRNDIS/files/3719733/HoRNDIS-9.2-catalina_install.pkg.zip
This version has a slightly changed installer so that it matches the OS requirements. Unfortunately, the developer who modified the installer couldn't sign the package, so it’s necessary to run it by right-clicking and pressing open:
After the installation, you will need to unlock the kernel extension in the settings:
Clicking the lock icon enables the user to make any changes. After unlocking it, there’s an option to allow the extension. After that, the installation will be finished and the system ready to work with tethering:
In case of problems with internet access when the Pure is connected, please update your DNS entries (eg. 8.8.8.8 or 1.1.1.1).
macOS 11 and above (Big Sur, Monterey)
Starting from macOS 11, the installation process is a little bit complicated as there’s a need to temporarly disable SIP (System Integrity Protection). The whole process comes down to those points:
Executing the script which pre-enables the developer’s Developer ID in the system
Rebooting into recovery mode, disabling SIP, and adding the Developer ID to the database
Installing the driver
Reenabling the SIP