Difference between revisions of "Bridge"
(Expand description somewhat) |
m (→External links: +How Engineers at Digital Equipment Corp. Saved Ethernet - excellent history article) |
||
| Line 1: | Line 1: | ||
A '''bridge''' is a type of [[packet switch]] which is fundamentally different from a [[router]]. It effectively unifies two otherwise separate [[physical network]]s; a [[host]] sending a [[packet]] cannot tell whether the destination [[network interface]] is on the same physical network as it is, or on another one, which is connected to its physical network through a bridge. The two physical networks must thus share a unified [[address space]]. | A '''bridge''' is a type of [[packet switch]] which is fundamentally different from a [[router]]. It effectively unifies two otherwise separate [[physical network]]s; a [[host]] sending a [[packet]] cannot tell whether the destination [[network interface]] is on the same physical network as it is, or on another one, which is connected to its physical network through a bridge. The two physical networks must thus share a unified [[address space]]. | ||
| − | The bridge thus operates on the [[protocol stack]] layer beneath the [[internetworking layer]]; bridges usually have no knowledge of that layer. A bridge operates mostly invisibly, and do not have its own address on the physical networks (although it may have one for | + | The bridge thus operates on the [[protocol stack]] layer beneath the [[internetworking layer]]; bridges usually have no knowledge of that layer. A bridge operates mostly invisibly, and do not have its own address on the physical networks (although it may have one for [[operation and maintenance]] purposes). |
| − | [[operation and maintenance]] purposes). | ||
A bridge thus needs no configuration; one merely plugs it in, and as soon as it is powered on, it starts to operate. (Hence the saying that "The advantage of a bridge is that it looks like a wire, but it isn't. The ''disadvantage'' of a bridge is that it looks like a wire, but it isn't.") | A bridge thus needs no configuration; one merely plugs it in, and as soon as it is powered on, it starts to operate. (Hence the saying that "The advantage of a bridge is that it looks like a wire, but it isn't. The ''disadvantage'' of a bridge is that it looks like a wire, but it isn't.") | ||
{{semi-stub}} | {{semi-stub}} | ||
| + | |||
| + | ==External links== | ||
| + | |||
| + | * [https://spectrum.ieee.org/how-dec-engineers-saved-ethernet How Engineers at Digital Equipment Corp. Saved Ethernet: Their groundbreaking learning bridge technology increased LAN performance] - the sub-heading has it wrong, but the article is excellent | ||
[[Category: Networking Basics]] | [[Category: Networking Basics]] | ||
Latest revision as of 22:05, 6 January 2025
A bridge is a type of packet switch which is fundamentally different from a router. It effectively unifies two otherwise separate physical networks; a host sending a packet cannot tell whether the destination network interface is on the same physical network as it is, or on another one, which is connected to its physical network through a bridge. The two physical networks must thus share a unified address space.
The bridge thus operates on the protocol stack layer beneath the internetworking layer; bridges usually have no knowledge of that layer. A bridge operates mostly invisibly, and do not have its own address on the physical networks (although it may have one for operation and maintenance purposes).
A bridge thus needs no configuration; one merely plugs it in, and as soon as it is powered on, it starts to operate. (Hence the saying that "The advantage of a bridge is that it looks like a wire, but it isn't. The disadvantage of a bridge is that it looks like a wire, but it isn't.")
External links
- How Engineers at Digital Equipment Corp. Saved Ethernet: Their groundbreaking learning bridge technology increased LAN performance - the sub-heading has it wrong, but the article is excellent
