starred/geodns

Fork 0

mirror of https://github.com/abh/geodns.git synced 2026-04-27 03:45:53 +03:00

[GH-ISSUE #66] Is MaxMind mmdb supported? #199

New issue

Closed

opened 2026-03-01 17:24:30 +03:00 by kerem · 10 comments

kerem commented

2026-03-01 17:24:30 +03:00

Owner

Originally created by @stutiredboy on GitHub (Jul 2, 2015).
Original GitHub issue: https://github.com/abh/geodns/issues/66

Thanks.

Originally created by @stutiredboy on GitHub (Jul 2, 2015). Original GitHub issue: https://github.com/abh/geodns/issues/66 Thanks.

kerem closed this issue

2026-03-01 17:24:30 +03:00

kerem commented

2026-03-01 17:24:31 +03:00

Author

Owner

@abh commented on GitHub (Jul 2, 2015):

No, not yet. It should be a relatively small change though.

They don't have an ASN database in the new format yet.

@abh commented on GitHub (Jul 2, 2015): No, not yet. It should be a relatively small change though. They don't have an ASN database in the new format yet.

kerem commented

2026-03-01 17:24:31 +03:00

Author

Owner

@skyred commented on GitHub (Sep 4, 2015):

http://dev.maxmind.com/geoip/geoip2/whats-new-in-geoip2/ says:

Autonomous System Number
In GeoIP Legacy, this was returned as a string like "AS1239 Linkem IR WiMax Network". This has been split into two keys, autonomous_system_number, an integer, and autonomous_system_organization, which is a string.

It seems the ASN data is merged with the two geolite2 databases, and using the new tokens.

I was wondering if the plan is to develop to support both formats?

@skyred commented on GitHub (Sep 4, 2015): http://dev.maxmind.com/geoip/geoip2/whats-new-in-geoip2/ says: > Autonomous System Number > In GeoIP Legacy, this was returned as a string like "AS1239 Linkem IR WiMax Network". This has been split into two keys, autonomous_system_number, an integer, and autonomous_system_organization, which is a string. It seems the ASN data is merged with the two geolite2 databases, and using the new tokens. I was wondering if the plan is to develop to support both formats?

kerem commented

2026-03-01 17:24:31 +03:00

Author

Owner

@abh commented on GitHub (Sep 6, 2015):

Nice; I didn't realize this was in the new format.

Yeah, I think it'd be nice to support the new format instead of using abh/geoip. Hopefully it could be done with a package that doesn't use cgo, too.

I'd like to see benchmarks before switching though.

@abh commented on GitHub (Sep 6, 2015): Nice; I didn't realize this was in the new format. Yeah, I think it'd be nice to support the new format instead of using abh/geoip. Hopefully it could be done with a package that doesn't use cgo, too. I'd like to see benchmarks before switching though.

kerem commented

2026-03-01 17:24:31 +03:00

Author

Owner

@oschwald commented on GitHub (Sep 9, 2015):

I came across this thread and was a bit curious about the relative speed myself. I made a simple benchmark for country lookups using my maxminddb package. Here are the results on my machine:

PASS
Benchmark_GetCountry-8    500000          2601 ns/op
BenchmarkMaxMindDB-8      500000          2744 ns/op
ok      test    2.753s

If you use a static IP, the results are again similar but about 1000 ns/op less.

As for ASN, there isn't a free ASN database for GeoIP2, but it is included with the ISP database.

@oschwald commented on GitHub (Sep 9, 2015): I came across this thread and was a bit curious about the relative speed myself. I made a [simple benchmark](http://play.golang.org/p/9fAy4Irq4F) for country lookups using my [maxminddb package](https://github.com/oschwald/maxminddb-golang). Here are the results on my machine: ``` PASS Benchmark_GetCountry-8 500000 2601 ns/op BenchmarkMaxMindDB-8 500000 2744 ns/op ok test 2.753s ``` If you use a static IP, the results are again similar but about 1000 ns/op less. As for ASN, there isn't a free ASN database for GeoIP2, but it is included with the ISP database.

kerem commented

2026-03-01 17:24:31 +03:00

Author

Owner

@AnoopAlias commented on GitHub (Feb 6, 2018):

https://support.maxmind.com/geolite-legacy-discontinuation-notice/

I guess we won't be able to use the GeoIP legacy one January 2, 2019

Is there a plan to support the new Lite2 format?

@AnoopAlias commented on GitHub (Feb 6, 2018): https://support.maxmind.com/geolite-legacy-discontinuation-notice/ I guess we won't be able to use the GeoIP legacy one January 2, 2019 Is there a plan to support the new Lite2 format?

kerem commented

2026-03-01 17:24:31 +03:00

Author

Owner

@abh commented on GitHub (Feb 6, 2018):

Yeah, it is supported in the 3.0 branch.

@abh commented on GitHub (Feb 6, 2018): Yeah, it is supported in the 3.0 branch.

kerem commented

2026-03-01 17:24:31 +03:00

Author

Owner

@AnoopAlias commented on GitHub (Feb 7, 2018):

you mean the 'dev' branch right as I tried building using the 3.0 branch and its still using libGeoIP.so.1 ?

I was unable to build the dev branch - any instructions for doing that?

@AnoopAlias commented on GitHub (Feb 7, 2018): you mean the 'dev' branch right as I tried building using the 3.0 branch and its still using libGeoIP.so.1 ? I was unable to build the dev branch - any instructions for doing that?

kerem commented

2026-03-01 17:24:31 +03:00

Author

Owner

@abh commented on GitHub (Feb 7, 2018):

Oh, yeah - dev sounds right!

@abh commented on GitHub (Feb 7, 2018): Oh, yeah - dev sounds right!

kerem commented

2026-03-01 17:24:31 +03:00

Author

Owner

@abh commented on GitHub (Feb 7, 2018):