olsrd mit Homebrew, apk, Nix installieren

Projektlinks

• Homepage
• Upstream-Dokumentation
• Paketmanager-Seite

Befehle und Aliase

• olsrd
• sgw_policy_routing_setup.sh

Projektgeschichte

The OLSR.org project says olsrd began in 2004 as Andreas Tonnesen's master's thesis implementation of the IETF MANET OLSR protocol. After the thesis work, development continued as an open source project because community networks needed a real daemon, not just a protocol specification.

The daemon evolved into a modular implementation with loadable plugins and ports beyond Linux. Historical project material records the addition of a plugin interface, Windows and BSD ports, an OS X port, and link-quality routing work during the 2004-2005 period.

Adoptionsgeschichte

olsrd's adoption story is unusually concrete for a routing daemon: Freifunk, FunkFeuer, and other community wireless networks used it to build multi-hop mesh networks. The GitHub repository identifies the OLSR.org v1 codebase as maintained by Freifunk Berlin, which matches its long association with European community mesh deployments.

Research and engineering literature around community networks treated the OLSR.org implementation as one of the widely deployed open source OLSRv1 daemons. That made olsrd a reference point for later comparisons with B.A.T.M.A.N., Babel, OLSRv2, and other mesh-routing approaches.

Wie es verwendet wird

Operators run olsrd as a standalone routing daemon on each mesh node. It discovers neighbors with OLSR messages, installs routes into the host routing table, and can advertise external networks through host/network association settings.

Package users usually care about the daemon plus its configuration and plugin ecosystem: interface selection, link-quality behavior, gateway advertisement, status output, and integrations for embedded router distributions such as OpenWrt.

Warum Paket-Nerds sich dafür interessieren

For package nerds, olsrd is a compact example of a network protocol escaping an RFC and becoming operational infrastructure. It sits at the intersection of IETF MANET work, hobbyist/community networking, embedded Linux routers, and distro packaging.

It also matters because it is old infrastructure with real-world wrinkles: platform ports, plugins, wireless link-quality extensions, and packaging across Unix-like systems all show the difference between a protocol paper and deployable routing software.

Zeitleiste

• October 2003: RFC 3626 documents the OLSR protocol for mobile ad hoc networks.
• 2004: olsrd starts as Andreas Tonnesen's master's thesis implementation and then continues as an open source project.
• 2004-2005: project history records plugin support, additional platform ports, and link-quality routing work.
• 2010s-2020s: the OLSR.org v1 repository lives on GitHub under the OLSR organization, with the repository description identifying Freifunk Berlin maintenance.

Related projects

• OLSRv2 is the IETF successor to OLSR and keeps the multipoint-relay family resemblance while using newer MANET components. In package collections, olsrd is commonly compared with other mesh daemons such as Babel and B.A.T.M.A.N. rather than with general-purpose wired routing suites.

Quellen

• https://api.github.com/repos/OLSR/olsrd
• https://datatracker.ietf.org/doc/rfc3626/
• https://datatracker.ietf.org/doc/rfc7181/
• https://github.com/OLSR/olsrd
• https://ieeexplore.ieee.org/document/6673346/
• https://openwrt.org/docs/guide-user/network/wifi/mesh/olsr
• https://wirelesspt.net/arquivos/docs/olsr/Implementation.Of.Olsrd.pdf
• https://www.olsr.org/