Local Network Bridge Component Description The Network Bridge component is a driver that transparently connects two or more network segments so that hosts on those segments identify the resulting internetwork as one network segment. The Network Bridge component sets up small multisegment networks where ease of configuration is more important than scalability. When using Internet Protocol (IP) on a bridged internetwork, the internetwork is treated as a single IP subnet, eliminating the need to configure IP routing.

The network bridge supports any network interface that is an Ethernet media type and uses standard Ethernet framing. In addition, the network bridge supports IP over 1394 segments with the Microsoft IP1394 driver.

The network bridge implements the spanning tree algorithm as described in IEEE 802.1D-1990. When hardware permits, the spanning tree algorithm functions as a Media Access Control (MAC) bridge as described in the specification. When the network bridge operates over hardware that does not support promiscuous send and receive operations, such as many wireless adapters, it only supports IP and uses Address Resolution Protocol (ARP) to transparently connect network segments.

Component Configuration

The bridge is implemented as a Network Driver Interface Specification (NDIS) intermediate network driver. As such, it functions as both a network protocol and a network miniport, also known as a virtual adapter. To operate correctly, the bridge must be bound to two or more network adapters. All components other than the network bridge should be unbound from bridged adapters. Protocols and services that the user wishes to operate over the bridged segments should be bound to the virtual adapter exposed by the network bridge. The tools that allow network protocols, such as TCP/IP, to be bound or unbound from particular network adapters also enable binding operations with the bridge.

Once bound, the network bridge requires no additional configuration.

Special Notes

The HNetMon component can be used to force the network bridge to operate in layer 3, for IP-only, mode. This is necessary for certain network adapters that incorrectly report that they support promiscuous send and receive.

]]> %12% bridge.sys False Layer Two Bridge Intermediate Driver Layer Two Ethernet, and IP Bridge File ndis.sys File netbrdgm.inf File netbrdgs.inf {00000000-0000-0000-0000-000000000000} File snetcfg.exe Dependency upon 'snetcfg.exe' Local Network Bridge 1.0 Layer Two Ethernet, and IP Bridge 2000 Microsoft Corp. Microsoft Corp. maiken billi;rgatta; paulclap 3/5/2001 11/3/2001 4:47:32 AM