Network Bridges (Layer-2 Networking) and Their Types

A bridge is a Layer 2 networking device that connects multiple network segments (LANs) and forwards frames based primarily on MAC addresses.

Operationally, a bridge:

• Receives frames from one port (segment)
• Learns which source MAC addresses are reachable via which port using a MAC address table
• Filters frames when the destination is on the same port (does not forward)
• Forwards frames to the correct port when the destination is on a different port
• Floods frames when the destination MAC is unknown (sends to all ports except the ingress)

This behavior improves efficiency compared with hubs (which typically broadcast/flood everything) and reduces unnecessary traffic by limiting where frames travel within the LAN.

Mermaid overview of frame handling:

Key concepts and terminology

• MAC address table: Stores learned source MAC → port mappings.
• Filtering: Done when destination MAC is on the same port as the ingress.
• Flooding: Common for new/unknown destinations.
• Transparent behavior: Typically used by IEEE 802.1D-style bridges.

Why bridges matter (vs. hubs and beyond)

A bridge reduces wasted traffic by localizing broadcasts/unknown-destination traffic to only the relevant segments via learning and per-port forwarding decisions.

In practice, bridges are also important foundations for:

• Segmenting LANs
• Supporting multiple collision domains (classic Ethernet bridge behavior)
• Enabling spanning-tree-based loop prevention (in many Ethernet deployments)

Spanning Tree Protocol (STP) prevents Layer 2 loops in bridged/switching networks (notably in Ethernet bridging with multiple paths).

Types of Network Bridges

Network bridges are commonly categorized by how they determine paths/forwarding decisions and/or by the historical forwarding model.

1) Transparent Bridge (IEEE 802.1D / “learning bridge”)

A transparent bridge behaves as described in the learning + filtering + flooding process: it is “transparent” to hosts because end devices do not need special configuration.

Behavior highlights

• Learns MAC addresses dynamically from frame source addresses
• Forwards based on destination MAC table entries
• Floods on unknown destinations
• Typically pairs with loop prevention mechanisms like STP

2) Source Routing Bridge

A source routing bridge relies on routing information carried by frames themselves. Instead of the bridge learning “destination MAC → port” in the same way as transparent bridging, the forwarding behavior follows route/segment information included in the frame.

Behavior highlights

• Route information is associated with frames (sender-driven routing)
• Bridges make forwarding decisions based on that embedded route context

Source-routing concepts appear in historical enterprise LAN designs such as token ring environments.

3) Translational / Protocol-Interworking Bridge (conceptual category)

Some references describe bridges that interconnect different LAN technologies or frame formats. In such cases, the device may need to translate or adapt between environments.

Behavior highlights

• Connects dissimilar LAN types
• May require frame format adaptation or mapping

(Modern “switches/routers” often handle most of these roles, but the bridging concept remains relevant.)

4) Composite / Hybrid Bridge (combination behavior)

A hybrid bridge may implement multiple forwarding modes or blend learning-based and other route-based mechanisms depending on the environment.

Behavior highlights

• Useful when networks combine different assumptions/technologies

Summary table (what differs across bridge types)