newman_r@cho006.cho.ge.com (02/03/91)
Hello Netlanders! I'm looking for ways to implementing a PC to PC file transfer mechanism over a non-ethernet LAN, and it seems like TCP/IP would be a natural for this. Specifically, I was thinking of using NCSA Telnet as the PC application software, and writing a packet driver to provide the interface to the LAN hardware. My question for the net: `is this a reasonable approach?', and if so, where can I find the specifics for Telnet/packet driver interface? Many thanks, -- Bob Newman internet: newman_r@cho006.CHO.GE.COM GE Fanuc Automation, Inc. uunet: ...uunet!virginia!edison!rfn
nelson@sun.soe.clarkson.edu (Russ Nelson) (02/04/91)
In article <1991Feb3.085247.1922@cho006.cho.ge.com> newman_r@cho006.cho.ge.com writes:
I'm looking for ways to implementing a PC to PC file transfer
mechanism over a non-ethernet LAN, and it seems like TCP/IP would
be a natural for this. Specifically, I was thinking of using NCSA
Telnet as the PC application software, and writing a packet driver
to provide the interface to the LAN hardware.
My question for the net: `is this a reasonable approach?',
Yes. There are two ways to do it:
1) You can lie, and claim that your packet driver interfaces to Ethernet.
This can be easy to do if your network allows packets as large
as 1514 bytes. It can also violate the layering concept, which can
make your life more difficult.
2) You can invent a new kind of packet type, and modify NCSA Telnet so that
it can access this new packet type. I suggest you start with a version
of NCSA Telnet that also supports SLIP packet drivers, because the code
to handle multiple packet driver types will already be there.
and if so, where can I find the specifics for Telnet/packet driver
interface?
vax.ftp/com:pub/packet-driver.ascii
--
--russ <nelson@clutx.clarkson.edu> Humble Quaker, and damned proud of it.
It's better to get mugged than to live a life of fear -- Freeman Dyson
I joined the League for Programming Freedom, and I hope you'll join too.