• 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
Re: MacOS X NKE and Classic Networking
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: MacOS X NKE and Classic Networking


  • Subject: Re: MacOS X NKE and Classic Networking
  • From: Joshua Graessley <email@hidden>
  • Date: Tue, 6 Aug 2002 17:49:56 -0700

There are a number of places you could run in to problems. The most common is the result of an assumption in SharedIP.kext. SharedIP assumes that the packet header (for ethernet packets) immediately precedes the data at m_data. If this isn't the case, SharedIP does the wrong thing and usually doesn't divert packets to classic as it ought to. This is fixed in the SharedIP shipping with Mac OS X 10.2.

Another common problem is that SharedIP is implemented as two protocol filters and a socket filter. If you are also implementing a protocol filter, packets may not be getting to the filters in the right order.

You will need to explain more about where you're inserting/intercepting packets. Are you working on a socket filter, a protocol filter, or an interface filter?

-josh

On Tuesday, August 6, 2002, at 03:01 PM, Mike Dolan wrote:

Hi all,

I've got an NKE that works fine for OS X networking but fails on inbound
packets to Classic applications. By Classic I mean running in Classic mode,
not booted into < 10. For example, ftp. I can create an ftp session from the
terminal just fine, but using Fetch in Classic fails. I've tried various
different things to try to fix this; pull-ups, copies, etc., but nothing
seems to be working. I grabbed clear packets and re-injected them with
success, so it seems that it's definitely something with the packet I'm
processing. When I process the inbound packet, the dlil_inject_if_input call
returns good status, but nothing gets to the Classic app. When looking at
the inbound mbuf vs. the mbuf I create and inject, the only real difference
that I see are the csum_flags and csum_data field are set in the original
mbuf, but zeroed in the one I inject. Is this a problem, or is there some
magic bit I need to flip to make this work for Classic (and not break the
working MacOS X)?

So I guess my real, basic question is, what's different between MacOS X and
Classic networking?

Thanks!

--
Mike
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.

References: 
 >MacOS X NKE and Classic Networking (From: Mike Dolan <email@hidden>)

  • Prev by Date: Re(2): How to create dial-up settings in OS X 10.0?
  • Next by Date: Getting the primary interface name ?
  • Previous by thread: MacOS X NKE and Classic Networking
  • Next by thread: Getting the primary interface name ?
  • Index(es):
    • Date
    • Thread