122
edits
Geolocation statistics: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 47: | Line 47: | ||
The IP address can be clicked to reach the [[IP_module|IP module]] page about that IP address. The table contains the alternative names for each IP, which includes all known sources of name lookup such as DNS, DHCP, or HTTP/SSL information. | The IP address can be clicked to reach the [[IP_module|IP module]] page about that IP address. The table contains the alternative names for each IP, which includes all known sources of name lookup such as DNS, DHCP, or HTTP/SSL information. | ||
The number of packets and bytes and the history graph is shown for each IP, and there is a capture button to record traffic for the corresponding IP address. | The number of packets and bytes and the history graph is shown for each IP, and there is a capture button to record traffic for the corresponding IP address. | ||
=== Configuration === | |||
'''Custom local subnets''' | '''Custom local subnets''' | ||
The button | The button ''Configure custom local subnets'' opens a dialog where IPv4 and IPv6 subnets can be added and removed to and from the custom local subnet list. | ||
If an IP address matches one of the configured subnets no further country, city | If an IP address matches one of the configured subnets no further country, city or ASN lookup will be performed and the address will be shown as a local address wherever geolocation information is shown. | ||
Traffic for such an address will also be accounted as local traffic in the geolocation statistics. | Traffic for such an address will also be accounted as local traffic in the geolocation statistics. | ||
Changes to the custom local subnets will only affect new connections. Existing connections will still be accounted towards the country that was determined when the connection was established. | Changes to the custom local subnets will only affect new connections. Existing connections will still be accounted towards the country that was determined when the connection was established. | ||
'''Custom location databases''' | |||
The button ''Install custom location databases'' opens a dialog that can be used to upload user-provided city- and ASN-databases. The database files must be in the MaxMind binary database format (MMDB). It is not required to upload both databases. If only one database is uploaded the default database will be used for the other one. | |||
User-provided databases will only be used after the next restart of the device or after restarting the processing. If any error occurs while loading a user-provided database this error will be reported as an incident when the processing is stared. | |||
The | The button ''Reset to default location databases'' will remove any user-provided geolocation database but the default databases will only be used after the next restart of the device or after restarting the processing. | ||