The main practical difference between a legacy hub and a switch is that the switch will do its best to forward ethernet frames only on the port allowing to reach the recipient, it won’t blindly forward everything everywhere as as a dumb hub would do.
To achieve this, upon reception of a frame the switch stores the senders MAC address associated to its input port in an internal memory, usually implemented as a CAM table. Thanks to this information, would a packet have the same address as recipient, the switch will now forward this packet only to this port and not the other ones.
I already wrote a more focused article on MAC table overflow within the context
of GNS3 simulated environments, which resulted in patch being submitted
upstream and initiated the development of the macof.py
tool.
The original article is available here.
In this article I detailed …