Re: Failing to bind to port
Re: Failing to bind to port
- Subject: Re: Failing to bind to port
- From: Chris Hanson <email@hidden>
- Date: Sun, 6 Apr 2003 13:26:29 -0500
At 6:55 PM -0500 4/4/03, Brooks Bell wrote:
I'm writing an app that is using racoon to set up a VPN. The racoon client
is using port 500 for IKE. Unfortunately, if it is installed, so is
PGPnetService. So my client fails to bind to the socket unless I kill
PGPnetService first.
I'm new to this. What is the "Mac way" to handle this type of conflict?
The "Mac way" would be to both publish and locate the port a service
is running on via Rendezvous, and to let the IP stack pick a port for
your service at random.
Unfortunately, lots of software doesn't yet support Rendezvous, and
lots of software on both the Mac and other platforms expects
particular services to be running on specific well-known ports, so
this isn't really practical for anything but one's own protocols...
-- Chris
--
Chris Hanson, bDistributed.com, Inc. | Email: email@hidden
Custom Application Development | Phone: +1-847-372-3955
http://bdistributed.com/ | Fax: +1-847-589-3738
http://bdistributed.com/Articles/ | Personal Email: email@hidden
_______________________________________________
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.