<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Troubleshooting tips for vDash DOE connection]]></title><description><![CDATA[<p dir="auto">Spent a few evenings troubleshooting why vDash couldn't recognise my connection to a 2021 Polestar2. Initially suspected the cheap DOE cable but dug in and ended up getting trace from Wireshark.<br />
Side question, why does Wireshark and vDash running together just crash. This was a little tedious.</p>
<p dir="auto">In the end I ruled out the cable and figured that my Tailscale (VPN tunnel) service was swallowing all the DoIP packets.</p>
<p dir="auto">So the lesson to share is as follows. If you're trying to connect via DOE then do first check you don't have odd VPN stuff going on at all.<br />
The specific tell that gave it away was<br />
'Get-NetRoute -DestinationPrefix "169.254.0.0/16"' from an admin powershell. In error mode this returned multiple entries. Once I'd disabled tailscale it only returned one.</p>
<p dir="auto">Hope this helps someone save a bit of debugging time.</p>
]]></description><link>https://forum.d5t5.com/topic/401/troubleshooting-tips-for-vdash-doe-connection</link><generator>RSS for Node</generator><lastBuildDate>Wed, 12 Aug 2026 23:38:28 GMT</lastBuildDate><atom:link href="https://forum.d5t5.com/topic/401.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 12 Aug 2026 19:40:30 GMT</pubDate><ttl>60</ttl></channel></rss>