Bug#775638: IPv6 database is corrupt

2015-01-24 Thread Andrew Moise
Okay, I sorted it out. The reason the city DB was corrupted is because we were putting so many locations into the location file that we were overflowing the addressable places to put them. The Maxmind format uses 3 bytes to store offsets, so when we exceed offset 0xFF our offsets wrap around

Bug#775638: IPv6 database is corrupt

2015-01-23 Thread Andrew Moise
Hi Patrick. I tracked it down to a few broken entries in the city DB. It looks like the DB creation code makes almost all the entries correctly, but there are a couple of them that come out corrupted: (jessie)moise@localhost:~$ geoiplookup 1.120.146.170 GeoIP Country Edition: AU, Australia Geo

Bug#775638: IPv6 database is corrupt

2015-01-23 Thread Patrick Matthäi
Hi Andrew, do you have got any news? :) Am 20.01.2015 um 18:43 schrieb Andrew Moise: Thanks Patrick. One note - just like the v6 issue, the gdnsd test suite is detecting a genuine problem in the city DB. It is something wrong with the city DB creation tools that's causing it (i.e. not just

Bug#775638: IPv6 database is corrupt

2015-01-20 Thread Andrew Moise
Thanks Patrick. One note - just like the v6 issue, the gdnsd test suite is detecting a genuine problem in the city DB. It is something wrong with the city DB creation tools that's causing it (i.e. not just an issue with the gdnsd tests). I just haven't finished tracking down exactly what the issu