Re: ipf_inject_input returns ENOTSUP
Re: ipf_inject_input returns ENOTSUP
- Subject: Re: ipf_inject_input returns ENOTSUP
- From: Allan Hoeltje <email@hidden>
- Date: Tue, 20 Sep 2005 13:19:53 -0700
I tried using ctl_send_func first but had a number of problems. First, I
was not able to specify any options in the send call which my kext could
then interpret as "outgoing" or "incoming" packet. I suppose my kext code
could keep track of which IP address is used as the remote source and decide
accordingly.
If I use ctl_send_func, will the mbuf chain contain a proper M_PKTHDR in the
first mbuf? That is my biggest problem right now.
> Using setsockopt to pass in a whole packet is less than ideal
Why is setsockopt less than ideal? Inspection of the source code does not
reveal why this would be a poor choice.
>I hope you're using ctl_enqueuembuf to send the packet
>to your user app.
No, I am using ctl_enqueuedata to send the IP packet to my user app because
I needed to include my own control information, such as: is it incoming or
outgoing, was it removed from the IP stack (and thus needs to be returned
for insertion), etc. I realize that ctl_enqueuedata duplicates the mbuf
before sending it as flat (void *) data but is that too terribly expensive?
-Allan
_______________________________________________
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