[2384] in Hotline Meeting
Question about net addresses?
daemon@ATHENA.MIT.EDU (deckjf@ATHENA.MIT.EDU)
Thu Nov 8 11:01:54 1990
From: deckjf@ATHENA.MIT.EDU
To: hotline@ATHENA.MIT.EDU
Date: Thu, 08 Nov 90 11:01:33 EST
I often use ic3-462-17, and frequently use it to rlogin to another machine.
Yesterday, when I tried to login to ic3-462-17, it complained that there was "No
Hesiod information for ic3-462-17" at activation. I rebooted the machine and
that problem went away.
However, now I have noticed that, if I rlogin, the remote machine recognizes me
as "F.CRL.MIT.EDU", not "IC3-462-17." Furthermore:
IC3-462-17% hostinfo -a f.crl.mit.edu <----- different hosts
18.58.0.109 <------ same address
IC3-462-17% hostinfo -a ic3-462-17 <----- different hosts
18.58.0.109 <------- same address
so both of these machines appear to have the same net address.
Now, if I execute the command hostinfo -h `hostinfo -a ic3-462-17` on itself, it
returns itself:
IC3-462-17% hostinfo -h `hostinfo -a ic3-462-17`
IC3-462-17.MIT.EDU
but if I run the same command on the remote machine:
m3-461c-1% hostinfo -h `hostinfo -a ic3-462-17`
F.CRL.MIT.EDU
I don't know whether this is intended or not, but it occurred to me that it
might be a problem! My first thought is that the same address may have been
assigned to two different machines, but I don't even know whether that's
possible. Just out of curiosity, I would be interested to know if this
phenomenon is a problem, and if so, what causes the problem. Also, what is the
usual cause for the "No Hesiod information available..." error message? Does
Hesiod store the assigned NFS servers for each workstation, and is that the
information that the activate script is looking for? (I wonder about these
questions, but I don't have a "need to know.")
-J. Deck
