POLICY SERVER

The policy Server is needed on the server side when a client platform is a Unity 3 web player. It is not needed when using the web player in older versions of Unity. The purpose of the policy server is to make the Unity web player more secure. The security details are well described at this page on the Unity website: http://unity3d.com/support/documentation/Manual/Security Sandbox.html.
The web player in Unity 3 first sends a special request over the network to the server, using a TCP connection on port 843. The policy server is running on the server machine and it is listening on port 843. When it gets this request it sends an OK reply to the web player. After this sequence the web player will accept incoming network traffic from the game server. When hosting a game server based on uLink, we recommend that the policy server is running on the same host, accessible by the same network adress. A policy server is included in uLink. On Windows it is installed by default at the following path. C:/Users/Public/Documents/uLink Tools/PolicyServer For most situations, the policy server can be used without any special configuration. Just start uLinkPolicyServer.exe and it will work out-of-the-box. For Mac OS the file name is uLinkPolicyServer.sh. In the latter case, the server usually needs to be started as root. To do this, use the "sudo" command: The policy server included in uLink is very similar to the policy server that is available from Unity. You can use either one of the policy servers; they are very simple and they both do the same job. UnityPark will support the policy server included in uLink. The policy server is a console application and can be configured with a number of options. To see a listing of these options, run the policy server with the -help command line switch.