It's a little harder to compare TP-Link switches (which is the brand used in the linked article), since their $53 managed switch also has 4 ports of PoE, while their $18 unmanaged switch doesn't have PoE.
I’m sure there is one because they’re more expensive.
The only thing I was able to discover is that they detect a network loop.
[This is back when IPv6 is relatively novel and so the refit of a large building with brand new high end Cisco managed switches was justified as research, also leading to a hilarious "bidding" process in which Cisco's lone authorised supplier tells us what the price is, which of course is completely unaffordable, then we tell a Cisco exec what we want to pay, then they calculate a research "discount" which we are to be offered so that magically we pay exactly this much to the lone supplier].
Feature I really liked 1.: Time Domain Reflectometry. Port #123 failed? Ask the switch, it says the fault is 19 metres from the switch, measure by eye or with tape, oh yeah, there's the problem.
Feature I really liked 2.: Port history. You can see at a glance that ports #120 through #140 are not in use now but with history you can see that port #130 and #136 were used last Tuesday night. Aha! The only thing these ports actually do is support a madcap arrangement where Astronomy run laptops on the roof for stargazing. They can just use WiFi! No need to run all this extra stuff.
For the research we had MLDv2 group multicast support - e.g. 80 people have 100baseT networking, 10 watch video channel A at 40Mbps, 10 watch channel B at 40Mbps, yet the network is only moving 80MBps (40 + 40) and their links only have 40 Mbps each, the 60 non participants have all 100Mbps free - in principle that could be done in a relatively dumb switch, but also at home scale it's irrelevant anyway, and even at corporate it's cool but hardly worth diverting serious effort when you probably don't need such a feature.
I even managed to find an unmanaged 16-port 2.5GbE PoE switch so now I have 2.5Gbps and PoE at every wall jack in my house. (PoE is amazing. Get PoE if you're upgrading anything.) It's a no-name Chinese brand, but who cares? It's not like anything in this house is even trying to saturate 1GbE, much less 2.5GbE. So QoS or whatever on an internal network doesn't seem particularly useful.
I guess I could try to segregate the Internet of Shit devices I have (they're already on their own WiFi SSID which is most of the battle) but I mostly fight that fight by owning as few IoS things as I can.
What am I missing? Why bother with managed switches at home?
If your WiFi doesn't have client isolation, IoT devices can still scan your network. WiFi client isolation will prevent that, having them on separate VLAN also makes sense.
Another usecase is a Guest network, when friends come over. You might not want to isolate clients there and allow devices to talk to each other, but also don't interfere with your home network.
If you work from home, depending on what you do, you might want to have 'office' VLAN. Or a 'Kids' VLAN, where internet turns off every night at 8pm.
At this point, it may be easier to QoS and give only 10% of your internet bandwidth to Guest network, and 5% to IoT device network, etc.
- IoT
- Personal
- Work
- Kids/guests
- Lab
The first four have their own WiFi SSID.
I don't want various cameras/sensors/lightbulbs that rarely get updates to have access to my personal network.
I don't want to mix personal use with work use (I work from home).
In a similar vein, I trust my kids about as much as I trust random IoT devices.
The lab network is just random stuff, like an archive team warrior vm that I have running.
I could do everything on one single network, but if a single host or device is compromised everything is, and I'm too paranoid to run like that.
rossant•5h ago