Spanning tree protocol still doesn't have a toggle in the web UI

I had to disable STP from the terminal using the following incantation:

midclt call interface.update br0 '{"stp": false}'

The STP on the bridge interface otherwise causes the machine to take upwards of a minute to bring up the network on startup.

1 Like

“The administrator decided to disable spanning tree …”

cue gloomy foreshadowing background music

1 Like

And what is that supposed to mean?

Disabling spanning tree on a bridge is a desaster waiting to happen. Build a loop by accident → complete meltdown by broadcast storm.

1 Like

So how do I have a software bridge on Scale without it taking a full minute to bring up on every boot?

That failing, how am I supposed to have VMs without a bridge? I can’t get them to have working network without one. NAT resulted in no network.

You don’t. That’s a safeguard protecting you from bringing down your network. How often do you boot, anyway?

Not often enough for it to be a significant delay, actually.

But then, how does one cause network loops with a bridge that only contains a single interface port?

Not knowing what you might add in the future - VLANs for example, second port possibly - I just wrote a warning with an attempt at humour. That’s all.

STP prevents loops in the topology. Build a loop without STP and your network will be fried. Of course not irreversibly so, no hardware damage, just unplug the device that caused it and probably reboot everything else.

Sorry, I frequently fail to detect jokes. :confused:

It was a good one, though. But yeah, I will probably re-enable it if I ever dabble in VLANs.