Since these are link-local IPv6 addresses, they were created by the machine itself and not assigned by an ISP, so they contain no information about machine location.
Came here to say the same thing about link local. Might also be worth mentioning how ISP's generally assign subnets for v6, not addresses, though not entirely relevant here.
I have a /56 and /64 assigned to me I've been learning how to use for my own stuff ;p
Thanks for trying your best to break this down truthfully to people here. When I first saw OP try to convert IPv6 to IPv4 I was like "wtf?" because.. that's not how that works, lol. It's like trying to take somebody's name and convert the letters into numbers and then try to say that equals their GPS coordinates or some shit, haha.
But thinking of this further, though, the use of a local address simply suggests to me that the webserver is being accessed by some other local process on the device. Could be a service or something else, but, probably just interacting with that other component on the system by way of the webhost. Just because something runs a webserver doesn't automatically mean it's being accessed externally.
Thanks for the explanation.
So what would be the proper way to determine a rough location?
Since these are link-local IPv6 addresses, they were created by the machine itself and not assigned by an ISP, so they contain no information about machine location.
Came here to say the same thing about link local. Might also be worth mentioning how ISP's generally assign subnets for v6, not addresses, though not entirely relevant here. I have a /56 and /64 assigned to me I've been learning how to use for my own stuff ;p
Thanks for trying your best to break this down truthfully to people here. When I first saw OP try to convert IPv6 to IPv4 I was like "wtf?" because.. that's not how that works, lol. It's like trying to take somebody's name and convert the letters into numbers and then try to say that equals their GPS coordinates or some shit, haha.
But thinking of this further, though, the use of a local address simply suggests to me that the webserver is being accessed by some other local process on the device. Could be a service or something else, but, probably just interacting with that other component on the system by way of the webhost. Just because something runs a webserver doesn't automatically mean it's being accessed externally.