branderson/blog
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Reformat lists

Browse Source
This commit is contained in:
branderson
2026-01-12 20:56:02 -08:00
parent 47ab655348
commit 6eef6412e3
1 changed files with 13 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files
server-rack-wifi/index.md
+13 -13
View File
@@ -15,7 +15,7 @@ which had been running in LXC to dedicated VMs. Assuming network congestion may
be an issue, I reduced the amount of internal traffic my services generate by
scaling back the rate of backups and file scans. I replaced cables in my server
rack. Almost nothing helped (I say almost because the migration from CIFS -> NFS
actually did significantly reduce IO pressure in my main server :frog-yay:).
actually did significantly reduce IO pressure in my main server :yay-frog:).
At this point, I decided to start more deeply investigating the state of the
network itself, having ruled out network congestion and service configuration as
@@ -39,17 +39,17 @@ a closer look at the network configuration itself.
The intended ethernet route from my router to my server rack looks something
like this:
- ![Intended Topology](./assets/intended-topology.png)
- Ethernet is run from my router, to a network closet switch, then through my
walls to my living room switch, then into my garage to the server rack switch,
where my servers and NAS are connected.
![Intended Topology](./assets/intended-topology.png)
Ethernet is run from my router, to a network closet switch, then through my
walls to my living room switch, then into my garage to the server rack switch,
where my servers and NAS are connected.
Looking at the port configuration for my living room switch showed something
unexpected:
- ![STP blocked](./assets/stp-blocked.png)
- The switch port handling the ethernet connection between my network closet
switch and living room switch had been disabled by the network due to a
spanning tree protocol (STP) issue!
![STP blocked](./assets/stp-blocked.png)
The switch port handling the ethernet connection between my network closet
switch and living room switch had been disabled by the network due to a
spanning tree protocol (STP) issue!
It turns out that around the time the slowness began, the living room switch had
performed a factory reset and set its STP priority to a very large number (and
@@ -64,10 +64,10 @@ house.
This resulted in my network route from my router to my server rack being
configured something like this:
- ![Actual Topology](./assets/actual-topology.png)
- Instead of functioning as a wifi access point, Mr. Stabby had instead become a
giant wifi dongle for my entire server rack! I would not have assumed this was
possible.
![Actual Topology](./assets/actual-topology.png)
Instead of functioning as a wifi access point, Mr. Stabby had instead become a
giant wifi dongle for my entire server rack! I would not have assumed this was
possible.
Fixing the STP priority for my living room switch to the correct (lower) value
allowed it to take priority over Mr. Stabby for STP, reconfiguring the network