1.4.1 Bus

Concept of the Bus Topology

In a bus topology, all devices share a single main communication line that runs across the network. You can imagine this as a single long cable with multiple computers connected along its length. Every device taps into the same central cable, often called the bus or backbone.

When one device sends data, it places the signal onto this main cable. The signal travels along the bus and passes by every device. Each device checks whether the data is meant for it, and only the intended recipient accepts and processes the data. All other devices ignore it.

Bus topology was common in early local networks because it was simple and inexpensive to build. Today it is mostly of historical or educational interest, but the concept is still important for understanding how shared media networks work.

Physical Layout and Logical Operation

Physically, a traditional bus network used a single coaxial cable that ran in a straight line through a room, building, or floor. Nodes, such as computers or printers, attached to this cable either directly or through connectors that pierced the cable.

Logically, the bus acts as a shared communication medium. At any given moment, all devices listen to the same cable. When a device wants to send data, it must first check if the cable is idle. If the cable is free, it starts transmitting. The signal propagates along the bus in both directions until it reaches the physical ends of the cable.

Because the bus is shared, only one successful transmission can happen at a time. If two devices start sending at the same time, their signals overlap and interfere. This causes a collision, which corrupts the data and requires retransmission according to rules that belong to another chapter.

Termination and Signal Reflections

A crucial physical detail of a bus topology is termination. At each physical end of the bus cable, a terminator is installed. This is a resistor that absorbs the signal when it reaches the end of the cable.

Without proper termination, the signal would hit the end of the cable and reflect back in the opposite direction. These reflections would mix with new signals and create noise on the cable, which would damage communication.

Terminators also define where the bus begins and ends. The bus should not simply be “cut” or left open at any point. Any break in the cable, whether accidental or intentional, acts like a missing terminator and can stop the network from working.

Addressing and Broadcast on a Bus

Because every device on a bus hears every transmission, addressing is essential. Each device has a unique address at a suitable layer, and data frames or packets include a destination address.

When a frame is sent, all devices receive it from the bus. Each device compares the destination address inside the frame with its own address. If the addresses match, the device processes the frame. Otherwise, it discards it.

This method also makes broadcast communication simple. To send a message to all devices, the sender uses a special broadcast address. All devices accept frames addressed to this broadcast value. On a bus topology, broadcast traffic reaches every device automatically because the medium is shared.

Shared Medium and Collisions

The most characteristic property of a bus topology is that the medium is shared. There is only one main cable and all attached devices compete for its use. This competition creates several important behaviors.

Only one device can successfully transmit at a time. If two devices transmit simultaneously, their signals overlap and interrupt each other. This event is called a collision. When a collision occurs, none of the transmitted data is usable and the devices must try again later.

To reduce collisions, devices use a set of rules that coordinate access to the shared bus. These rules specify how to check if the cable is idle, how to detect a collision, and how long to wait before trying again. The details of these mechanisms are covered in other chapters, but they are tied closely to the bus topology because of the shared nature of the medium.

As more devices are added to the bus, the chance that two devices will want to transmit at the same time increases. This raises the collision rate and lowers the effective throughput for everyone.

Advantages of Bus Topology

Bus topology has several advantages that made it attractive in early networking:

It is simple to understand and visualize. One main cable with devices attached along it is easy to imagine and explain.

It is relatively cheap for small networks. Only one long main cable and connectors are required. There is no need for central active devices in the basic form of a bus topology.

It uses less cable than some other topologies for the same number of devices and physical distance. There are no separate cables running back to a central point for each node.

It is easy to add a new device in theory. A technician can attach a new node to the existing bus at a convenient location, provided the physical and electrical requirements are followed.

For small, low traffic networks, the performance can be acceptable. With few devices and light usage, collisions occur rarely and the shared medium is not a serious bottleneck.

Disadvantages and Limitations

Despite its simplicity, the bus topology has several important disadvantages that led to its decline in modern networks.

First, a single point of failure exists in the main cable. If the bus cable is physically cut, damaged, or unplugged, the network can fail completely or at least split into unusable segments. Because signals must travel along the bus to reach all devices, any break interrupts this flow.

Second, troubleshooting can be difficult. Finding the exact point of a cable fault along a long bus is not trivial. A loose connector or faulty terminator anywhere along the cable can bring down the entire network or cause intermittent errors that are hard to trace.

Third, performance does not scale well. As more devices join, more collisions occur, and each device must wait longer to obtain access to the cable. The shared bandwidth is divided among all active users, and the effective throughput per device drops as usage grows.

Fourth, there is limited flexibility in layout. The bus must be a single continuous cable. Extending it to new areas can require significant re-cabling. Physical obstacles and building structures may make a neat bus difficult to maintain.

Fifth, the cable length is limited. Physical and electrical properties restrict the maximum length of the bus. Beyond a certain distance, signals become too weak and distorted, even with terminators, which restricts the size of a pure bus network.

Because of these weaknesses, bus topologies are rarely used for new designs. More robust and scalable topologies have replaced them in most environments.

Bus Topology Compared With Other Topologies

When compared to a star topology, bus topology uses less cable and does not require a central active device such as a switch, but it is less reliable. In a star topology, the failure of one cable usually affects only the single connected device, while the others remain online. In a bus topology, a cable problem can impact the entire network segment.

Compared to a ring topology, the bus does not require data to pass sequentially through each device in a closed loop. Instead, all devices listen to the same shared medium. However, both topologies share a sensitivity to cable problems, because a break at the wrong point can affect many devices.

A mesh topology can provide multiple paths and high fault tolerance, which a bus cannot. Bus topology is much simpler but offers almost no redundancy.

In modern practice, bus concepts survive mostly inside other technologies that internally use shared media or logical buses, even when the physical layout is different.

Historical Context and Modern Relevance

Bus topology was popular in early Ethernet networks that used coaxial cable. Several hosts were connected along a single cable, and terminators were attached at each end. Over time, this design gave way to star based Ethernet with twisted pair cables and central switches, which offer better reliability and scalability.

Although you are unlikely to design or deploy a new physical bus network today, understanding bus topology remains valuable for several reasons. It clarifies the behavior of shared media networks, explains the origin of certain Ethernet access methods, and provides a foundation for understanding collision domains that appear in later chapters.

Some modern technologies still use bus like behavior internally, even when individual devices are not visibly arranged along a single cable. Learning the bus topology prepares you to recognize shared medium behavior in these systems and to anticipate the limitations that come with it.