It looks like we have geopip issues on relays.syncthing.net . The reported locations lack essential information, like city or location. As expected with the transition of the free to paid geo ip location service.
When using the “free” GeoLite2-City.mmdb as mentioned in cmd/strelaypoolsrv/main.go IP’s do not resolve anymore to cities/locations.
If I feed it a paid version GeoIP2-City.mmdb it works fine.
sigh… this is sad… so sad… my little lonesome geotag in Berlin now shows up in Kassel… Kassel… that’s almost Bielefeld… (germans will understand. There is no “Bielefeld”)
Maybe someone has a good idea to what kind of geoip service syncthing should move in the future ?
Syncthing does not use geoip when picking a relay, it picks latency.
If you run your relay in Berlin, and my device A is in Berlin, it’s likely I’ll pick your relay. Regardless the fact that my device B is in Japan, if I want to talk to A from B, and there is no direct connection, I will end up connecting to your relay to talk to A from Japan.
If I take for example two IP adresses on my strelaysrv interface, both with geoiplocation in CN, both in a class C network and both using almost the same bandwidth. The only difference is: One is incoming traffic and the other is outgoing traffic.
I’ll check what geoip2-golang is used for today but it definitly is used:
