Well there's nothing like realizing that you may run into issues until you're already deep into a plan. My company currently has colocation at a datacenter we'll call DC-Colo in city A. Internet is delivered into our cabinet via a connection from the colocation facility, we'll call this subnet 192.168.0.0/24. We have a wavelength circuit from our cabinet at DC-Colo in city A to our headquarters in city B. Headquarters is using a public IP to NAT/PAT from the corporate network, we'll call this public NAT IP 192.168.1.2. When I browse around on the Internet from headquarters, I see city B listed on websites that find location by IP such as https://whatismyipaddress.com/ even though the connection is going over the wavelength back into our cabinet at city A. We are working to get another wavelength circuit delivered from DC-Colo to our branch office in City C. This branch office will NAT using another public IP, 192.168.1.3. Is geo-location going to be tied to our entire /24 public block and bounce around between city B and C based on the websites we visit or is it going to tie the location based on individual public IP so city B geo-location is tied to 192.168.1.2 and city C geo-location is tied to 192.168.1.3 (since each respective sites visits from these NAT addresses)? Is this even an issue that I should be worrying about? Basically, I'm looking for someone to school me on how IP geo-location works on a more granular level (does it go by provider address block delegation out of their ASN, by individual IPs, etc)?
No comments:
Post a Comment