Location

Overview

Location is a position-dedependent config.txt/ezproxy.cfg directive that interacts with other Location directives and that associates IP addresses with geographic locations.

GeoLite data

EZproxy is licensed to include support for GeoLite City data created by MaxMind, available from www.maxmind.com .

The GeoLite City data is updated every month and available for download from www.maxmind.com/download/geoip/database/GeoLiteCity.dat.gz . This file should be downloaded to the directory where EZproxy is installed. EZproxy can then be directed to use this data by adding:

Location -File=GeoLiteCity.dat.gz


to config.txt/ezproxy.cfg. EZproxy will automatically decompress this file to GeoLiteCity.dat.

When download updated versions of GeoLiteCity.dat.gz, it is necessary to restart EZproxy to make EZproxy load the updated file, but it is not necessary to delete GeoLiteCity.dat unless you suspect it has become corrupt.

Manually specifying IP information

In addition to supporting GeoLite City data, EZproxy also allows you to specify location information manually by IP address. Any IP address that matches a manual rule overrides the data found in the GeoLite City data. Sample usage is:

Location IPStart-IPEnd Country/Region/City


Country should specified using two-character extended ISO 3166 codes.

Region is optional, but if present should be specified using the two-character ISO 3166-2 subcountry code for the US and Canada or the FIPS 10-4 subcountry code for other regions of the world.

City is optional and should be specified using the textual name of the city.

Private IP addresses

The most typical use of manually specifying location information is to assign geographic information for private IP addresses, such as those that start with 10, 172.16-172.31, or 192.168. For example,

Location 192.168.0.0-192.168.255.255 US/OH/Dublin


If no manual rules are specified for private IP addresses, these addresses appear as country 98, no region, no city.

See also

Audit Common Conditions and Action