[6322] in Athena Bugs
[Saltzer@mit.edu: netconfig]
daemon@ATHENA.MIT.EDU (Jerome H Saltzer)
Fri Nov 2 15:02:47 1990
Date: Fri, 2 Nov 90 15:02:26 EST
From: Jerome H Saltzer <Saltzer@mit.edu>
To: bugs@ATHENA.MIT.EDU
I don't recall ever getting a response to this report, and it looks
like the reason is that I forgot to include a copy to bugs at the
time. The program still doesn't work in my environment in release
7.1H.
---Begin Forwarded Message---
Date: Tue, 27 Mar 90 15:46:59 EST
From: Jerome H Saltzer <Saltzer@mit.edu>
To: jon@PTT.LCS.MIT.EDU, jis@PTT.LCS.MIT.EDU
Subject: netconfig
Jon or Jeff,
Athena Release 6.4 replaced most of the code in /etc/rc.net with a
call to a binary named /etc/athena/netconfig. When I installed 6.4
back at the end of January I found that the network connection went
dead. I backed up to the old /etc/rc.net and it worked; I didn't have
time then to follow it up. I'm just now getting back to trying to
understand what went wrong.
Apparently one of the things that netconfig does is figure out what
the default gateway should be. Running strings over the binary of
netconfig I notice that it has an embedded list of what appear to be
exceptional gateway addresses, including one for 18.26.0.121. That is
the address of Lithium, which I thought was a nameserver rather than a
gateway. I suspect that this has something to do with why netconfig
failed for my RT, which is on 18.26.
Do I have this analyzed right, and is there some option to netconfig
that I should give to get it to do the right thing? Or should I
continue to run with the old rc.net, which is a script with the
exception list (including my own addition for 18.26) coded in?
Jerry
---End Forwarded Message---
