# Is it possible to use the old GeoIP format rather than the new GeoIP database format with Logstash 5?

**URL:** <https://discuss.elastic.co/t/is-it-possible-to-use-the-old-geoip-format-rather-than-the-new-geoip-database-format-with-logstash-5/65516>\
**Category:** Logstash\
**Created:** [November 9, 2016, 3:34pm UTC](https://discuss.elastic.co/t/is-it-possible-to-use-the-old-geoip-format-rather-than-the-new-geoip-database-format-with-logstash-5/65516 "2016-11-09T15:34:52Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Justin\_Henderson](https://avatars.discourse-cdn.com/v4/letter/j/8edcca/32.png) [@Justin\_Henderson](https://discuss.elastic.co/u/Justin_Henderson)\
**Post date:** [November 9, 2016, 3:34pm UTC](https://discuss.elastic.co/t/is-it-possible-to-use-the-old-geoip-format-rather-than-the-new-geoip-database-format-with-logstash-5/65516/1 "2016-11-09T15:34:52Z")

</div>

In Logstash versions prior to 5 myself and others use the free geoipasnum.dat from MaxMind considerably. The main reason we haven't switched to version 5 is it seems Logstash 5.0 requires the new geoip database format which does not offer a free ASN number database.

Is there a way to tell Logstash 5 to load the older GeoIP .dat format so we can continue using ASN # lookups?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [December 7, 2016, 3:35pm UTC](https://discuss.elastic.co/t/is-it-possible-to-use-the-old-geoip-format-rather-than-the-new-geoip-database-format-with-logstash-5/65516/2 "2016-12-07T15:35:08Z")

</div>

Closed on December 7, 2016, 3:35pm UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.