Hey folks, I am trying to administer a pair of Cobalt web server
appliances remotely and would welcome your advice.
One's a Raq 3 and the other is a Cube. The Raq 3 appears to be the
main server. The main problem appears to be that although the Raq 3
and the Cube can both get to the outside world, they can't talk to
each other. (Error is "no route to host".)
Both machines have two interfaces, one on a local LAN using unroutable
class C addresses (192.168.x.x) and a connection to the outside world
with "real" addresses.
The "real" address for the Raq is the default gateway of the network
on which the "real" addresses reside.
The machines can contact each other on the unroutable interface but
not via the "real" IP addresses. I suspect that this is a feature.
So, I put entries in the hosts files on both machines so that their
names would resolve to the local unroutable IPs, and most things
(telnet, et al) started working again.
The holdout is sendmail. Sendmail apparently doesn't consult
/etc/hosts, and skimming the sendmail.cf, it looks like neither
HostsFile nor ServiceSwitchFile m4 options are set.
So, now I'm looking at finding the original m4 file, (or writing one),
adding HostsFile and ServiceSwitchFile, and regenerating sendmail.cf.
But, I'm beginning to think that I'll continue to find communication
issues between the machines, and perhaps I should instead try to get
the "real" IPs talking to each other.
My idea is to tell both machines that the other machine's "real" IP
address is on the local network. As so:
IP routing table for machine 1:
IP routing table for machine 2:
Would this work, or should I be doing something else? For instance,
should the gateway for machine 2's "real" IP be machine 2's unroutable
IP? This goes a bit beyond my understanding of this stuff.
All assistance gratefully accepted.
"Save the whales. Collect the whole set."