26 Sep
2019
26 Sep
'19
11:32 a.m.
Hi all,
We are migrating our TKNet network to AMPRNet addressing. For machines
directly connected to Internet (ie : XLX, DMR), we are using
44.190.11.0/24 range. Those addresses are geo-located in Chicago. This
has funny consequences. F/ex, when doing speed tests with online
services such as nperf.com, the automatically-selected "nearest" server
is very far from here :-)
I have absolutely no idea about how geolocation works. Just for
curiosity, where is this information taken from ? The Whois database ?
But Brian's address is in San Diego, not in Chicago...
Is there an easy way to change geo-location information for a specific
AMPR subnet ?
Thank you in advance. 73 de TK1BI
26 Sep
26 Sep
4:06 p.m.
On 26. Sep 2019, at 12:32, Toussaint OTTAVI via 44Net
<44net(a)mailman.ampr.org> wrote:
Just for curiosity, where is this information taken from ? The Whois database ? But
Brian's address is in San Diego, not in Chicago...
Is there an easy way to change geo-location information for a specific AMPR subnet ?
There is no one true source. Thats one of the reasons the information is not terribly
accurate.
One of the big providers of geolocation data however is MaxMind - probably partially
because you can get much of the info for free. You can lookup IPs on their website and
submit corrections (though I think there is some verification required so I don’t know if
they accept all updates).
Other people have their own databases though so even if MaxMind update theirs it’s no
guarantee a particular service will notice.
HTH
Andrew DL1UGH
5:02 p.m.
Le 26/09/2019 à 17:06, Andrew Stevenson a écrit :
One of the big providers of geolocation data however
is MaxMind - probably partially because you can get much of the info for free. You can
lookup IPs on their website and submit corrections (though I think there is some
verification required so I don’t know if they accept all updates).
Hi Andy,
Thank you for the info. I submitted a correction request to Maxmind,
giving this link as justification :
https://portal.ampr.org/networks.php?a=region&id=3302
Now, let's see what happens...
As you said, there seems to be several different databases. This one,
for example, geo-locates our addresses more accurately in Paris (which
is the place where our BGP announcement is made)
https://www.ultratools.com/tools/geoIp
73 de TK1BI
5:08 p.m.
Le 26/09/2019 à 18:02, Toussaint OTTAVI a écrit :
This one, for example, geo-locates our addresses more
accurately in
Paris (which is the place where our BGP announcement is made)
... and this one geo-locates us in Buskerud, Norway :
https://ipgeolocation.io/
With TCP/IP over meteor scatter, this may be doable, HI :-)
73 de TK1BI
5:21 p.m.
Le 26/09/2019 à 18:02, Toussaint OTTAVI a écrit :
> This one, for example, geo-locates our addresses
more accurately in
> Paris (which is the place where our BGP announcement is made)
This one is a little bit more interesting and complete. It returns data
from 3 different GeoIP databases. One locates us in France, another one
in the US, and the third in Norway.
https://www.iplocation.net/
None of them seem to provide a correction request form, anyway...
73 de TK1BI
10:17 p.m.
We are in the same boat as our isp will not do bgp over vdsl although its stable except
when the fibre caboney gets smashed by under age drivers lol
tried the updates dodnt work. As i use our bgp in cairns, melbourne and sydney we are at
the luck of the dice to a correct value
Samantha
VK4AA
On Fri, Sep 27, 2019 at 6:56 AM +1000, "Toussaint OTTAVI via 44Net"
<44net(a)mailman.ampr.org> wrote:
Le 26/09/2019 à 17:06, Andrew Stevenson a écrit :
One of the big providers of geolocation data however
is MaxMind - probably partially because you can get much of the info for free. You can
lookup IPs on their website and submit corrections (though I think there is some
verification required so I don’t know if they accept all updates).
Hi Andy,
Thank you for the info. I submitted a correction request to Maxmind,
giving this link as justification :
https://portal.ampr.org/networks.php?a=region&id=3302
Now, let's see what happens...
As you said, there seems to be several different databases. This one,
for example, geo-locates our addresses more accurately in Paris (which
is the place where our BGP announcement is made)
https://www.ultratools.com/tools/geoIp
73 de TK1BI
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
5:37 p.m.
On Thu, 26 Sep 2019, Toussaint OTTAVI via 44Net wrote:
We are migrating our TKNet network to AMPRNet
addressing. For machines
directly connected to Internet (ie : XLX, DMR), we are using
44.190.11.0/24 range. Those addresses are geo-located in Chicago.
If you have delegated reverse DNS, one could publish DNS LOC records:
1.11.190.44.in-addr.arpa. IN LOC 42 N 42 W
see, for optional precision/elevation parameters:
https://en.wikipedia.org/wiki/LOC_record
https://tools.ietf.org/html/rfc1876
Whether or not the forward/reverse records are consumed by the various
third-party Geo-IP sites remains to be seen, but under the guise of
amateur radio, it might make sense to *experiment*, try, and
report back.
...Perhaps even with a proposal that all networks/IP addresses under
44.0/8.415 MAY or SHOULD provide LOC records. Thus opening things up
to a bit of data analysis---perhaps something CAIDA would be
interested in?
-Paul
27 Sep
27 Sep
9:14 a.m.
Le 26/09/2019 à 18:37, Paul Sladen a écrit :
If you have delegated reverse DNS, one could publish
DNS LOC records:
1.11.190.44.in-addr.arpa. IN LOC 42 N 42 W
Thank you for the info.
I'm planning to deploy internal DNS servers, for direct and reverse
lookups. Then, I'll be able to add LOC records. But as far as public DNS
servers have some security concerns, and I have no experience about
that, DNS server has been delayed to later ;-)
73 de TK1BI
7:47 a.m.
In my experience, some of them use
[maxmind](https://www.maxmind.com/en/home), as the widely used geoip was
built upon a free version from them. You can correct them at their
[site](https://support.maxmind.com/geoip-data-correction-request/).
As for the sites behind Cloudflare, they can get two letter location
code from the CloudFlare. Other CDNs may have their own version.
As for the Google overlord, they have their own GeoIP db, unfortunately
it's next to impossible to change GeoIP for them. Yes, I know they have
a webform where you can submit correction data to them, but for me it
never worked. To update your GeoIP for Google you will need to register
at their [Peering Portal](https://peering.google.com), wait for
approval, and wait another weeks for your update to take effect.
I think the easiest and quickest way is to announce the prefix by
yourself. It looks most GeoIP databases are built from ASN whois and/or
country lists on RIRs.
- Quan
On 9/26/19 6:32 PM, Toussaint OTTAVI via 44Net wrote:
Hi all,
We are migrating our TKNet network to AMPRNet addressing. For machines
directly connected to Internet (ie : XLX, DMR), we are using
44.190.11.0/24 range. Those addresses are geo-located in Chicago. This
has funny consequences. F/ex, when doing speed tests with online
services such as nperf.com, the automatically-selected "nearest"
server is very far from here :-)
I have absolutely no idea about how geolocation works. Just for
curiosity, where is this information taken from ? The Whois database ?
But Brian's address is in San Diego, not in Chicago...
Is there an easy way to change geo-location information for a specific
AMPR subnet ?
Thank you in advance. 73 de TK1BI
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
9:27 a.m.
Le 27/09/2019 à 08:47, Quan Zhou a écrit :
I think the easiest and quickest way is to announce
the prefix by
yourself. It looks most GeoIP databases are built from ASN whois and/or
country lists on RIRs.
Currently, I'm announcing 44.190.11.0/24 by myself via a Vultr VPS
located in Paris. It's interesting to see I have several kinds of
geolocation results :
- In San Diego, California (not too bad, this is the WHOIS address of Brian)
- In Chicago (which seems to be the headquarters of Choopa, the company
who owns my VPS provider Vultr)
- In Paris (the most clever one, which probably recognised that my BGP
announcements are made from a data center in Paris)
- In Norway (this one just shows how inaccurate and unreliable GeoIP can
be, HI )
73 de TK1BI
1:46 p.m.
On Sep 27, 2019, at 04:27, Toussaint OTTAVI via 44Net
<44net(a)mailman.ampr.org> wrote:
Currently, I'm announcing 44.190.11.0/24 by myself via a Vultr VPS located in Paris.
It's interesting to see I have several kinds of geolocation results :
- In San Diego, California (not too bad, this is the WHOIS address of Brian)
- In Chicago (which seems to be the headquarters of Choopa, the company who owns my VPS
provider Vultr)
Actually, Vultr.com (Choopa) offices are in Matawan, NJ, near New York City. But it
doesn’t really matter. They seem to do an outstanding job regardless of the data center
chosen.
-k9dc
1683
days inactive
1684
days old
10 comments
6 participants
participants (6)
-
Andrew Stevenson -
Dave Gingrich -
Paul Sladen -
Quan Zhou -
Toussaint OTTAVI -
vk4aa