truck
Well-known member
- Joined
- Sep 23, 2023
- Threads
- 26
- Messages
- 194
- Reaction score
- 272
- Location
- Texas
- Vehicles
- Tesla Model X 2017 100D LR/S 2015 P85D/Cyberbeast
- Thread starter
- #1
Anyone been able to figure this out yet? I have an obdii to rj45 cable but can't figure out how to connect it to savvycan. I'm able to use it with wireshark but there's no CAN data coming through, only random TCP/UDP data (although it does reveal some internal IPs, so far they all match up with previous models). Sadly the cybertruck service manual has absolutely zero info on anything. Unlike all the other manuals which have plenty of info. I'm assuming that the cybertruck has the same configuration as the new models where everything is done through the OBD port over DoIP. Gonna try to order a OBD to USB and bluetooth to see if it'll make configuration a little bit easier.
Edit 9/6/24 8:15 PM CST:
Current findings:
Some actions like turn signal, enabling/disabling offroad mode, and pulling up/disabling cameras pop up, they stick out like a sore thumb as opposed to all the other logs. I don't know how IGMP works and I don't know why the requests are doubled. Hex also looks identical throughout all the different actions (might be encrypted ?‍
) I sadly don't know how to replay requests in wireshark. Feel free to PM if you want the pcap file. Will try logging a normal drive tomorrow to see if anything special pops up. I am an amateur at car hacking so please bear with me if anything seems obvious/wrong!
Edit 9/6/24 9:30 PM CST:
Turns out that the IGMP request is sent whenever the car is trying to access the cameras. Started up nmap and found some interesting things.
192.168.90.100 has ports 22,8001,8080,8081 open
You can (try) to ssh into the car at 192.168.90.100:22, problem is you'll be denied due to "publickey". I don't know what the bottom two things are in the authorized principals so I censored it, top two are the exact same VINs of the car. If it says remote ssh is not allowed due to it being a "customer vehicle" go to controls -> service -> scroll down to the switch that says "allow remote debugging".
Port 8001 has nothing useful, can't figure out anything to do with it. Port 8080 just results in a page that says "404: Not Found". Port 8081 is interesting, you must specify to visit the site using https, if you don't it returns "Client sent an HTTP request to an HTTPS server." When you do connect with https, it asks for a certificate.
In the wireshark logs, there’s a whole bunch of 5 digit ports that 192.168.90.100 is sending requests from.
In my wireshark logs, there are two IPs that show up which claim they have no open ports even though they communicate with 192.168.90.100 with various ports. These two ips are 192.168.90.30 and 192.168.90.107.
Edit 9/6/24 8:15 PM CST:
Current findings:
Some actions like turn signal, enabling/disabling offroad mode, and pulling up/disabling cameras pop up, they stick out like a sore thumb as opposed to all the other logs. I don't know how IGMP works and I don't know why the requests are doubled. Hex also looks identical throughout all the different actions (might be encrypted ?‍
) I sadly don't know how to replay requests in wireshark. Feel free to PM if you want the pcap file. Will try logging a normal drive tomorrow to see if anything special pops up. I am an amateur at car hacking so please bear with me if anything seems obvious/wrong!
Edit 9/6/24 9:30 PM CST:
Turns out that the IGMP request is sent whenever the car is trying to access the cameras. Started up nmap and found some interesting things.
192.168.90.100 has ports 22,8001,8080,8081 open
You can (try) to ssh into the car at 192.168.90.100:22, problem is you'll be denied due to "publickey". I don't know what the bottom two things are in the authorized principals so I censored it, top two are the exact same VINs of the car. If it says remote ssh is not allowed due to it being a "customer vehicle" go to controls -> service -> scroll down to the switch that says "allow remote debugging".
Port 8001 has nothing useful, can't figure out anything to do with it. Port 8080 just results in a page that says "404: Not Found". Port 8081 is interesting, you must specify to visit the site using https, if you don't it returns "Client sent an HTTP request to an HTTPS server." When you do connect with https, it asks for a certificate.
In the wireshark logs, there’s a whole bunch of 5 digit ports that 192.168.90.100 is sending requests from.
In my wireshark logs, there are two IPs that show up which claim they have no open ports even though they communicate with 192.168.90.100 with various ports. These two ips are 192.168.90.30 and 192.168.90.107.
Sponsored
Last edited:
