mstpd - GitLite

KO | EN

gitlite — search

#python #react #typescript #go #machine-learning #deep-learning #linux #docker #macos #java #windows #awesome #kubernetes #openai

mstpd

(★ 153)

Multiple Spanning Tree Protocol Daemon

파일 탐색기

최종 버전 다운로드 (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

mstpd: Multiple Spanning Tree Protocol Daemon
=============================================

[![Build Status](https://travis-ci.org/mstpd/mstpd.svg?branch=master)](https://travis-ci.org/mstpd/mstpd)

MSTPD is an open source user-space daemon licensed under GPLv2.

MSTPD is reported to be compliant with IXIA ANVL RSTP test suite, with
the notable exception of looped-back BPDUs (see discussion on the matter
on the Implementation Features wiki page:
https://github.com/mstpd/mstpd/wiki/ImplementationFeatures).

**Important note!** MSTP part of the code (as opposed to STP/RSTP part)
is mainly untested, so I believe it will behave unexpectedly in many
situations. Don't use it in production!

Official repository: https://github.com/mstpd/mstpd

*IRC: Feel free to join and chat with us on #mstpd @ OFTC!*

Implementation Features
-----------------------

See the wiki page: https://github.com/mstpd/mstpd/wiki/ImplementationFeatures

Also MSTPD includes a number of useful features which are not defined in
802.1Q-2005 standard, but are found on many commercial switches. Namely:

- BPDU Guard. Added by Satish Ashok.

- Bridge Assurance. Added by Satish Ashok.
  (WARNING: it might be dropped in the future and replaced by the
  AutoIsolate feature of 802.1Q-2011)

- Enhanced statistics: TX/RX BPDU/TCN counters, Forwarding/Blocking
  transitions counters, last 2 ports which caused topology change. Added
  by Satish Ashok.

Goals of the project
--------------------

- Create reliable and well-tested MSTP code.

- Get some user base - the more users of this code, the more test
 coverage is.

- Replace rstpd.

Current state
-------------

The daemon depends on the bridge Linux kernel code to gather basic info
about bridge, such as bridge state (up/down, STP on/off), slave
interfaces for the bridge and their state (up/down). Also daemon
translates CIST states to the kernel bridge slaves, so mstpd in (r)stp
mode can be used as replacement for the current rstpd (and even for the
in-kernel stp!).

MSTP standard (802.1Q-2005) requires from the bridge to be heavily
interconnected with the VLANs infrastructure, namely:

- Support several (2 .. 4094) independent FIDs (Forwarding Information
  Databases). Each VLAN belongs to the one of FIDs, and learning of the
  MAC addresses is done independently in the each FID (independent
  learning as opposed to shared learning in the current Linux bridges);

- Support several (2 .. 64) Multiple Spanning Tree Instances in
    addition to the CIST. Each FID belongs to the one of MSTIs or CIST;

- Support per-MSTI port states (Discarding / Learning / Forwarding) so
  that each bridge port can have different states for different MSTIs.

Linux bridging supports either IVL or SVL, but does not support dynamic
allocation of VIDs to FIDs.

This is controlled via the VLAN filtering attribute:

- When VLAN filtering is enabled, the bridge supports 4094 VLANs with
    IVL, and requires configuration of all VLANs permitted;
  - When VLAN filtering is disabled, the bridge is not VLAN aware and only
    learns via the MAC address (into a separate "untagged" FID), so it does
    SVL.

Additionally Linux bridging gained support for MSTIs in version 5.18:

- VLANs configured on the bridge can be assigned to MSTIs;
  - Once a VLANs is assigned to a MSTI, the port states of ports that are
    members of that VLAN can be configured

MSTPD currently does not handle this, so MSTP daemon is not as useful
for the bare Linux box (except for the (R)STP case - as stated above it
works with the kernel bridge well enough in this case). But there are
plenty embedded cases where bridging functions are implemented by
specialized hardware with support of custom drivers. For such cases MSTP
daemon can be successfully utilized. The daemon code has a few hooks
where driver-specific code should be inserted to control the bridge
hardware.

Packaging
---------

MSTPD is currently packaged for the following distributions:

[![Packaging status](https://repology.org/badge/vertical-allrepos/mstpd.svg)](https://repology.org/project/mstpd/versions)

It is also available as a [recipe in Yocto](https://layers.openembedded.org/layerindex/recipe/340642/).

ACKNOWLEDGEMENTS
----------------

Initial code was written by looking at (and shamelessly stealing some
parts from):

- [rstpd](https://github.com/shemminger/RSTP) by Srinivas Aji `<Aji_Srinivas
    ? emc DOT com>` and Stephen Hemminger `<stephen ? networkplumber DOT org> ,
    used as the base of `mstpd`

- [rstplib](https://sourceforge.net/projects/rstplib/) by Alex Rozin `<alexr
    ? nbase DOT co DOT il>` and Michael Rozhavsky `<mike ? nbase DOT co DOT
    il>`, as inspiration for `mstp.{c,h}`