• 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
netstat vs. Network Utility
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

netstat vs. Network Utility


  • Subject: netstat vs. Network Utility
  • From: email@hidden
  • Date: Wed, 21 Feb 2007 09:33:22 -0800


Hello, all ...

I'm developing network applications that run on OSX, among other platforms. However, on OSX (10.4.8 Intel on my MacBook), the "netstat" command seems to behave a bit differently than on, say, Linux or Windows. Specifically, "netstat -a" doesn't show ports open by server processes on OSX. I know that my code binds to a port, because I can use Network Utility to do a portscan and it shows me that the port is open ... but i've not been able to get netstat to show me that. Am I missing something basic? I'd like to use netstat, as often I only have a bash shell as my interface to the machine.

Regards,

John

Falling You - exploring the beauty of voice and sound
http://www.fallingyou.com











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


  • Follow-Ups:
    • Re: netstat vs. Network Utility
      • From: "Timothy D. Keanini Sr." <email@hidden>
    • Re: netstat vs. Network Utility
      • From: Jonas Maebe <email@hidden>
  • Prev by Date: Re: Read-Timeout with Blocking Socket
  • Next by Date: Re: netstat vs. Network Utility
  • Previous by thread: Re: Bug in TCP stack: RST has wrong sequence number?
  • Next by thread: Re: netstat vs. Network Utility
  • Index(es):
    • Date
    • Thread