home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!gatech!usenet.ins.cwru.edu!agate!dog.ee.lbl.gov!ucbvax!swdev.si.com!tillman
- From: tillman@swdev.si.com ("Brian Tillman, Smiths Industries, VAX Support, x8425")
- Newsgroups: comp.os.vms
- Subject: RE: Using DECNET ALIAS to masquerade
- Message-ID: <00965832.45DFC3A0.18569@swdev.si.com>
- Date: 23 Dec 92 15:05:43 GMT
- Sender: usenet@ucbvax.BERKELEY.EDU
- Organization: The Internet
- Lines: 24
-
- Anders Ostling (anos@ineab.ikea.se) writes:
-
- >I was thinking of using the
- >Decnet alias facility to let the whole cluster be seen as X from the
- >outside world and thus let Y send data to (and recieve) the IBM system
- >without chaning routing tables etc at the remote site.
-
- This is my understanding of how the alias works.
-
- The cluster alias is used in two ways. It allows a cluster to accept *in-bound*
- connections addressed to the alias (SET EXEC ALIAS INCOMING ENABLED, SET EXEC
- ALIAS NODE clustename). It also allows certain objects to substitute the
- cluster alias name for the node name in outbound connections (SET OBJECT MAIL
- ALIAS OUTGOING ENABLED) or inbound connections (SET OBJECT PHONE ALIAS INCOMING
- ENABLED). It does not allow general outbound connections to have the alias
- address in the source field of the DECnet packet (i.e. with a COPY command).
-
- -----------------------------+--------------------------------
- Brian Tillman | Internet: tillman@swdev.si.com
- Smiths Industries, Inc. | tillman_brian@si.com
- 4141 Eastern Ave., MS129 | Hey, I said this stuff myself.
- Grand Rapids, MI 49518-8727 | My company has no part in it.
- -----------------------------+--------------------------------
-
-