You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For geolocating caches and clients, we currently rely on IP addresses and use a combination of the MaxMind database and manually maintained list of overrides. Handling unlocated clients is an ongoing manual effort, and will likely continue as IPv6 usage increases. How can we improve the process? Some ideas from initial discussion:
Storing GeoIPs in Registry, instead of every Director (for multi-directors) since it’s sort of stateful
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
For geolocating caches and clients, we currently rely on IP addresses and use a combination of the MaxMind database and manually maintained list of overrides. Handling unlocated clients is an ongoing manual effort, and will likely continue as IPv6 usage increases. How can we improve the process? Some ideas from initial discussion:
GLIDEIN_Resource_Name) to Director to assist in geolocationSee also BrianB's comments on improving the algorithm for using GeoIP data: https://github.com/orgs/PelicanPlatform/discussions/1198
Beta Was this translation helpful? Give feedback.
All reactions