GeoIP - Library for country/city/organization to IP address or hostname mapping

Distribution: CentOS 7
Repository: Atomic x86_64
Package name: GeoIP
Package version: 1.6.9
Package release:
Package architecture: x86_64
Package type: rpm
Installed size: 299.65 KB
Download size: 116.68 KB
Official Mirror:
GeoIP is a C library that enables the user to find the country that any IP address or hostname originates from. It uses file based databases that can optionally be updated on a weekly basis by installing the geoipupdate-cron (IPv4) and/or geoipupdate-cron6 (IPv6) packages.



  • GeoIP =
  • GeoIP(x86-64) =
  • geoip =


  • geoip <


    Source package:

    Install Howto

    1. Download the latest atomic-release rpm from
    2. Install atomic-release rpm:
      # rpm -Uvh atomic-release*rpm
    3. Install GeoIP rpm package:
      # yum install GeoIP


    • /usr/bin/geoiplookup
    • /usr/bin/geoiplookup6
    • /usr/lib64/
    • /usr/lib64/
    • /usr/share/doc/GeoIP-1.6.9/AUTHORS
    • /usr/share/doc/GeoIP-1.6.9/ChangeLog
    • /usr/share/doc/GeoIP-1.6.9/
    • /usr/share/doc/GeoIP-1.6.9/
    • /usr/share/licenses/GeoIP-1.6.9/COPYING
    • /usr/share/man/man1/geoiplookup.1.gz
    • /usr/share/man/man1/geoiplookup6.1.gz


    2016-02-03 - Fedora Release Engineering <> - 1.6.9-2 - Rebuilt for

    2016-01-12 - Paul Howarth <> - 1.6.9-1 - Update to 1.6.9 - Allow compilation on older systems by relaxing the autoconf and automake minimum versions - Avoid potential problems in multi-threaded environments by consistently using pread() rather than read() - Fix various small issues reported by clang's static analyser - Fix a regression introduced in version 1.6.8, which caused GeoIP_database_info to erroneously return NULL

    2015-11-01 - Paul Howarth <> - 1.6.7-1 - Update to 1.6.7 - Fixed a MSVC parser stack overflow when parsing 'regionName.c' and 'timeZone.c' (GH#54) - Updated region codes and timezones - When using 'GEOIP_MEMORY_CACHE' with an invalid database file, the search tree traversal could attempt to read memory outside of the memory allocated for the memory cache, resulting in a segmentation fault; a check was added to ensure that the traversal code does not try to read beyond the end of the file, whether in memory, memory mapped, or on disk - Previously the return values from file reads were ignored; we now check these values to ensure that there were no errors