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
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
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
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
tag #775638 + confirmed
clone #775638 -1
reassign -1 geoip-bin
retitle -1 geoip-generator produces faulty v6/city database
severity -1 grave
found -1 1.6.2-3
thanks
Hi
Am 18.01.2015 um 05:21 schrieb Debian Bug Tracking System:
> Processing commands for cont...@bugs.debian.org:
>
>> reassign 7756
Processing commands for cont...@bugs.debian.org:
> tag #775638 + confirmed
Bug #775638 [geoip-database] IPv6 database is corrupt
Added tag(s) confirmed.
> clone #775638 -1
Bug #775638 [geoip-database] IPv6 database is corrupt
Bug 775638 cloned as bug 775851
> reassign -1 geoip-bin
Bug #775851 [geo
6 matches
Mail list logo
