Re: Failing to bind to port
Re: Failing to bind to port
- Subject: Re: Failing to bind to port
- From: Joshua Graessley <email@hidden>
- Date: Mon, 7 Apr 2003 12:50:58 -0700
On Friday, Apr 4, 2003, at 15:55 US/Pacific, 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?
This is more than just a Mac problem. You'll also run in to racoon, a
daemon included with Mac OS X that implements IKE. IKE requires that
you use port 500, which is a significant shortcoming of the standard,
in my opinion. If all of the tools using port 500 set the SO_REUSEPORT
socket option, then it would be possible for all of them to bind to
port 500. This would probably lead to undesirable behavior.
-josh
_______________________________________________
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.