MantisBT - Doomseeker |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0004028 | Doomseeker | [All Projects] Documentation | public | 2022-09-07 12:35 | 2022-09-07 17:53 |
|
Reporter | WubTheCaptain | |
Assigned To | | |
Priority | normal | Severity | feature | Reproducibility | have not tried |
Status | new | Resolution | open | |
Platform | | OS | | OS Version | |
Product Version | | |
Target Version | | Fixed in Version | | |
|
Summary | 0004028: IpToCountry_v3.dat.SPECS.txt GeoIP section does not indicate support for IPv6 addresses |
Description | Nevermind that Doomseeker doesn't support IPv6 well (as of 1.3.3) or the currently available source (Mailfud / MaxMind) may not have IPv6 IP2C data, the IP2C version 3 spec does not specify support for IPv6 (for the future) in the GeoIP section. Currently only support for IPv4 is specified. |
Steps To Reproduce | 'https://bitbucket.org/Doomseeker/doomseeker-blobs/src/1401483906a6a6efede29f55eb7a0542165fdf46/IpToCountry_v3.dat.SPECS.txt [^]'
Quote from IpToCountry_v3.dat.SPECS.txt
GeoIP section
-------------
The GeoIP structure contains a series of GeoID tables with content
structured in the following way. The number of IP Blocks varies between
each table.
Field | Size | Description
--------------------------------------------
Location ID | STRING | This is usually a 3-character code of
| | the location. For countries this is the
| | ISO ALPHA-3 Code. Doomseeker matches
| | country flags to IPs basing on this code.
| | Usually only the political country entities
| | are present here, however an exception for
| | this is a generic location somewhere in
| | the European Union that is expressed as
| | a 2-character STRING "EU".
| |
IP Blocks Count | ULONG | Amount of IP Blocks for this GeoID
| |
IP Blocks | 8 * <Count> | Pairs of IPs repeating as many times
| | as specified by the "Count" field.
A singular "IP Block" structure denotes a range of IPs understood as a set
of continuous integer numbers beginning from the "Begin" IPv4 and ending
on the "End" IPv4. A GeoID can have many non-continuous IPv4 addresses
assigned to it, so while the continuous range can be expressed as a min-max
integer pair, the non-continuous ranges are expressed as separate blocks.
Field | Size | Description
----------------------------
Begin | ULONG | First IPv4 in the block, inclusive
End | ULONG | Final IPv4 in the block, inclusive
In current version (3) of the database the data is not presented in any
particular order. Doomseeker's parser loads the data into hashtables
where it is eventually ordered solely by the "IP Block Begin" value
with GeoID information duplicated for each non-continuous block
belonging to the same GeoID. |
Additional Information | The quoted text in steps to reproduce has the following copyright notice:
Quote from IpToCountry_v3.dat.SPECS.txt
Copyright
=========
Copyright (C) 2022 The Doomseeker Team
Copying and distribution of this file, with or without modification,
are permitted in any medium without royalty provided the copyright
notice and this notice are preserved. This file is offered as-is,
without any warranty. |
Tags | No tags attached. |
Relationships | |
Attached Files | |
|
Issue History |
Date Modified | Username | Field | Change |
2022-09-07 12:35 | WubTheCaptain | New Issue | |
2022-09-07 12:43 | Zalewa | Note Added: 0022370 | |
2022-09-07 13:07 | WubTheCaptain | Note Added: 0022372 | |
2022-09-07 13:07 | WubTheCaptain | Note Edited: 0022372 | bug_revision_view_page.php?bugnote_id=22372#r13705 |
2022-09-07 13:07 | WubTheCaptain | Note Edited: 0022372 | bug_revision_view_page.php?bugnote_id=22372#r13706 |
2022-09-07 13:14 | WubTheCaptain | Note Edited: 0022372 | bug_revision_view_page.php?bugnote_id=22372#r13707 |
2022-09-07 13:19 | WubTheCaptain | Note Added: 0022373 | |
2022-09-07 13:22 | WubTheCaptain | Note Edited: 0022372 | bug_revision_view_page.php?bugnote_id=22372#r13708 |
2022-09-07 13:29 | WubTheCaptain | Note Edited: 0022373 | bug_revision_view_page.php?bugnote_id=22373#r13710 |
2022-09-07 13:37 | WubTheCaptain | Note Edited: 0022372 | bug_revision_view_page.php?bugnote_id=22372#r13711 |
2022-09-07 15:02 | Zalewa | Note Added: 0022374 | |
2022-09-07 17:53 | WubTheCaptain | Note Added: 0022376 | |
2022-09-07 17:53 | WubTheCaptain | Note Edited: 0022376 | bug_revision_view_page.php?bugnote_id=22376#r13713 |
Notes |
|
(0022370)
|
Zalewa
|
2022-09-07 12:43
|
|
|
|
(0022372)
|
WubTheCaptain
|
2022-09-07 13:07
(edited on: 2022-09-07 13:37) |
|
Quote the currently available source (Mailfud / MaxMind) may not have IPv6 IP2C data
The data from Mailfud (7 September 2022) has it. But Doomseeker (or forks of it conforming to V3 spec) can't use it. There is no common specified format for this and interoperability.
|
|
|
(0022373)
|
WubTheCaptain
|
2022-09-07 13:19
(edited on: 2022-09-07 13:29) |
|
I'd like to propose/see a new Type "GeoIP6" (4?) supported, or type numbers reserved for vendor-implementations / future use. May be a good idea to also indicate an URL of a registry for types, maintained by an entity. (Who or what that entity and its commitment to standards neutrality may be is an open question.)
|
|
|
(0022374)
|
Zalewa
|
2022-09-07 15:02
|
|
Well, sure, geolocation method for IPv6 could be devised, although I didn't have the plans to implement it at any time near now. You made it sound like it's the problem with V3 that there's no IPv6 in V3, but the first sentence in the specs file says specifically that this is a database for IPv4 geolocation.
In any case, V3 does not need to be the end-all of all problems with this format so in case if we find it not flexible enough in the future there's always room for another version.
I don't think that "type numbers reserved for vendor-implementations / future use" is a thing that is realistically applicable here either, but I'll mention in the specs that sections of unknown types must be handled with grace. |
|
|
|
I'll be submitting a new draft specification update soon to address some of my common concerns.
|
|