NOTE: An IP address can be manually identified as a Botnet IP address by using the Botnet Test diagnostic tool accessed from the System > Diagnostics page.
Use the General Settings section of the Geo IP & Botnet Filter > Settings page to globally enable or disable the Geo IP & Botnet Filter, which is disabled by default.
|
NOTE: An IP address can be manually identified as a Botnet IP address by using the Botnet Test diagnostic tool accessed from the System > Diagnostics page.
|
|
1
|
Check the Enable Geo IP & Botnet Filter check box to enable this feature. When enabled, a Location column is added to the NetExtender > Status, Virtual Assist > Status, Virtual Meeting > Status, and User > Status pages that identifies the location of users’ source IP addresses. Mousing over an icon in the Location column displays the City (if applicable), Region, and Country of the source IP.
|
|
2
|
Click Accept.
|
|
•
|
Enforce Geo IP Policy — Select this option to enforce Geo IP polices.
|
|
•
|
Enforce Botnet Filter Policy — Select this option to enforce Botnet Filter policies. If this is disabled, Botnet IPs will not be blocked, however they will still be detected and included in the Botnet Filter Statistics.
|
|
•
|
Find Geo IP Location for Logs — When this option is enabled, a column indication the location of the source IP is added to the following screens: End Point Control > Log, Web Application Firewall > Log, Geo IP & Botnet Filter > Log, and Log > Views.
|
|
•
|
Enable Packet Log (Debug mode) — Select this option to generate logs for allowed or denied packets. This option is for debug purposes only. Enabling the Packet Log will make logs increase rapidly if the log level is set to Debug.
|