You can install our site as a web app on your iOS device by utilizing the Add to Home Screen feature in Safari. Please see this thread for more details on this.
Note: This feature may not be available in some browsers.
The car does not "know" where each packet is going.
The car does DNS resolution for the service it's trying to reach, finds an IP address that it's trying to reach and ships the packet out the default gateway for the service provider it has an IP address on.
The car doesn't know jock shot about where the packet actually goes beyond that point.
Your workstation will then create a packet, stamp it with the destination IP address, and forward the packet to the network gateway
You could potentially lock it down at the app/service level so that if an owner has no paid data plan then specific apps/functions are restricted from accessing while leaving other vehicle functions alone. That is doable but not as trivial as you make it sound.
of course it does.
Every packet sent has a destination IP address.
Again- sure it does. The destination IP is in the header of the packet
Surely Tesla knows where its own cloud servers are right? And it knows the addresses of any other servers the car talks to (slacker or whatever else)
So it knows outgoing packet A was diagnostic data going to their server...and it knows incoming packet B was from their OTA update servers.... and it knows packet C was from slacker radio... and so on.
So yes, they absolutely know how much data is being used for each thing. How could they not?
this might help you out-
How Do Packets Get Around? | Understanding Networks and TCP/IP | InformIT
So the car knows where the data is going if it's going out. It doesn't know the whole route, nor does it need to... but it knows the end destination.
Likewise incoming packets have the source address in them.
The car knows where all the data is going, and where it originally came from.
10 year old hasbro-class home routers are capable of doing this with a simple GUI- so yes, it's pretty trivial.
You can even QoS this stuff trivially, which even cheap home routers have also done for many years now... so for example if bandwidth were limited it wouldn't cause the radio stream to stutter because a big OTA update is being pulled down... since, again, it already knows which traffic is which
Likewise if in the future they wanted to charge for data, and you didn't pay, it would could allow OTA updates , and maybe diagnostic and AP data because it benefits Tesla to get it, but would block anything else. That's incredibly trivial to do.
The car knows what IP address it is sending the traffic to.... which is kind of meaningless from a "black that service" perspective.
How do you propose programming the car so that it knows which of the 3.7 billion publicly addressable IP addresses it can or can't send traffic to?
The car has services that run on it and those services refer to their servers with DNS entries. Those DNS entries resolve to public IPs and those IPs change all the time.
Perhaps what you meant to say is that the car could have a white-list of IP addresses or DNS names it is allowed to communicate with and all other IP address is blacklisted? This is still a headache for Tesla... the car communicates with a lot of servers I imagine and this creates a situation in which Tesla has to do some hokey white-list/black-list thing in order to control what communications the car can do
This is precisely why they have not announced any plans. I think it is very difficult for them to differentiate exactly how much data software updates and Road Planning/mapping for EAP and FSD use up in comparison to the small amount used for streaming and google maps.