Friday, October 17, 2008

Bridge

1. In classic terms, a bridge is a data communications device that connects two or more network segments and forwards packets between them. Such bridges operate at Layer 1 (Physical Layer) of the OSI Reference Model. At this level, a bridge simply serves as a physical connector between segments, also amplifying the carrier signal in order to compensate for the loss of signal strength incurred as the signal is split across the bridged segments. In other words, the bridge is used to connect multiple segments of a single logical circuit. Classic bridges are relatively dumb devices, which are fast and inexpensive; they simply accept data packets, perhaps buffering them during periods of network congestion and forward them. Bridges are protocol-specific, e.g., Ethernet or Token Ring in the LAN domain. Bridges also are used in the creation of multipoint circuits in the WAN domain, e.g., DDS (Dataphone Digital Service).

Bridges also can operate at Layer 2 (Link Layer) of the OSI Reference Model. At this level, a bridge connects disparate LANs (e.g., Ethernet and Token Ring) at the Medium Access Control (MAC) sub-layer of Layer 2. In order to accomplish this feat, the MAC Bridge may be of two types, encapsulating or translating.

Encapsulating bridges accept a data packet from one network and in its native format; they then encapsulate, or envelope, that entire packet in the format acceptable to the target network. For instance, an Ethernet frame is encapsulated in a Token Ring packet in order that the Token Ring network can deliver it to the target device, which must strip away several layers of overhead information in order to get to the data payload, or content. In order to accomplish this process, a table lookup must take place in order to change basic MAC-level addressing information.

Translating bridges go a step further. Rather than simply encapsulating the original data packet, they actually translate the data packet into the native format of the target network and attached device. While this level of translation adds a small amount of delay to the packet traffic and while the cost of such a bridge is slightly greater, the level of processing required at the workstation level is much reduced.

Bridges also can serve to reduce LAN congestion through a process of filtering. A filtering bridge reads the destination address of a data packet and performs a quick table lookup in order to determine whether it should forward that packet through a port to a particular physical LAN segment. A four-port bridge, for instance, would accept a packet from an incoming port and forward it only to the LAN segment on which the target devices is connected; thereby, the traffic on the other two segments is reduced and the level of traffic on those segments is reduced accordingly. Filtering bridges may be either programmed by the LAN administrator or may be self-learning. Self-learning bridges "learn" the addresses of the attached devices on each segment by initiating broadcast query packets, and then remembering the originating addresses of the devices which respond. Self-learning bridges perform this process at regular intervals in order to repeat the "learning" process and, thereby, to adjust to the physical relocation of devices, the replacement of NICs (Network Interface Cards), and other changes in the notoriously dynamic LAN environment.

While bridges are relatively simple devices, in the overall scheme of things, they can get quite complex as we move up the bridge food chain. Bridges also can be classified as Spanning Tree Protocol (STP), Source Routing Protocol (SRP), and Source Routing Transparent (SRT).
Spanning Tree Protocol (STP) bridges, defined in the IEEE 802.1 standard, are self-learning, filtering bridges. Some STP bridges also have built-in security mechanisms which can deny access to certain resources on the basis of user and terminal ID. STP bridges can automatically reconfigure themselves for alternate paths should a network system fail.

SRP bridges are programmed with specific routes for each data packet. Routing considerations include physical node location and the number of hops (intermediate bridges) involved. This IBM bridge protocol provides for a maximum of 13 hops.

SRT bridges, defined in IEEE 802.1, are a combination of STP and SRP. SRT bridges can act in either mode, as programmed.



2. Bridge is also a verb, as in "to bridge." Imagine a phone line. It winds from your CO (Central Office) through the streets and over the poles to your phone. Now imagine you want to connect another phone to that line. A phone works on two wires, tip and ring (positive and negative). You simply clamp each one of the phone's wires to the cable coming in. That's called bridging. Imagine bridging as connecting a phone at a right angle. When you do that, you've made what's known as a "bridged tap." The first thing to know about bridging is that bridging causes the electrical current coming down the line to lose power. How much? That typically depends on the distance from the bridged tap to the phone. A few feet, and there's no significant loss. But that bridged tap can also be thousands of feet. For example, the phone company could have a bridged tap on your local loop, which joined to another long-defunct subscriber. The phone company technicians simply saved a little time by not disconnecting that tap. If you want the cleanest, loudest phone line, the local loop to your phone should not be bridged. Instead it should be a direct "home run" from your CO to your phone.

Bridging can be a real problem with digital circuits. Circuits above 1 Mbps (e.g, T-1) should never, ever be bridged. Because of the power loss, they simply won't work or will work so poorly they won't be worth having. ISDN BRI (Integrated Services Digital Network Basic Rate Interface) channels are also digital. But they were specifically designed to work with the existing telephone cable plant, which has a huge number of bridged circuits. Telephone companies typically will install ISDN BRI circuits with up to six bridged taps and about 6,000 feet of bridged cabling.

No comments: