IIRC, in Google Chrome you can set your geolocation to something you specify manually, this is not the case?
I’m using firefox not chrome.
This computer location is set to Canada. So are the clients that need to connect to the CCR1009 as I have asked them.
Thanks.
Check the geolocation settings in Firefox. Settings → Privacy and Security → Permissions → Position → Settings (the names may not be precise, my Firefox language is not English).
I don’t think the issue is directly with the VPN, and once you’ve described how you test it, I don’t think any more it’s an issue with leakage via DNS, I second @CZFan in assuming it’s the browser sending the geolocation info.
As suggested earlier, try to assign addresses from a private pool to the CCR users and do a src-nat/masquerade to some public IP you’ve never assigned to any VPN user so far (or maybe just do the src-nat/masquerade without changing the pool).
Given that you assign public IPs to the VPN clients, I could also imagine some routing shortcut if there is a LAN connection between the test PC and the CCR, but I don’t know your test network topology. If you connect the test PC to the internet e.g. using a mobile connection while it is disconnected from the wired LAN, the routing shortcut is definitely not the reason.
Tried your suggestion of settings => privacy => Permissions => Location to block new requests for location. Cleared cache, closed and then reopened firefox. Open google.com and it shows the location of the computer. Location permissions is not the issue.
Disconnected from CCR VPN, cleared cache in firefox then connected to the hEX S VPN. Open google.com and it sees my computer in Canada.
Thanks.
Hi there,
It’s intriguing that you’re seeing varied geolocation results on your MikroTik routers’ L2TP/IPsec VPNs. The discrepancy might stem from how the geolocation service interprets the IP addresses assigned by each router’s VPN.
The settings you mentioned, UPnP and fast path, usually don’t influence geolocation in this way. Geolocation hinges on the public IP address, which could differ between your routers.
To address this, consider:
IP Address Ranges: Check VPN-assigned IP ranges for each router. Differences could impact geolocation.
Routing and NAT: Ensure routing and NAT settings match, as these affect how traffic is seen.
Public IP: Verify the CCR1009 router’s IP isn’t inaccurately tagged in my location databases.
VPN Setup: Align L2TP/IPsec settings on both routers for consistent configuration.
Browser Factors: Remember browser settings and privacy extensions might affect geolocation.