---
title: "CAN channels"
description: "Instantiate CAN channels in RemotiveTopology with RemotiveBus and SocketCAN on Linux and WSL, or UDP emulation on macOS, and choose the right driver."
source: https://developer.remotivelabs.com/docs/remotive-topology/usage/channels/can
last_updated: 2026-11-20
---

# CAN channels

RemotiveTopology supports two ways of instantiating a CAN channel:

1. [RemotiveBus using SocketCAN](#remotivebus)
2. [Emulation using UDP](#emulation-using-udp)

RemotiveBus is the default driver. You can change the default driver for all CAN channels in the [instance settings](https://developer.remotivelabs.com/docs/remotive-topology/reference/settings.md#default-can-and-lin-drivers).

> **Tip: Choosing a driver**
>
>
> - **Linux and Windows (WSL)**: Use RemotiveBus. It's needed to connect to physical hardware and to use standard CAN tooling such as `candump`.
> - **Mac**: RemotiveBus isn't available on macOS. The preferred way is to run RemotiveTopology in a Linux virtual machine so you can use RemotiveBus. UDP emulation is available as a fallback.
>

## RemotiveBus

RemotiveBus provides SocketCAN access to Docker containers. It's available on Linux, including WSL on Windows. On macOS, run it in a Linux virtual machine. You need to [install RemotiveBus](https://developer.remotivelabs.com/docs/remotive-bus/install.md) before using it.

The driver is configured on two levels. `driver.type: remotivebus` selects RemotiveBus as the driver, while `driver.config.type` selects the RemotiveBus mode:

- `can` connects to an existing SocketCAN network interface on the host.
- `vcan` uses a virtual CAN interface.

### Connecting to a CAN interface on the host

To connect to an existing CAN network interface, you specify:

- `type: can` in the driver config.
- `device`: the interface name inside the container.
- `host_device`: the interface name on the host. This is optional and defaults to the value of `device`.

```yaml
channels:
  DriverCan:
    type: can
    driver:
      type: remotivebus
      config:
        type: can
        device: drivercan
        host_device: can5  # if a specific name is needed on the host
```

### Virtual CAN

When running in a purely virtual environment, you specify:

- `type: vcan` in the driver config.
- `device`: the interface name inside the container. If omitted, the lowercase channel name is used.
- `host_device`: the interface name on the host. This is optional. If omitted, the network isn't visible on the host.

```yaml
channels:
  DriverCan:
    type: can
    driver:
      type: remotivebus
      config:
        type: vcan
        device: drivercan
```

## Emulation using UDP

Emulation using UDP is available on all platforms and doesn't require any additional setup. It sends the CAN frames using UDP multicast. Each frame is encoded as an Ethernet PDU, so the signals are encoded exactly as on a real CAN bus.

Specify the driver for each channel, or make UDP the [default driver](https://developer.remotivelabs.com/docs/remotive-topology/reference/settings.md#default-can-and-lin-drivers):

```yaml
channels:
  DriverCan:
    type: can
    driver:
      type: udp
```

### Naming devices

> **Info**
>
> Linux limits network interface names to 15 characters. This applies to both `device` and `host_device`. If your channel name is too long, set a shorter name explicitly.

Recommendations:

- Avoid names such as `can0` or `can1`. These are the names Linux gives physical CAN devices by default, so they don't tell which bus a device is connected to.
- Rename physical devices to match your target architecture, e.g. `sudo ip link set can0 name drivercan`
- Inside the container try to use a name similar to the channel. This makes it easier to understand in a virtual context.

RemotiveBus also supports [plugins](https://developer.remotivelabs.com/docs/remotive-bus/plugins.md), for example to [connect to hardware LIN](https://developer.remotivelabs.com/docs/remotive-topology/usage/channels/lin.md#connecting-to-hardware-lin).
