Skip to content

network_bridge

  • Software
  • Middleware
  • Tool

A ROS2 node that bridges ROS2 topics across networks over UDP, TCP, or ZMQ, for remote communication between a base station and robots or between several robots.

Source on GitHub: github.com/brow1633/network_bridge (opens in a new tab). Facts read at commit 24ce039 (opens in a new tab).

Licenses

Code
MIT (opens in a new tab)

Read by Robotheca from LICENSE (opens in a new tab) (MIT) at commit 24ce039 (opens in a new tab), on 16 Oct 2026.

Commercial use
Yes

What it does

  • Bridges ROS2 topics between systems using UDP, TCP, or ZMQ, which are supported out of the box.
  • UDP suits low-latency telemetry where occasional loss is acceptable; TCP suits reliable delivery of commands.
  • ZMQ offers one-to-many publish/subscribe or round-robin push/pull; its links are one-directional.
  • Special handling for TF topics: the subscriber side accumulates transforms and sends them at a configured rate, with include/exclude regex filters.
  • Network protocols are pluginlib plugins built on an abstract base interface, so new protocols can be added.

Written by Robotheca from the project's README (opens in a new tab) at commit 24ce039.

Getting started

Difficulty
Intermediate

Maintenance

Status
Active: a commit in the last 90 days
Newest commit
12 Oct 2026 on main
Latest release
None published on GitHub

Checked on GitHub on 16 Oct 2026.

Robots that can run it

No robot on Robotheca is linked to it yet. Links come from a robot's robot.yaml, from its dependency files read as text, or from Robotheca's editors.

Robotheca lists software as a reference: nothing is hosted or run here, and every fact links to where it was read.