Remote Enet VPN

kasfearles said:

Would anyone be kind enough to share a guide to set up a remote ENET connection for use with ESYS an...

Click to expand...

Setting up a remote ENET connection over VPN is a fairly well-documented approach. The general idea is to bridge your ENET interface at the car's location to your remote PC over a VPN tunnel so that ISTA/E-Sys sees the car as if it were on the local network.

General Concept

You need two machines:

• Car-side PC/laptop – physically connected to the car via ENET cable (OBD port)
• Remote PC – where you run E-Sys / ISTA

Both machines join the same VPN so they share a virtual LAN.

Typical Setup Steps

1. Choose a VPN solution – Radmin VPN, ZeroTier, or Tailnet/Tailscale are popular choices. Radmin VPN and ZeroTier are free and create a Layer 2 or Layer 3 virtual network between the two PCs. ZeroTier is often recommended as it's easy and reliable.
   
2. Install the VPN on both PCs – Create a network and join both machines to it. Confirm they can ping each other over the VPN.
   
3. Connect the car-side PC to the car via ENET – Set the ENET adapter to a static IP (e.g., 169.254.x.x range or 192.168.x.x depending on your setup). Make sure the car-side PC can communicate with the car locally first.
   
4. Bridge the network interfaces on the car-side PC – This is the key step. On the car-side PC, bridge the ENET (physical) adapter and the VPN virtual adapter together. In Windows: select both adapters in Network Connections → right-click → Bridge Connections. This puts the remote PC on the same Layer 2 segment as the car.
   
5. Configure the remote PC – Set the VPN adapter on the remote PC to a static IP in the same subnet as the car (e.g., 169.254.x.x with subnet 255.255.0.0 if using the default BMW ENET range).
   
6. Test connectivity – From the remote PC, ping the car's IP (typically 169.254.0.1 for F/G series). If you get a reply, you're good.
   
7. Launch E-Sys or ISTA – On the remote PC, configure the connection as you normally would for a local ENET connection. E-Sys: set the connection to the car's IP. ISTA: it should detect the vehicle via the network.

Important Notes

• Latency matters – Remote coding with E-Sys generally works fine over VPN as the data packets are small. However, flashing via ISTA over VPN is risky – a connection drop mid-flash can brick a module. Only do coding/diagnostics remotely, not programming/flashing.
• Firewall – Disable Windows Firewall on both PCs (or at least on the bridged/VPN adapters) during the session.
• Sleep/power settings – Make sure the car-side PC won't go to sleep, and the car stays awake (use a battery charger).
• ZeroTier tip – If using ZeroTier, you need to enable Ethernet bridging for the car-side member in the ZeroTier network admin panel, and also check "Allow Ethernet Bridging" in the local ZeroTier client on that machine.

VPN Comparison

• Radmin VPN – Simple, Layer 2, Windows-only. Bridging works well. The Bimmerscene guide likely uses this.
• ZeroTier – Cross-platform, Layer 2 capable, slightly more setup but very reliable. Probably the best option overall.
• Tailscale – Layer 3 only (no bridging), so it requires port forwarding/routing instead of bridging. More complex for this use case.

If you get stuck at a specific step, post back with details on which VPN you chose and where it fails – happy to help troubleshoot.