Jump to content

Network bridge

From Wikipedia, the free encyclopedia
(Redirected from Bridging (networking))

A high-level overview of network bridging, using the ISO/OSI layers and terminology

A network bridge is a computer networking device that creates a single, aggregate network from multiple communication networks or network segments. This function is called network bridging.[1] Bridging is distinct from routing. Routing allows multiple networks to communicate independently and yet remain separate, whereas bridging connects two separate networks as if they were a single network.[2] In the OSI model, bridging is performed in the data link layer (layer 2).[3] If one or more segments of the bridged network are wireless, the device is known as a wireless bridge.

The main types of network bridging technologies are simple bridging, multiport bridging, and learning or transparent bridging.[4][5]

Transparent bridging

[edit]

Transparent bridging uses a table called the forwarding information base to control the forwarding of frames between network segments. The table starts empty and entries are added as the bridge receives frames. If a destination address entry is not found in the table, the frame is forwarded to all other ports of the bridge, flooding the frame to all segments except the one from which it was received. By means of these flooded frames, a host on the destination network will respond and a forwarding database entry will be created. Both source and destination addresses are used in this process: source addresses are recorded in entries in the table, while destination addresses are looked up in the table and matched to the proper segment to send the frame to.[6] Digital Equipment Corporation (DEC) originally developed the technology in 1983[7] and introduced the LANBridge 100 that implemented it in 1986. [8]

In the context of a two-port bridge, the forwarding information base can be seen as a filtering database. A bridge reads a frame's destination address and decides to either forward or filter. If the bridge determines that the destination host is on another segment on the network, it forwards the frame to that segment. If the destination address belongs to the same segment as the source address, the bridge filters the frame, preventing it from reaching the other network where it is not needed.

Transparent bridging can also operate over devices with more than two ports. As an example, consider a bridge connected to three hosts, A, B, and C. The bridge has three ports. A is connected to bridge port 1, B is connected to bridge port 2, C is connected to bridge port 3. A sends a frame addressed to B to the bridge. The bridge examines the source address of the frame and creates an address and port number entry for host A in its forwarding table. The bridge examines the destination address of the frame and does not find it in its forwarding table so it floods (broadcasts) it to all other ports: 2 and 3. The frame is received by hosts B and C. Host C examines the destination address and ignores the frame as it does not match with its address. Host B recognizes a destination address match and generates a response to A. On the return path, the bridge adds an address and port number entry for B to its forwarding table. The bridge already has A's address in its forwarding table so it forwards the response only to port 1. Host C or any other hosts on port 3 are not burdened with the response. Two-way communication is now possible between A and B without any further flooding to the network. Now, if A sends a frame addressed to C, the same procedure will be used, but this time the bridge will not create a new forwarding-table entry for A's address/port because it has already done so.

Bridging is called transparent when the frame format and its addressing aren't changed substantially. Non-transparent bridging is required especially when the frame addressing schemes on both sides of a bridge are not compatible with each other, e.g. between ARCNET with local addressing and Ethernet using IEEE MAC addresses, requiring translation. However, most often such incompatible networks are routed in between, not bridged.

Simple bridging

[edit]

A simple bridge connects two network segments, typically by operating transparently and deciding on a frame-by-frame basis whether or not to forward from one network to the other. A store and forward technique is typically used so, as part of forwarding, the frame integrity is verified on the source network and CSMA/CD delays are accommodated on the destination network. In contrast to repeaters which simply extend the maximum span of a segment, bridges only forward frames that are required to cross the bridge. Additionally, bridges reduce collisions by creating a separate collision domain on either side of the bridge.

Multiport bridging

[edit]

A multiport bridge connects multiple networks and operates transparently to decide on a frame-by-frame basis whether to forward traffic. Additionally, a multiport bridge must decide where to forward traffic. Like the simple bridge, a multiport bridge typically uses store and forward operation. The multiport bridge function serves as the basis for network switches.

Implementation

[edit]

The forwarding information base stored in content-addressable memory (CAM) is initially empty. For each received Ethernet frame the switch learns from the frame's source MAC address and adds this together with an interface identifier to the forwarding information base. The switch then forwards the frame to the interface found in the CAM based on the frame's destination MAC address. If the destination address is unknown the switch sends the frame out on all interfaces (except the ingress interface). This behavior is called unicast flooding.

Forwarding

[edit]

Once a bridge learns the addresses of its connected nodes, it forwards data link layer frames using a layer-2 forwarding method. There are four forwarding methods a bridge can use, of which the second through fourth methods were performance-increasing methods when used on switch products with the same input and output port bandwidths:

  1. Store and forward: the switch buffers and verifies each frame before forwarding it; a frame is received in its entirety before it is forwarded.
  2. Cut through: the switch starts forwarding after the frame's destination address is received. There is no error checking with this method. When the outgoing port is busy at the time, the switch falls back to store-and-forward operation. Also, when the egress port is running at a faster data rate than the ingress port, store-and-forward is usually used.
  3. Fragment free: a method that attempts to retain the benefits of both store and forward and cut through. Fragment free checks the first 64 bytes of the frame, where addressing information is stored. According to Ethernet specifications, collisions should be detected during the first 64 bytes of the frame, so frame transmissions that are aborted because of a collision will not be forwarded. Error checking of the actual data in the packet is left for the end device.
  4. Adaptive switching: a method of automatically selecting between the other three modes.[9][10]

