|
現: 2008-12-21 (日) 03:29:18 iseki  |
| | + | ** White List Filter [#a5961b64] |
| | | | |
| | + | ***Limitation on function [#je4a756d] |
| | + | When the access limitation to SIM by the White List Filter is done, it is necessary to block the packet from the machine (use it with Second Life Viewer) to the Internet by the firewall. The function of White List Filter doesn't operate normally, if the access for the Internet has been permitted. Please note it. |
| | + | |
| | + | ***White List File [#v0a1e749] |
| | + | When [[sl_info>sl_info (E)]] is started with ''-wf'' option, [[sl_info>sl_info (E)]] starts reading specified White List File. |
| | + | Though White List File can be specified following ''-wf'' option, it is possible to specify it even by the [[White_List_File>../White_List_File]] item of the configuration file.~ |
| | + | [[White_List_File>../White_List_File]] of the configuration file is given to priority when specified by both the command option and the configuration file. The default of White List File is ''/var/sl_proxy/filter/white_sim.list''. |
| | + | |
| | + | The White List File specified by ''-wf'' option, or by [[White_List_File>../White_List_File]] or by default is a default configuration for all users (avatars). The White List of each avatar or each machine besides such a setting can be set in [[sl_info>sl_info (E)]], too. |
| | + | |
| | + | When the file of avatar name is made in the directory where the entire White List File for all avatars is put, it becomes the White List of each avatar. Moreover, when the file of IP address is made in the same directory, it becomes the White List of each machine with the IP address.~ |
| | + | -''/var/sl_proxy/filter/Fumi\ Hax'' for Fumi Hax~ |
| | + | -''/var/sl_proxy/filter/202.26.159.158'' for PC~ |
| | + | |
| | + | The priority level of each setting is the highest the setting of each avatar, sets for each machine is next, and sets for all avatars is end. |
| | + | |
| | + | It is necessary to make the effective user of [[sl_info>sl_info (E)]] can read this file, to read this file at the Control Process of the Information Server. |
| | + | |
| | + | The one SIM name is written at one line in the White List File. ''@ALL'' and ''@PG'' can be used to instead of SIM name as a special description. ''@ALL'' shows all SIM and ''@PG'' shows all SIM of the PG setting. |
| | + | |
| | + | ***Check on White List [#i912018a] |
| | + | [[sl_info>sl_info (E)]] checks the existence of SIM in the White List by using the SIM DB after White List File is read, and SIM that there is no information on the SIM DB is deleted from the White List. |
| | + | |
| | + | In a word, it cannot be a movement of avatar to the SIM, if there is no data of the SIM on the SIM DB even if existing SIM is specified in White List. |
| | + | |
| | + | ***Attention at information gathering [#nb3dc82e] |
| | + | At present, information on SIM that [[sl_relay>sl_relay (E)]] gathers is only information on SIM by which Viewer (avatar) did handshaking. Therefore, information on new SIM is never sent from avatar in the state that the limitation by the white list filter. |
| | + | Because it is the following with the state that the limitation by the white list filter. |
| | + | +As for SIM that can be visited avatar, only data exists in the data base and the SIM has been permitted by the white list. |
| | + | +SIM that cannot be visited cannot obtain those information it is not to be able to do handshaking by it. |
| | + | |
| | + | When you gather information on new SIM, avatar that doesn't limit by the white list must be used. So, the permission of ''@ALL'' is given to at least one user or more and it is necessary to collect information on SIM through those users.~ |
| | + | The collection of infomation with sl_relay never does a special operation. Only avatar flies around of SIM that has not been visited, and information is sent to the Information Gathering Server automatically. |
| | + | |
| | + | ***Movement to limited SIM [#ob60bc05] |
| | + | -Limited SIM cannot be logged in. (Information of having logged in the server seems to remain. ) |
| | + | -The teleport to limited SIM fails without fail, and is logged out. |
| | + | -When linited SIM is adjacent, the SIM looks like the sea. The half can enter the SIM by flying. |
| | + | -Other unlimited avatar in limited SIM is not seen. |
| | + | -The chat with other unlimited avatar in limited SIM is possible. |
| | + | -The limited avatar looks like the phantom avatar when seeing from other unlimited avatar. |
| | + | |
| | + | ***Attention at Login [#p17f347c] |
| | + | When White List Filter is used, it is necessary to permit SIM logged in, in the White List. When neither "''My Last Location''" nor "''My Home''" on the login screen are included in the White List, please specify SIM recorded on the white list at "''<Type region name>''". |
| | + | |
| | + | ***Attention when Viewer sets WEB Proxy function [#r96da7de] |
| | + | When Viewer set the [[WEB Proxy function>/sl_relay (E)/WebProxy]], IP address seems to have changed from the WEB proxy into the one of Viewer on the way when seeing from [[sl_relay>sl_relay (E)]] (please refer [[WEB Proxy function>/sl_relay (E)/WebProxy]]). This state is detected, and [[sl_relay>sl_relay (E)]] is notified to the Information Tendering Server.~ |
| | + | The Information Tendering Server that receives the notification reads new White List File after annulling the White List. |
| | + | |
| | + | Therefore, when the White List of the WEB proxy and Viewer machine is set at the same time, it falls into the complex situation that changes the same machine White List on the way.~ |
| | + | When Viewer uses the WEB Proxy function, it is necessary to stop the White List of each machine being described for the Viewer machine and the WEB proxy. |
