Hi, It is located in Tokyo, Japan. https://ipleak.net/?q=198.13.48.219 -------- Mensagem original -------- Em 18/01/2024 14:48, noury <noury@noury.ee> escreveu:

Hey,

For what it's worth ipinfo.io says it's in Ōi, Saitama, Japan.

https://ipinfo.io/198.13.48.219

On 18.01.24 18:22, Jag Talon wrote:

...

Hello,

I have a relay in Japan with the IP of 198.13.48.219, but it's being marked as being in the US. I've tried using different websites like www.iplocation.net, iplocation.io, and www.wolframalpha.com and they're all telling me that the IP is in Japan.

I'm wondering if perhaps there's an issue with the GeoIP lookup? Or perhaps an outdated database?

Thanks!

_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

The reality is that there's multiple IP databases, and each operates differently. 198.0.0.0/8 is an ARIN IP allocation, and even though the server's in Japan, the IP addresses are allocated to a US company, in this case Choopa/Vultr. This is why some databases show the IP in the USA: they might look at the first allocation after the RIR, which says "USA". When I ran Tor exit relays on leased IP space, some abuse reports went directly to me, but some went to the IP lessors, not realizing IP leasing and reallocations are now commonplace. -Neel On Thu, Jan 18 2024 at 12:50:22 PM -0600, NodNet <tor@nodnetwork.org> wrote:

I think tor and Tor Project use IPFire's DB for GeoIP lookups, and 198.13.48.219 shows the following:

NETWORK: 198.13.48.0/20 AUTONOMOUS SYSTEM: AS20473 - AS-CHOOPA COUNTRY: United States of America

https://www.ipfire.org/projects/location/lookup/198.13.48.219

On 1/18/2024 11:22 AM, Jag Talon wrote:

...

Hello,

I have a relay in Japan with the IP of 198.13.48.219, but it's being marked as being in the US. I've tried using different websites like www.iplocation.net, iplocation.io, and www.wolframalpha.com and they're all telling me that the IP is in Japan.

I'm wondering if perhaps there's an issue with the GeoIP lookup? Or perhaps an outdated database?

Thanks!

_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

---

tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Hello, unfortunately this happens more often. you are not alone :-)

Am 18.01.2024 um 20:50 schrieb NodNet <tor@nodnetwork.org>:

I think tor and Tor Project use IPFire's DB for GeoIP lookups, and 198.13.48.219 shows the following:

Yes, libloc/location is used. I had the same problem with one or two relays years ago. This was then fixed by a manual override. This is currently also the case with 3 of my relays (37.252.255.135 / 37.252.254.33 / 217.146.2.41) However, I can't explain why. Because the hoster has a geofeed (https://opengeofeed.org/feed/as42473.html) and RIPE also has the correct country information. In any case, it is not so important to me that it is correct in the metrics. But it would be nice. Maybe I'll get round to mentioning it again on the location mailing list soon. Ahoy, Martin

Oh excellent thank you for pointing me to the right place! I'll make sure to create an issue there. On 1/18/24 17:11, trinity pointard wrote:

Hi everyone,

If tor's geoip db (which indeed is IPFire) has the wrong country for your IP, and you want it fixed, the correct place to fill an issue is on IPFire's bugzilla. You can see an instance of a previous report here https://bugzilla.ipfire.org/show_bug.cgi?id=13037 . It's not very important for the purpose of tor, but you'd be making one of the only embedable geoip database a little more accurate for everyone else 😃

Regards,

trinity-1686a

On Thu, 18 Jan 2024 at 22:08, Martin Gebhardt via tor-relays <tor-relays@lists.torproject.org> wrote:

...

Hello,

unfortunately this happens more often. you are not alone :-)

...

Am 18.01.2024 um 20:50 schrieb NodNet <tor@nodnetwork.org>:

I think tor and Tor Project use IPFire's DB for GeoIP lookups, and 198.13.48.219 shows the following: Yes, libloc/location is used. I had the same problem with one or two relays years ago. This was then fixed by a manual override.

This is currently also the case with 3 of my relays (37.252.255.135 / 37.252.254.33 / 217.146.2.41)

However, I can't explain why. Because the hoster has a geofeed (https://opengeofeed.org/feed/as42473.html) and RIPE also has the correct country information.

In any case, it is not so important to me that it is correct in the metrics. But it would be nice.

Maybe I'll get round to mentioning it again on the location mailing list soon.

Ahoy, Martin

_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

---

tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

-- Jag Talon Designer for the Tor Project

On Donnerstag, 18. Januar 2024 23:52:00 CET Jag Talon wrote:

Bug has been filed here for anyone following the thread: https://bugzilla.ipfire.org/show_bug.cgi?id=13541

It's best to ask the provider for their geofeed and mention it in the bug report. Then all subnets in this AS will be corrected. https://bugzilla.ipfire.org/show_bug.cgi?id=12774​ -- ╰_╯ Ciao Marco! Debian GNU/Linux It's free software and it gives you freedom!