Skip to content

Releases: CAIDA/libipmeta

V3.2.1

01 Oct 22:53
Compare
Choose a tag to compare

Changes:

  • Remove repeated call to AM_INIT_AUTOMAKE in configure.ac.
  • Drop malformed rows of maxmind data that are missing latitude/longitude.

V3.2.0

19 Jul 03:45
Compare
Choose a tag to compare

Code cleanups, ensure licensing is consistent.

V3.1.0

14 Sep 23:39
f557cce
Compare
Choose a tag to compare

Changes

  • add PROVMASK, provider mask, for the usage by pyipmeta

V3.0.0

06 Jul 16:31
Compare
Choose a tag to compare

LibIPMeta V3.0.0 release added support for IPv6.

Changes

  • Add support for IPv6
  • Add support for MaxMind v2 data files

V2.2.0

01 Jul 16:19
5ca5f8d
Compare
Choose a tag to compare

This is the last version 2 release for libipmeta.

Changes since 2.1.0

  • Fixed debian package build-time dependency
  • Fixed build instruction in README.md
  • Fix bug when printing provider name to file
  • Fix bug where ASNs were printed as signed integers
  • Fix command line option error handling
    • crashed on unknown option, because ipmeta was uninitialized
    • used a nonstandard glibc extension (leading ":" in optstring)
    • suppressed all builtin error messages but replaced only one of them
  • Fix returning multiple results from patricia lookup
  • Fix address count for prefix lookup in patricia
  • Expose datastructure name-to-id mapping

v2.1.0

22 Sep 10:42
f716b9a
Compare
Choose a tag to compare

This is a minor release that removes the concept of "default" providers.

This change results in a minor change to the public libipmeta API. Users will need to remove the "set_default" argument to the ipmeta_enable_provider function.

v2.0.0

07 Jan 22:40
da1ce91
Compare
Choose a tag to compare

This is the first release in the v2 series of libipmeta.
This version has a different public API to v1 so will require some changes to code that uses it, but may be more efficient when using multiple providers simultaneously.

v1.0.0

21 Sep 15:44
Compare
Choose a tag to compare

We do not plan to continue development of this version, so it should be considered deprecated and users should switch to the new v2 API.