CydandClaude Opus 4.8
4a61a9f8c3
Reconfigure timeout (launcher reinstall of an already-configured pod): - The console pings each configured pod and connects on success, on a loop, and never tore that down — so it kept hammering the pod's old IP with a stale connection while SecureConfig tried to bring the pod up on that address, which timed out. Only a console restart (closing all sockets) cleared it. - DeletePod now Disconnect()s the pod's connection (closes the lingering socket) so delete-to-reconfigure works WITHOUT a console restart. - Reconfiguring a known pod in place now pauses that pod's ping/connect loop (OperationInProgress) and drops its stale connection before SecureConfig, and resumes on completion (success or failure) so it reconnects with the new key. (StopPing kills the ping thread irreversibly, so pause via OperationInProgress.) Note: PodInfo's static mPods registry is dead code (nothing registers), so the real fix is the disconnect, not an unregister. Console deployment: - Console/install.bat: installs the console to C:\Program Files\TeslaConsole, preps the %ProgramData%\Tesla Console data dir (Users: modify), creates a Start Menu shortcut, and adds a per-program inbound firewall rule so it can receive pod discovery beacons. net48 is in-box, no runtime install. - Console/build-package.bat: publishes the console (net48 framework-dependent) to dist\TeslaConsole\App and assembles the package with install.bat. 74 tests green; the pod-config fix is UI/network behavior, validate on a pod. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
TeslaSuite
The Tesla cockpit-pod software, in one repository:
| Folder | What it is | Target |
|---|---|---|
Console/ |
TeslaConsole — the operator console (WinForms) that configures and drives the pods. A decompiled reconstruction of the original TeslaConsole.exe (now the modernized 4.11.4.x line), with a differential test suite pinning it to the original 4.11.3.37076 baseline. |
.NET Framework 4.8 |
Launcher/ |
TeslaLauncher — the pod-side Service (Session 0 RPC listener) + Agent (user-session app launcher). A clean rewrite of the original launcher. | .NET Framework 4.8 |
Contract/ |
Tesla.Contract — the shared Console↔Launcher RPC contract: wire types, the client, and the framed-JSON protocol. Emits assembly TeslaConsoleLaunchLib. |
.NET Framework 4.8 |
SecureConfig/ |
Tesla.SecureConfig — the first-boot pod provisioning protocol (UDP beacons, OFB crypto, RSA key exchange). Emits assembly TeslaSecureConfiguration. |
.NET Framework 4.8 |
The console and launcher talk over TCP 53290 using length-prefixed
System.Text.Json frames over an OFB-encrypted stream (Contract/PodRpcProtocol.cs),
dispatched by method name. The wire contract lives in one source project
(Contract/) referenced by both sides — a single source of truth, no
duplication or hand-syncing.
Note: Red Planet game control uses a separate protocol (Munga, TCP 1501) via the vendored
Munga Net.dll— not the RPC channel above. The game itself is C++ and lives in its own repo (gitea.mysticmachines.com/VWE/RP411.git).
Building
dotnet build TeslaSuite.sln -c Release
dotnet test Console/tests/TeslaConsole.DiffTests # differential + protocol + crypto guards
Pod deployment: Launcher/build.bat publishes the
framework-dependent net48 package into Launcher/TeslaLauncher/ (~3.7 MB on disk /
~1.6 MB zipped — no runtime to install, since .NET Framework 4.8 ships in Windows 10/11),
and Launcher/install.bat deploys it on a cockpit PC (registers
the Service, sets up the Agent for auto-login, hardens the box).
Layout notes
Console/original/TeslaConsole.exe— the 4.11.3.37076 reference baseline the differential tests compare against. Keep it.Console/lib/*.dll— the remaining vendored binary dependencies (Munga Net,BitmapLibrary,WeifenLuodocking). The originalTeslaConsoleLaunchLib.dllandTeslaSecureConfiguration.dllare also kept here, but only as byte-compatibility test baselines — both are now built from source (Contract/,SecureConfig/).Console/RedPlanet/Apps.xml— the data-driven product catalog (see the console's Site Management → Add Product / Register Product on Pods).
History
The system was modernized in 2026: the duplicated wire contract was extracted to a single
source project, BinaryFormatter (an RCE sink, and what pinned the launcher to an old
runtime) was replaced with the framed-JSON protocol, and the launcher was rebuilt — briefly
on net8/x64, then settled on net48 to match the console and ship a tiny, runtime-free
package. The whole console↔pod path (provisioning, install, launch) is validated on real
pods.