Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#10910 closed enhancement (fixed)

Update to February GeoIP2 database

Reported by: karsten Owned by:
Priority: Medium Milestone:
Component: Core Tor/Tor Version:
Severity: Keywords: tor-client tor-relay
Cc: nickm Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

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).

Child Tickets

Change History (3)

comment:1 Changed 6 years ago by karsten

Status: newneeds_review

comment:2 Changed 6 years ago by nickm

Resolution: fixed
Status: needs_reviewclosed

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?

comment:3 in reply to:  2 Changed 6 years ago by karsten

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 for this.

Note: See TracTickets for help on using tickets.