Open Source RoboticsRobots, software & learning

rmw_zenoh

Software

Official ROS 2 RMW middleware implementation built on Eclipse Zenoh (zenoh-cpp), providing router-mediated discovery, optional shared memory, and security tooling as a non-DDS transport. [2] [4]

Installation & first result →Official websiteGetting started

For
ROS 2 robotics engineers; Multi-robot and Wi-Fi/WAN fleet developers; Middleware and robotics systems architects [2]
Source rights
Named licenses are documented by part. Review licenses

Source researched · Not tested by us
Sources checked · Research details

Licenses & related hardware
Ecosystem
ROS 2

Requirements · Research details and dates

On this page

Overview

rmw_zenoh is the official ROS 2 RMW implementation built on Eclipse Zenoh (zenoh-cpp), packaged as rmw_zenoh_cpp, zenoh_cpp_vendor, and zenoh_security_tools. This review inspects the rolling branch at commit 5a2ea3622b25ea430923d3d71bc3379717179481 (checked 2026-11-21); because the README directs users to distribution-specific branches (such as jazzy), confirm defaults and known issues against your target ROS 2 distro branch before migrating. It is installable from Tier-1 ROS 2 binary repositories (sudo apt install ros-<DISTRO>-rmw-zenoh-cpp) or from source via colcon, and switching a DDS graph uses RMW_IMPLEMENTATION=rmw_zenoh_cpp, but several default behaviors and hard incompatibilities need to be accounted for first. [1] [2] [4]

Is this for you?

Workflows
  • Single-host ROS 2 graph with local rmw_zenohd router
  • Multi-host router-to-router TCP bridging or remote client mode (e.g., RViz)
  • Enabling implicit Zenoh shared memory across host or Docker containers
  • Generating authenticated/encrypted configs with zenoh_security_tools

[2]

