For all of you other network geeks, I'd like to know if you've seen this odd behavior. Tonight, I noticed that the car no longer had connectivity through Tesla's VPN tunnel while on Wi-Fi. It had Slacker, the web browser worked, etc., but the remote app couldn't "see" the car and all my API calls returned "car unavailable".
I logged into the management portal for my AP's (Meraki), did a packet capture, and saw the following:
Every 5 seconds, the car was querying my nameserver (BIND9). This continued for well over 15 minutes. There were no errors on the nameserver, just query after query after query. I didn't see a problem with the query or response, it just seemed that the car was ignoring them and retrying again.
I fixed it by turning off Wi-Fi in the car, stopping my nameserver, and turning Wi-Fi back on. The car then tries to send nameserver requests for a while, gets frustrated, and gives up. I then restarted the nameserver and then the car did a query and reconnected its tunnel.
(One other behavior - it appears the car cannot use a secondary nameserver. When I took my primary nameserver down, it just kept sending queries despite getting back port unreachable messages. It never tried to contact the backup nameserver.)
Has anyone else seen this behavior?
I logged into the management portal for my AP's (Meraki), did a packet capture, and saw the following:
Code:
16:56:06.152567 IP y.y.y.y.53 > x.x.x.x.15413: 56407| 26/0/0 CNAME usvpn.vn.teslamotors.com., A 209.11.133.38, A 209.10.208.44, A 209.10.208.49, A 209.11.133.30, A 209.11.133.29, A 209.10.208.51, A 209.11.133.23, A 209.11.133.40, A 205.234.27.254, A 209.10.208.75, A 209.11.133.12, A 209.11.133.22, A 209.11.133.27, A 209.10.208.43, A 209.11.133.39, A 209.10.208.48, A 209.10.208.42, A 209.10.208.47, A 205.234.27.198, A 205.234.27.234, A 209.10.208.50, A 209.10.208.45, A 209.11.133.24, A 209.11.133.28, A 209.10.208.46 (488)
16:56:06.068971 IP y.y.y.y.53 > x.x.x.x.15413: 56407| 26/0/0 CNAME usvpn.vn.teslamotors.com., A 209.11.133.38, A 209.10.208.44, A 209.10.208.49, A 209.11.133.30, A 209.11.133.29, A 209.10.208.51, A 209.11.133.23, A 209.11.133.40, A 205.234.27.254, A 209.10.208.75, A 209.11.133.12, A 209.11.133.22, A 209.11.133.27, A 209.10.208.43, A 209.11.133.39, A 209.10.208.48, A 209.10.208.42, A 209.10.208.47, A 205.234.27.198, A 205.234.27.234, A 209.10.208.50, A 209.10.208.45, A 209.11.133.24, A 209.11.133.28, A 209.10.208.46 (488)
16:56:11.085548 IP y.y.y.y.53 > x.x.x.x.47240: 31174| 26/0/0 CNAME usvpn.vn.teslamotors.com., A 209.11.133.30, A 209.10.208.51, A 209.10.208.43, A 209.10.208.47, A 209.11.133.38, A 205.234.27.234, A 209.11.133.22, A 209.11.133.28, A 209.11.133.24, A 209.11.133.27, A 205.234.27.254, A 209.11.133.23, A 209.10.208.50, A 209.10.208.48, A 209.11.133.40, A 209.11.133.39, A 205.234.27.198, A 209.10.208.44, A 209.10.208.45, A 209.11.133.12, A 209.10.208.46, A 209.11.133.29, A 209.10.208.42, A 209.10.208.75, A 209.10.208.49 (488)
16:56:11.100927 IP y.y.y.y.53 > x.x.x.x.57265: 50032| 26/0/0 CNAME usvpn.vn.teslamotors.com., A 209.10.208.75, A 209.11.133.29, A 209.10.208.45, A 209.10.208.49, A 209.11.133.23, A 205.234.27.254, A 209.10.208.51, A 209.10.208.43, A 209.11.133.38, A 209.10.208.47, A 209.11.133.28, A 209.11.133.40, A 209.10.208.48, A 205.234.27.198, A 209.11.133.12, A 209.11.133.27, A 209.11.133.24, A 209.11.133.22, A 209.10.208.42, A 209.10.208.44, A 209.11.133.30, A 209.11.133.39, A 205.234.27.234, A 209.10.208.50, A 209.10.208.46 (488)
16:56:16.114600 IP y.y.y.y.53 > x.x.x.x.32164: 47423| 26/0/0 CNAME usvpn.vn.teslamotors.com., A 209.11.133.22, A 209.11.133.30, A 209.10.208.43, A 209.10.208.50, A 209.11.133.23, A 209.11.133.24, A 209.11.133.12, A 205.234.27.234, A 209.10.208.75, A 205.234.27.254, A 209.11.133.40, A 209.10.208.51, A 209.10.208.42, A 209.10.208.46, A 209.11.133.38, A 205.234.27.198, A 209.11.133.27, A 209.10.208.48, A 209.10.208.44, A 209.10.208.49, A 209.10.208.45, A 209.11.133.39, A 209.10.208.47, A 209.11.133.28, A 209.11.133.29 (488)
16:56:16.125739 IP y.y.y.y.53 > x.x.x.x.34201: 43294| 26/0/0 CNAME usvpn.vn.teslamotors.com., A 209.11.133.29, A 209.10.208.45, A 205.234.27.234, A 209.10.208.44, A 209.11.133.24, A 209.10.208.43, A 205.234.27.254, A 209.10.208.50, A 209.10.208.47, A 209.11.133.22, A 209.10.208.42, A 205.234.27.198, A 209.11.133.30, A 209.11.133.39, A 209.10.208.49, A 209.10.208.51, A 209.10.208.46, A 209.11.133.40, A 209.10.208.75, A 209.11.133.38, A 209.11.133.28, A 209.11.133.12, A 209.10.208.48, A 209.11.133.23, A 209.11.133.27 (488)
Every 5 seconds, the car was querying my nameserver (BIND9). This continued for well over 15 minutes. There were no errors on the nameserver, just query after query after query. I didn't see a problem with the query or response, it just seemed that the car was ignoring them and retrying again.
I fixed it by turning off Wi-Fi in the car, stopping my nameserver, and turning Wi-Fi back on. The car then tries to send nameserver requests for a while, gets frustrated, and gives up. I then restarted the nameserver and then the car did a query and reconnected its tunnel.
(One other behavior - it appears the car cannot use a secondary nameserver. When I took my primary nameserver down, it just kept sending queries despite getting back port unreachable messages. It never tried to contact the backup nameserver.)
Has anyone else seen this behavior?