Welcome to Tesla Motors Club
Discuss Tesla's Model S, Model 3, Model X, Model Y, Cybertruck, Roadster and More.
Register

Does the Tesla browser use a VPNor proxy to get to the net?

This site may earn commission on affiliate links.

wayner

Active Member
Oct 29, 2014
4,299
1,792
Toronto
I live in Toronto but when I access the Google News page on the browser on my Tesla it shows me local news for Houston. That makes me think that my Tesla is using a VPN or something that gives it a Houston based IP address or an address tied to a Houston based company. Does anyone know exactly how the Tesla browse gets to the internet? Does it use some proxy or VPN to go through Tesla's servers first? Does this differ if you are on 3G vs wifi?

This appears to have the effect of my Nav system giving me voice directions in miles rather than km, despite the fact that I have my car set to use metric and the speedo shows km/h and range is shown in km. It seems that the Google Nav bases the units on what country you are in.

How do I change this? Do I log into Google with my Google ID? Will that even work for determining my location since people do travel.
 
As of a couple of firmware updates ago, GPS positioning was available for web pages requesting it (altho I seem to recall having to allow it via a permission request). Perhaps Google is picking that up?
 
But Google news isn't - it thinks I am in Houston. So I am assuming that all Google services are using the same geolocation method, except that the Nav/GPS know exactly where I am. But for some reason it is using non-metric units.
 
Sounds like you are suffering the same problem as UK owners. The browser in all our cars thinks it is in Spain.

In our case it's because Tesla have done a pan-Europe deal with Telefonica for 3G service and the SIM cards are obviously registered somewhere so that they get allocated IP addresses that geolocate to Spain.

It's hugely annoying - for example lots of region-locked internet radio streams (like all the BBC services) can't be accessed over 3G.
 
Absent GPS information, Google also attempts to use your IP address/routing to determine location by looking at the location of the ISP to which your IP belongs. Could be some weirdness with your cellular provider up there or with Google itself. Note that both SF and Houston are major Tier 1 hubs for internet traffic, so it's likely your traffic is going through one or both on the way from Toronto. It may be mistaking one of those hubs as your location somehow.
 
I was told that this location may also be linked to why the Nav system is giving me voice commands referencing US units (miles, feet) rather than metric units. And this is despite the fact that I have my Units set to metric and everything else on the car displays in metric units.
 
Cellular connections in general have horrible IP-based geolocation. I've seen my phone on AT&T connect from IP addresses in places a thousand or two miles away. IP addresses kind of assume a fixed location, so cellular internet has to play some fun games that mean it's likely there will be some indirection there. The Tesla's 3G connection is surely no different.
 
From what I have read the Canadian Teslas are still tied to AT&T but they are roaming on Rogers' network while in Canada and Tesla has a deal with Rogers to cover the "roaming" fees. I have a Rogers LTE wifi hotspot. I will try using this today and see if things work any differently in terms of either geolocation or units used in voice commands.

So my premise that the networking is done via a VPN back to Tesla, and then out to the internet is incorrect? With my corporate VPN it can work in two ways when you try to access internet services - either it can send all traffic over the VPN and then you hit the internet from the "mother ship". This always makes it appear that I am in Toronto. Or the VPN only sends corporate traffic over the VPN and all other internet traffic hits the internet locally. The former method is slower than the latter but it allows you to access sites that may be blocked locally, like Facebook, Twitter, Google, etc while in China.
 
Cellular connections in general have horrible IP-based geolocation. I've seen my phone on AT&T connect from IP addresses in places a thousand or two miles away. IP addresses kind of assume a fixed location, so cellular internet has to play some fun games that mean it's likely there will be some indirection there. The Tesla's 3G connection is surely no different.

All UK cars get their IP addresses from the same block - it just happens to be assigned to Telefonica in Spain. In this circumstance, there really is no justification for not providing the cars with an IP block that can be marked as at least being within 1000 miles of where we are!

The 3G SIM in my laptop has a static IP address (so it also always thinks it's in exactly the same location) but that's another story...
 
With a 3G connection What's My IP returns a Tennesee address with Jasper technologies as my ISP. When I switch to my wifi hotspot it correctly returns Rogers in the Toronto area. Google News give me the correct local news but the voice commands are still in miles.
 
Last edited:
Most GeoIP services have a terrible time with the IP address we use at work. I'm on the same ISP at home but with a dynamic IP address which they do better, but far from perfect.

- - - Updated - - -

As of a couple of firmware updates ago, GPS positioning was available for web pages requesting it (altho I seem to recall having to allow it via a permission request). Perhaps Google is picking that up?

Really? Am going to have to try GasBuddy.com just for laughs! Drive around in an EV using its built-in browser to report gas prices! :smile:
 
All UK cars get their IP addresses from the same block - it just happens to be assigned to Telefonica in Spain. In this circumstance, there really is no justification for not providing the cars with an IP block that can be marked as at least being within 1000 miles of where we are!

The 3G SIM in my laptop has a static IP address (so it also always thinks it's in exactly the same location) but that's another story...


Hi, did this issue get fixed in the UK at all?