• 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: OTListen in OS 9
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: OTListen in OS 9


  • Subject: Re: OTListen in OS 9
  • From: Quinn <email@hidden>
  • Date: Fri, 2 May 2003 11:47:05 +0100

At 15:12 -0400 1/5/03, Lyndsey Ferguson wrote:
Does anyone have any suggestions as to why information is being sent to the
a machine and OTListen does not respond?

After reading your message I'm not sure what works and what doesn't. Is the following correct?

client server result
------ ------ ------
OS 9 OS 9 fails rarely
OS X OS 9 fails rarely
OS 9 OS X works
OS X OS X works

Here is a sample of the tcpdump. It is set to monitor ports 6020 to 6029 and
a dst (destination address) of 192.168.0.70

It would be helpful if we also had the packets coming back from the server. After a little post processing, your packet trace looks like:

client > server: S 4165120739:4165120739(0) win 32768
client > server: . ack 2150715765 win 33304
client > server: P 0:43(43) ack 1 win 33304
client > server: F 43:43(0) ack 1 win 33304

All we can see is the client to server traffic. Can you post a trace that has both that and the server -> client traffic.

What you really need to find out is whether OT on 9 has received any asynchronous events (specifically, the T_LISTEN event) and what it's done with them. You can work this out by exploiting the logging facility built into OTMP. You enable logging of systems by calling MPLogSetMask with a particular mask. For OTMP, the types of log point are defined by the following (from "OTMP.h").

kOTMPWaitRecordLogID = 1,
kOTMPNotificationLogID = 2,
kOTMPStdActionLogID = 3,
kOTMPAPILogID = 4,
kOTMPRetriesLogID = 5

[This need to be turned into a bit mask (1 << logID) when you call MPLogSetMask.]

You probably should start with kOTMPAPILogID and kOTMPNotificationLogID. The first logs all calls and returns from OTMP routines, and will tell you what your thread is doing. The second logs all OT event notifications. Once you've figured out roughly what's going wrong, you can enable more log points to narrow down the debugging.

S+E
--
Quinn "The Eskimo!" <http://www.apple.com/developer/>
Apple Developer Technical Support * Networking, Communications, Hardware
_______________________________________________
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.

  • Follow-Ups:
    • Re: OTListen in OS 9
      • From: Lyndsey Ferguson <email@hidden>
References: 
 >OTListen in OS 9 (From: Lyndsey Ferguson <email@hidden>)

  • Prev by Date: Re: URLAccess kURLDisplayProgressFlag issue
  • Next by Date: Re: Obtaining Ethernet link speed
  • Previous by thread: OTListen in OS 9
  • Next by thread: Re: OTListen in OS 9
  • Index(es):
    • Date
    • Thread