OS/2 Shareware BBS: 8 Other

home *** CD-ROM | disk | FTP | other *** search

/ OS/2 Shareware BBS: 8 Other / 08-Other.zip / NBR11I.ZIP / NBRIDGE.DOC < prev next >

Wrap

Text File | 1992-11-12 | 39KB | 1,105 lines

NBridge.Doc for NIC Bridge Version 1.1i Nov 12 1992 Copyright (c) Eighth Layer Systems 1990-1992. All rights reserved. Warning: The possibility of file corruption exists when using any software. Please take whatever steps are required to protect vital files. This documentation is formatted with 23 line pages. It contains IBM PC type block graphics characters. ┌──────────┐ │ CONTENTS │ └──────────┘ RELEASE NOTES.................................................. 4 INTRODUCTION............Definitions............................ 5 Files Included......................... 6 NBridge Drivers........................ 10 SRTok Drivers.......................... 11 NBr Bridge Utility..................... 14 NicSetup Setup Utility................. 15 CONSIDERATIONS..........Ethernet Transparent Bridging.......... 16 Token Ring Source Routing Bridging..... 21 SETUP/MAIN CONFIGURATION....................................... 31 OPERATION...................................................... 36 NBRIDGE PARAMETERS............................................. 37 SRTOK PARAMETERS............................................... 43 ACKNOWLEDGEMENTS............................................... 48 ┌───────────────┐ │ RELEASE NOTES │ └───────────────┘ - The Install.Exe utility can be used to upgrade recent releases of the software by installing over a previous version. - The NBridge CUSTOMFILTER parameter is now documented. - The SRTok SRBC parameter is now documented. ┌──────────────┐ │ INTRODUCTION │ └──────────────┘ ───────────── Definitions ───────────── The term "LanRoot" denotes the directory under which all network software is installed. For MS Lan Manager this is \LANMAN.DOS for DOS or \LANMAN for OS/2. For IBM Lan Server this is \IBMLAN for OS/2. NIC is a common network industry acronym for Network Interface Card. This is the Ethernet, Token Ring or other adapter which connects PCs to a network. NIC Async allows an asynchronous serial port to be used as a NIC. MAC is an acronym for Medium Access Control. Network adapter drivers are often referred to as MAC drivers. NDIS is an acronym for the Microsoft/3Com Network Driver Interface Specification. This is a software interface designed to allow multiple network protocols to control network adapter drivers. NIC Async adheres to the NDIS version 2.01 specifications. ──────────────── Files Included ──────────────── The following files are included on the Install Disk: \Readme .Doc NIC Bridge/Async introductory document \NBridge .Doc This NIC Bridge document \Tune .Doc Tuning document \Readme .Bat DOS batch file for NicDoc.Exe \Readme .Cmd OS/2 command file for NicDoc.Exe \NicDoc .Exe NIC Bridge/Async DOS & OS/2 Documentation Viewer \Install .Exe NIC Bridge/Async DOS & OS/2 Install Utility \NicSetup.Exe NIC Bridge/Async DOS & OS/2 Setup Utility \NicCfg .Exe NIC Bridge/Async DOS & OS/2 Configuration Utility \NBr .Exe NIC Bridge DOS & OS/2 Full Screen Interface \NBridge .DOS DOS NIC Bridge Driver for 386 & up \NBridge .D86 DOS NIC Bridge Driver for 8086 & up \NBridge .OS2 OS/2 NIC Bridge Driver for 386 & up on OS/2 1.2 & up \NBridge .O86 OS/2 NIC Bridge Driver for 286 & up or OS/2 1.1 \SRTok .DOS DOS Src Route Driver for 386 & up \SRTok .D86 DOS Src Route Driver for 8086 & up \SRTok .OS2 OS/2 Src Route Driver for 386 & up on OS/2 1.2 & up \SRTok .O86 OS/2 Src Route Driver for 286 & up or OS/2 1.1 \Ethern .DOS DOS Dummy Ethernet Driver \Ethern .OS2 OS/2 Dummy Ethernet Driver \Protman\Protman .DOS DOS Protocol Manager Driver \Protman\Protman .OS2 OS/2 Protocol Manager Driver \Protman\Protman .Exe DOS Protocol Manager Transient Portion \Protman\Pro .Msg Protocol Manager Message File \Protman\Proh .Msg Protocol Manager Help Message File \Protman\NetbindD.Exe DOS Protocol Manager Netbind Utility \Protman\NetbindO.Exe OS/2 Protocol Manager Netbind Utility \MSLM\Protocol.BD DOS Protocol.Ini for NIC Bridge \MSLM\Protocol.BO OS/2 Protocol.Ini for NIC Bridge \MSLM\NBridge .XD DOS 386 NBridge.Xif \MSLM\NBridge .XD8 DOS 8086 NBridge.Xif \MSLM\NBridge .XO OS/2 386 NBridge.Xif \MSLM\NBridge .XO8 OS/2 8086 NBridge.Xif \MSLM\Protocol.SD DOS Protocol.Ini for Src Route Token driver \MSLM\Protocol.SO OS/2 Protocol.Ini for Src Route Token driver \MSLM\SRTok .ND DOS 386 SRTok.Nif \MSLM\SRTok .ND8 DOS 8086 SRTok.Nif \MSLM\SRTok .NO OS/2 386 SRTok.Nif \MSLM\SRTok .NO8 OS/2 8086 SRTok.Nif ───────────────── NBridge Drivers ───────────────── The DOS and OS/2 drivers NBridge.DOS and NBridge.OS2 are the "engine" of NIC Bridge and the vast majority of work is done within them. They are NDIS protocol level drivers and can be bound to multiple MAC level drivers to provide bridging between them. They do NOT provide the NetBIOS interface that protocol drivers such as MS/IBM NetBEUI or 3Com NBP do. The NBridge drivers can be bound to a maximum of 9 MAC level drivers. These MAC level drivers may be NAsync serial port drivers, SRTok Token Ring drivers or NDIS ethernet adapter drivers. If you need support for PCs based on 80286 or lesser CPUs you will have to use the slower drivers: NBridge.D86 for DOS or NBridge.O86 for OS/2. The slower OS/2 driver is also required on OS/2 versions prior to version 1.2. ─────────────── SRTok Drivers ─────────────── The DOS and OS/2 drivers SRTok.DOS and SRTok.OS2 are required to use NIC Bridge in Source Routing mode on a Token Ring Network. The NDIS specs provide for adapter drivers to advertise themselves as providing Source Routing Bridge capability but no such drivers are readily available. These drivers provide this capability for IBM Token Ring adapters. If you need support for PCs based on 80286 or lesser CPUs you will have to use the slower drivers: SRTok.D86 for DOS or SRTok.O86 for OS/2. The slower OS/2 driver is also required on OS/2 versions prior to version 1.2. These drivers should work with all IBM Token Ring Adapters except for the original "IBM Token-Ring Adapter" and the new Bus Mastering adapter. Specifically the drivers should work with any of the following: "IBM Token-Ring Network Adapter II" "IBM Token-Ring Network Adapter II/A" "IBM Token-Ring Network 16/4 Adapter" "IBM Token-Ring Network 16/4 Adapter/A" "IBM Token-Ring Network PS/2 Model P70 386 Adapter/A" At this time the SRTok drivers have been tested and verified with the "IBM Token-Ring Network Adapter II", "IBM Token-Ring Network 16/4 Adapter" and "IBM Token-Ring Network 16/4 Adapter/A" cards. The SRTok drivers are not currently supported for any use other than with NIC Bridge. IE, no other NDIS protocol drivers may be bound to SRTok. Thus, given that only 2 IBM Token Ring Adapters may be installed in a single PC, a two port local bridge configuration with the SRTok drivers will NOT be able to act as a network workstation or server unless it does so via a non-IBM Token Ring adapter. A workstation or server may act as a remote bridge with 2 IBM Token Ring adapters: 1 for the workstation/server functions and 1 for the bridge function. The use of "RAM paging" is not currently supported by these drivers, nor is the use of shared interrupts on MCA machines. It is generally best to set the adapter for the maximum available "Shared RAM Size". This is usually 16 KBytes on 4 Megabit per second cards and 64 KBytes on 4/16 cards. ──────────────────── NBr Bridge Utility ──────────────────── The bridge utility NBr.Exe provides a full-screen interface to view NIC Bridge statistics, NDIS statistics and other information provided by the network card drivers. It runs under both DOS & OS/2. In addition to the function keys shown at the bottom of the Nbr display, shortcut keys to the menu are implemented. These include Alt-O for the Options menu, Alt-M for the Mode menu and Alt-A for the Adapter menu. ──────────────────────── NicSetup Setup Utility ──────────────────────── The setup utility NicSetup.Exe can be used to setup NIC Bridge on standalone or networked PCs. It runs under both DOS & OS/2. Please refer to the Setup & Configuration section for further details on use of the NicSetup utility. ┌────────────────┐ │ CONSIDERATIONS │ └────────────────┘ ─────────────────────────────── Ethernet Transparent Bridging ─────────────────────────────── NIC Bridge can provide MAC Level transparent bridging when used in conjunction with virtually any NDIS Ethernet driver and adapters. Installed on a PC with two Ethernet cards this can provide local bridging. With the NIC Async drivers on a PC with one Ethernet card a multi-port remote bridge can be configured. A remote bridge configuration may be used to link distant networks or to provide remote access to the local network by standalone PCs. Transparent bridging is so named because network protocol software needs no knowledge of the bridge's existence. The bridge operates by putting the Ethernet adapters into "promiscuous" mode where every network packet is seen. By monitoring these packets the bridge learns where network stations are by looking at the IEEE source addresses of the packets. When a packet must cross the bridge to reach it's destination the bridge recognises this and forwards the received packet to the proper adapter. Broadcast packets are forwarded to all adapters except the source adapter. On busy networks this constant monitoring of all packets can use all of the PC's CPU power. For this reason it is recommended that a dedicated PC be used for transparent bridging on busy networks. It is further recommended that high quality adapters and drivers be used with NIC Bridge. The high data rates that the bridge is capable of can expose rare bugs in drivers. A list of which adapters and drivers are fastest and most compatible with NIC Bridge will be compiled and maintained. Testing has been done mostly with 3Com 3C503 Etherlink II adapters. The 3C503 drivers have been found to be very stable. The promiscuous mode necessary for transparent bridging is available on most true Ethernet NDIS drivers. Many NDIS drivers which merely emulate an Ethernet driver do not support promiscuous mode however. These drivers include those for Arcnet and FDDI. Among the true Ethernet NDIS drivers included with MS Lanman 2.1 only the Spider Systems Ethernet SC-100E driver appears to lack promiscuous mode. Some Ethernet NDIS drivers provide a feature known as "Loopback". This causes an adapter driver to appear to receive packets which it has transmitted and can reduce the performance of NIC Bridge. Although they may otherwise be excellent, the drivers from Accton, DCA, Western Digital and Ungermann Bass provide Loopback and may be less than ideal for bridging. The address learning responsibility of a transparent bridge requires the use of an address table. The current version of NBridge allows a maximum of 256 network addresses to be stored. This should present no problems except on very busy, very large networks. It should be noted that the NAsync drivers on a server acting as a remote bridge may need to be bound to server protocols as well as the NBridge protocol. This is because the NBridge protocol provides remote access to the external network, but not local protocols on the PC on which it is installed. One exception to this occurs when using a second network adapter exclusively for bridging, as the second adapter provides full access to all protocols bound to the first adapter. Another potential exception occurs when the adapter driver fully supports loopback in promiscuous mode. No special parameters are required for NIC Async when used with NIC Bridge in transparent bridge mode. The [NASYNC_NIF] parameter MAC_TYPE should be set to it's default of "DIX+802.3". The following Protocol.Ini parameters are relevant for a transparent bridge configuration and are set in the [NBRIDGE_XIF] section of Protocol.Ini. ; Only allowed parameter for Drivername. DRIVERNAME = NBRIDGE$ ; "TRANSPARENT" required for transparent bridging. BRIDGEMODE = "TRANSPARENT" ; 1 Binding specified for each port of the bridge. ; This example is for a combined local and remote bridge. BINDINGS = "ELNKII_NIF", "ELNKII_NIF2, "NASYNC_NIF", "NASYNC_NIF2" ; Enables Bridging for each NIC driver. Order identical to BINDINGS. ; Allowed: "YES" or "NO". ; Default: "YES" for all. BRIDGE_MAC = YES, YES, YES, YES, YES, YES, YES, YES, YES ; Enables Packet Capture for each NIC driver. Order identical to BINDINGS. ; Allowed: "YES" or "NO". ; Default: "YES" for all. ; Recommend "NO" for high-performance production use. CAPTURE_MAC = YES, YES, YES, YES, YES, YES, YES, YES, YES ; Filters Broadcasts rcvd by each NIC driver. Order identical to BINDINGS. ; Allowed: "YES" or "NO". ; Default: "NO" for all. ; Set "YES" ONLY on local NICS to eliminate broadcast traffic. ; Note: "YES" does not allow correct operation of MS TCP/IP. FILTERBC_MAC = NO, NO, NO, NO, NO, NO, NO, NO, NO ──────────────────────────────────── Token Ring Source Routing Bridging ──────────────────────────────────── NIC Bridge provides Source Routing bridging when used in conjunction with the SRTok driver and an IBM Token Ring Adapter. Installed on a PC with two IBM Token Ring Adapters this can provide local Source Routing bridging. With the NIC Async drivers on a PC with one IBM card a multi-port remote Source Routing bridge can be configured. A remote bridge configuration may be used to link distant networks or to provide remote access to the local network by standalone PCs. Note that an IBM adapter is only required on the bridge PC. Other stations on the network can use virtually any Token Ring adapter. Source Routing Bridging is so named because the source of a network packet must explicity specify the route the packet will take through bridges. Thus the network protocol software must explicitly support Source Routing. Protocols such as MS/IBM NetBEUI support this but 3Com NBP does not. The bridge operates by putting the Token Ring adapter into Source Routing Bridge mode, where only packets needed to be forwarded by the bridge are seen. The bridge then forwards received packets to the proper adapter. Because Source Routing Bridge mode on the IBM Token Ring adapters can be set to only cause packets which need forwarding to be received, busy networks are less of a problem. It is still recommended, however, that a dedicated PC be used for Source Routing bridging on busy networks. The Source Routing architecture requires that each ring in the Token Ring inter-network be assigned a ring number from 0 to decimal 4095. The IBM scheme for Source Routing Bridging on IBM Token Ring adapters requires that the adapter be programmed with the "Local Ring Number" for the ring that adapter is connected to, and an "Other Ring Number" for the ring another adapter in the same bridge PC is connected to. This generally restricts IBM Token Ring adapter Source Routing bridges to supporting only two adapters. As only two IBM adapters may be installed in a single PC this is no problem for a local bridge based on IBM adapters. This is however a problem for a multi-port remote bridge. NIC Bridge tackles this problem by using the concept of an "Internal Ring" in the bridge. This Internal Ring has no stations on it, only virtual internal bridges. The diagram following shows this. Note that all "bridges" shown are virtual bridges within NIC Bridge. This configuration employs two IBM Token Ring adapters and three serial ports for a total of five ports. The local rings, Ring 1 and Ring 2 are each served by one of the IBM Token Ring adapters. Ring 3 is the internal ring and exists in a logical sense only. The remote rings, Rings 4-6, are served by one of the three serial ports. This "Internal Ring" scheme allows the use of a common "Other Ring Number" for all ports and thus allows multiple port configurations. The only potential disadvantage to this scheme is that two "bridges" must be crossed by a packet moving from one port to another. As a "Hop limit", or maximum crossed bridged count, of 8 is used in Source Routing, this 2 bridge hop will limit the number of bridges a packet may cross to 4, rather than 8. As a remote bridge must exist at each end of a serial link, the actual limit to the maximum number of serial links a packet may cross is 2. { LS = Local Station, RS = Remote Station } LOCAL RINGS SHARED RING REMOTE RINGS (Wired) (Internal) (Async) ┌───┐ ┌───┐ ┌───┤LS1├─────┤LS2├───┐ ┌────────┐ ┌───────┐ │ └───┘ └───┘ ┌─┴─────────┴─┐ ┌─┴─────────┴─┐ ┌─┴─┐ │ Ring 1 │ Loc Bridge 1│ │ Rem Bridge 1│ │RS1│ Ring 4 │ ┌───┐ ┌───┐ └─┬─────────┬─┘ └─┬─────────┬─┘ └─┬─┘ └───┤LS3├─────┤LS4├───┘ │ │ └───────┘ └───┘ └───┘ │ Ring 3 │ ┌───────┐ │ ┌─┴─────────┴─┐ ┌─┴─┐ │ │ Rem Bridge 2│ │RS2│ Ring 5 │ └─┬─────────┬─┘ └─┬─┘ ┌───┐ ┌───┐ │ │ └───────┘ ┌───┤LS5├─────┤LS6├───┐ │ │ ┌───────┐ │ └───┘ └───┘ ┌─┴─────────┴─┐ ┌─┴─────────┴─┐ ┌─┴─┐ │ Ring 2 │ Loc Bridge 2│ │ Rem Bridge 3│ │RS3│ Ring 6 │ ┌───┐ ┌───┐ └─┬─────────┬─┘ └─┬─────────┬─┘ └─┬─┘ └───┤LS7├─────┤LS8├───┘ │ │ └───────┘ └───┘ └───┘ └────────┘ It should be noted that remote Source Routing bridging from one network to another requires attention to ring numbering. A two port remote bridge, for example, requires three ring numbers: a local ring number, an internal ring number and a serial port ring number. All three of these must be different from each other and all other rings accessible via bridges. The asynchronous serial data path between two remote bridges, however, acts as if it is a single ring. Thus, the serial port ring number of two remote bridges which connect must be identical. This is illustrated below. ┌──────────┐ ┌──────────┐ ┌──────────┐ │ LOCAL │ │ INTERNAL │ │ SERIAL │ │ ├─┤ ├─┤ ├─┐ │ Ring # 1 │ │ Ring # 2 │ │ Ring # 3 │ │ Serial Data Path └──────────┘ └──────────┘ └──────────┘ │ ┌──────────────┘ │ ┌──────────┐ ┌──────────┐ ┌──────────┐ │ │ SERIAL │ │ INTERNAL │ │ LOCAL │ └─┤ ├─┤ ├─┤ │ │ Ring # 3 │ │ Ring # 4 │ │ Ring # 5 │ └──────────┘ └──────────┘ └──────────┘ NIC Async must be configured to appear as a Token Ring adapter when used with NIC Bridge in Source Routing bridge mode. This applies to the NAsync drivers loaded on the bridge as well as those loaded on remote PCs. This can be done by changing the MAC_TYPE parameter in the [NASYNC_NIF] section of Protocol.Ini from the default of "DIX+802.3" to "802.5". ; NIC Async parameter in [NASYNC_NIF] section of Protocol.Ini ; required for driver installed on Bridge PC AND remote PC. ; Ensure "802.5" exactly, default is "DIX+802.3" for Ethernet. MAC_TYPE = "802.5" The following Protocol.Ini parameters are relevant for a Source Routing bridge configuration. These are set in the [NBRIDGE_XIF] section of Protocol.Ini. ; Only allowed parameter for Drivername. DRIVERNAME = NBRIDGE$ ; "SOURCEROUTING" required for Source Routing bridging. BRIDGEMODE = "SOURCEROUTING" ; Internal Ring number for virtual ring connecting all internal bridges. ; Allowed: 0x0 - 0x0FFF or 0 - 4095. ; Use any valid unassigned Ring Number. INTERNALRING = 1110 ; 1 Binding specified for each port of the bridge. ; This example is for a combined local and remote bridge. BINDINGS = "SRTOK_NIF", "SRTOK_NIF2, "NASYNC_NIF", "NASYNC_NIF2" ; Enables Bridging for each NIC driver. Order identical to BINDINGS. ; Allowed: "YES" or "NO". ; Default: "YES" for all. BRIDGE_MAC = YES, YES, YES, YES, YES, YES, YES, YES, YES ; Enables Packet Capture for each NIC driver. Order identical to BINDINGS. ; Allowed: "YES" or "NO". ; Default: "YES" for all. ; Recommend "NO" for high-performance production use. CAPTURE_MAC = YES, YES, YES, YES, YES, YES, YES, YES, YES ; Ring number for each NIC driver bound. Order identical to BINDINGS. ; Allowed: 0x0 - 0x0FFF or 0 - 4095. ; If you already have SR Bridges assigned Ring Numbers MUST match these. RING_MAC = 1111, 1112, 1113, 1114, 1115, 1116, 1117, 1118, 1119 ; Filters Broadcasts rcvd by each NIC driver. Order identical to BINDINGS. ; Allowed: "YES" or "NO". ; Default: "NO" for all. ; Set to yes ONLY on local NICS to eliminate broadcast traffic. ; Note: "YES" does not allow correct operation of MS TCP/IP. FILTERBC_MAC = NO, NO, NO, NO, NO, NO, NO, NO, NO The SRTok driver Protocol.Ini parameters are the same as those for the IBM Token Ring NDIS driver. The following parameters are those that are most important and are set in the [SRTOK_NIF] section of Protocol.Ini. ; SRTOK$ for first adapter, SRTOK2$ for second adapter. DRIVERNAME = SRTOK$ ; Required to set non-default Ram address. RAM = 0xD800 ; Either Primary or Alternate adapter, NOT BOTH ! Default = PRIMARY. PRIMARY ;ALTERNATE ; Setting SRBC = NO allows single route broadcasts to be filtered. SRBC = YES ┌──────────────────────────┐ │ SETUP/MAIN CONFIGURATION │ └──────────────────────────┘ To setup and configure NIC Bridge: 1) Install Lan Manager or Lan Server if needed on this PC. Ensure that all local Ethernet and Token Ring adapters have been configured properly. 2) Install NIC Bridge/Async on the PC. With the NIC Bridge/Async install disk inserted into the A: drive the command "A:\Install" will initiate the installation procedure. When this is complete the PC should be rebooted. 3) If remote ethernet bridging will be provided and this PC is a server, NIC Async must be setup and configured. This will provide remote access to this server, while the bridge component provides access to other servers. Token ring bridges should not have NIC Async installed. as the second Token Ring adapter provides access to this server. Refer to the NIC Async document for NIC Async installation instructions. 4) If this will be an ethernet bridge, any device drivers required for your ethernet adapter should be copied to the NICDIR directory, normally C:\NIC11. Run NicSetup.Exe and ensure that the General Configuration information displayed is appropriate. Option 2 "Change General Configuration" may be used to make any changes. Select option 3 to "Setup NIC Bridge" and answer the prompts with appropriate selections. If setting up an Ethernet bridge: If your network adapter is not listed as a selection, specify the "Dummy Ethernet Driver". This will require Config.Sys lines of the form "DEVICE = C:\NIC11\ETHERN...." be replaced with entries for your ethernet adapter driver. The Protocol.Ini [ETHERN_NIF] sections will also have to be modified to set the appropriate options for that adapter driver. 5) Before rebooting your PC, the Protocol.Ini file may need modification. This can be done with the NicCfg.Exe utility. Within NicCfg select "Config", "Bridge". When each screen of options is appropriate press the <Enter> key. The Ring Number variables are important only when the bridge is setup as a source routing bridge. Other Bridge options may be left at default or changed as appropriate for your environment. Press <Enter> to save the options. If Source Routing is being used, select "Config", "SR Token 1" to configure the Source Routing Token Ring driver. Ensure that the Ram Address selected is available on your PC. Other SRTOK options may be left at default or changed as appropriate for your environment. Press <Enter> to save the options. If this is a remote bridge select "Config", "Async 1". When each screen of options is appropriate press the <Enter> key. Repeat this for "Async 2" and all other serial ports configured. The MAC Type option should be set to Ethernet unless this is a Source Routing bridge when it should be set to Token Ring. The Network address value should be unique among all network addresses in use on the network. Remember to set a DIFFERENT Network address on the host and all clients. Other options may be left at default or changed as appropriate for your environment. Exit NicCfg with the <F3> key. Inspect and edit Protocol.Ini to ensure any Ethernet adapter drivers are configured as desired. Note that many ethernet adapters use IRQ 3 by default and that this will interfere with COM2. 6) All servers and workstations which will use remote resources or be remotely accessed must be tuned for low speed operation. Run NicSetup.Exe and select option 4 to tune NetBEUI and the LAN software for low speed operation on all servers and workstations which will communicate via a remote bridge. NicSetup.Exe may be copied to and run from a floppy disk to perform this on servers. 7) Reboot the PC and ensure that all drivers load properly. NOTE: Running the MS Lan Manager Setup.Exe or IBM Lan Server LanInst.Exe utilities after NIC Bridge is setup and configured by cause information in Config.Sys and Protocol.Ini to be deleted. This will require that the NIC Bridge setup and configuration be repeated. ┌───────────┐ │ OPERATION │ └───────────┘ The NIC Bridge PC should start and run normally. The Device driver(s) should load from Config.Sys and display ID messages. Note that should any of the drivers cause problems booting a PC, installation of the driver may be aborted by holding down the Alt-Key. No errors should be produced when NetBind is run (or when the NETWKSTA.SYS IFS is loaded). If you get any errors, inspect the Protocol.Ini file for configuration errors and/or try changing the adapter settings. If the Netbind has succeeded the bridge should now be operational. Executing NBr.Exe will provide a screen showing the bridge statistics. Note that when the NAsync drivers are in a "Closed" state, packets will still appear to be forwarded to them. It is only when a client connects to the host bridge that these packets are actually forwarded through the serial port. ┌────────────────────┐ │ NBRIDGE PARAMETERS │ └────────────────────┘ The following pages detail Protocol.Ini parameters for the NBridge driver. Defaults are shown. Parameter values shown in quotes are ASCII string parameters. All other parameters are numeric. Numeric parameters preceded with "0x" are hexadecimal values while all others are decimal values. REQUIRED NDIS PARAMETERS: ; Required parameter ; Range: NBRIDGE$ only DRIVERNAME = "NBRIDGE$" ; Required parameter ; 1 Binding specified for each port of the bridge. ; Form: "Driver1_NIF", "Driver2_NIF", etc. up to 9 ports BINDINGS = No Default GENERAL PARAMETERS: ; Configures Transparent Ethernet or Source Routing ; Token Ring bridge mode. ; Range: "TRANSPARENT" or "SOURCEROUTING" BRIDGEMODE = "TRANSPARENT" ; Enables Bridging for each NIC driver. ; Order identical to BINDINGS. ; Range: "YES" or "NO" BRIDGE_MAC ="YES","YES","YES","YES","YES","YES","YES","YES","YES" ; Enables Packet Capture for each NIC driver. ; Order identical to BINDINGS. ; Range: "YES" or "NO" CAPTURE_MAC ="YES","YES","YES","YES","YES","YES","YES","YES","YES" ; Enables filtering broadcasts received by each NIC driver. ; Order identical to BINDINGS. ; Range: "YES" or "NO" ; Set "YES" ONLY on local NICS to eliminate broadcast traffic. ; Note: "YES" does not allow correct operation of MS TCP/IP. FILTERBC_MAC = "NO", "NO", "NO", "NO", "NO", "NO", "NO", "NO", "NO" ; Each CUSTOMFILTER parameter configures one condition whereby ; packets which would normally be forwarded are filtered. ; Up to 16 individual CUSTOMFILTER lines may be configured. ; Each custom filter consists of a string of 8 - 58 characters ; representing a hexadecimal string of 4 - 29 bytes. ; The first byte represents the offset in the packet used ; for filtering criteria. ; The second and third bytes represent a mask to determine ; which bridge ports the filter shall affect. ; The subsequent bytes represent the filtering criteria. ; See the following pages for examples. CUSTOMFILTER = No Default ; The example below filters all Ethernet packets with a ; destination address of 02608C010203. The offset of 00 ; corresponds to the beginning of the destination address ; in an Ethernet packet. The mask value of FFFF prevents ; packets matching the filter criteria from being forwarded ; on all bridge ports. CUSTOMFILTER = "00FFFF02608C010203" 00 offset = 0 = dest address FFFF Filter on all ports 02608C010203 match value ; The example below filters Ethernet packets with a source ; address of 02608C010203 from MAC 2, 1 and 0. MAC 1 and 2 ; are the ports corresponding to the first and second drivers ; bound to NBridge. MAC 0 is the virtual packet capture port. CUSTOMFILTER = "06000702608C010203" 06 offset = 6 = source address 0007 Filter on MAC 2, 1 and 0 02608C010203 match value ; The example below filters all Token Ring packets with a ; destination address of 10005A010203. The offset of 02 ; corresponds to the beginning of the destination address ; in a Token Ring packet. Note that the destination address ; of a Token Ring packet begins at offset 02, after the start ; delimiter and access control bytes of Token Ring. CUSTOMFILTER = "02FFFF10005A010203" 02 offset = 2 = dest address FFFF Filter on all ports 10005A010203 match value ; The example below filters all source routed Token Ring ; packets with a source address of 10005A010203. Note that ; the highest bit of the source address is set to accomodate ; the source routing bit of Token Ring. CUSTOMFILTER = "08FFFF90005A010203" 08 offset = 8 = source address FFFF Filter on all ports 90005A010203 match value SOURCE ROUTING PARAMETERS: ; Internal Ring number for virtual ring connecting internal ; bridges in Source Routing Token Ring bridge mode. ; Range: 0 - 4095 ; Use any valid unassigned Ring Number INTERNALRING = 1110 ; Ring number for each NIC driver. ; Order identical to BINDINGS. ; Range: 0 - 4095 ; If you already have Source Routing Bridges the assigned ; Ring Numbers MUST match these on Local RING_MAC = 1111, 1112, 1113, 1114, 1115, 1116, 1117, 1118, 1119 ┌──────────────────┐ │ SRTOK PARAMETERS │ └──────────────────┘ The following pages detail Protocol.Ini parameters for the SRTok driver. Defaults are shown. Parameter values shown in quotes are ASCII string parameters. All other parameters are numeric. Numeric parameters preceded with "0x" are hexadecimal values while all others are decimal values. REQUIRED NDIS PARAMETERS: ; First driver is "SRTOK$", second is "SRTOK2$", etc. ; Range: SRTOK$ - SRTOK2$ ; Only required parameter DRIVERNAME = "SRTOK$" GENERAL PARAMETERS: ; Sets Primary or Alternate adapter ; Do not set both ! (semicolon starts remark line) ; PRIMARY is default PRIMARY ;ALTERNATE ; Sets adapter Ram address ; Range: 0x0000 - 0xFFFC where low 2 bits = 0 RAM = 0xD800 ; Maximum queued transmits ; Range: 1 - 32 MAXTRANSMITS = 8 ; Sets the adapter product identification ; Range: exactly 36 hex digits PRODUCTID = "0110F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0" ; Enables reception of Single Route Broadcasts ; Range: "YES" or "NO" SRBC = "YES" ; Enables Early Token Release feature on 16 Mbps rings ; Range: "YES" or "NO" EARLYRELEASE = "NO" IBM ISA TOKEN RING ADAPTER SWITCH SETTINGS: Off = Up = U On = Down = D ┌────────────┐ │123456789111│ Switch Block │ 012│ └────────────┘ D (12) 4 Mbps Ring Speed U 16 Mbps Ring Speed DD (10,11) 8 KB Shared RAM size UD 16 KB Shared RAM size DU 32 KB Shared RAM size UU 64 KB Shared RAM size U (9) Primary Adapter D Alternate Adapter Off = Up = U On = Down = D ┌────────────┐ │123456789111│ Switch Block │ 012│ └────────────┘ DD (7,8) IRQ 2 DU IRQ 3 UD IRQ 6 UU IRQ 7 UDDDDD (1-6) ROM @ C000 UDDUDD ROM @ C800 UDUDDD ROM @ D000 UDUUDD ROM @ D800 UUDDDD ROM @ E000 UUDUDD ROM @ E800 ┌──────────────────┐ │ ACKNOWLEDGEMENTS │ └──────────────────┘ All trademarks are the property of their owners. This includes, but is not limited to, the trademarks of 3Com, IBM, Microsoft, and Hayes. ;