Date: Sun, 14 Nov 93 04:30:01 PST
From: Advanced Amateur Radio Networking Group <tcp-group@ucsd.edu>
Errors-To: TCP-Group-Errors@UCSD.Edu
Reply-To: TCP-Group@UCSD.Edu
Precedence: Bulk
Subject: TCP-Group Digest V93 #296
To: tcp-group-digest
TCP-Group Digest Sun, 14 Nov 93 Volume 93 : Issue 296
Today's Topics:
SLIP, AX.25, KISS, Etc...
Send Replies or notes for publication to: <TCP-Group@UCSD.Edu>.
Subscription requests to <TCP-Group-REQUEST@UCSD.Edu>.
Problems you can't solve otherwise to brian@ucsd.edu.
Archives of past issues of the TCP-Group Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives".
We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party. Your mileage may vary. So there.
----------------------------------------------------------------------
Date: Sun, 14 Nov 93 08:39:31 UTC
From: n8fow@wsu.n8fow.ampr.org
Subject: SLIP, AX.25, KISS, Etc...
To: tcp-group@ucsd.edu
I'd rather see a packet driver get written first rather than code for
a tnc. Also I can't see SLIP being used either. Just about all software
supports ethernet cards and the code should be written to look like an
ethernet instead. That way things such as broadcast addresses, and LANS
instead of point-to-point can be used. I have drivers here (no source laying
around though) that look just like an ethernet to the software (ran NOS and
FTP software PC/TCP package) and messed around with it on SLIP and SLFP
dial-ins before. Also the SLIP8250 driver supports SLIP, KISS and AX.25
options too. I've run the SLIP and KISS before, but have no idea what the
AX.25 option does. Doesn't the SUN AX.25 code do something like take a
callsign and convert it into an ethernet type address? Then to the OS it'll
look just like an ethernet but the AX.25 code will convert it back to the
callsign again and send it out the serial port to a KISS tnc ??? Been a while
since I've looked at that program. How about just taking that code and
write a driver that you enter your callsign in. I really think that limiting
it to a SLIP driver is a waste of time to start with. WIth a packet driver
that does what I said you can run it on your KISS tnc. If you have a
point-to-point link though then you can get away with just running though, but
for regular TCP/IP packet networks you will probably need other capabilities
that SLIP can't handle.
73, Ron Michigan AMPRNet system #48 (TCP/IP)
AMPRNet : n8fow@n8fow.ampr.org
n8fow@wsu.n8fow.ampr.org
Internet : ron@chaos.eng.wayne.edu
------------------------------
End of TCP-Group Digest V93 #296
******************************
******************************