Known limitations
  • Cannot interoperate with eclipse-zenoh/zenoh-plugin-ros2dds or zenoh-bridge-ros2dds due to different Zenoh key expressions.
  • Incompatible across ROS 2 Humble and newer distributions (Iron+) because type hashes are embedded in key expressions, causing silent message drops.
  • Default router config binds IPv6 ANY (tcp/[::]:7447) and crashes on IPv4-only hosts unless replaced with tcp/0.0.0.0:7447; default SHM has a known high-CPU drop warning (issue #978); omitting rclcpp::shutdown() can panic on Rust tokio TLS destruction.

[2]

What you need

Operating system
  • ROS 2 Tier-1 supported platforms (e.g., Ubuntu Linux via apt binaries)

[2]

Languages / runtimes
  • C++ (RMW layer)
  • Rust (vendored Zenoh core)

[2] [4]

Dependencies
  • ROS 2 (matching distro branch)
  • zenoh_cpp_vendor (vendored zenoh-cpp/Rust Zenoh core, or system Zenoh via USE_SYSTEM_ZENOH)
  • fastcdr
  • nlohmann-json-dev
  • ament_cmake

[2] [4]

Host computer

Default serialization buffer pool is 8 MiB; when Zenoh SHM is enabled, each node allocates up to 48 MiB (50,331,648 bytes) in /dev/shm by default.

[2]

Compute for the workload
  • 8 MiB default serialization buffer pool (RMW_ZENOH_BUFFER_POOL_MAX_SIZE_BYTES)
  • 48 MiB default /dev/shm pool per SHM-enabled node (transport/shared_memory/transport_optimization/pool_size)

[2]

Skills
  • ROS 2 (colcon, rosdep, RMW_IMPLEMENTATION)
  • C++ / CMake
  • JSON5 configuration and networking (TCP/IPv6/multicast)
  • Linux /dev/shm sizing for shared memory

Inferred from README setup, configuration, and SHM sections.

[2] [4] · Editorial assessment

Installation & first result

Open the upstream getting-started guide [2]

  • Install binary package via sudo apt install ros-<DISTRO>-rmw-zenoh-cpp (or build from source with colcon build --cmake-args -DCMAKE_BUILD_TYPE=Release).
  • Stop any ROS 2 daemon started under another RMW (ros2 daemon stop).
  • Launch the Zenoh router with ros2 run rmw_zenoh_cpp rmw_zenohd (unless enabling multicast scouting).
  • Export RMW_IMPLEMENTATION=rmw_zenoh_cpp before running ROS 2 nodes (e.g., demo_nodes_cpp talker and listener).

[2]

Installation

Recommended binary install: sudo apt update && sudo apt install ros-<DISTRO>-rmw-zenoh-cpp; source build uses colcon build against the matching ROS 2 distro branch.

[2]

Hardware, models & data

Interfaces
  • ROS 2 RMW C/C++ interface (RMW_IMPLEMENTATION=rmw_zenoh_cpp)
  • Zenoh router daemon (rmw_zenohd)
  • JSON5 config files (ZENOH_ROUTER_CONFIG_URI, ZENOH_SESSION_CONFIG_URI) and ZENOH_CONFIG_OVERRIDE env var
  • zenoh_security_tools CLI

[2]

Inputs and outputs

Maps ROS 2 topics, services, actions, and graph discovery to Zenoh sessions, key expressions, liveliness tokens, and CDR-serialized payloads.

[2] [4]

File formats
  • CDR (fastcdr) message serialization
  • JSON5 router and session configuration files

[2] [4]

Evaluation

Documented smoke test via rmw_zenohd + demo_nodes_cpp talker/listener; not executed in this review.

[2]

Project notes

Router-mediated discovery is the default

Unlike DDS multicast discovery, rmw_zenoh disables multicast scouting in its default session config and relies on a local Zenoh router (ros2 run rmw_zenoh_cpp rmw_zenohd) for gossip discovery. Always stop any existing ROS 2 daemon started under a previous RMW (ros2 daemon stop) before testing, or CLI tools like ros2 node list will query stale graph state. [2]

All discovery and traffic are restricted to the local host by default. To span multiple machines, you either connect routers to each other via connect/endpoints in DEFAULT_RMW_ZENOH_ROUTER_CONFIG.json5 (or ZENOH_CONFIG_OVERRIDE), or switch a remote node such as RViz to mode="client" pointing at the robot's router so the router forwards traffic. Multicast scouting without a router is still possible by setting ZENOH_ROUTER_CHECK_ATTEMPTS=-1 and ZENOH_CONFIG_OVERRIDE='scouting/multicast/enabled=true' (plus listen/endpoints=["tcp/0.0.0.0:0"] across hosts). [2]

Implicit shared memory and memory-budget tuning

rmw_zenoh recycles serialization buffers in an 8 MiB default pool (RMW_ZENOH_BUFFER_POOL_MAX_SIZE_BYTES). To use Zenoh shared memory, SHM must be enabled on all participating Zenoh sessions exchanging messages (for example via ZENOH_CONFIG_OVERRIDE='transport/shared_memory/enabled=true'); communication with remote or non-SHM participants remains transparently supported over network transport. Between SHM-enabled local participants, Zenoh applies implicit SHM optimization to eligible messages exceeding a configurable threshold (default 512 bytes)—not only ROS 2 loaned messages—and seamlessly falls back to network transport if SHM allocation fails. [2]

Watch two operational details when turning SHM on: [2]

  • Per-process /dev/shm footprint: each node allocates up to 48 MiB (50,331,648 bytes) by default (sized for two in-flight 4K images), lazily on the first SHM message unless transport/shared_memory/mode is set to init. On hosts or Docker containers with many ROS 2 processes, size /dev/shm accordingly or lower pool_size.
  • High-CPU drop warning: the README flags a known issue (#978) where high CPU load (such as launching many nodes simultaneously) with SHM enabled can silently drop service calls or TRANSIENT_LOCAL historical publications.

Three documented incompatibilities and failure modes

1. No interoperability with zenoh-plugin-ros2dds: rmw_zenoh uses different Zenoh key expressions than eclipse-zenoh/zenoh-plugin-ros2dds and zenoh-bridge-ros2dds; the two cannot talk to each other. [2] 2. Humble vs. Iron+ mismatch: because Iron and newer ROS 2 distros embed message type hashes into Zenoh key expressions, Humble nodes and newer-distro nodes discover each other but silently drop messages. [2] 3. IPv4-only crashes and exit panics: the default router binds IPv6 ANY (tcp/[::]:7447) and exits on IPv4-only systems unless that entry is replaced with tcp/0.0.0.0:7447. On process exit, failing to call rclcpp::shutdown() explicitly (outside composable node containers) can trigger a Rust tokio Thread Local Storage panic. [2]

The repository is licensed under Apache-2.0, with rmw_zenoh_cpp/package.xml additionally declaring a BSD license for simplified_xxhash3.{cpp,hpp}. No ROS 2 packages were installed, compiled, or benchmarked in this review; the next step is running rmw_zenohd with demo_nodes_cpp talker/listener on your target distro and checking IPv6 and /dev/shm defaults before migrating production launch files. [2] [3] [4]

What we checked

Primary-source repository metadata, README, LICENSE, and package.xml inspection only. No ROS 2 packages were installed, compiled, or run, and no network or shared-memory benchmarks were performed.

Not yet established

  • Version-specific hardware compatibility (ecosystem tags alone do not establish it)

Updates

Upstream last updated
Nov 21, 2026 [1]
Latest release
Not established
Profile updated
Nov 21, 2026
Sources last checked
Nov 21, 2026
Next review
Feb 19, 2027
Reviewed revision
ros2/rmw_zenoh@5a2ea3622b25ea430923d3d71bc3379717179481 · software repository

Source files and licenses

Official ROS 2 non-DDS RMW middleware implementation with active maintenance, binary packages, and verified Apache-2.0 licensing (plus BSD for simplified_xxhash3).

LayerAvailability / license
softwareavailable · Apache-2.0
Root LICENSE is Apache-2.0; rmw_zenoh_cpp/package.xml additionally declares BSD for simplified_xxhash3.{cpp,hpp}. [3] [4]
documentationavailable · Apache-2.0
Repository README and docs covered by root Apache-2.0 LICENSE. [2] [3]

Middleware transport implementation; no model weights.

Middleware transport implementation; no datasets.

References

Each source links to the exact revision we read. “Used for” shows where this page relies on it.

  • S001 ros2/rmw_zenoh repository metadata, tags, and HEAD commit
    Confirms active rolling branch maintenance through 2026-11-21, Apache-2.0 license, and tag 0.14.1.
    Revision, date & where cited

    ROS 2 / Open Robotics contributors · github.com · revision 5a2ea36 · rolling HEAD (2026-11-21); latest tag 0.14.1 · Accessed Nov 21, 2026


    Used for: Overview, What we checked
  • S002 ros2/rmw_zenoh README.md
    Documents binary and source install, rmw_zenohd router requirement, ZENOH_CONFIG_OVERRIDE, Zenoh shared memory (48 MiB default pool, 512 B threshold, issue #978 warning), security tools, zenoh-plugin-ros2dds incompatibility, and known IPv4-only / TLS-shutdown / Humble issues.
    Revision, date & where cited

    ROS 2 / Open Robotics contributors · github.com · revision 5a2ea36 · README.md at · Accessed Nov 21, 2026


    Used for: Overview, Is this for you?, What you need, Installation & first result and 5 more
  • S003 ros2/rmw_zenoh LICENSE
    Apache License 2.0 covering the repository.
    Revision, date & where cited

    ROS 2 / Open Robotics contributors · github.com · revision 5a2ea36 · LICENSE at · Accessed Nov 21, 2026


    Used for: Three documented incompatibilities and failure modes, Source files and licenses
  • S004 rmw_zenoh_cpp/package.xml
    Declares package version 0.14.1, maintainer Yadunund (Open Robotics), authors Chris Lalancette and Franco Cipollone, Apache-2.0 plus BSD license for simplified_xxhash3.{cpp,hpp}, and ament_cmake/fastcdr/zenoh_cpp_vendor dependencies.
    Revision, date & where cited

    ROS 2 / Open Robotics contributors · github.com · revision 5a2ea36 · rmw_zenoh_cpp/package.xml at · Accessed Nov 21, 2026


    Used for: Overview, What you need, Hardware, models & data, Three documented incompatibilities and failure modes and 1 more

Correction guidance · Discussion is not enabled · Profile format 0.8.0-draft.1

Change history