| |
DB9ER > APPLE 27.02.97 21:48l 187 Lines 9423 Bytes #-10822 (0) @ EU
BID : 272732DB0EAM
Read: DH9MEC DJ3YQ DF5GI DB9SH GUEST DK3EL
Subj: Net/Mac2.3.62(JNOS)1/4.asc
Path: DB0AAB<DB0PV<DB0MAK<DB0SON<DB0SIF<DB0KH<DB0EAM
Sent: 970227/1802z @:DB0EAM.#HES.DEU.EU [Kassel TheBox DB8AS] $:272732DB0EAM
de DB9ER @ DB0EAM.#HES.DEU.EU (Dieter)
to APPLE @ EU
char version[] = "NET/Mac 2.3.62";
/*
* What this application is intended for:
* ======================================
* NET/Mac is an application, that has been created for ham-radio operators.
* It can be used to hook up a Macintosh to the amateur-radio 'packet-radio'
* wireless network. NET/Mac supports the TCP/IP protocolstack.
*
* If you want to get acquainted with TCP/IP over packetradio, then I suggest
* you read the book: NOSintro, TCP/IP over Packet Radio. It has been written
* for the PC world but PC's and Macintoshes mix well in this area. The author
* of the book is Ian Wade, G3NRW, ISBN: 0-897649-00-2.
*
* To use NET/Mac you need:
* a) a ham-radio license
* b) a transceiver connected to an antenna
* c) a TNC that supports the KISS protocol
* (A TNC is like a modem... A modem however drives a telephoneline, while
* a TNC drives a transmitter and receiver...)
* d) a Macintosh 512 or newer
* e) a complete working environment for NET/Mac, which consists of directories
* for mail, logfiles, an example of autoexec.net and some more configuration
* (example-)files.
* Also you need Ivo ON1XK's mailer (IM/Mac).
* Usually you can download both the environmentfile as well as IM/Mac from
* the same place you downloaded NET/Mac from. Look for the files that carry
* names like: 'IM_Mac_<verion-number>.sea.hqx' and 'radio-config.sea.hqx'
* (also seen around as: radio-environment.sea.hqx). Sometimes even the word
* 'radio-' isn't there.
*
* New versions ususally get downloaded to:
* - sumex-aim.stanford.edu (directory: info-mac/comm)
* - ftp.ucsd.edu (directory: pub/hamradio/packet/tcpip/incoming)
*
* History
* =======
* The application NET/Mac, was ported (from Phil Karn's NET) to the Mac
* by Dewayne Hendricks, WA8DZP.
*
* This release is based on Dewayne's NET/Mac 2.0 and contains all mods of
* the newer NET/Mac 2.2. Both NET/Mac 2.0 and 2.2 were released by Dewayne
* Hendricks and Doug Thom. Since some time I have been making mods (bug-
* fixes and enhancements) to their NET/Mac, and have always sent them these
* mods. Now that they are working on a new application, that will support
* high speed networks and will also support AppleTalk over that network,
* they have given me permission to distribute their NET/Mac with my mods
* installed.
*
* I hope you'll like the work I have done so far, and I will try to keep
* 'upgrading' this application as much as possible. Don't bother Dewayne
* or Doug in case you have problems or questions. Don't hesitate to call
* me if any help is needed. I will try to be as helpful as I can. If you
* want to become member of a 'NET/Mac distributionlist' (I myself prefer
* internet for sending out newer versions...) then please leave me a note.
* I may start sending out UpdateMaker documents that will allow you to
* update NET/Mac to a newer version as soon as one has become available.
*
* I'd like to thank Dewayne and Doug for the sources they gave me to work
* on and Joe AF2J for already sending me a number of mods.
*
* Adam van Gaalen, PA2AGA.
*
*
* My mail addresses are: internet: pa2aga@nitg.tno.nl (office)
* or: adam@caiw.nl (home)
* ham tcp/ip: pa2aga@pa2aga.ampr.org (44.137.33.4)
* ham BBS: pa2aga@pi8vnw.#zh2.nld.eu
*/
---------------------------------- Snip ------------------------------------
About some new things and new (or changed) commands and how to use those:
UPLOAD and RECORD: Switch from the AX.25- or TELNET window to the console
window and type 'UPLOAD <filename>' or 'RECORD <filename>'. So make sure
you go from the window for which the UPLOAD/RECORD is intended DIRECTLY
to the console window, otherwise you'll get an errormessage.
In NET/Mac(58) and higher versions you may also use the format:
upload <filename> [<session>] and record <filename> [<session>|off]
ROUTE EXPANDED: Displays the routing table like the ROUTE command does,
but IP-numbers will be translated into hostnames. This may take some time
because the hostnames have to be looked up in the HOSTS.NET file.
I suggest you just use this form when you have a RAM-cache enabled in
your controlpanel. Oh... you cannot type a shortcut for EXPANDED, so
'ro e' will not work. This is just to prevent one from accidently typing
this command.
TCP MRTT [<milliseconds>]: You may use this new command to set a Maximum
ReTry Timer. The default time is 3600 seconds (3600000), which means
that when a link has gone down, or has gone bad, there will be a retry
at least once every hour. This timer was created so that the retry-
timer doesn't go up too high. Don't set this timer to a (too) low value,
because you may introduce a lot of retries for a down link, which means
a lot of unnecessary traffic on the frequency. This MRTT is valid for
ALL open connections. I suggest you DON'T set it to a value lower than
900000 (900 seconds) or so.
#$debug on: You may choose to list the commands in the autoexec.net-file
when they are being executed. This is very handy to trace errors in the
startup-file. NET/Mac will start showing the commands when it discovers
a line containing #$debug on in the autoexec.net file.
FLOW [ON|OFF]: Enable or disable 'flow-control' for TELNET-, NET/ROM-
and AX.25-sessions. With flowcontrol ON an incoming line will not be
written to the screen as long as you are in the middle of typing a line
for the remote station. Incoming data will be displayed as soon as you
hit the <RETURN> key. So far flowcontrol is not perfect, but I think it
is a lot better than it used to be. Anyway, it works fine, as long as
you don't type HALF a line in one session, and then switch to another and
do some typing there, and then switch back and so on. If you simply type
a COMPLETE line at a time it's OK.
ALERTS [<number>]: Sets the number of bell-strikes for incoming sessions.
<number> may be a number from 0 to 5. When <number> is 0, no bell will
sound for incoming sessions or incoming mail. When <number> is bigger than
0 incoming mail will sound 1 bell (like it used to be), but incoming
live sessions like TELNET-, AX.25- and NET/ROM-sessions will sound as
many bells as defined in the ALERTS command. This command was created so
incoming sessions may draw more attention than incoming mail- or finger-
sessions.
At startup the program prints out a line containing the Macintoshtype and
two type-numbers. If it says 'Macintosh Computer', then please inform me
about the type of Macintosh you are running NET/Mac on (like Plus, SE etc.)
and the typenumbers it printed, so that I can add the Macintoshtype you
are using. So far it should recognize most of the Macintoshes.
Note that a Mac-XL running a Mac Plus emulator, or a 512Ke with a SCSI-
interface and/or 1 MByte of memory (or more), are considered to be a Plus!
TRACEONLY [ALL|CALLSIGN] allows you to only expand packets to or from a
given station (doesn't work for AppleTalk-tracing). This 'option' was
installed because sometimes, on a very busy channel, it used to be close
to impossible to return from the trace-window to the console-window (in
order to switch tracing off).
OUTGOING-MAIL-OPTIMIZER: NET/Mac(54) and higher versions contain an
'outgoing-mail-optimizer'. It performs the following task:
Suppose someone sends me (pa2aga) ONE mail for a number of hams, like:
To: pe0mar@pa2aga pa0aax@pa2aga pa0gln@pa2aga on1xk@pa2aga
Now, what used to happen is the following:
Using the alias-file of pa2aga, mail would be re-queued to:
pe0mar@pi8hvh pa0aax@pi8hvh pa0gln@pi8mac on1xk@pi8hvh
4 files in total, of which 3 would be sent (one after another) to pi8hvh.
I always thought this was a waste of bandwidth, so...
My optimizer does the trick now, NET/Mac takes care of it all!
It will send one file to pi8mac and ONE file to pi8hvh!
RIP TRACE [ON|OFF]: Allows you to trace RIP-activity in a RIP-dedicated
Window. These mods came from Joe AF2J (thanks Joe!). Note that when A LOT
of routes get added through the RIP-mechanism, the RIP-trace-window may
slow down NET/Mac for a while, because (like ROUTE EXPANDED) all IP-numbers
will get translated to hostnames before the messages in the RIP-trace window
are displayed. This may require some (a lot) of disk-accesses when the file
'hosts.net' is not in a RAM-cache. I suggest you turn on the RIP TRACE when
indeed you want to trace the RIP-stuff, otherwise turn RIP TRACE OFF.
We have experienced some outgoing CHECKSUM ERRORs on both AppleTalk and
TNC links. This problem causes AppleTalk links to become very S L O W.
To minimize this problem I have set both TCP MSS and TCP WINDOW to 216 so
that there will never be more than 1 frame at a time going out over the
AppleTalk link. This seems to have reduced it by 95%. Unfortunately MSS
and WINDOW are being used for all tcp-connections, so setting both of them
to the same value also limits the possibilities on the TNC-link, but as
far as I've noticed here that doesn't really hurt. PE1CHL told me that the
CHECKSUM ERROR problem also exists in his NET.PE1CHL, and that he is not
going to solve it. He believes that it has been solved in NOS.
Read previous mail | Read next mail
| |
