TradeExpert Docs

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== IP block list module ======
~~NOTOC~~

  * [[te3:ip_block_list#IP block list|IP block list]]
  * [[te3:ip_block_list#Auto blocking|Auto blocking]]
  * [[te3:ip_block_list#IP whitelist|IP whitelist]]

TE3 logs IP addresses of all surfers who have visited your site over the past 24 hours. IPs that produced the most clicks get listed in the [[te3:cheat_logs|Cheat logs]] window, which greatly simplifies detection of repetetive occuring IPs and other types of abnormal traffic activities.

IP block list module is a part of TE3 anti-cheat features. It allows you to manually block IPs you decide to be suspicious, to automatically block IPs based on settings you determine and to allow exceptions for IP addresses of your choice. 

----

===== IP block list =====

Menu: {{:te3:tools_logo2.png?nolink|}} Tools / IP block list

"IP block list" contains a list of blocked IP addresses. Surfers with IPs listed on the “IP block list” are counted under system trade [[te3:outgoing_redirections#Blocked|“blocked”]]. 

Note, that IPs listed on the "IP block list" are not blocked from your site completely. By default blocked traffic doesn't get skimmed / sent to trades, it is sent to content (URL behind [[te3:outgoing|''u='', ''purl='']] parameters). If you would prefer to send blocked traffic to a specified URL, navigate to {{:te3:settings_logo.png?nolink|}} Settings / [[te3:outgoing_redirections|Outgoing redirections]], and enable outgoing redirections for the system trade "Blocked" (not recommended).     

=== Visual presentation ===

{{:te3:ip_blocklist6.png?nolink|}} \\ 
|< 100% 3% 20% 77% >|
^ # ^ Action ^ Description ^
| 1. | ''Edit'' | edit settings for system trade ''Blocked''. | 
| 2. | ''IP block list'' | switch to "IP block list" module. | 
| 3. | ''Auto blocking'' | switch to [[te3:ip_block_list#auto blocking|Auto blocking]] module. | 
| 4. | ''IP whitelist'' | switch to [[te3:ip_block_list#IP whitelist|IP whitelist]] module. | \\ 

{{:te3:ip_blocklist7.png?nolink|}}

|< 100% 3% 20% 77% >|
^ # ^ Action ^ Description ^
| 1. | ''Checkbox'' | you can checkbox one or multiple records for manipulation. There is a ''mass checkbox'' option - click on it to select or deselect all entries. | 
| 2. | ''IP address'' | click on the individual IP to open the [[te3:ip_lookup|IP lookup window]] and inspect a detailed description of that IP address. This information is provided via a [[http://www.webhostingbuzz.com/wiki/what-is-whois-search/|whois]] command. | 
| 3. | ''Raw'', ''Clk TG'', ''Out T'' | sort "IP block list" acording to [[te3:interface_manager_available_parameters#Last 60: minutes|''Raw'', ''Clk TG'' or ''Out T'']] hits for the last 24 hours. | 
| 4. | ''Time added'' | time elapsed from the moment you added the record to the "Ip block list". Place your cursor over the table cell to inspect the date an time the respective record was added to the "IP blocklist".  | 
| 5. | ''Time expire'' | time remaining until a record will be removed from the "IP block list". Place your cursor over the table cell to inspect the date and time at which the respective record will be deleted by the [[te3:pseudo_cron|Pseudo-cron]].  | 
| 6. | ''Proxy detect'' | if [[te3:outgoing_redirections#proxy|proxy]] was detected using environment variables, ''Yes'' will appear in the field, otherwise the field will be empty. | 
| 7. | ''Add record'' | to add a record, click {{:te3:add_button.png?nolink|}} and open a "Manually add IP(s) to IP Block list" pop-up window. You can add one or multiple IPs at the same time. To enter multiple IPs, add one IP per line. You can add a whole IP block to the list as well (x. - A block, x.x. - B block, x.x.x. - C block). If the last character in the string is ''.'' (dot), a whole block will be blocked. Select ''Block time'' and click ''Add''. \\ <color grey>Note, that ''Raw'', ''Clk TG'' and ''Out T'' are not available (''N/A'') for records you have added manually.</color> | 
| 8. | ''Delete record'' | click {{:te3:backup_delete.png?nolink|}} to delete selected record. |  


{{:te3:ip_blocklist8.png?nolink|}}

|< 100% 3% 20% 77% >|
^ # ^ Action ^ Description ^
| 1. | ''Network multiselect'' | select preferred sites or click ''Select all''. | 
| 2. | ''To whitelist'' | move the selected IP/multiple IPs to the "IP whitelist" | 
| 3. | ''Delete'' | delete selected record(s). | 
| 4. | ''Network update'' | export selected records to other sites in your [[te3:network|Network]]. Select preferred sites from the "Network multiselect window", then click ''Network update'' button. | 










----

===== Auto blocking =====

Menu: {{:te3:tools_logo2.png?nolink|}} Tools / Auto blocking

"Auto blocking" module allows you to automatically block IPs that meet the auto blocking rules. If a certain IP address produces more than the set number of incomming raws or total clicks (Clk TG) in a period of one minute, it will automatically get blocked for a set time period and placed on the [[te3:ip_block_list#IP block list|IP blocklist]]. 

<color red>Auto blocking is enabled by default. </color>

<WRAP caution>


Based on our research it is not advisable to set Auto blocking rules too strictly - ''Out T'' could decrease as a result of too much "Blocked" traffic. It is also usually better to overlook a suspicious IP address or two, than to block IPs who don't deserve it.  
</WRAP>
----

===== IP whitelist =====

Menu: {{:te3:tools_logo2.png?nolink|}} Tools / IP whitelist

"IP whitelist" module allows you to exempt certain IP addresses from being blocked by the "Auto blocking" module.

Some providers use public [[te3:outgoing_redirections#proxy|proxys]] (such as AOL proxy). They are all legitimate, but a lot of Incoming raws and Clk TG can come from a single IP - when you identify such IP addresses in the "Cheat logs window", you should add them to the "IP Whitelist".  

We also advise you to add your own IP address to the "IP whitelist". TE3 will block you, if you have "Auto blocking" enabled and you exceed set auto blocking rules (for example, this could happen when testing your site).