|
Cur: 2008-12-21 (Sun) 03:29:18 gambled  |
| | + | ** Cooperation with the Information Server [#m12d84c9] |
| | | | |
| | + | ***Negotiation with the Information Server [#e9d04adb] |
| | + | When Relay Server ([[sl_relay>sl_relay (E)]]) is started with ''-is'' option, the Relay Server connects to the Information Server ([[sl_info>sl_info (E)]]) by TCP in the middle of login processing to Second Life. Later, negotiation with the Control Process of the Information Server ([[sl_info>sl_info (E)]]) is done, a connection password and port numbers necessary for communication are exchanged. |
| | + | |
| | + | Moreover, ([[sl_relay>sl_relay (E)]]) collects information on the avatar while processing the login. This information is then transmitted via the Relay Process to the Information Gathering Server. |
| | + | |
| | + | ***Data transfer to the Information Gathering Server [#z355f3d1] |
| | + | In [[sl_relay>sl_relay (E)]], information obtained by each Relay Process (of Relay Server) on the SIM and the avatar is sent once to the Relay Controller. ~ |
| | + | The Relay Controller transmits data to the Relay Process (of Information Server) to the Information Gathering Server. |
| | + | |
| | + | ***Information Tendering Server [#l7941d95] |
| | + | The current version (v1.5.1) of [[sl_relay>sl_relay (E)]] only uses the White List retrieval function of [[sl_info>sl_info (E)]]. |
| | + | |
| | + | ***Filtering by White List [#v0560200] |
| | + | When the ''-wf'' option is specified, operation of [[sl_relay>sl_relay (E)]] becomes a limited by the White List. When ''-wf'' is specified, ''-is'' is automatically specified. ~ |
| | + | |
| | + | When in white list mode an incoming connection packet for a new SIM server causes the UDP Relay Process to check, through the Relay Controller to [[sl_info>sl_info (E)]], whether the SIM is recorded on the White List. If it is on the white list then a new UDP Relay Process is started for the new SIM.~ |
| | + | If it isn't recorded on the White List, or it is unknown (there is no data on the SIM in the data base), the incoming connection packet is deleted.~ |
| | + | In the current version (1.5.1), only the UDP Relay Process does this, the HTTPS Relay Process doesn't. |
| | + | |
| | + | When the UDP Relay Process deletes the incoming connection packet, the Viewer and SIM see this as a packet loss. Therefore the SIM server repeats transmission of this packet again. |
| | + | |
| | + | Because repeat enquiry for these packets to be sent again by [[sl_info>sl_info (E)]] is inefficient, the Relay Controller maintains the result of the previous inquiry. |
| | + | |
| | + | *** Things to note when a WEB Proxy is used [#jb3acb27] |
| | + | For the White List filtering function of [[sl_info>sl_info (E)]], the White List can contain the Viewer machine IP address and the user (avatar). |
| | + | |
| | + | However when the Viewer is set to use a WEB proxy (Refer to the [[WEB Proxy function>../WebProxy]]) the IP address seen by sl_relay is changed. Thus the Information Tendering Server cannot accurately determine if a particular machine is on the White List when a WEB Proxy is used. |
| | + | |
| | + | To avoid this the UDP Relay Process notifies the Information Tendering Server that the Viewer IP address has changed. When the Information Tendering Server receives this notification it uses the new information for the White List. |
| | + | |
| | + | Because of the complexity involved here it is probably best to avoid using machine IP addresses on the white list when the Viewer uses a [[WEB Proxy>../WebProxy]]. |
| | + | |
| | + | |
