home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!pipex!doc.ic.ac.uk!uknet!comlab.ox.ac.uk!dominic
- From: dominic@natcorp.ox.ac.uk (Dominic Dunlop)
- Newsgroups: comp.sys.sun.hardware
- Subject: Re: Using non-TCP/IP ethernet
- Message-ID: <1993Jan25.100420.1109@onionsnatcorp.ox.ac.uk>
- Date: 25 Jan 93 10:04:20 GMT
- References: <1993Jan22.171043.23286@msc.cornell.edu> <1993Jan22.152802.1233@uoft02.utoledo.edu>
- Organization: British National Corpus, Oxford University, GB
- Lines: 20
- Originator: dominic@onions.natcorp.ox.ac.uk
-
- I lost the original post, but, in article
- <1993Jan22.152802.1233@uoft02.utoledo.edu> jkp@anwsun.phya.utoledo.edu
- (Jens Petersohn) follows up:
- > If you are refering to EtherTalk from Apple, you are out of luck since the
- > interface does nothing by itself, what you need is a packet driver and a
- > network stack to drive Ethertalk over the ethernet. Those are software modules
- > generally bound to the kernel. I am not aware of such software for EtherTalk,
- > but I know they exist for NetOS like DECnet.
-
- Jens is mostly right, BUT
-
- a) You can also do protocol stacks in user space. SunOS (Solaris
- too??) gives you access to the raw Ethernet packet driver through
- /dev/nit in order that you can do this sort of thing.
-
- b) An Ethertalk stack (and much else besides) exists for UNIX in the
- form of the CAP (Columbia AppleTalk Protocol) package, freely
- available from an archive site near you.
- --
- Dominic Dunlop
-