|
|
1.1 root 1: From research!cbosgd!mark Thu Dec 4 14:06:19 1986
2: Received: from cbpavo.cbosgd.ATT.COM (cbpavo.ARPA)
3: by cbosgd.ATT.COM (4.12/smail2.1/11-29-86)
4: id AA24279; Thu, 4 Dec 86 14:05:32 est
5: Received: by cbpavo.cbosgd.ATT.COM (4.24/3.14)
6: id AA11054; Thu, 4 Dec 86 14:05:26 est
7: Date: Thu, 4 Dec 86 14:05:26 est
8: From: [email protected] (Mark Horton)
9: Message-Id: <[email protected]>
10: To: [email protected]
11: Subject: use of mhuxc
12: Cc: [email protected], [email protected], [email protected]
13:
14: > I want to require that chessie remain a gateway and not a login machine.
15: > That means I would like only administrative personell to have access to
16: > it.
17:
18: Fine, but my use really fits better under the administrative heading
19: than the random user heading, in the long term. Also, I am willing
20: to do whatever I can to help with the general adminstration setup.
21:
22: > However, mark's problem is valid. His access will be painful if he does
23: > not have IP access from his machine to the gateway. Therefore, I suggest
24: > that we solve the real problem and figure out how to do that. Smb
25: > already has code that allows 4.2 systems to talk IP over a dk. Why not
26: > use that?
27:
28: The long term plan is to do exactly that. However, we have to do it
29: with subnets; we aren't going to be able to get all the AT&T networks
30: into the ARPA tables, so we have to present them with a single network
31: face. This means migration to our class A network number. From what I
32: can gather, this will take considerable time. It's going to require smb's
33: DKIP running under 4.3BSD, for example.
34:
35: Also, my long term need for administrative access doesn't go away. I'm
36: thinking primarily of the mail gateway and nameserver function. If that
37: will be done on ulysses instead of mhuxc, and mhuxc is nothing but a
38: packet forwarder, then what I'll really want access to is ulysses.
39:
40: Mark
41:
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.