Update to February GeoIP2 database

Finally, and thanks to Nick's efforts on dumping MaxMind's GeoIP2 database format, we have updates for src/config/geoip and src/config/geoip6. Three branches, all in my public repository:

• mmdb-convert contains Nick's mmdb-convert.py script with some tweaks he already merged on GitHub and with two more tweaks that are only in my branch: the first tweak (749ead7) is trivial, but the second (436f710) is quite important for the geoip6 file. Without that commit, we'd include a full copy of IPv4 assignments to the Teredo IPv6 address space 2001::/32. This branch also removes our previous workaround that cleaned up A1 ranges from GeoIP databases using the old format. This branch is supposed to be merged into master.

• geoip-feb2014 contains the updated geoip file with IPv4 ranges and is supposed to be merged into maint-0.2.2.

• geoip6-feb2014 contains the updated geoip6 file with IPv6 ranges and is supposed to be merged into maint-0.2.4 (the first maint-* branch that contains a geoip6 file).

added component::core tor/tor priority::medium resolution::fixed status::closed tor-client tor-relay type::enhancement labels

Trac:
Status: new to needs_review

ACK and merged on everything except merging into 0.2.2. 0.2.2 is dead -- or at least, if there is for some reason ever another 0.2.2 released, it will probably be based on the last released 0.2.2. So, merged into 0.2.3 and later.

Also, I would like an improved README.geoip if possible, to explain how the geoip files are generated now. Should I open a new ticket for that?

Trac:
Resolution: N/A to fixed
Status: needs_review to closed

Replying to nickm:

ACK and merged on everything except merging into 0.2.2. 0.2.2 is dead -- or at least, if there is for some reason ever another 0.2.2 released, it will probably be based on the last released 0.2.2. So, merged into 0.2.3 and later.

Okay. I made a note to base the next update on maint-0.2.3.

Also, I would like an improved README.geoip if possible, to explain how the geoip files are generated now. Should I open a new ticket for that?

Created #10924 (moved) for this.

closed

mentioned in issue #10924 (moved)

moved to tpo/core/tor#10910 (closed)

mentioned in issue tpo/core/tor#10924 (closed)