In the business world, and good practice, vlans should only exist on ports where that vlan’s traffic needs to pass.

Example: say my cameras are on vlan 3, and my default vlan is 1. I’ve also got IoT on vlan 9. IoT does not need access to the internet. Neither do the cameras (they’re viewed from a vm running blueiris)… The port going to the modem only needs vlan 1 on it, all others excluded.

IoT needs to talk to the cams sometimes, so the cams have both 3 and 9, and IoT has 3 and 9. (this could also be done with some l3-fu on the switches, but I configured the routes in opnsense so I could log peculiarities).

I’ve only got two machines that are allowed access to the management vlan (13), which has all my IDRAC/ilo/bmc/nm configured on their ports, and no other vlans.

Those two machines are firewalled on machine and the management access is only allowed when necessary (manually).

Hope that’s clearer than mud.

Stop Gatekeeping. Most of that equipment is still good for learning new concepts on, especially the Dell x20 servers.

Where are these located?

There are things that real server hardware does fasger/better, but there is no reason why old gaming hardware can’t be a fileserver, router, firewall, gateway, etc… It’ll do Just Fine ™ at it for home use.

My firewall (opnsense) does this… With very little configuration. Using UnboundDNS with its block list features makes filtering most ads out rather easy.

Without a banana for scale, or at least a potato, it’s impossible to tell if this is an air tag or a salad spinner or a spaghetti containment and distribution mechanism.