Date: Wed, 26 May 93 04:30:14 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 #135
To: tcp-group-digest
TCP-Group Digest Wed, 26 May 93 Volume 93 : Issue 135
Today's Topics:
386BSD and Linux as packet systems
AX-25 on BSD
Compiling new NOS code
CSLIP on AX.25 frames?
POP3 Bug Report. Anyone there?
RSPF code
TheNet X1H patch
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: Tue May 25 11:31:25 1993
From: iiitac@pyr.swan.ac.uk
Subject: 386BSD and Linux as packet systems
To: tcp-group@ucsd.edu
Before you leap off into porting things left right and centre take a look at
the software that is already ported. In paticular WAMPES although documented
atrociously is actually a superb piece of software when you play with it.
It lets you write simple application programs to talk to the network down
a socket, as well as providing all the usual ka9q net/nos functionality
and a much better netrom interface than the DOS ka9q code I was used too.
I've twiddled with my version a little and I've now got a machine giving
users accounts into a chrooted safe area as well as a pretty convincing
thenet node imitation any user can get to just by typing 'node', a
radio telnet, finger, pop client, rlogin (untested), ax25 connect commands.
Most of those are really simple programs because WAMPES does the work.
The other good thing I've found is that WAMPES is fairly resource friendly,
with a minimal machine kernel and wampes running pretty much alone I can
get WAMPES to run on a Linux machine in 1Mb.
The next project is to add an X windows redirector to it, which also should
be fairly easy.
Alan
------------------------------
Date: Tue, 25 May 93 13:50:00 +1000
From: wkt@csadfa.cs.adfa.oz.au (Warren Toomey)
Subject: AX-25 on BSD
To: dave@holl.com (David Vrona), TCP-Group@UCSD.Edu
In atricle by David Vrona:
>
> >
> > 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.
I meant in the OS kernel, where it belongs :-)
Warren vk1xwt
------------------------------
Date: Tue, 25 May 1993 16:56:02 -0600 (CST)
From: "Erik Olson" <erik@marge.phys.washington.edu>
Subject: Compiling new NOS code
To: tcp-group@ucsd.edu
I'm trying my best to compile up the new base code without punching my hand
through a wall. All I wanted was to fix a small POP3 bug I found, really
that's all. Thought it might be cool to use the latest code. Ha hahehaha!!
What's there? A docless zip file! I guessed it was the right one because
it was the largest one. Some code for RCS on the PC. No indications on
where I can put stuff or how I can do a simple extraction into normal source
code. (And this is all just PRELIMINARY to the "easy" part of integrating
the POP3 server and brand new LPD back into there).
So can anyone give me a quick rundown on how to deal with RCS? Directories,
config files, commands. Just the facts. Thanks
Erik ("Will they put POP3 and LPD in base code by the year 2000?") Olson
---
Erik Olson (in lab) erik@marge.phys.washington.edu
University of Washington olson@phys.washington.edu
Cosmic Ray Lab, Phys. 405
------------------------------
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: Tue, 25 May 1993 17:39:14 -0600 (CST)
From: "Erik Olson" <erik@marge.phys.washington.edu>
Subject: POP3 Bug Report. Anyone there?
To: tcp-group@ucsd.edu
I have no idea which flavors of NOS use the POP3 server, but I know a few
do. There is a small bug in the code that affects only the LIST command.
When messages sizes exceed 32k, a negative size is reported for the message
length. In the new pre-release of NUPOP, there is a nifty feature to reject
messages above a certain size, and is dependent on a working LIST command.
Here is the fix:
Change
list_single_rsp[] = "+OK %d %d\n",
to
list_single_rsp[] = "+OK %d %ld\n",
Drop me a line if you do the change; I'd be interested in who's actually
using the code.
- Erik
---
Erik Olson (in lab) erik@marge.phys.washington.edu
University of Washington olson@phys.washington.edu
Cosmic Ray Lab, Phys. 405
------------------------------
Date: Tue, 25 May 1993 13:52:00 +0200 (MET DST)
From: Lars Petterson <d8lars@dtek.chalmers.se>
Subject: RSPF code
To: tcp-group@ucsd.edu
I've just uploaded my latest modified (still sm0rgv base)
RSPF code to ucsd.edu. It's called rspf0519.zip and is
now in /hamradio/packet/tcpip/incoming but will soon be
moved to /hamradio/packet/tcpip/pa0gri
Some changes;
It works for routers with several interfaces.
It does have a problem if it can hear a station on several
interfaces and there is one interface on wich the link is
bad. When it receives a RRH or an ARP request on that interface
it will switch the route and start pinging. The ping will
perhaps not be successfull and we will lose our connection
to this router (or endstation). This is the famous (?) problem
with iproute, we need a way to send a route out to an interface
not using the route in the routing table. I'll look into
this later this summer when my holidays starts.
It can switch between interfaces (I think the base code
couldn't).
It works over ax25 digipeats and netrom. This is done by using
the manual ARP:s for these stations. As before, it also works
for SLIP and interfaces using ARP.
It will check stations sending ARP requests. This will make
the code a bit faster in finding new stations (end stations
or routers that have not yet sent RRH's). This will happen
even if the request is not sent to our station.
I have corrected some protocol errors (the base code not
following the protocol). The old code used to purge all
routes through a router that just sent it a routing update
with a sequence number higher than the old one. This was
not that good, especially when one has a station acting as
main router, as we have. We kept losing our routes and did
not understand why for a wery long time :-)
The old code also used to send out partial updates while
sending full updates creating a real mess. This has been
corrected
And lots, lots more. See rspf.c and rspf.inf for more information.
I would advice everyone using RSPF to switch to this one as it
is as close to the 2.1 protocol as one can get (i think).
If you experience any troubles, bugs etc, please write a
letter to me so I could correct the code.
If you have any suggestions on things to make the code better,
also write.
I will send a reply to Mike when I get some more spare time,
I'm doing some exams just now and have been studying the
last weeks but my summerholiday starts on saturday so I'll send
a reply later on.
Have a nice summer, all of you!
73 de sm6rpz, Lars.
--
Lars Pettersson Chalmers University of Technology
------------------------------
Date: Tue, 25 May 1993 21:01:40 -0400 (EDT)
From: MIKEBW@ids.net (Mike Bilow, <MIKEBW@ids.net>)
Subject: TheNet X1H patch
To: tcp-group@ucsd.edu
I applied the patch instructions which were circulated on the group to
the THENET2.X1H file which is part of the TheNet X1H distribution, and
I placed the patched file together with the text of the message to the
group in /hamradio/packet/tcpip/incoming/x1h-pat1.zip on UCSD.EDU. It
is about 19K in ZIPped format.
-- Mike Bilow, <mikebw@ids.net> (Internet)
N1BEE @ WA1PHY.#EMA.MA.USA.NA (AX.25)
------------------------------
End of TCP-Group Digest V93 #135
******************************
******************************