Date: Tue, 25 May 93 04:30:08 PDT
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 #134
To: tcp-group-digest
TCP-Group Digest Tue, 25 May 93 Volume 93 : Issue 134
Today's Topics:
AX-25 on BSD
BSD 386
CSLIP
CSLIP on AX.25 frames? (2 msgs)
Ham-Com anyone?
SVR4 files for WAMPES port on ucsd.edu (4 msgs)
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: Mon, 24 May 93 8:33:05 CDT
From: dave@holl.com (David Vrona)
Subject: AX-25 on BSD
To: TCP-Group@UCSD.Edu
>
> Once AX.25 code becomes available for 386bsd/BSD386/Net-2, I'll modify the
> existing cslip code and try it out.
>
Is it not already available on wampes? Wampes has been ported to 386bsd.
dave
--
David Vrona N9QNZ +1 708 680 2829 (voice)
Hollister Incorporated +1 708 918 3860 (fax)
2000 Hollister Drive Internet: dave@hp1.holl.com
Libertyville, IL 60048-3781 UUCP: {well connected}!ddsw1!hp1!dave
Opinions expressed are my own and not those of Hollister Incorporated.
------------------------------
Date: Mon, 24 May 1993 15:25:33 -0500 (CDT)
From: S. R. Sampson <ssampson@sabea-oc.af.mil>
Subject: BSD 386
To: TCP-Group@UCSD.Edu
I'm currently installing bsd386 on my box again. The first attempt died when
I downloaded the password encryption stuff from ugle.unit.no and made a series
of errors installing it, it was ugly. I installed the ugle stuff early this
time :-) (All this is because of the export restrictions on DES, which caused
the author to leave the passwords in the plain. The irony is that I went to
Norway to get the DES patches, ha). During the big crash I tried linux out, but
I didn't like all that partitioning stuff, and it just seemed less than what I
experianced on the bsd version. I did try bsd on a 386sx with 2Meg of RAM. It
thrashed itself to death, now I'm on 8Meg machine and it really glides. I
picked up a hard disk and just plug it in when I want to switch from DOS. Later
it will go into the 386sx (as soon as I find that bad memory chip) and become
my packet engine. It looks like about a 100 Meg of poop after installation, so
a big disk is in order (takes 4 boxes of 1.44 Meg disks to store distribution).
I tried the bsd SLIP with the NCSA FTP and it was *really* slow, rz worked much
better. My plans are to port the KISS, AX.25, and the JNOS BBS Mailbox "suite".
And use the uucp code for the internet mail transfers (I don't have access to
dial-up SLIP, or ethernet anyway).
I think this will be the way to go, as all the TCP/IP and DNS stuff is there,
and the trace code as a seperate process can now develop into an interface
and packet monitoring function. I took the old ax25 monitor program and made
it a process for Coherent which interfaced to the KISS routine via a named
pipe, but Coherent has so many bugs in the non-blocking I/O area and I got
tired of fighting it. The K5JB Net version, does work pretty good with it
though, and includes the pseudo terminal login code. Coherent also worked well
in the 2Meg space. I'm going with the version with source code however, and
any low level bugs can be dealt with directly.
--
Steve, n5owk@n5owk.ampr.org
------------------------------
Date: Mon, 24 May 93 10:30:06 -0700
From: karn@qualcomm.com (Phil Karn)
Subject: CSLIP
To: iiitac@pyr.swan.ac.uk, tcp-group@ucsd.edu
This topic has come up before, several years ago I think. There are
some other problems with header compression over AX.25 that haven't
been mentioned yet this time around.
1. The dominant source of overhead on most AX.25 channels is the
half-duplex turnaround time, including tx/rx switchover and modem
synchronization time. Next is the AX.25 link level protocol overhead,
which cannot be compressed on a multiple access channel (one sender
does not send everything that the receiver gets). So even if it worked
perfectly, TCP/IP header compression wouldn't buy much here.
2. And it won't work perfectly. Header compression assumes a
relatively low error rate on the physical channel, and it transmits an
uncompressed header whenever there is a TCP retransmission. These
occur frequently over amateur packet radio channels, further reducing
any advantage of compression.
TCP/IP header compression is a major win with interactive traffic over
slow point-to-point channels. I use it with TCP/IP over our CDMA
digital cellular system. But its characteristics are *very* different
from those of amateur packet radio.
Phil
------------------------------
Date: Mon, 24 May 93 13:19:55 +0200
From: jt@fuw.edu.pl
Subject: CSLIP on AX.25 frames?
To: tcp-group@ucsd.edu
> Date: Thu, 13 May 93 10:05:28 +1000
> From: wkt@csadfa.cs.adfa.oz.au (Warren Toomey)
> Message-Id: <9305130005.AA25866@csadfa.cs.adfa.oz.au>
>
> I had this idea last night, why not use Van Jacobsen TCP/IP header
> compression on AX.25 frames. Obviously, as an AX.25 interface isn't point
> to point, a machine would need structures for every destination that it is
> TCP connected to. Apart from that, I can't see any major obstacles.
Alan (iiitac@pyr.swan.ac.uk) wrote about few drawbacks (Mon May 24
11:37:04 1993, Message-Id: <516@feak>, Subject: CSLIP), I see few more:
1. Unlike data compression which affects end nodes only, header
compression requires every routing node to have compress/decompress
capability to know where the packet is to be routed to.
2. I suppose data sent in a packet can be recognized when data from
previous packets is known; when header is compressed what way can
identify which previous packets should be applied ?
Of course, it is possible to use compression at link level - sending
(either original sender or router) node compresses everything it sends,
and receiving (either destination or intermediate) node decompresses it
before any processing. It requires one set of tables for node pair and
may be restricted to pairs of nodes exchanging packets frequently.
In fact, it forces AX25 to act as point-to-point. And at least
information necessary to distinguish packet resent because of timeout
(some sequence number) should not be compressed! 73's, JT
------------------------------
Date: Tue, 25 May 93 13:14:41 +1000
From: wkt@csadfa.cs.adfa.oz.au (Warren Toomey)
Subject: CSLIP on AX.25 frames?
To: jt@zfja-gate.fuw.edu.pl (Jerzy Tarasiuk), tcp-group@ucsd.edu
In atricle by jt@fuw.edu.pl:
>
> > From: wkt@csadfa.cs.adfa.oz.au (Warren Toomey)
> >
> > I had this idea last night, why not use Van Jacobsen TCP/IP header
> > compression on AX.25 frames.
>
> Alan (iiitac@pyr.swan.ac.uk) wrote about few drawbacks (Mon May 24
> 11:37:04 1993, Message-Id: <516@feak>, Subject: CSLIP), I see few more:
>
> 1. Unlike data compression which affects end nodes only, header
> compression requires every routing node to have compress/decompress
> capability to know where the packet is to be routed to.
Ah yes,I hadn't thought of that :-)
Oh well, it was just an idea.....
Warren vk1xwt
------------------------------
Date: Mon, 24 May 93 05:16:10 CST
From: kf5mg@dfwgate.ampr.org
Subject: Ham-Com anyone?
To: tcp-group@ucsd.edu
Anyone going to be at Ham-Com? It's going to be held June 4, 5 and 6 at
the Arlington Convention Center. Arlington is located between Dallas and
Ft.Worth Texas.
Local IP is 1200b on 145.67 and 444.30/449.30. dfwgate.ampr.org should
be accessable from Ham-Com. If you need an account on dfwgate.ampr.org,
let me know now. Send an Internet note to kf5mg@kf5mg.ampr.org or
kf5mg@dfwgate.ampr.org and I'll set it up for you.
73's de Jack - kf5mg
AMPRnet - kf5mg@kf5mg.ampr.org - 44.28.0.14
AX25net - kf5mg@kf5mg.#dfw.tx.usa.na - work (817) 962-4409
Internet - kf5mg@vnet.ibm.com - home (817) 488-4386
-------------------------------------------------------------------
| "I am Homer, of Borg...prepare to be assim -- ooo, donuts." |
-------------------------------------------------------------------
------------------------------
Date: Mon, 24 May 93 11:30:54 CDT
From: dave@holl.com (David Vrona)
Subject: SVR4 files for WAMPES port on ucsd.edu
To: TCP-Group@ucsd.edu
I have put two files in the tcp-ip/incoming directory. They are:
svr4-wampes-readme
svr4-wampes.tar.Z
Please look at the readme before you start. The tar file contains all of the
modified wampes files for the SVR4 port.
Have fun!
--
David Vrona N9QNZ +1 708 680 2829 (voice)
Hollister Incorporated +1 708 918 3860 (fax)
2000 Hollister Drive Internet: dave@hp1.holl.com
Libertyville, IL 60048-3781 UUCP: {well connected}!ddsw1!hp1!dave
Opinions expressed are my own and not those of Hollister Incorporated.
------------------------------
Date: Mon, 24 May 93 11:30:54 CDT
From: dave@holl.com (David Vrona)
Subject: SVR4 files for WAMPES port on ucsd.edu
To: TCP-Group@ucsd.edu
I have put two files in the tcp-ip/incoming directory. They are:
svr4-wampes-readme
svr4-wampes.tar.Z
Please look at the readme before you start. The tar file contains all of the
modified wampes files for the SVR4 port.
Have fun!
--
David Vrona N9QNZ +1 708 680 2829 (voice)
Hollister Incorporated +1 708 918 3860 (fax)
2000 Hollister Drive Internet: dave@hp1.holl.com
Libertyville, IL 60048-3781 UUCP: {well connected}!ddsw1!hp1!dave
Opinions expressed are my own and not those of Hollister Incorporated.
------------------------------
Date: Mon, 24 May 93 11:30:54 CDT
From: dave@holl.com (David Vrona)
Subject: SVR4 files for WAMPES port on ucsd.edu
To: TCP-Group@ucsd.edu
I have put two files in the tcp-ip/incoming directory. They are:
svr4-wampes-readme
svr4-wampes.tar.Z
Please look at the readme before you start. The tar file contains all of the
modified wampes files for the SVR4 port.
Have fun!
--
David Vrona N9QNZ +1 708 680 2829 (voice)
Hollister Incorporated +1 708 918 3860 (fax)
2000 Hollister Drive Internet: dave@hp1.holl.com
Libertyville, IL 60048-3781 UUCP: {well connected}!ddsw1!hp1!dave
Opinions expressed are my own and not those of Hollister Incorporated.
------------------------------
Date: Mon, 24 May 93 11:30:54 CDT
From: dave@holl.com (David Vrona)
Subject: SVR4 files for WAMPES port on ucsd.edu
To: TCP-Group@ucsd.edu
I have put two files in the tcp-ip/incoming directory. They are:
svr4-wampes-readme
svr4-wampes.tar.Z
Please look at the readme before you start. The tar file contains all of the
modified wampes files for the SVR4 port.
Have fun!
--
David Vrona N9QNZ +1 708 680 2829 (voice)
Hollister Incorporated +1 708 918 3860 (fax)
2000 Hollister Drive Internet: dave@hp1.holl.com
Libertyville, IL 60048-3781 UUCP: {well connected}!ddsw1!hp1!dave
Opinions expressed are my own and not those of Hollister Incorporated.
------------------------------
End of TCP-Group Digest V93 #134
******************************
******************************