yammdb - just another .mmdb
Hey,
Today I wanted to present you, yammdb.
Which is another, different, geodatabase, based on real measurements.
You can find it here: https://github.com/Ne00n/yammdb
The Database is build weekly, on fridays.
As long the buildserver doesn't blow up.
The primary use case for me is to compare existing geo data, maybe someone of you will find it useful.
If you have any ideas and feedback, please lemme know.
Enjoy.
This discussion has been closed.

Comments
Latency is now included from the closest location.
Free NAT KVM | Free NAT LXC
Umm I'm stupid and new to all this. What is this???
Put in a IP, it'll tell you where the physical location of the server/host of the IP is.
Oh cool!
I'm trying this out with my gDNSd servers. The db seems much smaller than the ip-to-city-lite db I have been using, 16MB compared to 99MB. If this works as well it is going to save me a bunch of RAM.
Thank you for this !!
It has way less "useless" data on it, hence its so smol.
However, It should work with auto_dc maps using geo cords but I have no idea how accurate it is.
Free NAT KVM | Free NAT LXC
Thank you! I hope there is an acl version for bind9
I wrote a smol, 30 lines benchmark script, using a dump of the global routing table.
65%, 638k from 975k in the routing table, which is good, I expected less.
Github page said 600k.
Meanwhile the other .mmdb's have a 99% hit rate.
TLDR: Yes use it, but not as primary database, build your own, as my primary purpose was.
Free NAT KVM | Free NAT LXC
Fair enough.
if you build your own, you prob, can drop the memory usage even further.
Throw everything out and turn it into a flying gas can.
Free NAT KVM | Free NAT LXC
Speaking of hit rate, the benchmark I ran yesterday, gave me a 65% hit rate, against a routing table dump.
Which is more than I expected, roughly 648k from 975k, however, the second benchmark I ran, hit only 35% with 8.5 Million IP addresses.
This was due, that bigger subnets are splitted into smaller ones for more accurate data, however the ones which didn't respond where not filled, which has been fixed.
After fixing these bugs, the hit rate is at 74%.
The next step would be to see, where I can further improve the data I use for all of this, so I end up with higher hit rates.
Free NAT KVM | Free NAT LXC
Thanks to https://virtury.com/ we got a new Probe in Pakistan!
Free NAT KVM | Free NAT LXC
I took a bit longer than expected, however the software is now mostly optimized for more probes.
Expect more probes in the next weeks.
Daily test builds, not guaranteed, will be available under https://yammdb.serv.app/test.mmdb
Weekly build will happen as usual.
Also, thanks to https://ginernet.com for a new probe in Madrid.
Free NAT KVM | Free NAT LXC
It was supposedly to be already done, however I did a fuck up.
One function had the build hang for hours over hours.
This is fixed, thanks to GPT4 once again.
It should finish in a bit, once this is done, I will make a second test build, including a bunch of new locations.
Free NAT KVM | Free NAT LXC
i noticed its now smaller than the previous version i tested. did you reduce the coverage or change the format?
however, cool and useful idea to crosscheck other geolocators.
No, but I did noticed it too.
The only way I can explain it, is how the writer builds the database.
Basically I tried to aggregate the prefixes, to make the database even smaller, however it seems like the writer already does this.
So the size did not change after all, a while ago, the database had a lot of gaps, because the way it does ping bigger subnets.
These gaps have been closed, hence I do assume, that the writer now can optimize / aggregate the database even further, hence its smaller. The code definitely does not or has remove data.
Free NAT KVM | Free NAT LXC
I added a few more Locations for this test run.
Free NAT KVM | Free NAT LXC
Gonna be the biggest Friday run, yet.
Free NAT KVM | Free NAT LXC
Thanks to some people that followed my github repo, they actually gave me the idea, to make an mtr only geo database.
I did code it in less than 24 hours, however, the hit rates where to low and my brain did not manage to figure out yet where the fuck up was.
However, today I found the mapping error.
db/mtr.mmdb {'fail': 126502, 'success': 849072, 'percentage': 87.03306976200678}
From 64% to 74% now 87% hitrate, not bad.
I put the .mmdb as usual on https://yammdb.serv.app/mtr.mmdb
This database is only 4.2MB in size, only contains geo coordinates, right now.
I will add the usual info in a later build, such as country, continent etc.
Plus I will add a combined build later, with geo.mmdb and mtr.mmdb which first uses latency, then mtr for better accuracy.
Free NAT KVM | Free NAT LXC
Any plans to release a CSV version of the mmdb?
I updated the mtr.mmdb, it does now include continent, country and latency same as the geo.mmdb.
@somik Sure, I added the csv file: https://yammdb.serv.app/mtr.csv
Currently they are smaller than the geo.mmdb due to less measurements per subnet, this will change once I run them again.
Free NAT KVM | Free NAT LXC
I also added geo.mmdb as csv: https://yammdb.serv.app/geo.csv
There is no compression or anything, hence the file is so big.
Usually the .mmdb writer does the compression.
Free NAT KVM | Free NAT LXC
Best to have it without compression for maximum compatibility. I'm visiting our neighbouring country for some good foods now, so I'll test it out once I go back to Singapore.
On that note, seems like a lot of shops closed down over the last pandemic... Sad days.
Well, I guess a .mmtr only database with more tests per subnet, won't be happening.
It takes to long, roughly 1-2 days to finish a build with roughly 8+ million targets.
Even with 20 probes, running, at the same time.
Instead I am going to run another test build next week, which does .mtr on subnet's that doesn't ping and combines them with the latency results as mentioned before.
Free NAT KVM | Free NAT LXC
@Neoon I think your CSV headers (table titles) are missing for both geo.csv and mtr.csv
I will change that before the next build tomorraw.
Free NAT KVM | Free NAT LXC
It seems that a recent masscan is mandatory, I still used a 2 months old one.
The build just finished 3 hours earlier and with +7% higher hitrate, so 80% without mtr.
Lesson learned, masscan will be updated at least once per week, gg.
As soon I get the mtr integration working It should easily get a 90%+ hitrate.
Free NAT KVM | Free NAT LXC
I thought port scanning was frowned upon by most data-centers/hosts?
Btw, what's MRT?
90% hit rate as in for IPs or returning correct geo-loc/country?
I never said I was port scanning.
hit rate means, you get a result.
Accuracy depends on the amount of locations.
Free NAT KVM | Free NAT LXC
Isn't masscan used for port scanning? Are you using it to scan for something else?
You should read up what masscan can do.
Yes, as I said a few times.
Free NAT KVM | Free NAT LXC
Hello Sir, can you explain to me how to use that mmdb?
i never using mmdb before. thanks
Any database guru please help with an indexing and sql statement for best performance on searching the dataset given an IP address.
Thanks in advance
Virmach Deals
Probably if you store it in binary, the .mmdb uses a binary search tree and does lookups in a fraction of a second, also just 15MB in size compared to the csv.
You provide a IP address, it gives you the approximate location.
Python example is on github.
Free NAT KVM | Free NAT LXC
sorry, i mean step by step running/read file .mmdb , like as apt install blabla , and than next step.
on linux , or android , or windows
Convert the IP/subnet (CIDR) to a IP range containing the starting and ending IP.
Convert the starting and ending IP to a "long" number.
For PHP, you can use:
Save it in the DB like:
index, startingIPLong, endingIPLong, LocationWhen you want to check a IP, convert it to "long" number, and find the row
WHERE startingIPLong>= searchIP AND endingIPLong<= searchIPI think you'll be able to figure it out from there?
For PHP to convert the IP to long, use function: https://www.php.net/manual/en/function.ip2long.php
Thanks @somik for the function. That's really help.
Virmach Deals
Btw, i did it other way around. Guess should not be browsing LES first thing after waking up:
WHERE startingIPLong <= searchIP AND endingIPLong >= searchIPJust a small typo mistake
Virmach Deals
I just made a tiny shell script to add two columns: ipfrom and ipto to the datasets made available by @Neoon. Not sure if my style of making data ready before importing into databases will help
To use the script:
output sample
Virmach Deals
That's what I did as well, just with PHP. Process the data before importing it into DB to make subsequent queries faster.
Hi @Ganonk! Hi @Neoon!
I never tried something like this before. Here is a transcript of the steps I tried. Maybe the transcript will be helpful to anybody who can show me my mistakes or who wants a beginner style recipe.
I cut and pasted the program from https://github.com/Ne00n/yammdb
The IP address that I am using seems to be shown as located in CZ. However, the address best might be located here where I am using it, visiting, in Sonora, Mexico.
Probably I made some mistakes! Is everything reported as EU/CZ because I need to add additional, basic steps? Can someone please help me understand why my geolocation result seems possibly incorrect?
Because you didn't changed the IP in the script.
You probably want to replace the line 1.1.1.1 with
response = reader.city(sys.argv[1])which takes your argument.
Need to import sys though.
Free NAT KVM | Free NAT LXC
Thanks so much! I will make that change and post the result.
If you wish, here is another question:
What mistake am I making here? Have I wrongly identified the file whose checksum should match? Thanks!
The checksum wasn't updated since the last build, probably a issue in my build script.
Free NAT KVM | Free NAT LXC
Thanks!
Making the change that @Neoon suggested:
Looks like we need to import the sys module.
According to findlatitudeandlongitude.com the reported latitude and longitude is in Dallas, TX USA.
The ISP here, as of the last time I checked awhile ago, seemed to use multiple hops with private addresses between my location and 187.189.238.1. Based on ping times and other factors, I previously imagined that 187.189.238.1 might be located in Missouri. Maybe it was in Dallas, or it is in Dallas now.
Vendors seem universally to identify 187.189.238.1 as a Mexican IP. I can pretty much count on being offered default pages in Spanish and default prices in pesos.
Thanks @Neoon!
Yes, seems like the DB i am using also identifies your IP as mexico: https://ip2c.ziox.us/?ip=187.189.238.1
The source code is located here: https://github.com/somik123/IP-to-Country
I am currently using the "lite" database from ip2location.com
I don't have a probe in Mexico, the closest is Texas, so its as close as it can get.
Free NAT KVM | Free NAT LXC
how do you calculate the positions? i assumed you are triangulating different "nearby" probes? eg in this case the results of Texas and Sao Paulo.