Re: Control socket communication gets truncated...
Re: Control socket communication gets truncated...
- Subject: Re: Control socket communication gets truncated...
- From: Josh Graessley <email@hidden>
- Date: Thu, 05 Jun 2008 06:45:32 -0500
Did you check to see if there was another mbuf in the chain (mbuf_next)?
-josh
On Jun 5, 2008, at 12:58 AM, Thorsten Kramp wrote:
Hello all,
I'm developing a TCP filter NKE for 10.5, with a user-level process
communicating with the NKE via a control socket in stream mode. The
user-level process waits for data from the NKE by calling select and
read/write, respectively.
However, sometimes when the user-level process writes to the control
socket some data, not all the data seems to be passed to the NKE
(even though the return value of write indicates that all bytes have
been passed to the socket). More precisely, for some reason the NKE
only gets the first 204 bytes in the m parameter of the NKE's
ctl_send_func. Interestingly, it's always precisely 204 bytes even
though the user-level process sometimes writes 217 bytes, 218 bytes,
300 bytes...
Does anybody has ever seen this behaviour? All suggestions are very
welcome! Thanks in advance.
Best, Thorsten
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden