|
|
1.1 ! root 1: .TH TSBRIDGE 8C "08 March 1989" ! 2: .\" $Header: /f/osi/others/tsbridge/RCS/tsbridge.8c,v 7.4 90/03/20 05:08:45 mrose Exp $ ! 3: .\" ! 4: .\" Contributed by Julian Onions, Nottingham University in the UK. ! 5: .\" ! 6: .\" ! 7: .\" $Log: tsbridge.8c,v $ ! 8: .\" Revision 7.4 90/03/20 05:08:45 mrose ! 9: .\" jpo ! 10: .\" ! 11: .\" Revision 7.2 89/12/08 09:41:19 mrose ! 12: .\" touch-up ! 13: .\" ! 14: .\" Revision 7.1 89/11/27 05:43:27 mrose ! 15: .\" sync ! 16: .\" ! 17: .\" Revision 7.0 89/11/23 22:11:11 mrose ! 18: .\" Release 6.0 ! 19: .\" ! 20: .SH NAME ! 21: tsbridge \- Transport Service Bridge ! 22: .SH SYNOPSIS ! 23: .in +.5i ! 24: .ti -.5i ! 25: .B \*(SDtsbridge ! 26: \%[-a\ address] ! 27: \%[-s] ! 28: \%[-T\ tailorfile] ! 29: \%[configuration-file\ ...] ! 30: .in -.5i ! 31: (under /etc/rc.local) ! 32: .SH DESCRIPTION ! 33: The \fItsbridge\fP listens for transport connections on the ! 34: given address. Once a connection is accepted the transport selector ! 35: is examined for a transport address and a call initiated to that ! 36: address. ! 37: The TSB then shuffles data back and forth between the two connections. ! 38: This is used to solve interworking problems between OSI hosts/networks ! 39: using different lower-layer stacks (e.g., TP0/X.25, TP4/CLNP, ! 40: RFC1006/TCP, and so on). ! 41: .PP ! 42: Entries are seperated by end\-of\-line (or the end\-of\-file). ! 43: The character `#' at the beginning of a line indicates a comment line. ! 44: The syntax is: ! 45: .sp ! 46: .in +.5i ! 47: .nf ! 48: address [forwarding-address] [-s] [-n] [-f] ! 49: .fi ! 50: .in -.5i ! 51: .sp ! 52: as in ! 53: .sp ! 54: .in +.5i ! 55: .nf ! 56: # generic tsb operation ! 57: Internet=sheriff+19001\\|Janet=000021000018+PID+04010100 ! 58: ! 59: # specific use of transparent address with strict checking ! 60: Internet=sheriff+19002 Internet=sheriff+102 -s ! 61: .fi ! 62: .in -.5i ! 63: .PP ! 64: If the forwarding address is present, this specifies that the ! 65: \fItsbridge\fP should run in transparent mode. That is, it should ! 66: accept incoming connections as though it were the \fItsapd\fP daemon ! 67: and a call established to the given address (which is normally a ! 68: \fItsapd\fP process or a static listener). ! 69: .PP ! 70: The `\-s' option specifies strict transport addresses. When relaying ! 71: through the \fItsbridge\fP the calling transport address is changed to ! 72: indicate that of the \fItsbridge\fP. This can fail in several ways: ! 73: .TP ! 74: 1. ! 75: The original calling address when encoded into a string may be too big ! 76: to fit into the transport selector. ! 77: .TP ! 78: 2. ! 79: The \fItsbridge\fP may not be listening on an address on the outgoing ! 80: network. (E.g., it can call out on that network but not accept ! 81: incoming calls.) ! 82: .TP ! 83: 3. ! 84: The original calling address can not be converted to a text string (unusual). ! 85: .PP ! 86: In strict mode, any of these failures will abort the connection ! 87: attempt. If strict mode is not in force, then the bridge will leave ! 88: the original transport address alone and hope it is not needed. ! 89: .PP ! 90: The `\-n' option specifies that the original transport selector should not ! 91: be changed to indicate that the address came from a transport bridge. This ! 92: effectively passes the original T-Selector through unchaged. This option ! 93: is implied if a forwarding address is present. ! 94: .PP ! 95: The `\-f' option overrides the default application of the `\-n' flag when ! 96: a forwarding address is present. This permits one to set up a ! 97: semi-transparent listener --- transparent to the caller, visible locally. ! 98: .PP ! 99: If desired, the \fItsbridge\fP can run without a configuration file, ! 100: in which case the `\-a' flag specifies the address to listen on. If ! 101: this is not present, it will use use the value of the ! 102: \*(lqtsb_default_address\*(rq variable in the tailor file for the ! 103: default address. ! 104: The `\-s' flag may also be specified in this case. ! 105: .PP ! 106: Finally the `\-T' flag specifies a different \fIisotailor\fR file to use. ! 107: This should be a full pathname and, if present, ! 108: should be the first argument given. ! 109: .SH EXAMPLE ! 110: A configuration file on host 128.199.200.7 has in its tsbridge ! 111: configuration the line ! 112: .sp ! 113: .in +.5i ! 114: .nf ! 115: # specific use of transparent address with external visibility ! 116: Int-X25(80)=234212900115+PID+03010100 stcTCP=128.199.200.43+102 -f ! 117: .fi ! 118: .in -.5i ! 119: .sp ! 120: A call placed to 234212900115+PID+0301010 from X121+23421920030045 will ! 121: appear at the final recipient [128.199.200.43] to come from ! 122: .sp ! 123: .in +.5i ! 124: .nf ! 125: "X121+23421920030045"/stcTCP=128.199.200.7 ! 126: .fi ! 127: .in -.5i ! 128: .sp ! 129: .SH FILES ! 130: .nf ! 131: .ta \w'\*(EDisotailor 'u ! 132: \*(EDisotailor ISODE tailoring file ! 133: .re ! 134: .fi ! 135: .SH "SEE ALSO" ! 136: \fIThe ISO Development Environment: User's Manual, Volume 2: ! 137: Underyling Services\fR, \*(lqThe Transport Switch\*(rq. ! 138: .br ! 139: isotailor(5), ! 140: tsapd(8) ! 141: .SH AUTHORS ! 142: Julian Onions, ! 143: Nottingham University. ! 144: .br ! 145: Based on an idea by Steve Kille of University College London ! 146: and Christian Huitema of INRIA.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.