HoRNDIS (pronounce: "horrendous") is a driver for Mac OS X that allows you to use your Android phone's native USB tethering mode to get Internet access.
For more information, visit the home page for HoRNDIS on my site.
brew cask install horndis
sudo kextload /Library/Extensions/HoRNDIS.kext
HoRNDIS.kext
under /System/Library/Extensions
and /Library/Extensions
foldergit clone
the repositorymake
to assemble the package in the build/ directoryThis sections contains tips and tricks for developing and debugging the driver.
Mac OS System Menu -> About This Mac -> System Report --> Hardware/USB
Lists all USB devices that OS recognizes. Unfortunately, it does not give USB descriptors.
lsusb -v
It prints USB configuration, such as interface and endpoint descriptors. You can print it for all devices or limit the output to specific ones. In order to run this command, you need to install usbutils.
brew install mikhailai/misc/usbutils
sudo port install usbutils
ioreg -l -r -c IOUSBHostDevice
This command lists all the Mac OS IO Registry information under all USB devices. Unlike lsusb, ioreg tells how Mac OS recognized USB devices and interfaces, and how it matched drivers to these interfaces. The -r -c IOUSBHostDevice
limits the output to USB devices; to get complete OS registry, please run ioreg -l
.
The LOG(....)
statements, sprinkled throughout the HoRNDIS code, call the IOLog
functions. On Mac OS El Capitan (10.11) and earlier, the log messages go into /var/log/system.log
. Starting from Sierra (10.12), these messages are no longer written to system.log
and instead can be viewed via:
process:kernel
in the search box in order to filter the relevant messages.log
command. For example:log show --predicate process==\"kernel\" --start "2018-12-11 22:54:00"
log show --predicate process==\"kernel\" --start "$(date -v-3M +'%F %T')"
I've observed that Mac OS logging is unreliable (especially in Sierra). In some cases, the messages may come out garbled (looking like bad multi-threaded code). In other cases, either GUI or Command Line may be missing messages that were emitted. Sometimes, reloading the driver may fix the problem.