kode54
February 24, 2025, 7:54am
1
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
pmh
February 24, 2025, 8:45am
2
“The administrator decided to disable spanning tree …”
cue gloomy foreshadowing background music
1 Like
kode54
February 25, 2025, 1:30am
3
And what is that supposed to mean?
pmh
February 25, 2025, 5:36am
4
Disabling spanning tree on a bridge is a desaster waiting to happen. Build a loop by accident → complete meltdown by broadcast storm.
1 Like
kode54
February 25, 2025, 5:48am
5
So how do I have a software bridge on Scale without it taking a full minute to bring up on every boot?
kode54
February 25, 2025, 5:49am
6
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.
pmh
February 25, 2025, 5:59am
7
You don’t. That’s a safeguard protecting you from bringing down your network. How often do you boot, anyway?
kode54
February 25, 2025, 6:00am
8
Not often enough for it to be a significant delay, actually.
kode54
February 25, 2025, 6:10am
9
But then, how does one cause network loops with a bridge that only contains a single interface port?
pmh
February 25, 2025, 8:22am
10
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.
kode54
February 25, 2025, 10:23am
11
Sorry, I frequently fail to detect jokes.
It was a good one, though. But yeah, I will probably re-enable it if I ever dabble in VLANs.