• 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: OT vs. socket calls on 10.2
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: OT vs. socket calls on 10.2


  • Subject: Re: OT vs. socket calls on 10.2
  • From: Peter Sichel <email@hidden>
  • Date: Thu, 5 Sep 2002 12:01:17 -0400

At 6:54 AM -0400 9/5/02, Jim Matthews wrote:
I'm trying to help a user who can't FTP from OS X 10.2; the server never receives the passive mode data connection. The strange thing is that the built-in ftp client works, as does Fetch 3.0.3 running in Classic. But FTP clients that run native and use Open Transport APIs -- Fetch 4.0.2, Captain FTP, and NetFinder -- all fail to connect.

As far as I can tell the only distinction between the programs that work and the ones that don't is the API they use. I've seen one other case like this -- running the NortonPrivacyControl feature of Norton Personal Firewall on OS X blocks uploads of some text files with Fetch, but not with the command-line FTP client. I assume that's because the Norton software catches calls to the OT API but not BSD socket calls, but I don't know exactly why.

So are there "patching" mechanisms that would draw a distinction between networking APIs? Does the built-in firewall software?

Hi Jim,

This is a tough one. I would have the user try this:

- type "ifconfig -a" to see a list of configured interfaces.

- type "sudo ipfw list" to see a list of firewall rules.

My guess would be a problem obtaining the correct IP address
for use in the ftp port command. Have the user check the order
of configured interfaces in the Network Preferences pane to
make sure the primary interface is listed first.

It is true that Protocol Filter NKEs do not see Classic IP
traffic, but this should not apply to ipfw which I presume
is implemented as an Interface Filter NKE in Jaguar.

Finally, you can use the Monitor tool in IPNetMonitorX (and TCP Dump
tool if needed) to verify whether you can see the packets flowing
in each direction. It's free for 21-days.

Kind Regards,

- Peter
_______________________________________________
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: OT vs. socket calls on 10.2
      • From: Joshua Graessley <email@hidden>
References: 
 >OT vs. socket calls on 10.2 (From: Jim Matthews <email@hidden>)

  • Prev by Date: Re: OT vs. socket calls on 10.2
  • Next by Date: Re: OT vs. socket calls on 10.2
  • Previous by thread: Re: OT vs. socket calls on 10.2
  • Next by thread: Re: OT vs. socket calls on 10.2
  • Index(es):
    • Date
    • Thread