Return to READ-ME CVS log

Up to [CSRG BSD Unix] / 43BSDReno / contrib / isode-beta / others / tp0bridge

Annotation of 43BSDReno/contrib/isode-beta/others/tp0bridge/READ-ME, revision 1.1.1.1

1.1       root        1: [ READ-ME - Tue Nov  7 21:41:26 1989 - ISODE TCP/X.25 TP0 bridge notes - /mtr ]
                      2: 
                      3: 
                      4: [[ NOTE WELL: THE TP0BRIDGE IS BEING REMOVED FROM THE NEXT RELEASE OF
                      5:    THE ISODE -- USE THE TRANSPORT SERVICE BRIDGE INSTEAD ]]
                      6: 
                      7: 
                      8:     This program is used to bridge ISO TP0 packets between X.25 and TCP
                      9:     networks.  This technique is useful when interconnecting a DDN
                     10:     IP-based internet to an X.25-based subnetwork.  There is not a
                     11:     "magic bullet" solution to the DDN/ISO interoperability problem.
                     12:     Rather, if one is running higher-layer ISO protocols in both
                     13:     networks (namely ISO TP0), then a TP0 bridge can be used to achieve
                     14:     connectivity.  
                     15: 
                     16: 
                     17:     Configuration:
                     18: 
                     19:     On the host running the bridge, decide if you're using SUN_X25,
                     20:     CAMTEC, or UBC_X25 and define that in addition to X25 in your
                     21:     config.h file.  Next, the tailoring variable 
                     22: 
                     23:        x25_bridge_port
                     24: 
                     25:     should be set to the TCP port where the listens.  TCP port number
                     26:     146 has been officially assigned for this purpose, so you may wish
                     27:     to add the line
                     28: 
                     29:        tp0bridge       146/tcp
                     30: 
                     31:     to your /etc/services file.
                     32: 
                     33:     On the TCP hosts which will be using the bridge, define BRIDGE_X25
                     34:     in your config.h file.  Do not define X25 unless the TCP host also
                     35:     has its own X25 interface.  Next, the tailoring variable
                     36: 
                     37:        x25_bridge_host
                     38: 
                     39:     should be set to the domain name or DDN-IP address of the host which
                     40:     is running the bridge.  In addition, the tailoring variable 
                     41: 
                     42:        x25_bridge_addr
                     43: 
                     44:     should be set to the X.25 address that the TCP host is going to
                     45:     masquerade as (this is usually a subaddress of the X.25 address of
                     46:     the host running the bridge).
                     47: 
                     48:     Where a single set of binaries is to be shared by several hosts,
                     49:     or where the machine has access to two different X.25 networks,
                     50:     it is possible to define X25, one of the X25 interfaces, AND
                     51:     BRIDGE_X25.  This is convenient where a group of machines share
                     52:     binaries using NFS but only one of them has an X25 interface.  The
                     53:     tailoring variable
                     54: 
                     55:        x25_bridge_discrim
                     56: 
                     57:     may be used to determine which calls use the bridge and which use the
                     58:     X25 interface directly. If this is empty, the bridge will be used
                     59:     in all cases, if the string is a '-' then the bridge will not be
                     60:     used for any traffic, otherwise the string is compared against the
                     61:     called DTE. If the string is a prefix of the DTE, then the bridge
                     62:     will be used, otherwise it is assumed to be real X.25.
                     63: 
                     64:     Finally, the /etc/isoentities file should be updated to reflect the
                     65:     new X.25 addresses in use and this file should be propagated to all
                     66:     sites.

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.