Re: Attaching an NKE to Existing Sockets
Re: Attaching an NKE to Existing Sockets
- Subject: Re: Attaching an NKE to Existing Sockets
- From: Jones Curtis <email@hidden>
- Date: Tue, 29 Aug 2006 16:14:51 -0400
On Aug 29, 2006, at 15.57, Josh Graessley wrote:
The unfortunate answer is that there is no clean way to do this
right now.
We have a bug tracking this, 4355398. One trick is to have your
kext load at startup. There is a hook to let you start as soon as
the network stack has finished initializing. The common trick is to
create an IOKit kext that will get matched and loaded on startup
early in the boot process and register the function to run when the
network stack is done initializing.
In addition to the sockets you see associated with each process,
there are sockets in the kernel that are not associated with any
process. This makes it difficult to find all of the sockets. Most
protocols have a protocol specific method of doing this. I don't
think there is general linked list of all sockets.
Thanks for the response.
Any chance that you can point me to something, or otherwise elaborate
on non-clean ways of doing this? I'm not as concerned about in-kernel
sockets as I am about user-created TCP sockets (including listeners).
I'd be okay with a certain amount of un-clean-ness for the time being
(until a good solution is made available).
Thanks.
--
Curtis Jones
email@hidden
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden