Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!ames!ucbcad!ucbvax!ORVILLE.ARPA!lekash
From: lekash@ORVILLE.ARPA (John Lekashman)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: NSC HyperchannelB - Ethernet TCP/IP gateway
Message-ID: <8707030140.AA19759@orville.arpa>
Date: Thu, 2-Jul-87 21:40:45 EDT
Article-I.D.: orville.8707030140.AA19759
Posted: Thu Jul  2 21:40:45 1987
Date-Received: Sat, 4-Jul-87 20:48:18 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 36

hi.
There are things that will move IP packets between hyperchannels
and other networks.

vaxes running bsd.
suns.

Various vendors have mentioned the idea of building it into
their gatways.

Most that I have seen operate on hyperchannel A, the 50 mbit
version.  Porting to hyperchannel B should not be that
hard.  We just don't have any, because ethernets are so
much cheaper.

There is a spec from NSC on how to encapsulate IP over
hyperchannel.  It will likely occur as an RFC one day soon.

The distribution hyperchannel driver on a BSD tape is broken,
and doesn't follow this spec besides.

I have drivers for:
vaxes running 4.3 BSD.  (4.2 is trivial from that)
silicon graphics Irises, running 3.5 (or it may be 3.6 by now)

you can have these for free.  Wollongong has installed this driver
on a VMS vax for us, you can probably give them some amount
of money for it, but they shouldn't charge you much, because 
I gave it to them.

Availability: public ftp from orville.arpa.  I don't guarantee it is
as up to date as whatever I last built.  I'll probably copy
the current version over next week.  Upgrades include things
to deal with special NSC hardware, so its no great need.

					john