MantisBT - Doomseeker |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0003699 | Doomseeker | IP2C | public | 2019-08-19 20:51 | 2024-11-03 19:10 |
|
| Reporter | Zalewa | |
| Assigned To | Zalewa | |
| Priority | low | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | |
| Platform | | OS | | OS Version | |
| Product Version | 1.3 | |
| Target Version | | Fixed in Version | 1.4.0 | |
|
| Summary | 0003699: Inaccuracy in interpretation of MaxMind GeoLite's data |
| Description | This issue was detected on a specific case, therefore I will stick to the specific example: IP address 5.44.107.81 is located in Germany, however Doomseeker shows that it is located in USA. If we inspect MaxMind's IPv4 Country Blocks database we can locate the 5.44.107.81 to be under such record:
5.44.104.0/22,6252001,2921044,,0,0
The numbers 6252001 and 2921044 are of interest here. 6252001 is a "geoname_id" whereas 2921044 is "registered_country_geoname_id". The locations database points the first number to USA and the second to Germany. The conversion script that converts MaxMind's DB to Doomseeker's blob prefers "geoname_id" unless it's not defined, then the other value is used. It should be investigated whether that's the right course of action and whether the "registered_country_geoname_id" should be used at all times.
A fixed IP2C database blob should be uploaded to the Doomseeker's site after this is done.
|
| Steps To Reproduce | 1. Add 5.44.107.81 as a pinned server.
2. Notice that its location is in USA.
3. Location is reported as Germany by'https://www.ip2location.com/demo/5.44.107.81 [^]' |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | | related to | 0003950 | closed | Zalewa | MaxMind no longer a viable source of IP2C data |
|
| Attached Files |  diffblocks.txt.gz (265,913) 2019-08-20 08:21
/tracker/file_download.php?file_id=2496&type=bug |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2019-08-19 20:51 | Zalewa | New Issue | |
| 2019-08-20 08:21 | Zalewa | File Added: diffblocks.txt.gz | |
| 2019-08-20 08:25 | Zalewa | Note Added: 0020964 | |
| 2019-08-23 11:11 | Zalewa | Status | new => acknowledged |
| 2019-08-23 17:46 | WubTheCaptain | Note Added: 0020977 | |
| 2019-08-23 18:45 | WubTheCaptain | Note Added: 0020984 | |
| 2019-08-23 18:46 | WubTheCaptain | Note Added: 0020985 | |
| 2019-08-23 18:46 | WubTheCaptain | Assigned To | => WubTheCaptain |
| 2019-08-23 18:46 | WubTheCaptain | Status | acknowledged => feedback |
| 2019-08-23 18:47 | WubTheCaptain | Note Edited: 0020984 | bug_revision_view_page.php?bugnote_id=20984#r12792 |
| 2019-08-23 18:55 | WubTheCaptain | Assigned To | WubTheCaptain => |
| 2019-08-23 18:55 | WubTheCaptain | Status | feedback => acknowledged |
| 2019-08-23 21:04 | Zalewa | Note Added: 0020987 | |
| 2022-09-10 14:55 | Zalewa | Relationship added | related to 0003950 |
| 2022-09-10 15:48 | Zalewa | Note Added: 0022388 | |
| 2022-09-10 15:48 | Zalewa | Status | acknowledged => resolved |
| 2022-09-10 15:48 | Zalewa | Fixed in Version | => 1.4.0 |
| 2022-09-10 15:48 | Zalewa | Resolution | open => fixed |
| 2022-09-10 15:48 | Zalewa | Assigned To | => Zalewa |
| 2024-11-03 19:10 | Zalewa | Status | resolved => closed |
|
Notes |
|
|
(0020964)
|
|
Zalewa
|
|
2019-08-20 08:25
|
|
I filtered the current MaxMind's database to extract only those records where the two geoname_id values differ and matched them to the country or continent name. This is uploaded as diffblocks.txt.gz.
I tested several of those network IPs at the ip2location page. Depending on the IP, the page sometimes gives country that matches geoname_id, and sometimes the one that matches the "registered_country_geoname_id". Given this, there's no way to deduce from MaxMind's DB alone which ID is the one that should be used. |
|
|
|
|
|
I might've seen this issue with NE's Zandronum servers (Complex Doom Invasion) being reported as from France in Doomseeker 1.3, where they were reported as Canada more correctly in Doomseeker 1.2. |
|
|
|
(0020984)
|
|
WubTheCaptain
|
2019-08-23 18:45
(edited on: 2019-08-23 18:47) |
|
IP2Location website doesn't work with strict uBlock Origin (probably a JavaScript issue), so here's a copy:
Quote from WHOIS for 5.44.107.81 (5.44.104.0/22)
inetnum: 5.44.104.0 - 5.44.107.255
netname: ALVOTECH-US-VPS1
country: DE
org: ORG-dIG4-RIPE
admin-c: PBH-RIPE
tech-c: PBH-RIPE
status: ASSIGNED PA
mnt-by: providerbox-mnt
mnt-lower: providerbox-mnt
mnt-routes: providerbox-mnt
created: 2012-05-23T15:51:07Z
last-modified: 2018-12-11T21:21:07Z
source: RIPE
organisation: ORG-dIG4-RIPE
org-name: dogado GmbH
org-type: LIR
address: Saarlandstr. 25
address: 44139
address: Dortmund
address: GERMANY
phone: +492312866200
fax-no: +4923128662020
admin-c: PBH-RIPE
tech-c: PBH-RIPE
abuse-c: PBH-RIPE
mnt-ref: RIPE-NCC-HM-MNT
mnt-ref: providerbox-mnt
mnt-by: RIPE-NCC-HM-MNT
mnt-by: providerbox-mnt
created: 2008-04-21T14:11:50Z
last-modified: 2018-12-11T21:32:59Z
source: RIPE # Filtered
role: provider.BOX Hostmaster
address: dogado GmbH
address: Saarlandstrasse 25
address: D-44139 Dortmund
abuse-mailbox: abuse@dogado.de
admin-c: RTD-RIPE
admin-c: TMD-RIPE
tech-c: RTD-RIPE
tech-c: TMD-RIPE
mnt-by: providerbox-mnt
nic-hdl: PBH-RIPE
created: 2008-04-21T15:56:53Z
last-modified: 2014-04-28T16:14:55Z
source: RIPE # Filtered
route: 5.44.104.0/22
origin: as21413
mnt-by: ENVIA-TEL-MNT
mnt-by: providerbox-mnt
created: 2018-10-08T14:27:06Z
last-modified: 2018-12-11T07:11:40Z
source: RIPE
route: 5.44.104.0/22
origin: AS45012
mnt-by: CLOUDPIT-MNT
created: 2019-04-11T15:00:18Z
last-modified: 2019-07-18T16:17:59Z
source: RIPE
'https://bgp.he.net/ip/5.44.107.81 [^]' (better, but may require cookies & JavaScript)
|
|
|
|
|
Quote from Zalewa
Add 5.44.107.81 as a pinned server.
Which port? Which engine?
I tried Zandronum & 5.44.107.81:10666, it was not available at this time. |
|
|
|
(0020987)
|
|
Zalewa
|
|
2019-08-23 21:04
|
|
|
The server doesn't really need to be available and the game doesn't matter. The flag/location is resolved by the IP address alone. |
|
|
|
(0022388)
|
|
Zalewa
|
|
2022-09-10 15:48
|
|
|
5.44.107.81 - the case for this address has been fixed indirectly by updating the DB to Mailfud's. See 0003950. |
|