[comp.unix.aux] remote access from MacOS to A/UX over Appletalk?

ken@dali.gatech.edu (Ken Seefried iii) (12/07/90)

-----

Forgive me if this is trivial, but I know nothing about MacOS and only
a little about Appletalk.

The situation is this:  We have a Mac IIx, running A/UX 1.1 (soon to
be 2.0), that is connected to both our internal ethernet and a small
Appletalk network (secretaries and a few management types use MacOS).
The MacOS people would like to be able to read mail on the A/UX box
over Appletalk.

The question is, what are my options?  I assume that the simplest
thing would be to find some sort of terminal emulator that speaks
Appletalk and let them remote-login.  However, I'm interested in
looking at all solutions; for example, is there a nice front end like
`xmh' that used Mac look-n-feel?  Whats out there?

I'll summarize.  Thanks for the help...

--
	ken seefried iii	"A sneer, a snarl, a whip that
	ken@dali.gatech.edu	 stings...these are a few of
				 my favorite things..."

abm@alan.aux.apple.com (Alan Mimms) (12/08/90)

In article <18256@hydra.gatech.EDU>, ken@dali.gatech.edu (Ken Seefried iii) writes:
|> -----
|> 
|> Forgive me if this is trivial, but I know nothing about MacOS and only
|> a little about Appletalk.
|> 
|> The situation is this:  We have a Mac IIx, running A/UX 1.1 (soon to
|> be 2.0), that is connected to both our internal ethernet and a small
|> Appletalk network (secretaries and a few management types use MacOS).
|> The MacOS people would like to be able to read mail on the A/UX box
|> over Appletalk.
|> 
|> The question is, what are my options?  I assume that the simplest
|> thing would be to find some sort of terminal emulator that speaks
|> Appletalk and let them remote-login.  However, I'm interested in
|> looking at all solutions; for example, is there a nice front end like
|> `xmh' that used Mac look-n-feel?  Whats out there?
|> 

I personally would recommend Quickmail for your MacOS needs.  Its user
interface is quite nice, it's fast, it's based on Appletalk transports
(so it can use Ethertalk, Localtalk, and/or Tokentalk in any combination)
and it has all of the features I need in my normal work, so perhaps it
has all you need too.  It is also very useful for inter-MacOS mail and
doesn't require that you "go to the mountain" periodically to check for
incoming mail.  AND (this is where I answer your original question) you
can run a fast and efficient gateway between SMTP (Unix style) mail and
QuickMail trivially.

Note that Quickmail has some problems on A/UX, but they're fixing 'em and
we're working on fixing a (small) problem with Appletalk that they have
with our code (second hand info), so I'd expect an A/UX-studly Quickmail
release Real Soon Now.  So that'll mean you could use Quickmail on your
A/UX machines too, if you like.

|> I'll summarize.  Thanks for the help...
|> 
|> --
|> 	ken seefried iii	"A sneer, a snarl, a whip that
|> 	ken@dali.gatech.edu	 stings...these are a few of
|> 				 my favorite things..."

-- 

Alan Mimms (alan@apple.com, ...!apple!alan)   | My opinions are generally
A/UX X group                                  | pretty worthless, but
Apple Computer                                | they *are* my own...
"Laugha whila you can, monkey boy..." -- John Whorfin in Buckaroo Bonzai
"Never rub another man's rhubarb" -- The Joker in BatMan

herbw@wiskit.pdx.com (Herb Weiner) (12/08/90)

--------
In article <18256@hydra.gatech.EDU> ken@dali.gatech.edu (Ken Seefried iii) asks
> The MacOS people would like to be able to read mail on the A/UX box
> over Appletalk.

I asked a roughly similar question approximately a week ago.  The question
(and several replies) may still be on your system.  Look for the subject
"I can get news from around the world, but not to the next room".

The emailed and posted suggestions fell into the following categories:
1. Use the serial port.  (Sorry, I can't.  The printer port is used by
   AppleTalk.  The modem port is required for my modem.  Besides, I
   can't easily get a serial cable from here to there.)
2. Use some sort of news server (e.g. NNTP news server with NetNews stack).
   Unless I'm missing something, these require either a serial connection
   or an AppleTalk to Ethernet gateway, neither of which is available.
3. Use MacTCP, TopsTerm, or ADSP to log in.  Sorry.  As far as I know,
   none of these will allow me to log in to A/UX over AppleTalk.
4. Use NRC Software Router.  Sorry, according to NRC, they don't have
   drivers for A/UX.

One solution that will definitely work (but it's not cheap) is to
purchase a hardware AppleTalk to Ethernet gateway, such as the Kinetics
Fastpath, the Cayman Gatorbox, or others.  (Which would be the best choice?)

The other alternative is to put everyone on Ethernet.  This, of course,
assumes that you can easily get an Ethernet cable from here to there;
this is not always a valid assumption.  (What is a good choice of Ethernet
cards (with drivers for A/UX) for a Mac IIfx?)

A solution that ought to work, but probably will not, is to write a software
router that runs under A/UX.  However, I'm reluctant to spend money on the
required documentation, only to find out that it can't be done.  I've been
told that ADSP is NOT supported for A/UX applications (such as a Daemon).
The A/UX Toolbox: Macintosh ROM Interface manual (page 5-5) states "Apple
network calls are available at the program level [what DOES this mean?],
but not fully supported at the network level: there is no session protocol
or data stream."

As far as I can determine (Apple, please correct me if I am wrong), there
is a brick wall between A/UX programs (like Daemons) and AppleTalk.  They
can NOT access the Communication Toolbox.  They can not access the AppleTalk
drivers.  The ONLY thing they can do is print over AppleTalk.

Herb Weiner (herbw@wiskit.pdx.com)

liam@cs.qmw.ac.uk (William Roberts;) (12/11/90)

In <1990Dec8.045720.1507@wiskit.pdx.com> herbw@wiskit.pdx.com (Herb Weiner) 
writes:

>As far as I can determine (Apple, please correct me if I am wrong), there
>is a brick wall between A/UX programs (like Daemons) and AppleTalk.  They
>can NOT access the Communication Toolbox.  They can not access the AppleTalk
>drivers.  The ONLY thing they can do is print over AppleTalk.

A/UX programs don't talk to the Comms Toolbox - correct.

A/UX programs can and do access the AppleTalk protocols, which are actually 
implemented in A/UX as Streams drivers: the AppleTalk drivers for the A/UX Mac 
emulation are actually dummies which work through the A/UX kernel code, but it 
isn't clear where the split is (the kernel PAP code is probably not used by 
the Mac emulation, for example).

My changes to CAP make use of the A/UX AppleTalk support: the relevant manual 
pages are in section 3N called lap, ddp, atp, nbp, pap, and zip. These manual 
pages don't offer much help and don't seem to include ADSP.

As for your original problem, the short cut would be to hook into the 
AppleTalk streams stuff to get the IP-in-DPP packets fed back into something 
that looks to the kernel like an Ethernet interface, then use NCSA telnet. 
Given ADSP you'd use that instead with a specialised version of getty. Neither 
of these things currently exist.
--

William Roberts                 ARPA: liam@cs.qmw.ac.uk
Queen Mary & Westfield College  UUCP: liam@qmw-cs.UUCP
Mile End Road                   AppleLink: UK0087
LONDON, E1 4NS, UK              Tel:  071-975 5250 (Fax: 081-980 6533)