| Parameter | TESLA-Home-Network-two-weeks-20240101 |
|---|---|
| collection start date | 2023-01-01 00:00:00 |
| collection end date | 2023-01-15 23:59:59 |
| commercial use allowed | No |
| product review required | Yes |
| ongoing measurement | No |
| retrieval instructions | download |
| file type | pcap |
| download size | 3.6GB |
| usage agreement | dua-wes-20240420 |
| IRB approval required | No |
This dataset contains PCAP files collected from:
This data was collected over two weeks from a Tesla model Y and Wall Charger when they were in range of a home wifi network.
PCAPs were collected by using tcpdump filtered by the
ethernet MAC address for the Tesla and the wall charger. Collection was
rotated every two hours by tcpdump.
The PCAP files are in sub-directories and formatted as
There is also a system log file, contained in a
systemd-journal.txt file.
The network the devices connected two consisted of a wireless access point (eero-based) which was connected to a linux router that served as the DHCP server. The linux router provided Network Address Translation (NAT) service to the local network. Upstream from the linux router is a 1Gb AT&T fiber ISP.
Tesla --------> eero wireless -----> linux router -----> AT&T
^
|
Wall Charger ------/
The syslog from system offering DHCP service to the Tesla is
available in the tesla-systemd-journal.txt file. In
particular, the DHCPREQUEST timings are likely an accurate
way of determining exactly when the Tesla arrived when compared against
the manually crated logs in the “Usage activity notes” below.
The tesla-manual-event-record.csv file contains the
following fields that document the manually recorded events during the
two week period:
Event: Description of a note taken
Date: The date of the event
Time: The 24-hour time of the event
Plugged: If the Tesla was plugged as part of the event time
Unplugged: If the Tesla was unplugged as part of the event time
Left: If the Tesla left the house/network
Returned: If the Tesla returned to the network (DHCP logs will have accurate timing)
System Update: A start time of a system update (or end time if noted in the Event field)
Forced Charge: If the Tesla was told to start charging immediately.
Other: Another type of event (see the Event field)
Note: the Tesla was set up to normally start charging at midnight (when plugged in) unless directed to start immediately as the “Forced Charging” column indicates.
The owners of the Tesla agreed to the recording of this data and consent to its release under the terms of condition available on the COMUNDA portal. The only recordings made were external to the Tesla itself through the networks it connected through, and the Tesla owners also owned and controlled the network where the collection infrastructure was deployed.
If you use this trace to conduct additional research, please cite it as:
Tesla home network dataset, 2024. Provided by Wes Hardaker with the PIVOT project https://www.pivot-auto.org/.