Technology and Trends
 Linux Activists Mailing List Archives
  
Subject: BSD sockets+TCP/IP
Date: Thu, 16 Jan 92 15:14:19 -0500
From: entropy@ee.WPI.EDU (Lawrence C. Foard)
To: linux-activists@joker.cs.hut.fi

IF YOUR WORKING ON TCP/IP OR SOCKETS READ THIS...

It appears that no one is working on sockets or TCP/IP yet? A friend and I are
planning to start working on this if no one has already started work. 
If you are working on it please please write so we don't waste our time
duplicating efforts.

Questions:

What ethernet boards would you like to see supported?
Currently we are planning to buy an intel board but don't have money to buy
other boards so would appreciate donations or loans of other manufactorers
cards. Any technical docs would be helpful, or source code for software that
uses them.

Subject: Re: BSD sockets+TCP/IP
Date: Thu, 16 Jan 92 17:04:15 EST
From: hetrick@sparky.eeel.nist.gov (Paul Hetrick)
To: linux-activists@joker.cs.hut.fi
In-Reply-To: <9201162014.AA00798@wintermute.WPI.EDU>

> Date: Thu, 16 Jan 92 15:14:19 -0500
> From: entropy@ee.WPI.EDU (Lawrence C. Foard)
> To: linux-activists@joker.cs.hut.fi
> Subject: BSD sockets+TCP/IP
>
> IF YOUR WORKING ON TCP/IP OR SOCKETS READ THIS...
> 
> It appears that no one is working on sockets or TCP/IP yet? A friend and I
> are planning to start working on this if no one has already started work. 
> If you are working on it please please write so we don't waste our time
> duplicating efforts.
> 
> Questions:
>
> What ethernet boards would you like to see supported?
> Currently we are planning to buy an intel board but don't have money to buy
> other boards so would appreciate donations or loans of other manufactorers
> cards. Any technical docs would be helpful, or source code for software
> that uses them.
>

   TCP/IP and Sockets are more than I have time to tackle, but I might be 
able to point you to some Code and docs.  Try FTPing to zaphod.ncsa.uiuc.edu
[141.142.20.50].  They have a PD (or at least freely distributed) telnet
program for MS-DOS with drivers for LOTS of ethernet boards.  The source
code for all the drivers is in one BIG .zip file.  If you could base your
low-level drivers on this code it would probably make it easier to port to
other boards. 

  Hope this helps

Paul
hetrick@eeel.nist.gov

Subject: Re: BSD sockets+TCP/IP
Date: Thu, 16 Jan 92 17:12:39 -0500
From: tytso@ATHENA.MIT.EDU (Theodore Ts'o)
To: hetrick@sparky.eeel.nist.gov
To: entropy@ee.WPI.EDU (Lawrence C. Foard)
Cc: linux-activists@joker.cs.hut.fi
In-Reply-To: Paul Hetrick's message of Thu, 16 Jan 92 17:04:15 EST,
Reply-To: tytso@athena.mit.edu

   Date: Thu, 16 Jan 92 17:04:15 EST
   From: hetrick@sparky.eeel.nist.gov (Paul Hetrick)

      TCP/IP and Sockets are more than I have time to tackle, but I might be 
   able to point you to some Code and docs.  Try FTPing to zaphod.ncsa.uiuc.edu
   [141.142.20.50].  They have a PD (or at least freely distributed) telnet
   program for MS-DOS with drivers for LOTS of ethernet boards.  The source
   code for all the drivers is in one BIG .zip file.  If you could base your
   low-level drivers on this code it would probably make it easier to port to
   other boards. 

If this is the Clarson packet driver stuff, be aware that the code
assumes you are running in 16 bit real mode.  It may be non-trivial to
port them so that they work in a 32-bit protected mode.  You may want to
look at them and form your own opinion.

Whether or not you use the MS-LOSS packet drivers, it would be a very
good idea to have a well-defined abstraction boundary between the
Networking/IP layer and the Ethernet driver layer.  Then you can publish
the interface early on, and people can write their own drivers for their
ethernet cards with a minimum of pain.

Lawrence, I assume that you will be using the BSD networking release as
a base?

Subject: Re: BSD sockets+TCP/IP
Date: Thu, 16 Jan 92 16:46:58 -0800
From: Paul Rubin <phr@ocf.Berkeley.EDU>
To: hetrick@sparky.eeel.nist.gov, linux-activists@joker.cs.hut.fi

There are at least a couple of free implementations of TCP/IP,
though I don't know about sockets.  One was written by Russ Nelson
and is GNU-copylefted, but I don't know what functionality it
includes.  I believe it is ftpable from grape.soe.clarkson.edu.
The other was written by Phil Karn KA9Q and includes pretty
much everything, but I'm not sure of the exact distribution
permissions.  It's called the KA9Q TCP package.  I'm not sure
where to ftp a copy but "archie" should be able to find it,
or I could ask someone.  Having no network hardware I haven't
really looked into either of these.  I believe there was also
a free package written at MIT that was the basis for FTP Software's
implementation but I don't know more details.

Subject: Re: BSD sockets+TCP/IP
Date:    Fri, 17 Jan 92 09:26 CST
To: Paul Rubin <phr@OCF.BERKELEY.EDU>
From: Jay Maynard                          <S0JM@ADMIN.HSC.UTH.TMC.EDU>
Cc: linux-activists@joker.cs.hut.fi

(Paul Rubin, about existing TCP/IP packages:)
> The other was written by Phil Karn KA9Q and includes pretty
> much everything, but I'm not sure of the exact distribution
> permissions.  It's called the KA9Q TCP package.

The KA9Q NOS TCP/IP package is available in several flavors for anonymous
FTP from ucsd.edu; look in the hamradio/tcpip/nos directory. It is licensed
for amateur and non-profit educational use.

NOS is probably going to be a lot of work to port to a native Linux
environment, as it is a monolithic program with its own built-in
multitasker and user support system...some work has been done in that area,
but it's a pain. Different folks' efforts can be found on ucsd.edu as well.

...Jay Maynard