Shortest Path Bridging

[edit]

Shortest Path Bridging (SPB), specified in the IEEE 802.1aq standard and based on Dijkstra's algorithm, is a computer networking technology intended to simplify the creation and configuration of networks, while enabling multipath routing.[11][12][13] It is a proposed replacement for Spanning Tree Protocol which blocks any redundant paths that could result in a switching loop. SPB allows all paths to be active with multiple equal-cost paths. SPB also increases the number of VLANs allowed on a layer-2 network.[14]

TRILL (Transparent Interconnection of Lots of Links) is the successor to Spanning Tree Protocol, both having been created by the same person, Radia Perlman. The catalyst for TRILL was an event at Beth Israel Deaconess Medical Center which began on 13 November 2002.[15][16] The concept of Rbridges[17] [sic] was first proposed to the Institute of Electrical and Electronics Engineers in the year 2004,[18] whom in 2005[19] rejected what came to be known as TRILL, and in the years 2006 through 2012[20] devised an incompatible variation known as Shortest Path Bridging.

See also

[edit]
  • Audio Video Bridging – Specifications for synchronized, low-latency streaming through IEEE 802 networks
  • IEEE 802.1D – Standard which includes bridging, Spanning Tree Protocol and others
  • IEEE 802.1Q – IEEE networking standard supporting VLANs
  • IEEE 802.1ah-2008 – Standard for bridging over a provider's network
  • Promiscuous mode – Network interface controller mode that eavesdrops on messages intended for others

References

[edit]
  1. ^ "Traffic regulators: Network interfaces, hubs, switches, bridges, routers, and firewalls" (PDF). Cisco Systems. September 14, 1999. Archived from the original (PDF) on May 31, 2013. Retrieved July 27, 2012.
  2. ^ "What is a Network Switch vs. a Router?". Cisco Systems. Retrieved July 27, 2012.
  3. ^ Decker, Eric B.; Langille, Paul; McCloghrie, Keith; Rijsinghani, Anil (July 14, 1989). "RFC 1286 - Definitions of Managed Objects for Bridges". Tools.ietf.org. Retrieved October 19, 2013.
  4. ^ "Local Area Networks: Internetworking". manipalitdubai.com. Archived from the original (PowerPoint) on May 13, 2014. Retrieved December 2, 2012.
  5. ^ "Bridging Protocols Overview" (PowerPoint). iol.unh.edu. Retrieved December 2, 2012.
  6. ^ "Transparent Bridging". Cisco Systems, Inc. Archived from the original on November 21, 2015. Retrieved June 20, 2010.
  7. ^ US 4597078, "Bridge circuit for interconnecting networks" 
  8. ^ "How Engineers at Digital Equipment Corp. Saved Ethernet". IEEE Spectrum. April 7, 2024. Retrieved April 10, 2024.
  9. ^ Dong, Jielin (2007). Network Dictionary. Javvin Technologies Inc. p. 23. ISBN 9781602670006. Retrieved June 25, 2016.
  10. ^ "Cray makes its Ethernet switches responsive to net conditions". IDG Network World Inc. July 1, 1996. Retrieved June 25, 2016.
  11. ^ "Alcatel-Lucent, Avaya, Huawei, Solana and Spirent Showcase Shortest Path Bridging Interoperability". Huawei. September 7, 2011. Retrieved September 11, 2011.
  12. ^ Luo, Zhen; Suh, Changjin (March 3, 2011). "An improved shortest path bridging protocol for Ethernet backbone network". The International Conference on Information Networking 2011 (ICOIN2011). IEEE Xplore. pp. 148–153. doi:10.1109/ICOIN.2011.5723169. ISBN 978-1-61284-661-3. ISSN 1976-7684. S2CID 11193141.
  13. ^ "Lab Testing Summary Report; Data Center Configuration with SPB" (PDF). Miercom. September 2011. Retrieved December 25, 2011.
  14. ^ Shuang Yu. "IEEE approves new IEEE 802.1aq™ Shortest path bridging". IEEE Standards Association. Archived from the original on May 14, 2013. Retrieved June 19, 2012. Using the IEEE's next-generation VLAN, called a Service Interface Identifier (I-SID), it is capable of supporting 16 million unique services compared to the VLAN limit of four thousand.
  15. ^ "All Systems Down" (PDF). cio.com. IDG Communications, Inc. Archived from the original (PDF) on September 23, 2020. Retrieved January 9, 2022.
  16. ^ "All Systems Down". cio.com. IDG Communications, Inc. Archived from the original on January 9, 2022. Retrieved January 9, 2022.
  17. ^ "Rbridges: Transparent Routing" (PDF). courses.cs.washington.edu. Radia Perlman, Sun Microsystems Laboratories. Archived from the original (PDF) on January 9, 2022. Retrieved January 9, 2022.
  18. ^ "Rbridges: Transparent Routing". researchgate.net. Radia Perlman, Sun Microsystems; Donald Eastlake 3rd, Motorola.
  19. ^ "TRILL Tutorial" (PDF). postel.org. Donald E. Eastlake 3rd, Huawei.
  20. ^ "IEEE 802.1: 802.1aq - Shortest Path Bridging". ieee802.org. Institute of Electrical and Electronics Engineers.
Retrieved from "https://en.wikipedia.org/w/index.php?title=Network_bridge&oldid=1242622960"