• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
FW: dlil_attah_interface_filter
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

FW: dlil_attah_interface_filter


  • Subject: FW: dlil_attah_interface_filter
  • From: "Carl Smith" <email@hidden>
  • Date: Thu, 7 Apr 2005 15:32:45 -0400
  • Thread-topic: dlil_attah_interface_filter

OK thanks Justin I believe I understand. So as long as I am working only
in X I should ignore the logic in SharedIP and in my filtered 'in'
routine use dlil_inject_if_input and in my filtered 'out' routine
continue to use dlil_inject_if_output?

Carl

-----Original Message-----
From: darwin-kernel-bounces+csmith=email@hidden
[mailto:darwin-kernel-bounces+csmith=email@hidden]
On Behalf Of Justin Walker
Sent: Thursday, April 07, 2005 12:18 PM
To: darwin-kernel Dev
Subject: Re: dlil_attah_interface_filter


On Apr 6, 2005, at 13:33, Carl Smith wrote:

>> In my NKE I have attached some filtering using
>> 'dlil_attach_interface_filter' and pointed my call back functions via
>> this call.
>>
>> The filtering works find and in my call back function,
>> My_if_input(caddr_t cookie, struct ifnet **ifnet_ptr, struct mbuf
>> **mbuf_ptr), I want to get/look at the filter ID of the calling
> filter.
>> This is the value that was obtained in the previous calling to
>> 'dlil_attach_interface_filter'.
>>
>
> Another question I have relating to the above statement, is that in
> My_if_input I am trapping the mbuf, Ethernet frame, as it is coming
in.
[snip]

Sorry for the delay; I haven't had time to look at this.  Short answer:
Yes :-}

dlil_inject* injects into the indicated stream (input: World -> System;
output: System -> World).

The confusion arising from SharedIP (other than its twisted
architecture) comes from the need to treat "World" on output as
(World+X).  Therefore, when Classic sends a frame to the "world", that
includes X; the output processing then must (selectively) inject frames
intended for X into the *input* stream (even though the frame is really
going "out to the world").

HTH.

Regards,

Justin

--
Justin C. Walker, Curmudgeon-At-Large
Institute for General Semantics
--------
When LuteFisk is outlawed,
Only outlaws will have LuteFisk
--------

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
ch.com

This email sent to email@hidden
 _______________________________________________
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

  • Follow-Ups:
    • Re: dlil_attah_interface_filter
      • From: Justin Walker <email@hidden>
  • Prev by Date: Re: dlil_attah_interface_filter
  • Next by Date: Re: dlil_attah_interface_filter
  • Previous by thread: FW: dlil_attah_interface_filter
  • Next by thread: Re: dlil_attah_interface_filter
  • Index(es):
    • Date
    • Thread