---
title: "Supported platforms and protocols"
description: "Which RemotiveTopology drivers and features work on Linux, Windows with WSL2, and macOS, and which network protocols and file formats RemotiveTopology supports."
source: https://developer.remotivelabs.com/docs/remotive-topology/reference/supported-platforms
last_updated: 2026-11-20
---

# Supported platforms and protocols

RemotiveTopology runs on Linux, on Windows with WSL2, and on macOS. Linux has full support. Some features need [RemotiveBus](https://developer.remotivelabs.com/docs/remotive-bus.md), which is only available on Linux, including WSL2. For installation, see [Install RemotiveTopology](https://developer.remotivelabs.com/docs/get-started/install.md).

## Operating systems

| | Linux | Windows (WSL2) | macOS |
| --- | --- | --- | --- |
| Container engine | Docker Engine or Podman | Docker Engine, installed in WSL2 | Docker or Podman |
| RemotiveBus | Yes | Yes, with a WSL2 kernel that has the `vcan` and `vxcan` modules, see [WSL2 in Windows](https://developer.remotivelabs.com/docs/get-started/install.md#wsl2-in-windows) | No, run RemotiveTopology in a Linux virtual machine |
| `remotive topology` commands | Yes | In WSL2, not in PowerShell | Yes |
| Behavioral models and tests in Python | Python 3.10 or later | Python 3.10 or later | Python 3.10 or later |

On macOS, the preferred way is to run RemotiveTopology in a Linux virtual machine, so you can use RemotiveBus. Without RemotiveBus, CAN and LIN channels fall back to UDP emulation, and the features in the following table that need RemotiveBus aren't available.

## Channel drivers and features

| Feature | Needs | Linux | Windows (WSL2) | macOS |
| --- | --- | --- | --- | --- |
| [CAN with SocketCAN](https://developer.remotivelabs.com/docs/remotive-topology/usage/channels/can.md#remotivebus), the default | RemotiveBus | Yes | Yes | Linux VM |
| [CAN emulation using UDP](https://developer.remotivelabs.com/docs/remotive-topology/usage/channels/can.md#emulation-using-udp) | Nothing | Yes | Yes | Yes |
| [LIN](https://developer.remotivelabs.com/docs/remotive-topology/usage/channels/lin.md), over the CAN drivers | RemotiveBus or UDP | Yes | Yes | UDP, or Linux VM |
| [Ethernet with Docker bridge networks](https://developer.remotivelabs.com/docs/remotive-topology/usage/channels/ethernet.md), the default | Nothing | Yes | Yes | Yes |
| [Ethernet with VLAN](https://developer.remotivelabs.com/docs/remotive-topology/usage/channels/ethernet.md#vlan) | RemotiveBus | Yes | Yes | Linux VM |
| [Test access points (TAP)](https://developer.remotivelabs.com/docs/remotive-topology/usage/test/tap.md) | RemotiveBus with Docker | Yes | Yes | Linux VM |
| SocketCAN tools such as `candump` | RemotiveBus | Yes | Yes | Linux VM |
| [Virtual ECUs](https://developer.remotivelabs.com/docs/remotive-topology/usage/ecus/virtual-ecus.md) on CAN | RemotiveBus | Yes | Yes | Linux VM |
| [Connecting hardware](https://developer.remotivelabs.com/docs/remotive-topology/usage/hardware.md) | RemotiveBus and a Linux driver for the adapter | Yes | USB adapters passed through to WSL2 | Linux VM |

RemotiveBus provides TAP only for Docker networks, not for Podman.

## Protocols

| Protocol | Described by | Notes |
| --- | --- | --- |
| CAN | DBC, ARXML | Bit rate set in the platform, see [CAN channel](https://developer.remotivelabs.com/docs/remotive-topology/concepts/platform.md#can-channel) |
| CAN FD | DBC, ARXML | Data phase bit rate and bit rate switching set in the platform with `baudrate_fd` and `brs` |
| LIN | LDF | Transported inside CAN frames, see [LIN channels](https://developer.remotivelabs.com/docs/remotive-topology/usage/channels/lin.md) |
| Ethernet PDUs over UDP | ARXML, platform file | Point-to-point sockets, see [Ethernet PDUs](https://developer.remotivelabs.com/docs/remotive-topology/concepts/platform.md#ethernet-pdus) |
| SOME/IP over UDP | ARXML, Fibex | Services and instances, see [SOME/IP](https://developer.remotivelabs.com/docs/remotive-topology/concepts/platform.md#someip) |

## File formats

| Format | Used for |
| --- | --- |
| `*.platform.yaml` | Platforms, see [Describing the platform](https://developer.remotivelabs.com/docs/remotive-topology/concepts/platform.md) |
| `*.instance.yaml` | Instances, see [Instantiating topology](https://developer.remotivelabs.com/docs/remotive-topology/concepts/instance.md) |
| DBC | CAN channels, their ECUs, frames, and signals |
| LDF | LIN channels, their ECUs, frames, signals, and schedule tables |
| ARXML | System descriptions and ECU extracts: channels, ECUs, sockets, and SOME/IP services |
| Fibex | SOME/IP services |
| FMU, FMI 2.0 and 3.0 with co-simulation | [FMU models](https://developer.remotivelabs.com/docs/remotive-topology/usage/ecus/fmu.md) |
| CAN dump and CSV | [Recordings](https://developer.remotivelabs.com/docs/remotive-topology/usage/recordings.md) |

The [topology schema](https://developer.remotivelabs.com/apis/json/topology) describes every field of the platform and instance files.
