Re: struct dlil_if_flt_str
Re: struct dlil_if_flt_str
- Subject: Re: struct dlil_if_flt_str
- From: Justin Walker <email@hidden>
- Date: Tue, 15 Mar 2005 14:01:15 -0800
On Mar 15, 2005, at 13:17, Carl Smith wrote:
Not sure if I asked the question clearly enough in my last post, but to
rephrase the question -
Can I manipulate the Ethernet header, and packet data using the data
passed into my dlil_if_flt_str function, filter_if_input?
Do you really want to futz with the frame header on the input path? As
implied by Josh's earlier reply, anything above the DLIL layer will not
see the frame header (it is provided to the filters at the DLIL layer
"for information purposes". The only code that might look at it after
your filter would be other filters, and you have no idea what they
might be up to.
The only information retained as the packet is passed to the network
layer is the identity of the interface that received the packet (and
that is kept in the mbuf header).
I am just anxious because I do not want to spend a lot of development
time 'barking up the wrong tree'.
We learn by barking at trees and other things that move in the forest
:-}
Cheers,
Justin
--
Justin C. Walker, Curmudgeon-At-Large *
Institute for General Semantics | If you're not confused,
| You're not paying attention
*--------------------------------------*-------------------------------*
_______________________________________________
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