OpenThread-BR

OpenThread Border Router (OTBR) connects a Thread network to IP-based networks like Wi-Fi or Ethernet, providing end-to-end IP routing, bidirectional service…

  • Home Automation
OpenThread Border Router (OTBR) connects a Thread network to IP-based networks like Wi-Fi or Ethernet, providing end-to-end IP routing, bidirectional service discovery, and IPv6 prefix delegation so Thread and Matter devices can join and communicate on your home network.

Platform availability

Available on 1 of 9 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

69/100 Good

Maintained
100last commit 1 day ago
Popular
55577 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today

No GitHub repository data collected yet.

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Set up and start the Thread network Create and commit a Thread dataset, then bring the interface up with ifconfig up, start Thread, and enable the SRP server (a service directory for Thread devices). Without this, the border router has no network to lead and devices cannot discover services on it. source
  • Join a new device with the pre-shared key Use joiner start <pskd> in the OpenThread prompt to let a new device join; pskd is the pre-shared key (a secret code) the network accepts. If the key is missing or wrong, the device will not attach to your Thread network. source
  • Start an ephemeral key for Matter-style joins If your setup uses border-agent (ba) commissioning, start a short-lived pairing key with a timeout and port, for example ba ephemeralkey start <key> 5000 1234. Without it or the right port, a joining device may not be able to pair, and the command fails if another key is already running. source

Fetched today - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What must I enable before Thread devices can discover services through OTBR?

Create and commit a Thread dataset, bring the interface up, start Thread, and enable the SRP server. Without this, the border router has no network to lead and devices cannot discover services on it.

How do I join a Thread device using a pre-shared key?

Run joiner start <pskd> in the OpenThread prompt, where pskd is the network's pre-shared key. If the key is missing or wrong, the device will not attach to the Thread network.

Which NAT64 package did the OpenWrt openthread-br report use?

The user installed the openthread-br package and then installed Tayga for NAT64, configuring a NAT64 interface.

What benefit does the RCP design provide for OTBR?

It leaves only the sub-MAC and PHY in the 802.15.4 SoC, so most processing happens on the host processor. This makes debugging easier and allows more direct integration with the host IPv6 network stack.

Answers sourced from forum.openwrt.org, github.com, github.com, openthread.io

Community

No community discussions collected yet.