Actual Vehicle IP
The dashboard displays the real ENET or ICOM address detected at the customer's vehicle, such as 169.254.x.x. Tunnel addressing remains internal.
BMWVETGROUP REMOTE CONNECTIVITY
BMW X
BMW X combines the BMWVetGroup web platform with small Windows bridges to securely connect technicians to customer-side BMW ENET and ICOM networks.
Validated Discovery
The Customer Agent reuses the existing BMW X ENET/ICOM discovery, VIN identification and vehicle-data engine rather than replacing the working connection path.
Session Isolation
Each technician/customer job has a unique BMW X session. A vehicle receives an exclusive active-session lock to prevent two technicians from controlling it simultaneously.
Server Authorization
The customer client is paired to BMWVetGroup and is not a standalone permanent license. Every remote job is authorized through the secured BMW X control plane.
Multi-Technician
Independent technician/customer pairs can be online at the same time. The control plane is designed for multiple isolated concurrent jobs rather than one global connection.
BMW Software Stays Local
ISTA, E-Sys, Tool32, INPA and NCS Expert continue to run on the technician Windows PC. BMW X controls and transports the vehicle connection underneath them.
BMW X is currently restricted to BMWVetGroup administrators and members who are manually approved by an administrator. There is no self-service trial or automatic member access at this stage.
BMW X now includes the paired control plane plus a direct end-to-end encrypted TCP transport between the Customer Agent and Technician Bridge. Direct mode is preferred so the web server does not normally carry BMW diagnostic payloads. UDP discovery forwarding and relay fallback are the next transport additions for networks where direct connectivity cannot be established.