Re: Standard way to communicate between NKEs and user space?
site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com On Mar 3, 2005, at 2:27 AM, OL&L Lists wrote: - Peter Sichel Sustainable Softworks <http://www.sustworks.com> _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... I am sure this question has been asked many times but can someone point me to the docs that explain the standard way on OS X to enable two-way communication between a NKE KEXT and a user-space app? The standard way is through a socket. There are a few variations on this technique, but the basic idea is to make your NKE a socket filter and then intercept calls to set socket options and/or read and write data in the sockets buffer. To connect from your application, you open a UDP (or PF_NKE) socket and then set the option to add your socket filter. One wrinkle is that the documentation for this API is a little obscure, and the API itself is changing for Mac OS X Tiger. You'll want to dig through Apple's examples and find the file "NKE.pdf" on Jaguar or earlier to see how it all hangs together. This email sent to site_archiver@lists.apple.com
participants (1)
-
Peter Sichel