An Ethernet hub, active hub, network hub, repeater hub, multiport repeater or hub is a device for connecting multiple Ethernet devices together and making them act as a single network segment. It has multiple input/output (I/O) ports, in which a signal introduced at the input of any port appears at the output of every port except the original incoming. A hub works at the physical layer (layer 1) of the OSI model. The device is a form of multiport repeater. Repeater hubs also participate in collision detection, forwarding a jam signal to all ports if it detects a collision.
Some hubs may also come with a BNC and/or Attachment Unit Interface (AUI) connector to allow connection to legacy 10BASE2 or 10BASE5 network segments. The availability of low-priced network switches has largely rendered hubs obsolete but they are still seen in 20th century installations and more specialized applications.
A network hub is an unsophisticated device in comparison with, for example, a switch. A hub does not examine or manage any of the traffic that comes through it: any packet entering any port is rebroadcast on all other ports. Effectively, it is barely aware of frames or packets and mostly operates on raw bits or symbols. Consequently, due to the larger collision domains, packet collisions are more frequent in networks connected using hubs than in networks connected using more sophisticated devices.
100 Mbit/s hubs and repeaters come in two different speed grades: Class I delay the signal for a maximum of 140 bit times (enabling translation between 100Base-TX, 100Base-FX and 100Base-T4) and Class II hubs delay the signal for a maximum of 92 bit times (enabling installation of two hubs in a single collision domain).
The need for hosts to be able to detect collisions limits the number of hubs and the total size of a network built using hubs (a network built using switches does not have these limitations). For 10 Mbit/s networks built using repeater hubs, the 5-4-3 rule must be followed: up to 5 segments (4 hubs) are allowed between any two end stations. For 10BASE-T networks, up to five segments and four repeaters are allowed between any two hosts. For 100 Mbit/s networks, the limit is reduced to 3 segments (2 hubs) between any two end stations, and even that is only allowed if the hubs are of Class II. Some hubs have manufacturer specific stack ports allowing them to be combined in a way that allows more hubs than simple chaining through Ethernet cables, but even so, a large fast Ethernet network is likely to require switches to avoid the chaining limits of hubs.
Most hubs detect typical problems, such as excessive collisions and jabbering on individual ports, and partition the port, disconnecting it from the shared medium. Thus, hub-based twisted-pair Ethernet is generally more robust than coaxial cable-based Ethernet (e.g. 10BASE2), where a misbehaving device can adversely affect the entire collision domain. Even if not partitioned automatically, a hub simplifies troubleshooting because hubs remove the need to troubleshoot faults on a long cable with multiple taps; status lights on the hub can indicate the possible problem source or, as a last resort, devices can be disconnected from a hub one at a time much more easily than from a coaxial cable.
Hubs are classified as physical layer devices in the OSI model. At the physical layer, hubs support little in the way of sophisticated networking. Hubs do not read any of the data passing through them and are not aware of their source or destination addressing. A hub simply receives incoming Ethernet frames, regenerates the electrical signal on the bit (more precisely the symbol) level, and broadcasts these symbols out to all other devices on the network.
To pass data through the repeater in a usable fashion from one segment to the next, the framing and data rate must be the same on each segment. This means that a repeater cannot connect an 802.3 segment (Ethernet) and an 802.5 segment (Token Ring) or a 10 MBit/s segment to 100 MBit/s Ethernet.
In the early days of fast Ethernet, Ethernet switches were relatively expensive devices. Hubs suffered from the problem that if there were any 10BASE-T devices connected then the whole network needed to run at 10 Mbit/s. Therefore a compromise between a hub and a switch was developed, known as a dual-speed hub. These devices consist of an internal two-port switch, bridging the 10 Mbit/s and 100 Mbit/s segments. The device would typically consist of more than two physical ports. When a network device becomes active on any of the physical ports, the device attaches it to either the 10 Mbit/s segment or the 100 Mbit/s segment, as appropriate. This obviated the need for an all-or-nothing migration to fast Ethernet networks. These devices are considered hubs because the traffic between devices connected at the same speed is not switched.
Historically, the main reason for purchasing hubs rather than switches was their price. This motivator has largely been eliminated by reductions in the price of switches, but hubs can still be useful in special circumstances:
- For inserting a protocol analyzer into a network connection, a hub is an alternative to a network tap or port mirroring.
- When a switch is accessible for end users to make connections, for example, in a conference room, an inexperienced or careless user (or saboteur) can bring down the network by connecting two ports together, causing a switching loop. This can be prevented by using a hub, where a loop will break other users on the hub, but not the rest of the network (more precisely, it will break the current collision domain up to the next switch/bridge port). This hazard can also be avoided by using switches that can detect and deal with loops, for example by implementing the spanning tree protocol.
- A hub with a 10BASE2 port can be used to connect devices that only support 10BASE2 to a modern network. The same goes for linking in an old 10BASE5 network segment using an AUI port on a hub. Individual devices that were intended for 10BASE5 can also be linked to modern Ethernet by using an AUI-10BASE-T transceiver.
- Dean, Tamara (2010). Network+ Guide to Networks. Delmar. pp. 256–257.
- Hallberg, Bruce (2010). Networking: A Beginner's Guide, Fifth Edition. McGraw Hill. pp. 68–69.
- "What is the difference between Class I and Class II hubs?" Intel. Retrieved 2011-03-16.
- Charles Spurgeon (2000-02-16). "Chapter 13: Multi-Segment Configuration Guidelines". Ethernet: The Definitive Guide. ISBN 978-1-56592-660-8. Retrieved 2012-01-08. "The transmission path permitted between any two DTEs may consist of up to five segments, four repeater sets (including optional AUIs), two MAUs, and two AUIs."
- "Sniffing Tutorial part 1 - Intercepting Network Traffic". NETRESEC Network Security Blog. 2011-03-11. Retrieved 2011-03-13.