[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
TCP vs. CHAOS
Date: Thu, 20 Jun 1991 08:55 EDT
From: email@example.com (Steve Fulton)
Two of our Symbolics sites have operated independently for approximately
a year due to a physical separation of ~10 kilometers. We recently gained
network connectivity, but, due to political (and network traffic)
considerations, want to use TCP rather than CHAOS.
I would like to combine the two sites into one which communicates only via
TCP. Has anyone done this, or am I about to lose *big*? I'm willing
to sacrifice CHAOS specific commands (such as "show hosts"), but have
had no luck using the "set site" command without a CHAOS connection.
I don't find any mention of the NAMESPACE service being available via TCP
which appears to be a necessity.
NAMESPACE is supported via TCP and NAMESPACE-TIMESTAMP via UDP [since
8.0, c.f., the 8.0 release notes.] What you want to do is implemented
by cl-neti::link-namespaces; but the documentation unfortunately tells
you to call customer service to find out how to use it (I'm not sure
why). You can do what you want "manually" (without merging the sites)
by adding namespace services via tcp to your servers at each site and
giving your internet the same global network name at both sites so that
they realize they can talk to each other.
Alternatively, is anyone willing to share their experiences using Cisco
routers to route CHAOS traffic. (We tried bridging, but the traffic
load brought us to our knees)
Stuck in CHAOS,
Boeing Aerospace Operations
Kennedy Space Center