World of Ham Radio 1994 January/AMSOFT_1994.iso/packet/docs/pd199105.doc

Text File | 1993-12-31 | 282.3 KB | 7,031 lines

Wed,  1 May 91 04:30:04 PDT
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V91 #106
To: packet-radio


Packet-Radio Digest         Wed,  1 May 91       Volume 91 : Issue 106

Today's Topics:
              Anyone in Alberta, Canada?
             BBS Software needed
             Call sign from name.
               KA9Q under Unix
             PK232 COMMAND LIST (2 msgs)

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

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: 30 Apr 91 10:30:07 GMT
From: usc!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!spool.mu.edu!snorkelwacker.mit.edu!bloom-beacon!eru!hagbard!sunic!ugle.unit.no!mack.uit.no![e-mail]
Subject: Anyone in Alberta, Canada?
To: [e-mail]

Hi,
I'm moving to Calgary, Alberta later this year and I wonder if
there would be any point in bringing my packet equipment.

1. Is there any packet activity in Calgary?
2. Any possibilities for sending messages to Norway (any BBS/gtws/digi)?
3. What frequencies and baudrates are used?

Answers are MUCH appreciated.

73 es cul
de
LA1OEA Trond
[e-mail]

------------------------------

Date: 30 Apr 91 21:32:20 GMT
From: sdd.hp.com!spool.mu.edu!news.nd.edu!mentor.cc.purdue.edu!noose.ecn.purdue.edu!en.ecn.purdue.edu![e-mail]
Subject: BBS Software needed
To: [e-mail]

Where can I get the latest revision of the W0RLI BBS software?  I believe
it would be Version 12.0.

            Thanks,
                Tim, N9DKI
                [e-mail]

------------------------------

Date: 30 Apr 91 15:34:21 GMT
From: timbuk!cs.umn.edu!uc!noc.MR.NET!ns!ns![e-mail]
Subject: Call sign from name.
To: [e-mail]

Can anyone do searches to find a call sign from a name?  If so, please
email me.

Thanks

jim

------------------------------

Date: 30 Apr 91 17:24:15 GMT
From: uswnvg![e-mail]
Subject: KA9Q under Unix
To: [e-mail]

Well, I have now compiled and linked the Unix Sys5 (SCO) version of
the KA9Q software, and have a few lingering questions. Perhaps someone
out there can give me some answers.  If you feel that it's of general
interest, post; or email me and I'll sumarize.

1)  I was under the impression that the NOS was a TCP implementation for
Amateur packet and not much else; however, there is a lot of code
(some of which got compiled into the Unix version) that supports (or
seems to support) ethernet cards and other "local" network stuff. Is
there more to NOS than I'm seeing?

2)  I'm faced with having to write my own "attach" routines (to deal with
a multiplexed serial port) and have a couple of questions:
    A)  Does the NOS assume that by the time attach runs, the
    TNC is already in KISS mode, or does it rely on attach to
    send the KISS commands.
    B)  Is there any way to "suspend" a session (ie, "temporarily"
    unattach)?

3)  Is there any way under NOS to just talk out the serial port to the
TNC directly?

4)  Will the Unix version of NOS talk only to BM, or can it use the
standard Unix mail handlers (like mmdf)

If all of these questions (probably) are covered in TFM, I apologize in
advance.  If someone could point me at tha Unix specific version of
TFM, I'd appreciate it (we only have uucp here, so it would be helpful
if it was on an archive that supported uucp).


Thanks in advance!
--
Clay Jackson - N7QNM
US WEST NewVector Group, Inc
[e-mail] | ...uunet!uswnvg!cjackso

------------------------------

Date: 30 Apr 91 14:25:19 GMT
From: pmafire![e-mail]
Subject: PK232 COMMAND LIST
To: [e-mail]

Naturaly we want a copy, please do post , or email the commands !

   **** DISKclamer ****

  [e-mail]

------------------------------

Date: 1 May 91 05:15:15 GMT
From: pmafire![e-mail]
Subject: PK232 Command List
To: [e-mail]

   Please follow up, as the posted encoded file is incomplete.

   An ASCII file would be better, or a plain zip file please.
   Mail if you prefer.

   Thanks, [e-mail]

------------------------------

End of Packet-Radio Digest
******************************
Date: Thu,  2 May 91 04:30:03 PDT
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V91 #107
To: packet-radio


Packet-Radio Digest         Thu,  2 May 91       Volume 91 : Issue 107

Today's Topics:
            Call sign from name. (3 msgs)
             Janet<>Packet Radio
                TNC-1 problem

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

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: 1 May 91 17:37:46 GMT
From: elroy.jpl.nasa.gov!swrinde!zaphod.mps.ohio-state.edu!mips!apple!xanadu![e-mail]
Subject: Call sign from name.
To: [e-mail]

In article <[e-mail]> [e-mail] (Jim Hughes) writes:
>Can anyone do searches to find a call sign from a name?  If so, please
>email me.
>
>Thanks
>
>jim

A while ago I did lookups using the server "[e-mail]"
It worked then, but I don't know if its still up.

Does anyone know if its up?

To lookup a call on datapoint I sent the word lookup followed by the call
in the body of the message.  I also included the word path followed by
the path to me from the internet.  Also, the word help can be included
to get help.  For example:

    >To: [e-mail]
    >
    >help
    >lookup n6zfx
    >path uunet!markets!jeff

Jeff Crilly (N6ZFX)
AMIX Corporation  2345 Yale Street  Palo Alto, CA  94306
[e-mail], {uunet,sun}!markets!jeff, N6ZFX@N6IIU.#NOCAL.CA.USA

------------------------------

Date: 1 May 91 22:56:06 GMT
From: gatech!prism!mailer.cc.fsu.edu!sun13![e-mail]
Subject: Call sign from name.
To: [e-mail]

In article <[e-mail]> [e-mail] (Jeff Crilly N6ZFX) writes:
>In article <[e-mail]> [e-mail] (Jim Hughes) writes:
>>Can anyone do searches to find a call sign from a name?  If so, please
>>email me.
>>
>>Thanks
>>
>>jim
>
>A while ago I did lookups using the server "[e-mail]"
>It worked then, but I don't know if its still up.

And, for systems on the Internet (like ns.network.com :-) ) use the callbook
server at marvin.cs.buffalo.edu, or it's evil twin, ham.njit.edu. The 'name'
command 'name Murray' will find all Murrays, and using the -f <firstname>
filter should reduce that to a reasonable list (unless you're looking for a
"John Smith"). So:

    ftp marvin.cs.buffalo.edu 2000
    >> name -f <first> <last>

--
*Standard Disclaimers Apply*|        ---Get Out Of HELL Free!---
John R. Murray              |The bearer of this card is entitled to forgive
[e-mail]   |Himself of all Sins, Errors and Transgressions.
Supercomputer Research Inst.|                                -- D. Owen Rowley

------------------------------

Date: 2 May 91 00:04:37 GMT
From: mips!zaphod.mps.ohio-state.edu!ub![e-mail]
Subject: Call sign from name.
To: [e-mail]

In article <[e-mail]>, [e-mail] (Jeff Crilly N6ZFX) writes:
|> A while ago I did lookups using the server "[e-mail]"
|> It worked then, but I don't know if its still up.
|>
|> Does anyone know if its up?

------------------------------

Date: 1 May 91 07:59:13 GMT
From: mcsun!ukc!icdoc!syma![e-mail]
Subject: Janet<>Packet Radio
To: [e-mail]

Hi,
My name is Marc and I am new in the Newsgroup.
I would like to know if there is a gateway existing here in europe which
could allow me to mail my uncle in Austria, who is 24 hours online via
packet radio.
I am at the University of Sussex, ie connected to JANET.
Is there a possibility to reach my uncle or some other radio amateurs using
packet radio ?

------------------------------

Date: 1 May 91 09:24:54 GMT
From: uhccux!uhcmtg.phys.hawaii.edu![e-mail]
Subject: TNC-1 problem
To: [e-mail]

I've got a TNC-1 running in KISS mode which has a tendency to lose received
packets.  It doesn't lose all of them but just enough to be annoying.  When the
old EPROM (non-KISS) is restored, it works just great - no lost packets.  At
first I thought there was a problem with the KISS EPROM.  Other people
suggested that it might be a problem with a bad HDLC chip that can't handle
the KISS code.

Well I was able to get my hands on a friend's TNC to check out both the KISS
EPROM and the HDLC chip and it turns out both chips are OK.  In fact I ended
up swapping all the other chips in the first TNC into the second TNC and
they all work fine.  Put the chips from the second TNC into the first and it
still doesn't work reliably.  The symptoms are consistently reproducible but
they don't move with the ICs.

So where does that leave me?  The problem can't be caused by the ICs.  It's
probably not a problem with the modem 'cause the thing works in non-KISS mode.
But it must be something that is exercised by the KISS firmware but not
used or required when running the TAPR TNC-1 command set in the old EPROM.

Would appreciate anyone out there who has some knowledge of the TNC-1 KISS
firmware shedding some light on this problem.  Thanks!


--
Antonio Querubin
[e-mail] / [e-mail] / [e-mail]

------------------------------

Date: (null)
From: (null)
Devon

-------------
If you are at an Internet site you can connect using telnet to one
of the two primary servers:

callsign.cs.buffalo.edu (currently 128.205.32.4)
ham.njit.edu            (currently 128.235.1.10) (alias plan9.njit.edu)

The servers sit on port number 2000 which is a different port number
than what telnet usually defaults to. So if you just telnet to these
machines, you will get a login prompt instead of the server. How you
tell your telnet program to connect to port 2000 instead of the
default port is operating system dependent but it is usually done
with a line like

telnet callsign.cs.Buffalo.EDU 2000

If this doesn't work, consult your local systems guru for the proper
command string.

The interactive servers are designed to be somewhat self-explanatory
and they support fairly detailed help facilities. The first command
you should execute when connecting to one of these servers is "info".
This will list general info about that server and how to use it. You
should then type "help" to list the various commands available.
Typing "help" followed by a command name will give you a little more
detail about that command. Servers allow searches by call, last name,
zip code or city and also provide regular expression filters to trim
your searches so you get a reasonable amount of output.

Both these servers are built from a database distributed by Rusty
Carruth, N7IKQ. This database currently contains US and Canadian
callsigns and it does not contain club calls. A new version of the
database is sent around approximately once a year.

There is also an email callsign server at [e-mail].
In the body of the text, say "lookup" followed by callsigns you want
to look up.  If your mailer appends signature files, you should put
a line "quit" at the end of your request (before the signature file).
If you want help, put the word "help" on a line by itself.  Here is
what a request might look like:
    help
    lookup kc1sp wn4bbj
    lookup n0fzd
    quit

If you are a packet radio station, callserver data is available from
[e-mail], subject line should be up to 5 US callsigns,
separated by spaces.  Body of message is ignored.  The server is an
OS interface to the MBL packet BBS using the Buckmaster CD-ROM
callsign database.

------------------------------

End of Packet-Radio Digest
******************************
Date: Fri,  3 May 91 04:30:04 PDT
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V91 #108
To: packet-radio


Packet-Radio Digest         Fri,  3 May 91       Volume 91 : Issue 108

Today's Topics:
              Cost Benefit Ratio
              Pirates/security.

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

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: 30 Apr 91 18:15:31 GMT
From: hpl-opus!hpnmdla![e-mail]
Subject: Cost Benefit Ratio
To: [e-mail]

In rec.radio.amateur.packet, [e-mail] (Julian Macassey) writes:


>... The price of the
>keys is between $70 and $100.

>...There I saw that MFJ had an electronic keyer/key
>combo for $134.95, PSU $12.95 extra.

You can buy a key with built-in code practice oscillator from MFJ for $$25.
The local emporium has two types of hand keys for sale, a traditional J-38
style for $8.95 and a plastic-base type for $4.75.

My first keyer paddle was two J-38's mounted back-to-back mounted
on an electric iron base.  Total cost: about $5.

AL N1AL
"Does this make me an OF?)

------------------------------

Date: 2 May 91 16:13:25 GMT
From: [e-mail]
Subject: Pirates/security.
To: [e-mail]

The problems of people pirating BBSes and/or using pirate callsigns are
not unknown to us in the UK too. Some months back there was someone in the
North of England who was logging into a particular BBS and reading other
people's mail.
I always compare the 'last on at' time displayed when i log in, with the
time i recorded in my hard-copy log; this way i can see if anyone has
been aliasing my call. To get round the problem of a pirate looking in
the callbook and choosing a callsign of a non-=packet-user thats local
to him, then pirating it, i have requested that my call not be included in the
callbook. OK this does not cover every eventuality.
Maybe the time is right to start considering some form of 'token' based
system for BBS and network access. A system that has been used by the Military
on voice-networks for some time is a simple challenge/authenticate mechanism,
where all the users are issued monthly with 'authentication sheets'
(typically about 5 pages). Each sheet has an X-Y grid of letters and numbers
and when you wish to enter a net, you are asked to authenticate a particular
letter/number pair from a sheet; typically a challenge is of the form
'3 71:3A'   (meaning 'sheet 3, column 71 row 3A'). User looks it up and
enters the response, which is checked against the machine's tables. The
machine then marks that combination as 'used' so it is never selected again.
A similar system could easily be adopted for BBS access, either using paper
sheets, or by some sort of software mechanism and a computer/calculator at
the users end.
Alternatively, something along the lines of KERBEROS may be usable.
Packet transmissions are hard to DF (due to their short duration) using the
traditional hand-held-beam approach. Maybe Doppler-DF could get them?

       Pete Lucas [e-mail]  [e-mail]

------------------------------

End of Packet-Radio Digest
******************************
Date: Sat,  4 May 91 04:30:06 PDT
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V91 #109
To: packet-radio


Packet-Radio Digest         Sat,  4 May 91       Volume 91 : Issue 109

Today's Topics:
              Mac SE/30 system for sale
               Pirates/security
              Pirates/security.
          SOLAR TERRESTRIAL BULLETIN - ADMINISTRIVIA

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

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: 4 May 91 01:09:55 GMT
From: sdd.hp.com!uakari.primate.wisc.edu!dali.cs.montana.edu!milton![e-mail]
Subject: Mac SE/30 system for sale
To: [e-mail]

Complete Mac SE/30 with software. Only one year old and in mint condition. All
manuals and original packaging available.

40 meg hardrive
1  meg RAM
1  FDHD disk drive
1  Imagewriter II plus cables
1  Standard keyboard with cables and mouse

Software all original with manuals

Microsoft Word 4.0
microsoft Works 2.0
Quicken 1.2
Simcity
Quarterstaff
MacInTax

$2,500 obo.

reply to [e-mail] or phone [phone] and
ask for Shawn

------------------------------

Date: 3 May 91 13:51:32 GMT
From: [e-mail]
Subject: Pirates/security
To: [e-mail]

On Fri, 3 May 91 04:30:04 PDT Packet-Radio Mailing List and Newsgroup said:
>
>Date: 2 May 91 16:13:25 GMT
>From: [e-mail]
>Subject: Pirates/security.
>To: [e-mail]
>
>Alternatively, something along the lines of KERBEROS may be usable.
>
>           Pete Lucas [e-mail]  [e-mail]

I have heard of Kerberos but don't really know much about it. Isn't
some kind of data scrambling involved? If so, that would probably
break the rules about Ham transmissions having to be in the clear.

If someone could give me a quick overview of the Kerberos scheme,
I'd appreciate it. Thanks.

-WA0R

------------------------------

Date: 3 May 91 17:28:47 GMT
From: mcsun!ukc!acorn![e-mail]
Subject: Pirates/security.
To: [e-mail]

In article <02.May.91.17:16:32.BST.#[e-mail]> [e-mail] (Pete Lucas, NCS-TLC, Holbrook House, Swindon) writes:
>Packet transmissions are hard to DF (due to their short duration) using the
>traditional hand-held-beam approach. Maybe Doppler-DF could get them?
>
>           Pete Lucas [e-mail]  [e-mail]

Maybe a modified TNC that gated a carrier-strength signal with a qualified DCD,
opening the gate when the callsign was detected (ignoring the CRC) and closing
on the end flag ? Hard to use if the packet rate was slow, but perhaps good
enough ?

A connection to the illegal user (either from the DF TNC or from the BBS)
could also be used to generate a stream of packets on demand.

-adrian

--
--------------------------------------------------------------------------
Adrian Godwin                                        ([e-mail])

------------------------------

Date: 3 May 91 20:13:03 GMT
From: ubc-cs!alberta!cpsc.ucalgary.ca!yogi.fhhosp.ab.ca!honte.uleth.ca![e-mail]
Subject: SOLAR TERRESTRIAL BULLETIN - ADMINISTRIVIA
To: [e-mail]

        /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\

            SOLAR TERRESTRIAL BULLETIN

                   03 May, 1991

                  Administrivia

        /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\


PLEASE NOTE:

     Solar Terrestrial Dispatch now has access to the Usenet community.
Previously, the solar geophysical reports, alerts, warnings and other
messages were posted through gateways into several Usenet newsgroups.
Unfortunately, this prevented us from reaching some of the other relevant
newsgroups (ex. sci.astro).  Over the next week or so, we will be attempting
to determine whether the reports propagate through the newsgroups faster
by posting through the gateways or directly to Usenet by bypassing the
gateways.  We will choose whichever method yields the fastest general
propagation time.

     It would be appreciated if some of you could respond to this message,
confirming its arrival through Usenet and noting the time of arrival.  If any
of you are familiar with the previous delay which accompanied the Solar
Terrestrial Forecast and Review (STFR) reports, please send a note comparing
the time required to receive this message with those of previous STFR
reports.  This will help us determine which method and path will yield the
quickest delivery times.

     On another vein, please note that a mailing list does exist for those of
you who are aiding in the redistribution of the solar terrestrial
information, reports and/or warnings to the packet-radio networks and/or
other networks or sources.  Those organizations or individuals who require the
information quickly for research or dispersal purposes, or who redistribute
the information to other sources may request that their e-mail addresses be
added to the distribution list.

Please send replies, requests or questions to the following address:

   INTERNET:  [e-mail]

A public announcement of the Usenet address will be made after the final
adjustments and tests are complete.

     Thanks to all of you who send confirmation notes.


**  End of Bulletin  **

------------------------------

End of Packet-Radio Digest
******************************
Date: Sun,  5 May 91 04:30:04 PDT
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V91 #110
To: packet-radio


Packet-Radio Digest         Sun,  5 May 91       Volume 91 : Issue 110

Today's Topics:
           SUMMARY: Getting started in Packet Radio
        TAPR METCON-1 Beta Test Kits (2 msgs)

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

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: 4 May 91 18:37:58 GMT
From: o.gp.cs.cmu.edu!andrew.cmu.edu![e-mail]
Subject: SUMMARY: Getting started in Packet Radio
To: [e-mail]

Here is a compilation of replies I've received when I asked about getting
started in packet radio, specifcally when using Microware's OS9 operating
system, and possibly a Radio Shack Color Computer.
Date: Mon, 29 Apr 91 12:55 EDT
From: Eddie Kuns <[e-mail]>
Subject: Re: Packet Radio
To: [e-mail], [e-mail]

"Russell E. Hoffman, II" <[e-mail]> says:
]question: Is there any CoCo packet-radio (ka9q, internet-type stuff) software
]available or (better) any OS9 C-source (so i can run it on my OSK box)
I was talking to a friend just yesterday about CoCo packet-radio under OS-9!
<grin>  He told me he uses KBCom for packet, tho not as a BBS.  He's the sysop
or co-sysop or whatever of the Pinball Haven BBS (who's number I don't have
handy).  My mind is blanking on his name at the moment, but you can probably
contact him via Mark Farrell (XLIONX) on Delphi, or maybe on the list or StG.

Are there any packet-ers on the CoCo list?
--
        | School: [e-mail] (domain)  EKuns@zodiac (bitnet)
 Eddie Kuns | Home  : kilroy![e-mail]  {linac,liltyke}!kilroy!ekuns
        | [kilroy.chi.il.us doesn't work, temporarily]   Delphi: EddieKuns
Date: Mon, 29 Apr 91 10:32:46 PDT
From: [e-mail] (Tim Kientzle)
To: [e-mail]
Cc: [e-mail]
Subject: Packet Radio

>> Is there any CoCo packet-radio (ka9q, internet-type stuff) software
>>available or (better) any OS9 C-source (so i can run it on my OSK box)
>>for such stuff?
    There are two modes for running packet.  One is called AX.25, and
is usually supported by a microprocessor in the controller.  All you
need is a terminal program to talk to it.  The other is TCP/IP, and
requires special software in the host.  I haven't heard, but I suspect
the KA9Q software is easily ported to OSk.  For that matter, odds are
good that you could run it with Microware's Internet Package.

>> Also, in addition to the RFC's, is there a good source for
>>information on the subject (like specific issues of Rainbow, etc..)
    Dale Puckett (who's an amateur) occasionally comments on stuff in
his Rainbow column.  Seems he rumoured that someone was working on
porting the KA9Q package to CoCo3/OS9L2, but I haven't heard anything
recently.

Your best bet is to ask on Usenet, either or both of comp.os.os9 and
rec.radio.amateur.packet.  I suspect that the KA9Q package has already
been ported to OSk somewhere (shouldn't be too hard, I suspect), since
I recently noticed mention of Mac and Amiga versions.

                    - Tim Kientzle, KA4EJK

Date: Tue, 30 Apr 91 00:38:24 CDT
From: [e-mail] (Steve Schallehn)
To: [e-mail]
Subject: Re: How to get started in packet radio?

In rec.radio.amateur.packet you write:

>Hello, all.
>    I'm posting this for a moderately sizable group of people. Quite a few
>of us OS9 and Color Computer users are also (or want to be :-) ham operators.
>After a discussion on our network bulletin-board, we decided somebody should
>ask around, to get us all started in the right direction. We want to use
>packet-radio in conjunction with the Tandy Color Computer, running under
>the OS9 operating system, as well as other computers running this same
>operating system. It's very similar to Unix.
>     Our question is thus: Does anyone know of already existing software
>for doing packet radio under the OS9 operating system (whether or not
>specifically for the Color Computer). If so, where can we get it? If not,
>is there Unix source available, as this would be most likely the easiest to
>port from.
>    Also, as many of us are novices, we'd like to know basically what is
>necessary to get started in packet radio, and where to get information
>on the subject. I've heard that there are certain packet controllers that
>do most of the work themselves, and all you need is a terminal. Is this
>true? I know these are all FAQ, but i didn't see an FAQ list on this board.

Most packet radio controllers have self contained CPU's.  Operation of
them is very simular to land line modems where you can issue commands
directly to the modem or in this case TNC as it is called.  A terminal
program is all that is needed.

There is a particular type of packet radio protocol called TCP/IP.
Fortunately, there are some unix "hacks" to it from the origional
MS-DOS program.  Unfortunaly, in my short search I have not been
able to find it at any site.  I am sure it is out there, but
will have to look more to locate it.

Any more information needed, please send some more mail.

-Steve Schallehn, KB0AGD
 Kansas State University
Date: Tue, 30 Apr 91 09:28:46 -0500
From: [e-mail]
To: "[e-mail]"@skvax1.csc.ti.com
Subject: How to get started in packet radio?

>on the subject. I've heard that there are certain packet controllers that
>do most of the work themselves, and all you need is a terminal. Is this
>true? I know these are all FAQ, but i didn't see an FAQ list on this board.
>
Russell

This is correct.  Almost any term program will do for much of the work.
There are some specialized programs around in both public domain and commercial,but to get started, all you need is a computer, term program, Packet TNC, and
lets say a handy talkie.

I borrowed a TNC, bought a used HT for $115, and a power supply for $40.
I made a 2 meter ground plan for $5.00

That was it with the exception of my computer and term software.

John Anderson N5OPY
[e-mail]
Date:     TUE, APR 30 1991 11:36:33
From: Donald L Schleede   <[e-mail]>
Subject:  OS9 and Packet
To: <[e-mail]>

Russell,

    I saw your not on the list. I am just starting to get into OS9
however a friend of mine is very big into the CoCo Users group here,
And some of the people I met through him Could probably help you.
There Is a person in Rochester NY who runs a BBS on a CoCo III, and
I know that he is also running it on packet. Sorry, I don't have the
BBS phone Number (I can get it if you like) but his name is Bill
Whitman and he runs Delta Systems BBS, which ALSO happens to be on
USENET, as deltas.UUCP. You may see if he can help you.
    Last Time I knew though he was in the middle of upgrading to the
new 68000 machine for OS9, He was going to buy it at the convention
last weekend. Good LUCK!

****************************************************************************
Name: Donald L. Schleede                      Snail-Mail:
Call: KB2LZF                                    Dept. Earth Sciences
E-mail Addresses:                               SUNY Brockport
 [e-mail]        Brockport, NY 14420
 [e-mail]                   Twisted Pair:
 [e-mail]                               [phone]
Planet: Earth
****************************************************************************
Date: Tue, 30 Apr 91 13:29:07 -0500
From: [e-mail] (Dugal James P.)
To: [e-mail]
Subject: Re: How to get started in packet radio?

To access a Packet BBS you would need a TNC, a terminal emulator,
and an interface cable wired for either rs232 or perhaps TTL (depending
on computer and TNC capabilities).  The TNC has a Z80 cpu that does
all the work.   It has parameters to take care of wrapping long lines,
adding cr/lf, etc.  So a COCO should work fine.

Now, to use a COCO as a PBBS, you will have a problem ... most software
runs on a PC.  There may be C code available from TAPR which you
could recompile for the COCO, to do this.  Let me know if you need TAPR's
address (== Tucson Amateur Packet Radio, the tnc2 originator).


There is software now available from Germany that enables a PC to
emulate a TNC ... with minimal hardware and lots of software.  Waste
of a PC, in my opinion.
73,
--
-- James Dugal, N5KNX         Internet: [e-mail]
Associate Director             Ham packet: n5knx@k5arh
Computing Center               US Mail: PO Box 42770  Lafayette, LA  70504
University of Southwestern LA.  Tel. [phone]      U.S.A.
From: [e-mail] ( WB3FFV)
Subject: Re: AA4RE Packet Software?
Date: 30 Apr 91 18:51:45 GMT

[e-mail] (Ed Naratil) writes:
> Does anyone know of an FTP site where the AA4RE packet software
> resides for downloading?  I have looked at SIMTEL, and don't find
> it there.

    Hello Ed,

You should be able to find the latest AA4RE BBS code (which is 2.11) on
tomcat.gsfc.nasa.gov in the directory of bbs/aa4re...


-------------------------------------------------------------------------------
Internet  : [e-mail]     |      Howard D. Leadmon              -
UUCP      : wb3ffv!howardl             |      Advanced Business Solutions     -
TELEX     : 152252474                  |      210 E. Lombard St - Suite 410   -
FAX       : [phone]              |       Baltimore, MD 21202
PACKET    : WB3FFV @ WB3FFV.MD.USA.NA   |       Phone: [phone]

From: [e-mail]
To: andrew.cmu.edu![e-mail]
Subject: New to Packet Radio
Date:   Wed, 1 May 1991 07:23:56 -0600

Ok, to get started, contact your local A.R.C. (Amateur Radio Club) to get
classes and testing for your Amateur Radio Ticket.
Next, scrape $139US for an MFJ-1270B TNC. And YES all that is required is
a terminal. The TNC (Terminal Node Controller) is a Modem + Synchronous UART
+ Packetizer + Mailbox + Node + RS-232 interface. If you are REAL OS-9 hacks
then the TNC-1 (not sold anymore) uses a 6809 processor. The MFJ (A company
name, a prefix and a TLA for My Friends Junk :-) TNC is also called a TNC-2
and uses a Z-80 processor in it. The TNC uses AX.25 (modified X.25) over the
air.

Now, UNIX software, well there are BBS's all over the place for the Packet
Domain available. There is also TCP/IP networking software, commonly called
KA9Q NET or KA9Q NOS, and is publicdomain.
I have kept this short, if you have more detailed questions or want more
detailed answers, drop me a note, I'd be more than willing to fill you
in a LOT more.

Ciao, 73 de VE6MGS/Mark   ...!laberta!adec23!mark  [e-mail] -sk-

Date: Thu, 2 May 91 14:41:17 -0500
From: [e-mail] (Dugal James P.)
To: [e-mail]
Subject: Re: How to get started in packet radio?

I'll have to get TAPR's addr from home.  w/r/t Internet access via packet,
it can be done using KA9Q's NOS pkg but there are rules that really limit
how much can be done.  Recently the whole question of content has come up
and it hasn't settled down yet!  One problem is that a 24-hour gateway that
is well-known would permit non-hams to cause it to xmit by doing, say, a
ping.  This may very well be illegal (for the ham whose license IDs the
gateway).  Sort of like reverse autopatches (which exist in some areas of
the USA).  If you do get licensed and putr a gateway up, best keep a low
profile!

73,
-- James Dugal, N5KNX         Internet: [e-mail]
Associate Director             Ham packet: n5knx@k5arh
Computing Center               US Mail: PO Box 42770  Lafayette, LA  70504
University of Southwestern LA.  Tel. [phone]      U.S.A.

Date: Fri, 3 May 91 14:09:03 CDT
From: [e-mail] (Dave Effland)
To: [e-mail]
Subject: RE: How to get started in packet radio?
Cc: [e-mail]

Hi Russell ... You've probably already heard this ... but I
just answered this for KB5LBO here in Austin, and will pass it on to you also.
Find a copy of the May 1991 issue of "73 Amateur Radio Today" magazine, and
look on page #64 at the "RTTY Loop" column.  They list some sources for
Color Computer Packet software (and other goodies).

For starting materials, I suggest ARRL's "Gateway to Packet" book.  Some of the
material is outdated -- as will be any "book" on a subject that is changing
so fast.  Overall, though, it is a very good introduction.  There are other
books and authors available.  Most of the HAM magazines have regular columns
on packet radio.

Beyond that, check with your local Ham clubs, ask questions of your local Ham
friends -- SOMEONE in your area will be doing packet.  They will likely be
your best source of information re: what is happening locally.  It is different
from city to city even though some "standards" exist.

One other thing ... plan on upgrading to Technician (or higher).  Although
there is "some" packet on HF (10 Meter Band), most of the action in on 2 meters
(and higher).  For HF, other digital modes (AMTOR and RTTY) seem to be more
popular than packet.

Hope that helps!  Good Luck.

73 CUL ... de N5RNE ... Dave
Dave Effland                          |  Motorola Inc.       MD: OE37
                      |  Microprocessor Products Group
[e-mail]           |  6501 William Cannon Drive West
Packet:  N5RNE @ N5LJF.tx.usa.na      |  Austin, Texas  78735-8598
< ... standard disclaimer ... >       |  Ph. [phone]

------------------------------

Date: 3 May 91 22:52:11 GMT
From: ucselx!usc!cs.utexas.edu!solo.csci.unt.edu!vaxb.acs.unt.edu![e-mail]
Subject: TAPR METCON-1 Beta Test Kits
To: [e-mail]

TAPR METCON-1 Beta-Test kits available

    METCON-1, a simple teleMETry and CONtrol system for packet radio, is
now available for limited Beta-Testing.  Twenty complete Beta-test kits are
available from TAPR (Tucson Amateur Packet Radio) that where brough back from
Dayton.  The METCON-1 kit is composed of the main METCON-1 control board and
one Voltage-to-Frequency board.  The system operates by connecting the main
METCON-1 system board to the RS-232 connection of a TNC.  The remotely located
packet TNC and METCON-1 system are then accessed by connecting to the TNC.  The
METCON-1 system acts like a remote computer connected to the TNC, much like a
BBS operates.  The system uses a 8751 microcomputer to allow a connected user
to read and write on/off levels at the microcomputer's I/O port using a command
line oriented command language.  Outputs are dry relay contacts so you can hook
up anything you want, within reason.  A good upper limit is 24VAC/VDC at 1/2
amp.  There are 6 outputs possible with the standard METCON-1 PC Board.

    An added feature of each standard input is that METCON-1 can measure
the frequency of an input signal (0-10KHZ) in addition to simply indicating if
the input is an open or closed circuit.  The advantage of this type system is
that the external Voltage-to-Frequency converter board configured to read
either Temperature or Frequency can be placed right at the source to be
measured.  An opto-isolator is used to allow isolation between the V-to-F board
and the main system board. One V-to-F board comes with the kit and can be
constructed in either configuration (temperature or voltage).

    Although METCON-1 is a simple system, it does have a number of nifty
features.  These features include a time-of-day clock that can be used to time
stamp output, the status table can be dumped on set intervals (0,1,15 minutes),
block reads and writes are supported for fast memory transfers, notification
can be set at different states, and other additional features are available.

    This Beta-Test is for interested individuals that would like to
participate in a limited TAPR testing of the METCON-1 system.  The results of
the testing will help further refine the definition of METCON-1 and define
application usages for the next stage of development.

    Some of the applications described so far by beta-testers include using
the METCON-1 board during a balloon ascent for sending telemetry regarding
height, temperature, and other balloon status to the ground control station as
the mission proceeds.  Many other applications dealt with control and
monitoring of  remotely located sites.  Many of these remote sites included
mountain top stations and other difficult access areas.  Applications for the
METCON-1 system are endless.

    There are currently twenty METCON-1 beta-test kits available from TAPR.
If you would like more information on METCON-1 or how to participate with the
beta-testing, call the TAPR office at [phone].

Greg Jones, WD5IVD
TAPR

------------------------------

Date: 4 May 91 21:04:59 GMT
From: swrinde!cs.utexas.edu!solo.csci.unt.edu!vaxb.acs.unt.edu![e-mail]
Subject: TAPR METCON-1 Beta Test Kits
To: [e-mail]

In article <[e-mail]>, [e-mail] writes:

>>>> call the TAPR office at [phone].

OOOOPS, I made an error on the information regarding how to contact TAPR.

Tucson Amateur Packet Radio
Voice 602-749-9479.
FAX [phone]

or write

TAPR at P.O. Box 12925, Tucson, AZ 85732.

Sorry for any confusion :-)

Greg Jones, WD5IVD
TAPR

------------------------------

End of Packet-Radio Digest
******************************
Date: Mon,  6 May 91 04:30:17 PDT
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V91 #111
To: packet-radio


Packet-Radio Digest         Mon,  6 May 91       Volume 91 : Issue 111

Today's Topics:
          SOLAR TERRESTRIAL BULLETIN - ADMINISTRIVIA
       Using Low Orbit Satellites with Non-directional Antennas

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

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: 5 May 91 17:09:31 GMT
From: swrinde!zaphod.mps.ohio-state.edu!caen!umich!sharkey!clmqt!lopez![e-mail]
Subject: SOLAR TERRESTRIAL BULLETIN - ADMINISTRIVIA
To: [e-mail]

received bulletin

------------------------------

Date: 5 May 91 11:25:47 GMT
From: kb2ear!overlf![e-mail]
Subject: Using Low Orbit Satellites with Non-directional Antennas
To: [e-mail]

I am interested in using the new pacsat satellites with non-directional
antennas. I would like to hear from anyone who has done this. I would like
information on the antennas and power used, data throughput, and anyother
information you feel is necessary and important. Any information would be
appreciated.

Dave Marthouse
Internet: [e-mail]
Fidonet: dave marthouse 1:107/323
Packet (ax25) n2aam @ w2emu-4.nj.usa.na

------------------------------

End of Packet-Radio Digest
******************************
Date: Tue,  7 May 91 04:30:03 PDT
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V91 #112
To: packet-radio


Packet-Radio Digest         Tue,  7 May 91       Volume 91 : Issue 112

Today's Topics:
             40 chr term. progm?
              NOS and Kantronics Mailbox
              Pirates/security.
          Regarding Security/Piracy (2 msgs)

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

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: 6 May 91 19:47:56 GMT
From: sdd.hp.com!hp-pcd!hpcvra.cv.hp.com![e-mail]
Subject: 40 chr term. progm?
To: [e-mail]

Hello Packet World...

Being very new to packet, I was wondering if anyone out there has run across
any terminal programs that can be used in 40 chr mode? I am considering
running portable with one of the "palmtops". What do you Atari users do?
I'm actually interested in something more than a terminal program if anything
exists. Any help would be appreciated.

------------------------------

Date: 6 May 91 05:05:50 GMT
From: usc!cs.utexas.edu!asuvax!stjhmc![e-mail]
Subject: NOS and Kantronics Mailbox
To: [e-mail]

I'm my KAM, there is a mini-W0RLI compatible mailbox that will do message
forwarding and receiving of normal AX25 mbox commands.

We are trying to get a NOS system to forward/poll it, and so far we can get
email flowing between the NOS system and the Kantronics MBOX without any
difficulties.

However, the Kantronics mailbox will not call out, it has to wait to be
polled by the remote station.

Is there anyway to setup a polling schedule in NOS for AX25 BBS connects?

73,

David
[e-mail]



--
   -------------------------------------------------------------------------
      St. Joseph's Hospital and Medical Center, Phoenix, Arizona
    uucp: {gatech, ames, rutgers}!ncar!asuvax!stjhmc!ddodell
    Bitnet: ATW1H @ ASUACAD                    FidoNet=> 1:114/15
    Internet: [e-mail]       FAX: [phone]

------------------------------

Date: 6 May 91 10:44:24 GMT
From: mcsun!ukc!tcdcs!swift.cs.tcd.ie!ul.ie![e-mail]
Subject: Pirates/security.
To: [e-mail]

In article <02.May.91.17:16:32.BST.#[e-mail]>, [e-mail] (Pete Lucas, NCS-TLC, Holbrook House, Swindon) writes:
> The problems of people pirating BBSes and/or using pirate callsigns are
> not unknown to us in the UK too. Some months back there was someone in the
> North of England who was logging into a particular BBS and reading other
> people's mail.

There cannot be any security unless the messages are coded. This is not legally
posible. All anyone needs is to monitor the packet frequency and either read
everything or wtite a simple filter program to find 'header' frames that look
interesting!

David Tocher EI2AMB
Dept of Maths
University of Limerick
Ireland

------------------------------

Date: 6 May 91 08:48:32 GMT
From: [e-mail]
Subject: Regarding Security/Piracy
To: [e-mail]

>From : G4IZU @ GB7HSN._3212.GBR.EU

Regarding Security/Piracy.
=========================
This may be the simplistic solution, but surely the answer to this is
not to go the complicated route of Look-up tables, codes etc., after
all this is only a hobby, but never to put a Packet message to a friend
or anybody that contains something that you would not be ashamed to let
anybody read!!!
Your comments would be of interest.
Packet is confusing enough without codes, ciphers etc as well!!!
Let us keep it simple at all costs.

Best 73
Dennis

------------------------------

Date: 6 May 91 14:06:31 GMT
From: photon![e-mail]
Subject: Regarding Security/Piracy
To: [e-mail]

In article <9105060848.AA16344@tnoal1.>, [e-mail] writes:
|>
|>
|>
|> >From : G4IZU @ GB7HSN._3212.GBR.EU
|>
|> Regarding Security/Piracy.
|> =========================
|> This may be the simplistic solution, but surely the answer to this is
|> not to go the complicated route of Look-up tables, codes etc., after
|> all this is only a hobby, but never to put a Packet message to a friend
|> or anybody that contains something that you would not be ashamed to let
|> anybody read!!!
|> Your comments would be of interest.
|> Packet is confusing enough without codes, ciphers etc as well!!!
|> Let us keep it simple at all costs.
|>
|> Best 73
|> Dennis
I have one comment on & one problem with what you're saying.  First, security, passwords, etc. are because of the people who don't play by the
rules; if we all *knew* the "other person" would be OK, we wouldn't need
any security.  Because (as experience has shown) we can't trust everybody --
even if it's an honest mistake -- we need to explore ways to achieve
enforced trust with minimum hassle.

Now, re: "keep it simple at all costs".  I can spell SSB, but don't ask me
to design/build/modify a xcvr -- but I don't think everyone should be
restricted to AM 'cause that's all I can do.  If you only want to use a
service as a tool, without understanding, then lobby for a simple user
interface.  For me, anyway, the hobby is figuring out how to make it work.
And it should be easy enough for non-addicts.  8-)

Cheers,
 Willis Marti
  N5SZF


t

------------------------------

End of Packet-Radio Digest
******************************
Date: Wed,  8 May 91 04:30:09 PDT
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V91 #113
To: packet-radio


Packet-Radio Digest         Wed,  8 May 91       Volume 91 : Issue 113

Today's Topics:
            any 2400 bps activity?
              bbs, uucp to TNC (2 msgs)
           Crossposts of mod files and BIDs
              Pirates/security.
          SOLAR TERRESTRIAL BULLETIN - ADMINISTRIVIA
           Still trying for .. uucp to/fm Packet.PC
        UUCP (WAFFLE) and packet radio gateway
        UUCP and Packet on same PC .. Gateway

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

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: 8 May 91 07:10:14 GMT
From: media-lab.media.mit.edu![e-mail]
Subject: any 2400 bps activity?
To: [e-mail]

Can someone in-the-know give me a breakdown of the % of 2 meter packet
communication  that takes place at the various baud/bit rates?  1200,
2400, 9600?

Also, do the standard TNCs adapt their bit rate automatically (like a
telephone line modem) when connecting to a station at some arbitrary rate?
Or is all the activity at one rate anyway?

I can listen in on 145.01, etc, and hear the squawks, but I can't
tell much about the characteristics of the signals.  I guess you
have to have a trained ear...

And, gasp!, does anyone know what the average throughput of a moderately
busy packet channel is at various baud/bit rates?  How bad is it?

--Shawn, K3HI

------------------------------

Date: 7 May 91 05:55:31 GMT
From: elroy.jpl.nasa.gov!suned1![e-mail]
Subject: bbs, uucp to TNC
To: [e-mail]

Just ordered a TNC-2 ( MFJ127xB ? ).  For some months I have been using
my PC to do UUCP ( WAFFLE ) for email and news with the Usenet world.

Has anyone else been relaying and timesharing their PC between packet radio
and new/mail over usenet ?  found or written gateway software ?  Sure would
be neat to be able to ship some news and mail in and out.  (No it is not in
violation of any laws or rules.)

Thanks for any clues.  /Ev/
--
 +  [e-mail]  [e-mail]  [e-mail] +
 +  [e-mail]   WA6CRE    Gold Coast Sun Users   Vta-SB-SLO DECUS  gnu +
 +  Opinions, MINE, NOT Uncle Sam_s | b-news postmaster xntp dns  WAFFLE  +

------------------------------

Date: 7 May 91 05:59:13 GMT
From: elroy.jpl.nasa.gov!suned1![e-mail]
Subject: bbs, uucp to TNC
To: [e-mail]

Just ordered a TNC-2 ( MFJ127xB ? ).  For some months I have been using
my PC to do UUCP ( WAFFLE ) for email and news with the Usenet world.

Has anyone else been relaying and timesharing their PC between packet radio
and new/mail over usenet ?  found or written gateway software ?  Sure would
be neat to be able to ship some news and mail in and out.  (No it is not in
violation of any laws or rules.)

Thanks for any clues.  /Ev WA6CRE/

--
 +  [e-mail]  [e-mail]  [e-mail] +
 +  [e-mail]   WA6CRE    Gold Coast Sun Users   Vta-SB-SLO DECUS  gnu +
 +  Opinions, MINE, NOT Uncle Sam_s | b-news postmaster xntp dns  WAFFLE  +

------------------------------

Date: 7 May 91 13:19:36 GMT
From: sdd.hp.com!wuarchive!emory!att!cbfsb!cbnewsb.cb.att.com![e-mail]
Subject: Crossposts of mod files and BIDs
To: [e-mail]

Last weekend I cross-posted a mod file from the net to the packet net.
Only problem is that someone else did the same thing with the same file
at about the same time.  Which means that 2 copies of the same file are
floating around many packet BBSs.  I figure one solution to avoid this
duplication is for the original newsgroup poster to make up and assign
a BID (bulletin identification) number.  Such numbers take the form:

   $nnn_xxxxxx   or such similar.  n= number  x= letter

This BID is used by the packet BBS network to avoid duplicate copies of
the same bulletin arriving from different paths to be written into a BBS.
It will also make sure that only one copy of the same file that I crossposted
and someone else crossposted will be stored, if both cross-posters use the
same BID.  And the only way for that BID to be the same is for the file
author to assign it.  (or is there a unique number the newsgroup system
assigns that appears the same at all sites that we could use?)

We crossposters should append a 1 to the BID, so if one of us decides to
make multiple parts of the file (ie, part 1 of 3, etc), and another one
of doesnt, the first part BIDs still match.

Just want to avoid duplication while still providing acess to interesting
info.   73 de WA2ISE

------------------------------

Date: 7 May 91 11:36:52 GMT
From: [e-mail]
Subject: Pirates/security.
To: [e-mail]

Someone was wondering about authentication systems such as Kerberos - well
here's a brief absteact from a recent paper on the subject.....

Kerberos basically makes use of the concept of an 'authentication server'
(which may be a physically separate machine, or a 'service' running as
a process on your target device).


The following brief discussion makes many mentions of UNIX but this is
not 'obligatory'.

 Reprinted with permission of Denis Russell, University of Newcastle.



        Kerberos was produced as part of project Athena at MIT,  and  is
        freely  available  within  the  USA.   There are two versions of
        Kerberos that are relevant, versions 4  and  5.   Version  4  is
        widely  deployed  in the USA.  It provides strong authentication
        in an environment of networked Unix systems.  Kerberos  is  used
        to secure Unix high-level networking protocols.

         Kerberos  uses  a trusted key server, and uses a version of
        the well-known Needham and Schroeder  protocol  sitting  on  the
        Internet  suite  of protocols.  The protocol is weakly dependent
        on IP in that the IP address is  included  in  certain  protocol
        exchanges  in  order  to  make  the  protocol  more resistant to
        certain forms of attack.  The encryption  method  used  is  DES.
        There   are  optional  confidentiality  and  integrity  services
        available.

         Version 5 is an updated version of the protocol.  There are
        many  detailed  changes, but perhaps the most important are that
        the encryption method can  be  chosen  from  amongst  many;  the
        underlying  network  may be of any suitable kind, including ISO;
        inter-organizational   authentication   mechanisms   are    more
        extensively   developed;   and  several  limitations  have  been
        eliminated.

         Version  5  is  in  the  final stages of specification, and
        several Unix manufacturers have committed  to  implementing  the
        protocol.  Kerberos has been adopted by the OSF.

         The  Kerberos  protocols  are  in  the  public  domain, and
        implementations of version 4  are  freely  available  from  MIT.
        However,  certain  US export restrictions forbid its export from
        the USA.  The situation is complex, but it seems  that  versions
        of  Kerberos  that provide authentication only, and which cannot
        be used for confidentiality (i.e.  to  encrypt  arbitrary  data)
        are  exportable.   Thus,  in  order  to  avoid  export problems,
        implementations of version 5 originating in the  USA  will  only
        implement the authentication services.

         Full  implementations  of  version 4 are obtainable outside
        the USA.  Usually there have been obtained by exporting parts of
        the system excluding  the  encryption  routines  (the  so-called
        "bones"   version)   and  then  re-implementing  the  encryption
        routines afterwards.  Implementing  the  DES  algorithm  is  not
        hard.  It would seem that full implementations of version 5 will
        either  be obtained this way, or by implementing the system from
        scratch.   No  implementations  of  version  5,   even   partial
        implementations,  are  yet available (though DEC is committed to
        shipping a "USA-exportable" version soon).


       Limitations of Kerberos

        Kerberos  is  not  a  perfect  system.   The  most comprehensive
        analysis of its limitations  is  in  a  paper  by  Bellovin  and
        Merrit, and in the Kerberos email discussion list.  The appendix
        examines several of these limitations and tries to put them into
        perspective.It  is clear that these limitations do not mean that
        Kerberos is useless.  To quote the introduction to Bellovin  and
        Merritt's paper:

         "We wish to stress that we are not suggesting that Kerberos
         is  useless.   Quite  the contrary - an attacker capable of
         carrying out any of the attacks listed here could penetrate
         a typical network of UNIX systems far more easily.   Adding
         Kerberos   to   a   network   will,   under  virtually  all
         circumstances, significantly  increase  its  security;  our
         criticisms  focus  on  the  extent  to  which  security  is
         improved.  Further, we recommend changes to  the  protocols
         that substantially increase security.

         "Beyond its specific utility in production, Kerberos serves
         a   major  function  by  focussing  interest  on  practical
         solutions  to  the  network  authentication  problem.   The
         elegant  protocol  design and wide availability of the code
         has galvanized a wide audience.  Far from  a  condemnation,
         our  critique is intended to contribute to an understanding
         of Kerberos's properties and  to  influence  its  evolution
         into a tool of greater power and utility."

        As  noted earlier, several of Bellovin and Merritt's suggestions
        have been incorporated into Kerberos version 5.

         In  summary, while Kerberos is certainly not perfect, it is
        by far the best system that is easily attainable, and is  vastly
        better  than  nothing at all.  To use an everyday metaphor - the
        fact that I know several ways of thwarting the  security  on  my
        house and car does not mean that I should leave them unlocked.


        References

        [1]  M.   Merritt  and S.  Bellovin "Limitations of the Kerberos
         Authentication System" Computer Communications Review,  Vol
         20 No 5, pp 119-132, Oct 1990.

        [2]  W.Diffie  and  M.E.Hellman "New Directions in Cryptography"
         IEEE Transactions in Information Theory 6, pp 644-654  (Nov
         1976).


In a way, Ethernet and packet-radio have a lot in common; they are both
potential victims of aliasing. Fortunately, 'promiscuous' monitors for
Ethernet are not as commonplace as they are on Packet (every TNC is
easily switched to promiscuous mode!)
As to the implications of 'encryption', well, you are not actually passing
real data in the 'encrypted' exchange, only transferring an authentication
mechanism. So my reading is that you are not trying to obscure the meaning of
any 'message' in the usual sense. The text of any session you then have
once you have been granted access will, of course, still be in ASCII or
whatever your system uses....

*NOTE* I am not a lawyer. I do not answer to the FCC. All people using the
       above information do so at their own risk.



Please use the following addresses for reply:          +     \/Natural
                               +    \/\Environment
JANET    : [e-mail]            +   \/\/Research
Internet : [e-mail]        +  \/\/\Council
EARN     : PJML%UK.AC.NWL.IA@UKACRL                    +  NERC Computer Services
RADIO    : [e-mail]  {144.650MHz}           +   Holbrook House
SPAN     : STAR::\[e-mail] +    Station Road
PHONE    : [phone]                           +     SWINDON SN1 1DE
FAX      : [phone]                           +      GREAT BRITAIN

------------------------------

Date: 6 May 91 08:01:52 GMT
From: van-bc!oneb!onebdos!f28.n681.z89.onebdos.UUCP![e-mail]
Subject: SOLAR TERRESTRIAL BULLETIN - ADMINISTRIVIA
To: [e-mail]

To:  [e-mail]

 > From: [e-mail]  (Note that the return is different)
 > Date: Fri, 3 May 1991 20:13:03 GMT
 > Organization: University of Lethbridge
 > Message-ID: <[e-mail]>
 >
 >                         SOLAR TERRESTRIAL BULLETIN
 >
 >                                03 May, 1991
 >
 >                               Administrivia
 >
 >                 /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
 >
 >      It would be appreciated if some of you could respond to
 > this message, confirming its arrival through Usenet and noting
 > the time of arrival.

Arrived here May 5, 1991 at 5:40p PDT

Hope that this info is of some service.

Ted


--- TosScan 1.00
 * Origin:    << Patch Cord >>     Ladysmith, B.C. (89:681/28)
--
    Ted Waugh - via IMEx node 89:681/1
    [e-mail]

------------------------------

Date: 7 May 91 07:47:34 GMT
From: elroy.jpl.nasa.gov!suned1![e-mail]
Subject: Still trying for .. uucp to/fm Packet.PC
To: [e-mail]

Just ordered a TNC-2 ( MFJ127xB ? ).  For some months I have been using
my PC to do UUCP ( WAFFLE ) for email and news with the Usenet world.

Has anyone else been relaying and timesharing their PC between packet radio
and new/mail over usenet ?  found or written gateway software ?  Sure would
be neat to be able to ship some news and mail in and out.  (No it is not in
violation of any laws or rules.)

Thanks for any clues.  /Ev WA6CRE/

 +  [e-mail]  [e-mail]  [e-mail] +
 +  [e-mail]   WA6CRE    Gold Coast Sun Users   Vta-SB-SLO DECUS  gnu +
 +  Opinions, MINE, NOT Uncle Sam_s | b-news postmaster xntp dns  WAFFLE  +
--
 +  [e-mail]  [e-mail]  [e-mail] +
 +  [e-mail]   WA6CRE    Gold Coast Sun Users   Vta-SB-SLO DECUS  gnu +
 +  Opinions, MINE, NOT Uncle Sam_s | b-news postmaster xntp dns  WAFFLE  +

------------------------------

Date: 7 May 91 06:09:31 GMT
From: swrinde!sdd.hp.com!elroy.jpl.nasa.gov!suned1![e-mail]
Subject: UUCP (WAFFLE) and packet radio gateway
To: [e-mail]

Just ordered a TNC-2 ( MFJ127xB ? ).  For some months I have been using
my PC to do UUCP ( WAFFLE ) for email and news with the Usenet world.

Has anyone else been relaying and timesharing their PC between packet radio
and new/mail over usenet ?  found or written gateway software ?  Sure would
be neat to be able to ship some news and mail in and out.  (No it is not in
violation of any laws or rules.)

Thanks for any clues.  /Ev WA6CRE/


--
 +  [e-mail]  [e-mail]  [e-mail] +
 +  [e-mail]   WA6CRE    Gold Coast Sun Users   Vta-SB-SLO DECUS  gnu +
 +  Opinions, MINE, NOT Uncle Sam_s | b-news postmaster xntp dns  WAFFLE  +

------------------------------

Date: 7 May 91 07:14:28 GMT
From: nosc![e-mail]
Subject: UUCP and Packet on same PC .. Gateway
To: [e-mail]

Just ordered a TNC-2 ( MFJ127xB ? ).  For some months I have been using
my PC to do UUCP ( WAFFLE ) for email and news with the Usenet world.

Has anyone else been relaying and timesharing their PC between packet radio
and new/mail over usenet ?  found or written gateway software ?  Sure would
be neat to be able to ship some news and mail in and out.  (No it is not in
violation of any laws or rules.)

Thanks for any clues.  /Ev WA6CRE/

------------------------------

End of Packet-Radio Digest
******************************
Date: Thu,  9 May 91 04:30:06 PDT
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V91 #114
To: packet-radio


Packet-Radio Digest         Thu,  9 May 91       Volume 91 : Issue 114

Today's Topics:
                "Cheap" packet
             Cambridge Z88 - Help Needed
            PK-88 birdie on 145.01
              PK232 Command List
           Regarding Security.... (2 msgs)

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

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: 8 May 91 21:01:21 GMT
From: pyramid![e-mail]
Subject: "Cheap" packet
To: [e-mail]

I am trying to find a way to get a fellow ham into VHF packet as cheaply as
possible (he has three young kids to feed, so it's got to be cheap!)  He
has both a clone of the "original" PC and a Commodore 64.  I've remember
hearing something about a software TNC emulator for the C-64.  What is it,
how much does it cost, and how good of a job does it do?  Is there anything
similar for a PC?

I assume that this question has been asked before.  Please e-mail me
directly, and I'll post a summary if there's any interest.

+--------------------------------------------------+--------------------------+
| Andre Molyneux KA7WVV  [e-mail]|*** GENERIC DISCLAIMER ***|
+--------------------------------------------------+--------------------------+
|      -=-------- PYRAMID TECHNOLOGY CORPORATION   |All the usual disclaimers |
|    ---===------ 1295 Charleston Road             |apply although, as far as |
|  -----=====---- Mountain View, California 94043  |I can tell, my employer   |
|-------=======-- [phone]                   |doesn't care what I think!|
+--------------------------------------------------+--------------------------+

------------------------------

Date: 8 May 91 21:24:40 GMT
From: zephyr.ens.tek.com!gvgpsa!gold.gvg.tek.com![e-mail]
Subject: Cambridge Z88 - Help Needed
To: [e-mail]

I have acquired a Cambridge Z88 (very cheap) and would like
to use it is a packet terminal. I need some advice:

1) Where can I get more information, programs, RAM, etc.
   here in the U.S.?

   2) How can this be used as a simple terminal for a modem
      or packet radio. I am having no luck with it terminal
      mode and would like to get in touch with someone who
      is using the unit in this manner.

      Please E-Mail, or if you like telephone me at the number
      below. Thanks very much.

      Grover Cleveland
      The Grass Valley Group Inc.

      [phone]
      :wq

------------------------------

Date: 8 May 91 02:23:49 GMT
From: pacbell.com!att!emory!wa4mei!ke4zv![e-mail]
Subject: PK-88 birdie on 145.01
To: [e-mail]

In article <[e-mail]> [e-mail] ( the Penguin) writes:
>
>I have a very annoying birdie on 145.01 that is coming from my PK-88.
>Does anyone have the mod to eliminate it or move it somewhere else?
>It's not too bad when using an external antenna, but it is full scale
>if the antenna is anywhere near the TNC.

Welcome to class B computing devices and radio. About all you can do is
move the *harmonic* of the CPU oscillator somewhere else by tweaking it's
frequency. Solder a gimmick capacitor across the crystal and twist until
the signal moves off 145.01.

If the term "gimmick" is new to you, a short explanation. Solder two
lengths of insulated wire, one on each of the two terminals of the crystal,
and twist them together to form a crude variable capacitor.

Gary KE4ZV

------------------------------

Date: 5 May 91 03:35:06 GMT
From: hpfcso![e-mail]
Subject: PK232 Command List
To: [e-mail]

I also would like to have an ASCII file sent to my e-mail address as
follows:

        Cathy Nelson
        [e-mail]
Thanks muchly!

------------------------------

Date: 8 May 91 08:44:36 GMT
From: [e-mail]
Subject: Regarding Security....
To: [e-mail]

>
>In article <02.May.91.17:16:32.BST.#[e-mail]>, [e-mail] (Pete Lucas, NCS-TLC, Holbrook House,
Swindon)
>writes:
>> The problems of people pirating BBSes and/or using pirate callsigns are
>> not unknown to us in the UK too. Some months back there was someone in the
>> North of England who was logging into a particular BBS and reading other
>> people's mail.
>>
>There cannot be any security unless the messages are coded. This is not legally
>posible. All anyone needs is to monitor the packet frequency and either read
>everything or wtite a simple filter program to find 'header' frames that look
>interesting!
>
>David Tocher EI2AMB
>Dept of Maths
>University of Limerick
>Ireland
>
Alas it were so simple. What i am proposing is some mechanism for authenticating
the person (attempting to) log into a BBS. At the moment, anyone can simply
set 'MYCALL G6WBJ' on their TNC, and then log into my local BBS pretending
to be me (and read my mail, or even worse, send offensive/indecent/illegal
mail in my name - which means that *I* could get closed down for something
i have not done).

What i am proposing is an 'encoded' (a phrase i prefer instead of 'encrypted'
as it upsets fewer people) exchange when you call the BBS, to give some way
of carrying out a verification process, this will in most cases show that
it is actually me who is logging in. Once this exchange has taken place
then the rest of the session proceeds in ASCII, EBCDIC, third-shift Cyrillic,
Hebrew or whatever representation turns you on. *THE MESSAGES ARE NOT ENCRYPTED*.

Admittedly this will not stop messages being altered 'in flight' (i guess
only sysops can do this) or 'eavesdroppers' watching what is being said, but
thats the least of my worries.


       Pete Lucas [e-mail]  [e-mail]

------------------------------

Date: 8 May 91 20:12:58 GMT
From: [e-mail]
Subject: Regarding Security....
To: [e-mail]

(Pete Lucas, NCS-TLC, Holbrook House, Swindon) writes:
>
>Admittedly this will not stop messages being altered 'in flight' (i guess
>only sysops can do this) or 'eavesdroppers' watching what is being said, but
>thats the least of my worries.

Since the existing AX.25 BBS's exchange messages by logging on to the
next BBS in the chain, then inserting the message nearly as a normal
user would, there is NO way to prevent forgery of messages in the
current system, even if user access to the originating BBS is
verified.  What would be needed would be authentication at each step of
the message transfer.

With there being thousands of BBSs worldwide, and many different types
of software in use, I would propose that it will be easier to get the
US law changed than to update all the BBSs.

As more advanced methods of networking take over from the current
stone-age BBS network in ham packet radio, we could build a
message-exchange system which does make spoofing of messages rather
more difficult.  If we also require authentication of the users of the
messaging systems, we're closer to the point where messages can be
trusted.  The sophistication, computational complexity, and cpu power
required to do this increases with the degree of reliability and trust
we want to have in the authentication.  To be really sure will be
really expensive.

However, and this is a point that cannot be repeated too often, we
must learn that just because something is on a computer, it is NOT
NECESSARILY TRUE!  Too many people give credence to a message seen on a
screen that they would never believe if it were told to them.  If we,
as hams - supposedly technically sophisticated individuals - can't
understand that, how in Hell can the public be expected to cope?
(Garbage in, Gospel out, as they say.)
    - Brian

------------------------------

End of Packet-Radio Digest
******************************
Date: Fri, 10 May 91 04:30:08 PDT
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V91 #115
To: packet-radio


Packet-Radio Digest         Fri, 10 May 91       Volume 91 : Issue 115

Today's Topics:
              "Cheap" packet (revisited)
           For Sale : Brittanica Book of the Year .
            High Speed Modem List
            Mactronics T-3 Terminal system
              Security (3 msgs)

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

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: 9 May 91 23:22:05 GMT
From: swrinde!mips!apple!veritas!amdcad!jetsun!pyramid![e-mail]
Subject: "Cheap" packet (revisited)
To: [e-mail]

That was quick.  I've already gotten several responses to the message I posted
asking for cheap ways to get into packet for either a PC clone or a C64.

My friend would prefer to use the clone, so it appears that the choices are
"Poor Man's Packet" and "BAYCOM".  One reply indicated that BAYCOM was the
preferred program.  Anyone have a different opinion?  Are these programs
public domain, share-ware, or what?  Also, how do I obtain them, since I'm
not able to ftp to outside machines from my company?

I understand both programs require a simple circuit requiring a few chips
be built.  Anyone know how much these components cost?

+--------------------------------------------------+--------------------------+
| Andre Molyneux KA7WVV  [e-mail]|*** GENERIC DISCLAIMER ***|
+--------------------------------------------------+--------------------------+
|      -=-------- PYRAMID TECHNOLOGY CORPORATION   |All the usual disclaimers |
|    ---===------ 1295 Charleston Road             |apply although, as far as |
|  -----=====---- Mountain View, California 94043  |I can tell, my employer   |
|-------=======-- [phone]                   |doesn't care what I think!|
+--------------------------------------------------+--------------------------+

------------------------------

Date: 9 May 91 21:19:55 GMT
From: usc!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!netnews.upenn.edu!grip.cis.upenn.edu![e-mail]
Subject: For Sale : Brittanica Book of the Year .
To: [e-mail]

BOOK FOR SALE :

Encylopaedia Brittanica Book of the Year 1986 (Events of 1985)

Brand new, untouched ...

Asking $25 O.B.O.


Please reply by email ... Thanks ..

----------------------------------------------------------------------------
Tarek M. Sobh                                       [e-mail]
Computer and Information Science Dept.            University of Pennsylvania
----------------------------------------------------------------------------

------------------------------

Date: 11 May 91 03:37:05 GMT
From: sdd.hp.com!uakari.primate.wisc.edu!aplcen!wb3ffv![e-mail]
Subject: High Speed Modem List
To: [e-mail]

   Hello All,

I can see there has been a lot of recent discussion on high speed modems,
both here in Tcp-Group and in other areas.  A while ago I tried to start
a mailing list for the 56Kbps modems, but there just wasn't a lot of
interest (I guess the scope was a bit narrow).  Anyway with a lot of the
various manufactuers releasing some decent RF modems I thought I would give
the idea one more try.  I am going to start a maillist that is devoted to
high speed modems (since not everyone many not want to run TCP/IP, though
I can't imagine why :-) that run at speeds greater than 2400bps.  Here is
the information if you care to subscribe:


To subscribe or unsubscribe: [e-mail]

To send a messge to the list: [e-mail]



Well I guess I'll see if there is much interest in going faster than 1200bps
over packet (I hope so)..


-------------------------------------------------------------------------------
Internet  : [e-mail]     |       Howard D. Leadmon
UUCP      : wb3ffv!howardl              |       Advanced Business Solutions
TELEX     : 152252474                   |       210 E. Lombard St - Suite 410
FAX       : [phone]              |       Baltimore, MD 21202
PACKET    : WB3FFV @ WB3FFV.MD.USA.NA   |       Phone: [phone]

------------------------------

Date: 9 May 91 23:03:29 GMT
From: swrinde!zaphod.mps.ohio-state.edu!samsung!munnari.oz.au!metro!seagoon.newcastle.edu.au!wombat.newcastle.edu.au![e-mail]
Subject: Mactronics T-3 Terminal system
To: [e-mail]

Some years ago I purchased direct from the US, the Mactronics T-3 Terminal system for
RTTY and Amtor.  I was using a faithfull old TRS-80 Model 111 at the time
(still have it and it still works).

I now want to run the system on one of my 286 PCs and wrote to Mactronics fro
details on obtaining the interface card to connect the modem to my PC, plus the
software driver.  To date I have had no reply and can only assume that they
have gone out of business.

I regard the T-3 as an excellent RTTY/Amtor system and would realy like to
recycle it on the DOS system.

Can some one help with info on the interface card required for the IBM and with
the correct software.  Will pay reasonable costs to buy second material.

Please contact Philip Greentree VK2IW at ccpcg.cc.newcastle.edu.au
 or via 51 Jones Avenue
WARNERS BAY N.S.W. 2282
AUSTRALIA

73s de Philip VK2IW

------------------------------

Date: 9 May 91 20:39:52 GMT
From: [e-mail]
Subject: Security
To: [e-mail]

Maybe I'm missing something but whats the problem with using a
Pass Word for protection? Granted some people can "break"
Pass Words but it does take time. If i change my Pass Wordoften
it becomes less likely that mine will be broken. If Phone BBS's
support Pass Word protection why can't Packet BBS's do the same?
I'm sure someone has the answer. Who gets the Cigar?
de [e-mail]

------------------------------

Date: 10 May 91 01:08:23 GMT
From: theory.tn.cornell.edu![e-mail]
Subject: Security
To: [e-mail]

In article <[e-mail]> [e-mail] (ASQJ-NBF) writes:
>Maybe I'm missing something but whats the problem with using a
>Pass Word for protection? Granted some people can "break"
>Pass Words but it does take time. If i change my Pass Wordoften
>it becomes less likely that mine will be broken. If Phone BBS's
>support Pass Word protection why can't Packet BBS's do the same?
>I'm sure someone has the answer. Who gets the Cigar?

    The problem with using passwords over packet is that others can
easily monitor the packet channel.  So the first time you type your password
to the remote Packet BBS, everyone on the channel can see it!  So you change
your password every time you use the BBS.  How do you type in your new
password without everyone seeing it whiz by?  I think you get the picture.

    A simple authentication system that works well for packet goes
something like this (this has been discussed at length already, so I'll keep
it short):  suppose you and the BBS share a password.  This password is
arranged off the air and never goes out over the air.  Now, when you connect
to the BBS, it "challenges" you with a random string or word.  Now, you
must take this random string, encrypt it with your password, and send it
back to the BBS.  The BBS compares your answer to what it thinks it
should have gotten (remember, it has your password too).  If it is correct,
the BBS assumes you are you, because you are the only one who could have
properly encrypted the reply.

    Note that your password never went over the air, and anyone monitoring
who saw this go by on the channel would *not* be able to pose as you.  Why?
Because the string the BBS asks you to encrypt is randomly picked and
changes each time someone connects.  Also note that the authentication
in this example is strictly in one direction.  You proved your identity
to the BBS.  You can also reverse the exchange to prove the BBS's identity
to you, if you have a problem with people setting up bogus BBS systems....

    One final item:  this scheme is NOT illegal.  The intent here is
not to "obscure the meaning" of a message.  Read Part 97 (for US hams).
--
=  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =
Andrew C. Payne, N8KEI        UUCP:  ...!cornell!batcomputer!payne
              INTERNET:  [e-mail]

------------------------------

Date: 10 May 91 01:07:58 GMT
From: swrinde!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!unixhub!stanford.edu![e-mail]
Subject: Security
To: [e-mail]

In article <[e-mail]> [e-mail] (ASQJ-NBF) writes:
>Maybe I'm missing something but whats the problem with using a
>Pass Word for protection? Granted some people can "break"
>Pass Words but it does take time. If i change my Pass Wordoften
>it becomes less likely that mine will be broken. If Phone BBS's
>support Pass Word protection why can't Packet BBS's do the same?
>I'm sure someone has the answer. Who gets the Cigar?
>de [e-mail]

The reason, of course, is that with traditional (land line) BBS systems
the communications channel is somewhat secure, barring wiretaps.  In
the radio world, you're broadcasting your password to anyone within
line of sight, who may be listening.  Even if login authentication is
performed, the network itself is not secure.


-=Paul Flaherty, N9FZX      | "Think of it as evolution in action."
->[e-mail] |       -- Larry Niven and Jerry Pournelle

------------------------------

End of Packet-Radio Digest
******************************
Date: Sat, 11 May 91 04:30:07 PDT
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V91 #116
To: packet-radio


Packet-Radio Digest         Sat, 11 May 91       Volume 91 : Issue 116

Today's Topics:
              "Cheap" packet (revisited)
              AEA DSP Controller
            any 2400 bps activity?
         Internet address for hs modem list? (3 msgs)

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

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: 10 May 91 14:13:39 GMT
From: theory.tn.cornell.edu![e-mail]
Subject: "Cheap" packet (revisited)
To: [e-mail]

In article <[e-mail]> [e-mail] (Andre Molyneux) writes:
>My friend would prefer to use the clone, so it appears that the choices are
>"Poor Man's Packet" and "BAYCOM".  One reply indicated that BAYCOM was the
>preferred program.  Anyone have a different opinion?  Are these programs
>public domain, share-ware, or what?  Also, how do I obtain them, since I'm
>not able to ftp to outside machines from my company?

Up front disclaimer:  I wrote PMP.

    From the feedback I've gotten, the arguments for each tend to go
like this:

For BAYCOM:
    - Lots more features than PMP
    - Technically superior (e.g. doesn't hang the machine on TX & RX)
    - More people using it

For PMP:
    - "Aesthetically" better (e.g. nicer user interface)
    - Uses parallel port instead of serial port (e.g no worry about
      RS-232 levels on your modem)
    - FULL source code is available

Oh, one mark against PMP:
    - little, if any support from author (PMP is "as is", I have no time
      to do any additional work).

PMP is available via anonymous FTP on 'helios.tn.cornell.edu' in /pub.  If,
as you say, you don't have Internet FTP, try using an FTP mail server.
Send a mail message with the subject "HELP" and the message "HELP" to
'[e-mail]' for details.

>I understand both programs require a simple circuit requiring a few chips
>be built.  Anyone know how much these components cost?

    Yes, both programs use virtually identical modems.  The three
popular types are Exar chip based (ala the MFJs), AMD 7910 (check a
recent ARRL handbook), and TCM3105 (see Feb, 1989 issue of 73 for a design
based on this chip).  My modems are '3105 based:  a chip and xtal can be
had for $17 or so.





--
=  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =
Andrew C. Payne, N8KEI        UUCP:  ...!cornell!batcomputer!payne
              INTERNET:  [e-mail]

------------------------------

Date: 10 May 91 22:23:48 GMT
From: orion.oac.uci.edu!ucivax!jarthur!elroy.jpl.nasa.gov!aero-c![e-mail]
Subject: AEA DSP Controller
To: [e-mail]

Now that AEA has finally announced their DSP 1232/2232 controller, has
anyone obtained one and run it through its paces?  Any comments
pro/con?  And how does it compare to the L.L. Grace machine?  For
close to $800 (or $1000 for the dual channel version), I'm not willing
to be the first on the block to own one and have to work through
"hurry and get it out the door" bugs.  But if its mature and well
documented, my wallet may be considerably lighter.

73 de Joe, N6KK
[e-mail]

------------------------------

Date: 10 May 91 16:22:01 GMT
From: swrinde!mips!apple!altos!gumby![e-mail]
Subject: any 2400 bps activity?
To: [e-mail]

In article <[e-mail]> [e-mail] (Shawn O'Donnell) writes:

>And, gasp!, does anyone know what the average throughput of a moderately
>busy packet channel is at various baud/bit rates?  How bad is it?


Here in the Bay Area, where 145.01 is heavily congested, the throughput is
about 10 BPS (yes, 10 bits per second...)  The percentage of packets that
get through without retries is frightfully small.



--
Jerry Gardner, NJ6A                                     Altos Computer Systems
UUCP: {sun|pyramid|sco|amdahl|uunet}!altos!jerry        2641 Orchard Parkway
Internet: [e-mail]                               San Jose, CA  95134
Help stamp out vi in our lifetime.                      [phone]

------------------------------

Date: 10 May 91 14:40:00 GMT
From: [e-mail]
Subject: Internet address for hs modem list?
To: [e-mail]

Hello all,

      I just saw a message in the last packet radio digest that someone is
finally putting together a mailing list for high speed modems and that in
order to subscribe, I should send a message to
[e-mail].
      When I tried to mail to this address our mailer gave me a host/domain
unknown error. Could someone on the list (maybe the administrator of the hs
modem list) please give me directions on how I can use another Internet
gateway to cause mail to be bounced into wb3fvv?  Or a better question yet....
is wb3fvv.ampr.org acessible from regular internet or is it just part of a
local tcp/ip packet radio network? If it is part of internet could someone
please send me the address numbers so that I can bypass the name server on our
machine?
    For what it's worth my Internet addresses are:

    [e-mail]  and

    [e-mail]   (feel free to mail me at either).

73's de
Bernie NU1S

------------------------------

Date: 10 May 91 16:36:16 GMT
From: photon![e-mail]
Subject: Internet address for hs modem list?
To: [e-mail]

In article <[e-mail]>, [e-mail] (NU1S/2) writes:
|> Hello all,
|>
|>       I just saw a message in the last packet radio digest that someone is
|> finally putting together a mailing list for high speed modems and that in
|> order to subscribe, I should send a message to
|> [e-mail].
|>       When I tried to mail to this address our mailer gave me a host/domain
|> unknown error. Could someone on the list (maybe the administrator of the hs
|> modem list) please give me directions on how I can use another Internet
|> gateway to cause mail to be bounced into wb3fvv?  Or a better question yet....

You're victim of an older, non-MX mailer.   wb3ffv.ampr.org has a regular
net 44 address, *BUT* has mail sent to thumper.bellcore.com.  Your
mailer has to understand this.  Alternatively, you could try the hack of

[e-mail]

as an address.  Some day we'll get net 44 connected....

Willis Marti
 N5SZF
---------------------------------------
photon% nslookup
Default Server:  photon.tamu.edu
Address:  128.194.2.3

>  wb3ffv.ampr.org
Server:  photon.tamu.edu
Address:  128.194.2.3

Non-authoritative answer:
Name:    wb3ffv.ampr.org
Address:  44.60.0.1

>  set query=mx
>  wb3ffv.ampr.org
Server:  photon.tamu.edu
Address:  128.194.2.3

Non-authoritative answer:
wb3ffv.ampr.org preference = 10, mail exchanger = thumper.bellcore.com
Authoritative answers can be found from:
thumper.bellcore.com    inet address = 128.96.41.1
UCSD.EDU        inet address = 128.54.16.1
> photon%

------------------------------

Date: 10 May 91 18:23:00 GMT
From: usc!sdd.hp.com!apollo![e-mail]
Subject: Internet address for hs modem list?
To: [e-mail]

In article <[e-mail]> [e-mail] (NU1S/2) writes:
>      I just saw a message in the last packet radio digest that someone is
>finally putting together a mailing list for high speed modems and that in
>order to subscribe, I should send a message to
>[e-mail].
>      When I tried to mail to this address our mailer gave me a host/domain

My name server lookup gives the mail exchanger for wb3ffv as thumper.

Try: [e-mail]

John KD7UW

------------------------------

End of Packet-Radio Digest
******************************
Date: Sun, 12 May 91 04:30:07 PDT
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V91 #117
To: packet-radio


Packet-Radio Digest         Sun, 12 May 91       Volume 91 : Issue 117

Today's Topics:
                AA4RE and KAM
            Regarding Security....

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

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: 11 May 91 13:51:07 GMT
From: sdd.hp.com!elroy.jpl.nasa.gov!ncar!asuvax!stjhmc![e-mail]
Subject: AA4RE and KAM
To: [e-mail]

I am trying to get another local ham to setup my KAM's personal Mbox for
inbound mail forwarding / pickup.

He claims he has me setup as a Type A BBS, mail will forward in fine, but it
won't pickup mail already on the KAM mailbox as it is suppose to ... I have
seen this working already with other software such as NOS, but don't know
anything about AA4RE's package.

Any suggestions?

73, David [e-mail]



--
   -------------------------------------------------------------------------
      St. Joseph's Hospital and Medical Center, Phoenix, Arizona
    uucp: {gatech, ames, rutgers}!ncar!asuvax!stjhmc!ddodell
    Bitnet: ATW1H @ ASUACAD                    FidoNet=> 1:114/15
    Internet: [e-mail]       FAX: [phone]

------------------------------

Date: 12 May 91 00:31:05 GMT
From: sdd.hp.com!uakari.primate.wisc.edu!dali.cs.montana.edu!milton!sumax!polari!rwing!eskimo![e-mail]
Subject: Regarding Security....
To: [e-mail]

In article <08.May.91.09:47:36.BST.#[e-mail]>, [e-mail] (Pete Lucas, NCS-TLC, Holbrook House, Swindon) writes:
>
> >In article <02.May.91.17:16:32.BST.#[e-mail]>, [e-mail] (Pete Lucas, NCS-TLC, Holbrook House,
> Swindon)
>
> ....proposing is an 'encoded' (a phrase i prefer instead of 'encrypted'
> as it upsets fewer people) exchange when you call the BBS, to give some way

I'm not involved in packet radio (when time gets free, maybe) but I did
give this issue some serious thought a few years back. I'm kind of
thinking out loud and from a VERY theoretical basis but here goes.
What about a variation of the so called "enigma" cipher scheme which
changes your password from login to login? This way, if anyone did
catch your 'passwd' on login session N, it would not do any good
since the 'passwd' would be different for login session N+1. It seems
that a 3 rotor enigma cipher with the user specifying the initial rotor
positions, number of steps to advance each login and direction for each
rotor might produce a scheme which, while probably breakable, would
certainly improve the present situation. This certainly has problems
of software at each end of the connection and methods to 're-synch'
if something went wrong but I hope my ideas do generate some
thought/discussion on the issue

73 to all
Tom - KD9NL/7

------------------------------

End of Packet-Radio Digest
******************************
Date: Mon, 13 May 91 04:30:08 PDT
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V91 #118
To: packet-radio


Packet-Radio Digest         Mon, 13 May 91       Volume 91 : Issue 118

Today's Topics:
              "Cheap" packet (revisited)
             News from Australia.
                   Security
           Time bug in KA9Q, and nntp docs

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

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: 13 May 91 04:55:06 GMT
From: comp.vuw.ac.nz!cc-server4.massey.ac.nz![e-mail]
Subject: "Cheap" packet (revisited)
To: [e-mail]

Re PMP and BAYCOM:

I have been using PMP for about 18 months and still use it in preference
to BAYCOM except when the channel is BUSY.  The user interface is much
nicer with PMP (or alternatively it works the same way my brain does :-)

I tend to do an L for listing all the incoming bulletins /mail from a BBS
and then scroll back up to find the ones I want to read.  The limited
buffer size in BAYCOM and the use of multiple keys makes this more
awkward than with PMP as with a large number of incoming bulletins, the
early ones are often lost (using BAYCOM).

Also, I tend to read articles and then decide I wish to save them which
you can't do in BAYCOM, you have to open a download file FIRST,  before
reading anything.  PMP lets you save the scrollback buffer instead.

One topic which causes problems with BAYCOM although it IS NOT BAYCOM'S
FAULT is one of the local BBSs use of MSYS 1.10 which uses (I believe)
AX25 level one.  This doesn't set the final bit on the UA packet with the
end result that you can't connect to it using BAYCOM - PMP doesn't care.
Apparently MSYS 1.11 has fixed this ...

Neither BAYCOM nor PMP will let you download binary files using YAPP,
XMODEM or any of the commonly used protocols - So you can see all these
files on your BBS, you just can't get hold of any of them :-(

BAYCOM doesn't need a Data carrier detect, PMP does but this won't be a
problem if you're using a 7911 or 3105 modem chip as DCD is available.

With regard to using PMP only when the channel's not busy, PMP disable
the keyboard when either sending or receiving packets, BAYCOM doesn't.
This is on a turbo (8MHz) XT, there may be enough time left on faster PCs
to service the keyboard ...

Both work well ....  (and I'm sure glad I didn't have to write them :-)

Cheers
Giovanni ZL2BOI

--
------------------------------------------------------------------------------
Giovanni Moretti, Computer Science Dept, Massey University, Palmerston North,
Mail: Internet: [e-mail], Pkt-Radio: ZL2BOI@ZL2TCA | New Zealand
Ph 64 63 69099 x8694,FAX [phone] | QUITTERS NEVER WIN, WINNERS NEVER QUIT
------------------------------------------------------------------------------

------------------------------

Date: 13 May 91 01:35:48 GMT
From: munnari.oz.au!manuel!csc.canberra.edu.au!echo![e-mail]
Subject: News from Australia.
To: [e-mail]

Hi!

In Australia at the moment there is a growing movement to "rationalise"
the current crop of @ designators.

The problem is this, Australia has (roughly) split into two forwarding areas.
One based on the East Coast and loosly called VKNET and the other based
on the West Coast (also loosly) called OCNET (or just OC).

Due to the kind sponsorship of an unamed organisation there is a ROSE link
across the country linking the two groups together and the two designator
areas are starting to clash.  It's not helped by the fact that the West Coast
handles mail to/from Europe while the East Coast handles mail to/from the
Asia/Pacific region and there is a fair amount of designator swapping
going on.  For example a lot of mail is distributed in Europe with a
designator of @EU.  Somewhere (and we have our suspicions) it is being changed
to @VKNET or @OC.  The result we have a lot of useless European mail
floating around Australia.  Similar things are happening with the Asia/Pacific
region except there also appears to be heavy censorship somewhere around the
gateways. (Virtually no USA bulletins, for example, make it through. :-( )

The proposals we have seen so far basically sum up to;
@WW   Designator for World Wide distribution.
@AUS  Designator for Australia Wide distribution.
@ASIA Designator for Asia/Pacific distribution.

They may not end up being the actual designators however they will be something
similar.

I'd like to know how designators are worked out in the US and Canada and
what difficulties are currently being experienced in this regard.
Is there support for a @WW designator?
What bulletins should be forwarded between regions? (ie between the US and
Asia and so on.)
How well is heirarchical addressing working?
What heirarchical addresses are currently assigned (at a state level) and
how are they worked out?

Basically I'm after the above information to help me draft something for the
Australian network.  I'd like to know something about other networks before
putting forward proposals locally that might impact those other networks.

I'm also interested in hearing from European Amateurs.
How many bulletins from the Asia/Pacific area make it to North America
and Europe?

Also are people interested in Amateurs in different regions posting a
description of their local networks? If so I'll post a description
of the Australian system.

Carl
[e-mail]

------------------------------

Date: 12 May 91 12:24:19 GMT
From: usc!rpi!dali.cs.montana.edu!milton!sumax!polari!rwing!eskimo![e-mail]
Subject: Security
To: [e-mail]

In article <[e-mail]>, [e-mail] (Andrew Payne) writes:
>
>       A simple authentication system that works well for packet goes
> something like this >Description deleted<

This is an EXCELLENT scheme. Much simpler than the one I came up with.

>
>       One final item:  this scheme is NOT illegal.  The intent here is
> not to "obscure the meaning" of a message.  Read Part 97 (for US hams).
> --

The scheme I came up with is probably legal but too complex compared
to the not so legal one. I think it is time for a rule change.
Technology has clearly made the old rule counter-productive and a
change in rules or waiver this particular one  in the case of BBSs
is in everyones best interests.

------------------------------

Date: 13 May 91 01:21:39 GMT
From: munnari.oz.au!manuel!ccadfa!rodos2![e-mail]
Subject: Time bug in KA9Q, and nntp docs
To: [e-mail]

I have a couple of quick questions about KA9Q 910414.

For some reason, the date does increment to the next day when passing
through midnight. Is this a bug in KA9Q, or perhaps a feature of MS-DOS?!

Does anybody know how to use the nntp functions properly? At the moment
I'm accessing my nntp server every hour for one newsgroup, but it only
found news on the first access, built a few directories in spool/mail.
Since then, no news. Also, the news is left as a single file with all the
news bundled in it. Is there any way of having the news appear as
individual files in a spool/news/... subdirectory.

Thanks for your help!

    Warren Toomey


       Warren Toomey VK1XWT, slow kermiting.
      Deep in the bowels of ADFA Comp Science.
  `The key that I thought opened the door doesn't'

------------------------------

Date: 12 May 91 18:02:39 GMT
From: theory.tn.cornell.edu![e-mail]
To: [e-mail]

References <[e-mail]>, <[e-mail]>, <[e-mail]>
Subject : Re: Security

In article <[e-mail]> [e-mail] (8718) writes:
>In article <[e-mail]>, [e-mail] (Andrew Payne) writes:
>>
>>      A simple authentication system that works well for packet goes
>> something like this >Description deleted<
>
>This is an EXCELLENT scheme. Much simpler than the one I came up with.

    Actually, after a little generalization, the two schemes are virtually
identical.  Think of it this way:

    With the method you described (in a previous message:  using an
'Enigma'-type algorithm to change your password each time you log in),
suppose you pre-computed and printed out your next 500 passwords.  So the
next time you log in, you would use password #1 from the list, then #2,
etc.  Now, suppose the BBS prompts you with your login number when you
connect (e.g. "This is your 27th login, password please?").  You would
send the 27th password from your list to login.

    This is a version of the challenge/reply scheme I described.  The
BBS is challenging you (with your login number), and you are replying with
the password that corresponds to the challenge.

    The variations are endless:  you would probably want the BBS to
scramble up the password requests and not do them in order.  Or, better yet,
the BBS would prompt you with multiple challenges, only one of which is
valid (e.g. "Login with passwords #0567 #6723 #4534 please", where #0567
and #6723 are bogus challenges).
--
=  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =
Andrew C. Payne, N8KEI        UUCP:  ...!cornell!batcomputer!payne
              INTERNET:  [e-mail]

------------------------------

Date: 12 May 91 19:15:10 GMT
From: telebit![e-mail]
To: [e-mail]

References <[e-mail]>, <[e-mail]>, <[e-mail]>
Subject : Re: Security

We use a cryptographic challenge in our commercial stuff.  It works
like this:

1.  the called system generates a 64bit random number and transmits it
to the calling system as a 16 digit hex number like this:

    challenge: 197FE8BA001573FE

2.  the calling system then encrypts the challenge using DES and a key
known to both systems.

3.  the calling system then transmits the response back to the called
system again using a 16 digit hex number:

    response: 185FEA4780BE3A44

4.  the called system also does the same encoding and compares what
the calling systems sends as its response to what the called system
calculates.  No muss, no fuss.

Since one is using a 64 bit random number, the likelyhood that the
sequence will repeat is VERY small.  This can be implemented very
easily using the DES code that Phil Karn includes as part of the
KA9Q-NOS distribution.


--
Brian Lloyd, WB6RQN                              Telebit Corporation
Network Systems Architect                        1315 Chesapeake Terrace
[e-mail]                           Sunnyvale, CA 94089-1100
voice [phone]                             FAX [phone]

------------------------------

End of Packet-Radio Digest
******************************
Date: Tue, 14 May 91 04:30:06 PDT
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V91 #119
To: packet-radio


Packet-Radio Digest         Tue, 14 May 91       Volume 91 : Issue 119

Today's Topics:
            Hardware platforms & software
                  MSYS woes!
            PK-88 birdie on 145.01
                   Security
               Termcap entry for KA9Q?
              Time bug in KA9Q,
           Time bug in KA9Q, and nntp docs (3 msgs)
                 X.25

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

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: 14 May 91 06:20:55 GMT
From: RICEVM2.RICE.EDU![e-mail]
Subject: Hardware platforms & software
To: [e-mail]

Howdy

Is there a FAQ list for this newsgroup?  If so, could some kind soul
point me at it?  Is it available via ftp?

If not, could someone please take a shot at the following questions?
Email is fine unless you think that it is of general interest.

1.  What software is available for packet ... and what does it do?
     Protocol?  Bells & whistles?  Bugs?

2.  What hardware platforms does it run on?  386 clone?  286?  8088?  PS/2?
     Macintosh SE?  IIcx?  Amiga?  C-64?  VIC-20?  SPARCstation?  ;-)

3.  What additional hardware is required?  TNC?  Homebrew modem?  ???

4.  How much does it cost?  Registration cost if shareware?

5.  Any other comments you care to make?


TNX ES 73

---
 Jordan Kossack  |  n5qvi  |  [e-mail]  |  713 799 2950
------------------------------------------------------------------------
 "Congress has a distinguished tradition of completely misunderstanding
     the Constitution"   -- Earl Ryan  [ Nightline, 4 Dec 1990 ]

---
  Jordan Kossack  |  n5qvi  |  [e-mail]  |  799 2950
----------------------------------------------------------------------
"Congress has a distinguished tradition of completely misunderstanding
    the Constitution"   -- Earl Ryan  [ Nightline, 4 Dec 1990 ]

------------------------------

Date: 13 May 91 22:26:20 GMT
From: photon![e-mail]
Subject: MSYS woes!
To: [e-mail]

It seems that MSYS is fraught with weirdities.....  When one telnets to it, it
checks in its MSYSHOST.NET file to validate you.  I made a hosts file
according to the spec and the sysop installed it.  When I use my primary
address, it's OK.  When I use hamgate.wb5bbw, it tells me I'm not in the
hosts file.  Does anyone know if it requires simple callsigns as the hostname
in the MSYSHOST.NET file?  The sysop has gone home after semester end, so it'll
be a while before we can experiment.
If it requires simple hostnames, how does it specify "secondary" hostnames?
Or should I go somewhere else? 8-}
I guess I whould count myself lucky....  Before he put in the new hosts file,
it thought I was WA4EWV, who is .0.52, not .0.5.
Curiouser and curiouser.....

kurt
--
Kurt Freiberger, wb5bbw   [e-mail]   409/847-8706
Dept. of Computer Science, Texas A&M University  DoD #264
*** Not an official document of Texas A&M University ***

------------------------------

Date: 13 May 91 16:15:43 GMT
From: agate!apple!altos!gumby![e-mail]
Subject: PK-88 birdie on 145.01
To: [e-mail]

In article <[e-mail]> [e-mail] ( the Penguin) writes:
>
>I have a very annoying birdie on 145.01 that is coming from my PK-88.
>Does anyone have the mod to eliminate it or move it somewhere else?
>It's not too bad when using an external antenna, but it is full scale
>if the antenna is anywhere near the TNC.


Could you provide more information?  What kind of cabling are you using?
What radio, etc?

I have a PK-88 sitting about six inches from my 1/4-wave mag mount antenna
on top of a filing cabinet and have never had problems with birdies on
145.01.


--
Jerry Gardner, NJ6A                                     Altos Computer Systems
UUCP: {sun|pyramid|sco|amdahl|uunet}!altos!jerry        2641 Orchard Parkway
Internet: [e-mail]                               San Jose, CA  95134
Help stamp out vi in our lifetime.                      [phone]

------------------------------

Date: 13 May 91 16:20:24 GMT
From: agate!apple!altos!gumby![e-mail]
Subject: Security
To: [e-mail]

In article <[e-mail]> [e-mail] (ASQJ-NBF) writes:
>Maybe I'm missing something but whats the problem with using a
>Pass Word for protection? Granted some people can "break"
>Pass Words but it does take time. If i change my Pass Wordoften
>it becomes less likely that mine will be broken. If Phone BBS's
>support Pass Word protection why can't Packet BBS's do the same?
>I'm sure someone has the answer. Who gets the Cigar?


The answer to this question is fairly obvious:  when you call a phone-based
BBS, you are the only one on the line and others cannot monitor the line
and copy your password.

With packet, however, anyone on the same frequency can monitor your packets
and record your password.  Radio is like the old-fashioned telephone party
lines.



--
Jerry Gardner, NJ6A                                     Altos Computer Systems
UUCP: {sun|pyramid|sco|amdahl|uunet}!altos!jerry        2641 Orchard Parkway
Internet: [e-mail]                               San Jose, CA  95134
Help stamp out vi in our lifetime.                      [phone]

------------------------------

Date: 14 May 91 02:01:44 GMT
From: swrinde!sdd.hp.com!spool.mu.edu!munnari.oz.au!manuel!ccadfa!rodos2![e-mail]
Subject: Termcap entry for KA9Q?
To: [e-mail]

Thanks for the people who told me that the midnight bug was in DOS! I
haven't had any word on nntp yet. My next question is: can somebody
give me a termcap entry for the ka9q telnet `terminal'. It seems to
be a vt100-like thing, but ^[[? sends it into 40-column land. Would
looking through the source (which I can get) be of any help?

Thanks,

    Warren Toomey.

       Warren Toomey VK1XWT, slow kermiting.
      Deep in the bowels of ADFA Comp Science.
  `The key that I thought opened the door doesn't'

------------------------------

Date: 13 May 91 15:45:26 GMT
From: [e-mail]
Subject: Time bug in KA9Q,
To: [e-mail]

munnari.oz.au!manuel!ccadfa!rodos2![e-mail]     writes:

-For some reason, the date does increment to the next day when passing
-through midnight. Is this a bug in KA9Q, or perhaps a feature of MS-DOS?!

Do you really mean "does" or should it be "doesn't" ?

If the answer is "doesn't" then this rings a bell as a long-standing bug in
MS-DOS, I think its fixed in a version later than 3.1 but I'm not sure. The
symptom is that the date rolls over fine if the machine is off but if the
system is running it does not increment the day number as midnight goes by.

Try getting the very latest version of MS-DOS.

Steve

------------------------------

Date: 13 May 91 16:35:00 GMT
From: ucselx!usc!sdd.hp.com!apollo![e-mail]
Subject: Time bug in KA9Q, and nntp docs
To: [e-mail]

In article <[e-mail]> [e-mail] (Warren Toomey) writes:
>I have a couple of quick questions about KA9Q 910414.
>
>For some reason, the date does increment to the next day when passing
>through midnight. Is this a bug in KA9Q, or perhaps a feature of MS-DOS?!
>
>       Warren Toomey
>
At least one version of MS/DOS exhibited this characteristic (3.2 ???)

John KD7UW

------------------------------

Date: 13 May 91 23:08:05 GMT
From: agate!usenet.ins.cwru.edu!ncoast![e-mail]
Subject: Time bug in KA9Q, and nntp docs
To: [e-mail]

As quoted from <[e-mail]> by [e-mail] (Warren Toomey):
+---------------
| I have a couple of quick questions about KA9Q 910414.
|
| For some reason, the date does increment to the next day when passing
| through midnight. Is this a bug in KA9Q, or perhaps a feature of MS-DOS?!
+---------------

I assume you meant "...does not increment...".

If you are running DOS 2.11 or earlier, then it's an MS-DOS bug.  Otherwise,
I can't see it, since KA9Q depends on the DOS clock.

++Brandon
--
Me: Brandon S. Allbery                    Ham: KF8NH on 10m,6m,2m,220,440,1.2
Internet: [e-mail]                   (restricted HF at present)
Delphi: ALLBERY                          AMPR: kf8nh.AmPR.ORG [44.70.4.88]
uunet!usenet.ins.cwru.edu!ncoast!allbery       KF8NH @ WA8BXN.OH

------------------------------

Date: 14 May 91 04:40:47 GMT
From: usc!cs.utexas.edu!convex![e-mail]
Subject: Time bug in KA9Q, and nntp docs
To: [e-mail]

[e-mail] (Brandon S. Allbery KF8NH) writes:
- As quoted from <[e-mail]> by
-               [e-mail] (Warren Toomey):
- +---------------
- | I have a couple of quick questions about KA9Q 910414.
- |
- | For some reason, the date does increment to the next day when passing
- | through midnight. Is this a bug in KA9Q, or perhaps a feature of MS-DOS?!
- +---------------
-
- I assume you meant "...does not increment...".
-
- If you are running DOS 2.11 or earlier, then it's an MS-DOS bug.  Otherwise,
- I can't see it, since KA9Q depends on the DOS clock.

    Actually, it is a know (at least around here) bug with MS-DOS.
If you don't do some form of a date/time request each 24 hours, then
MS-DOS loses days.  It is because MS-DOS doesn't count how many times it
passes midnight, just that midnight has been passed, and doesn't
actually update the system's concept of the date and time until a date
or time request is made.  Thus, running two days with out a date/time
request (about any file operation causes one) would cause MS-DOS to lose
a day.

    Neat, eh.. :-)

--
Eric Schnoebelen                [e-mail]           [e-mail]
Arthur C. Clarke's Law :
    It has yet to be proven that intelligence has any survival value.

------------------------------

Date: 13 May 91 14:50:11 GMT
From: uupsi!phage!helix.cshl.org![e-mail]
Subject: X.25
To: [e-mail]

I am interested in learning X.25 internals ... for
a project I am about to undertake.

Can anybody suggest a IP site or a book that
would have more on the PROTOCAL

Thanks ..

Fred J. Stellabotte
Computer Systems Manager
Cold Spring Harbor Lab
[e-mail]

------------------------------

Date: 13 May 91 21:25:14 GMT
From: agate!apple![e-mail]
To: [e-mail]

References <[e-mail]>, <[e-mail]>, <[e-mail]>
Subject : Re: Security

In article <[e-mail]> [e-mail] (Brian Lloyd) writes:
>We use a cryptographic challenge in our commercial stuff.  It works
>like this:

I believe that Phil Karn used much the same approach in his DES package.
--
Ed Carp  N7EKG/6        [e-mail]         ...uunet!khijol!erc
UUWEST Consulting       Alameda, CA             415/814-0550

Computers HAVE caused a revolution in how much information we
can safely ignore!    [e-mail] (Rob Schaeffer)

-- Absolutely unabashed Gates McFadden groupie! --

------------------------------

Date: 13 May 91 19:37:02 GMT
From: orion.oac.uci.edu!ucivax!jarthur!bridge2!mips!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!src.honeywell.com!msi.umn.edu!noc.MR.NET!ns!ns![e-mail]
To: [e-mail]

References <[e-mail]>, <[e-mail]>, <[e-mail]>wel
Subject : Re: Security


Another method of authentication works like this.  Somehow a list of
(truely) random numbers (passwords) are created.  These are like
pre-computed passwords except that they are not password variants and
do not cary the true password in any form.  The exact method of
picking the passwords, or the password form is irrevelant except that
all the passwords should be random to each other and to their position
in the list.

The passwords are passed to the user over a secure channel and kept in
the BBS.

During initialization, the BBS asks for a password from the list and
the user must provide the correct answer from the list as a reply.  If
it is correct, then user is allowed in and the BBS marks that entry so
it is not to be used again.

Short of breaking into the BBS and finding the password list or
getting a copy of the list from the user, this is not breakable.

If the passwords are used up in sequence, then the user can tell if
someone else has used one.

jim, N0NKJ

Yes, I know this is just like (but a little different than) the
others.  Yes, I know that the BBS sysop can break this.

Comments about making truely random numbers should be sent to
sci.crypt.

------------------------------

End of Packet-Radio Digest
******************************
Date: Wed, 15 May 91 04:30:06 PDT
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V91 #120
To: packet-radio


Packet-Radio Digest         Wed, 15 May 91       Volume 91 : Issue 120

Today's Topics:
               Does anyone have PORTAL
             DRSI 9600 bps card?
             msys ax25 ver-1 help
          PMP Source & Designators (2 msgs)
           Time bug in KA9Q, and nntp docs

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

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: 15 May 91 00:13:20 GMT
From: swrinde!zaphod.mps.ohio-state.edu!ub![e-mail]
Subject: Does anyone have PORTAL
To: [e-mail]

I was wondering if anyone knew of something called PORTAL for packet communications.   I saw a brief mention of it in an article about Unix and
packet.  Also, does anyone know where it would reside if it is FTP'able

                            - Chris (KB2JTP)
                            [e-mail]

------------------------------

Date: 14 May 91 16:01:26 GMT
From: [e-mail]
Subject: DRSI 9600 bps card?
To: [e-mail]

Andy at DRSI mentioned to me this morning that they're making a new PCPA
card with both 1200 bps and 9600 bps modems on the card.

Anyone had a chance to play with one of these yet?
    - Brian

------------------------------

Date: 14 May 91 20:01:38 GMT
From: [e-mail]
Subject: msys ax25 ver-1 help
To: [e-mail]

Hello just started to test and hope to use a nice bit of bbs code
however can anyone help me how do you get the code to use ax25 ver2
the entire soft package is some what usless in a ax25 ver2 network
infact if i try to use it to connect to the local node all i get
back in responce to a SABM is DM and busy from the node
i have been looking at the g8bpq code and have used it in the past
for a long time on my home bbs [gb7sau] but that was in the days of
bpq v 3.53 its changed some what! is it posible to use bpq-code
in kiss input to get wa8bxn's msys code to talk ax25 v2 and make it
work please any help to me
internet = [e-mail]
ax25-bbs = [e-mail]
tcpip    = [e-mail] [44.130.24.71]
thanks all

------------------------------

Date: 14 May 91 15:49:33 GMT
From: [e-mail]
Subject: PMP Source & Designators
To: [e-mail]

I have two questions:

1.  Where can PMP be obtained?

2.  Can a file listing the designators (world wide) be obtained via this
    net.  So far, I am only accessing packet via a dumb terminal.  There
    are a few files I'd like to get a hard copy of, but the designators
    is my first priority.

PS:  I currently us Wash. St. Univ. club station W7YH.

Regards,                                       The "OTHER" Washington
                       ____________________________
ROBERT GIDEN, N7KCG                        \   /\/\             /\  /\|
Sys-Analyst & Programmer        P   ______  |  /\/\               /\  |
College of Ag & Home Ec         aO \      / \   /\          Spokane + |
Washington State University     cc \  /\ \   |+Seattle                |
PULLMAN, WA 99164-6230          IE  |  /\ \ /    /\                   |
U.S.A.                          fa   \     |     /\                   |
                in   |          /\      Pullman/WSU->*|
TELEPHONE: [phone]         C     \        /\          ____________\
Fax: [phone]                      ----\   /\    _____/
BITnet: [e-mail]                 \-------/
Internet: [e-mail]            \-------/

------------------------------

Date: 14 May 91 18:53:55 GMT
From: theory.tn.cornell.edu![e-mail]
Subject: PMP Source & Designators
To: [e-mail]

In article <[e-mail]> [e-mail] (Robert Giden N7KCG) writes:
>1.  Where can PMP be obtained?

    The latest version of PMP can be found on 'helios.tn.cornell.edu'
in the /pub directory via anonymous FTP.

    If you don't have Internet connectivity, try the FTP mail server at
Princeton.  Send a message with the Subject "HELP" and the message "HELP"
to '[e-mail]' for details.


--
=  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =
Andrew C. Payne, N8KEI        UUCP:  ...!cornell!batcomputer!payne
              INTERNET:  [e-mail]

------------------------------

Date: 14 May 91 19:09:59 GMT
From: pacbell.com!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!rphroy!caen!uwm.edu!psuvax1!psuvm![e-mail]
Subject: Time bug in KA9Q, and nntp docs
To: [e-mail]

In article <[e-mail]>, [e-mail] (Eric
Schnoebelen) says:


>        Actually, it is a know (at least around here) bug with MS-DOS.
>If you don't do some form of a date/time request each 24 hours, then
>MS-DOS loses days.  It is because MS-DOS doesn't count how many times it
>passes midnight, just that midnight has been passed, and doesn't
>actually update the system's concept of the date and time until a date
>or time request is made.  Thus, running two days with out a date/time
>request (about any file operation causes one) would cause MS-DOS to lose
>a day.

>        Neat, eh.. :-)

>--
>Eric Schnoebelen                [e-mail]           [e-mail]
>Arthur C. Clarke's Law :
>        It has yet to be proven that intelligence has any survival value.

The problem in the latest versions of NOS doesnt follow this pattern at all.
On my PC system running DOS 3.2 the date didnt increment at all for over
a week until there was a power glitch from a thunderstorm yesterday and
I rebooted.  During this time there were plenty of disk accesses going on,
the smtp timer and the mbox forwarding timers both cause a disk read once
an hour or so, and there were lots of writes to the log file.  73's Jim KB3KJ

------------------------------

End of Packet-Radio Digest
******************************
Date: Thu, 16 May 91 04:30:08 PDT
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V91 #121
To: packet-radio


Packet-Radio Digest         Thu, 16 May 91       Volume 91 : Issue 121

Today's Topics:
          PC software for Packet operation.
   ROSE X.25 Source/Executable/Documentation Announcement (2 msgs)
               Which TNC would you buy?

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

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: 14 May 91 15:59:56 GMT
From: swrinde!sdd.hp.com!spool.mu.edu!cs.umn.edu!msi.umn.edu!noc.MR.NET!ns!ns![e-mail]
Subject: PC software for Packet operation.
To: [e-mail]

I just purchased the Heathkit pocket TNC and was wondering if there
was freeware available for the PC to run it (especially if it's
available via anonymous FTP).

Please reply via email.

Thanks

jim

------------------------------

Date: 15 May 91 15:43:37 GMT
From: usc!rpi!uwm.edu!linac!att!cbnewsh![e-mail]
Subject: ROSE X.25 Source/Executable/Documentation Announcement
To: [e-mail]

The Radio Amateur Telecommunications Society (RATS) is pleased
to announce that the complete, source, executable and documentation
for the ROSE X.25 Switch by Tom Moulton, W2VY is now available for
non-commercial Amateur Radio use.

RATS encourages others to port the code to other platforms and to
use it to develop new applications in amateur radio and other areas.
Amateur Radio use of the code requires the developer to simply send
RATS the source code to the new environment or application for further
distribution by RATS as part of the growing RATS Open Systems Environment
(ROSE) platform.  Other development uses of the code are also possible,
with licensing available through RATS.  For further information contact:
J. Gordon Beattie, Jr., N2DSY at the address or telephone listed below.


Points of Distribution

The software will be posted to the RATS Bulletin Board System
at +1.201.387.8898.   login as "rats" and use xmodem.

Folks wishing to obtain the software via e-mail can contact
[e-mail].   A uuencoded copy of the ZIP archive
will be sent to you.

ftp via the Internet will be arranged shortly.


RSWS0422.INF
.
   The Radio Amateur Telecommunications Society is pleased to
   provide you with a complete archive of the latest version of the
   ROSE X.25 Switch software.  Please follow the directions for
   unpacking this version of the software and you will minimize
   problems.  If you have any questions please call Gordon Beattie,
   N2DSY at +1.201.387.8896 or via packet: [e-mail].

1. Make sure that you have about 2 megabytes of free disk space.
   You won't need to use it all, but it will give you room to play
   with the code once you explode the ZIP file.

2. Create the directory path "c:\SRC\RATS\ROSE0422".  You may
   use another drive if you like, but this structure will keep you
   out of trouble when you get future releases of software.

3. With the ZIP file archive on a diskette use the following
   command to break down the ZIP archive onto your "c:" drive:

           PKUNZIP -d a:\RSWS0422.ZIP c:\SRC\RATS\ROSE

4. Please note that the "-d" option will create the required
   subdirectories for you.  If you have problems, make sure that
   the version of PKUNZIP is as current as the one shown below or
   later.

   PKUNZIP (tm)    FAST!    Extract Utility    Version 1.01    07-21-89
   Copyright 1989 PKWARE Inc.  All Rights Reserved.  PKUNZIP/h for help


5. Now go make something useful using this code and send us a copy!

   The Radio Amateur Telecommunications Society
   206 North Vivyen Street
   Bergenfield, NJ  07621
   +1.201.387.8896

------------------------------

Date: 15 May 91 20:42:23 GMT
From: usc!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!unixhub!lll-winken!aunro!atha!aupair.cs.athabascau.ca![e-mail]
Subject: ROSE X.25 Source/Executable/Documentation Announcement
To: [e-mail]

>The Radio Amateur Telecommunications Society (RATS) is pleased
>to announce that the complete, source, executable and documentation
>for the ROSE X.25 Switch by Tom Moulton, W2VY is now available for
>non-commercial Amateur Radio use.

>Points of Distribution

>ftp via the Internet will be arranged shortly.

Now available via anonymous FTP from:

    nro.cs.athabascau.ca:~ftp/hams/rose-422.zip

I will also place a (12 bit) compressed tar archive there in a day
or so containing everything except the binaries (and with CRLF to LF
bashing done on the text files) for the Unix crowd.


--
    Lyndon Nerenberg  VE6BBM / Computing Services / Athabasca University
       atha!cs.athabascau.ca!lyndon || [e-mail]
            Packet: [e-mail]
      The only thing open about OSF is their mouth.  --Chuck Musciano

------------------------------

Date: 15 May 91 00:43:31 GMT
From: hpl-opus!hpspdra![e-mail]
Subject: Which TNC would you buy?
To: [e-mail]

I am trying to decide which model TNC to buy.  Does anyone have any
recommendations?  Is one brand or model especially better than the
others? or are all the ones with similiar features about the same?

tnx & 73 Paul AA6PZ

------------------------------

End of Packet-Radio Digest
******************************
Date: Fri, 17 May 91 04:30:10 PDT
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V91 #122
To: packet-radio


Packet-Radio Digest         Fri, 17 May 91       Volume 91 : Issue 122

Today's Topics:
            Grace NET Version 1.01
            Hardware platforms & software
           Kyokuto Denshi radio on packet?
            msys ax25 ver-1 help (2 msgs)
           Proposed SoCal 220 MHz bandplan revision
              Time bug in KA9Q v 910423
              west coast ham bbs
               Which TNC would you buy?

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

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: 16 May 91 05:07:03 GMT
From: usc!cs.utexas.edu!asuvax!stjhmc![e-mail]
Subject: Grace NET Version 1.01
To: [e-mail]

I have received my disk for Gracilis NET Version 1.01 ... I have placed it up
on asuvax.eas.asu.edu for ftp (located in subdirectory "stjhmc")

David


--
   -------------------------------------------------------------------------
      St. Joseph's Hospital and Medical Center, Phoenix, Arizona
    uucp: {gatech, ames, rutgers}!ncar!asuvax!stjhmc!ddodell
    Bitnet: ATW1H @ ASUACAD                    FidoNet=> 1:114/15
    Internet: [e-mail]       FAX: [phone]

------------------------------

Date: 16 May 91 13:04:08 GMT
From: swrinde!mips!cs.uoregon.edu!ns.uoregon.edu!milton!sumax!polari!rwing!eskimo![e-mail]
Subject: Hardware platforms & software
To: [e-mail]

In article <[e-mail]>, [e-mail] (Jordan M Kossack) writes:
>
> Is there a FAQ list for this newsgroup?  If so, could some kind soul
> point me at it?  Is it available via ftp?
>

I'd be interested in the same type of info. I've been out of amateur
radio for a number of years and am about to dust off the transcievers,
etc.

73
Tom
KD9NL/7

------------------------------

Date: 16 May 91 15:23:27 GMT
From: swrinde!mips!apple!xanadu![e-mail]
Subject: Kyokuto Denshi radio on packet?
To: [e-mail]

I recently got a "Kyokuto Denshi" VHF transciever (model something-146-
something). This is a crystal controlled radio with 12 channels.
The TR switching is with relays.  Power out is about 7 to 10 watts.
Mobile style.  The price was right.

Anyhow it has about 6 channels filled out with crystals and
I'd like to get it on packet.  So I got some crystals for 145.07 MHz.
(It takes one each for transmit and receive.)  Put the new crystals in
and, well it doesn't work on the frequency.  In fact it doesn't seem
to work below 146 MHz.

So I took it apart and found out that the oscillator isn't putting out
the same voltage level on 145.07 as it is on 146.10; it's putting out
much less.  Hence, it's not enough to drive the amplifier.  Though it
is putting out a signal on 145.07MHz.  So I'm about to try and lower
the operating frequency of the oscillator.

My question is: Before I dig into this, has anyone else done this
already and can tell me what parts to replace?

Thanks

Oh, I have schematics for the transmit and receive section (but not
the amplifier) already.

P.S. I understand that the IC22 is a crystal controlled radio for
146-148 MHz.  Is this true?  If so, is there a mod sheet somewhere
to get it to work below 146MHz?  I hear that this radio is used
alot on 9600bps packet in socal.

Jeff Crilly (N6ZFX)
AMIX Corporation  2345 Yale Street  Palo Alto, CA  94306
[e-mail], {uunet,sun}!markets!jeff, N6ZFX@N6IIU.#NOCAL.CA.USA

------------------------------

Date: 16 May 91 13:17:20 GMT
From: sdd.hp.com!spool.mu.edu!munnari.oz.au!manuel!csc.canberra.edu.au!echo![e-mail]
Subject: msys ax25 ver-1 help
To: [e-mail]

In <[e-mail]> [e-mail] (BARRY TITMARSH) writes:

>Hello just started to test and hope to use a nice bit of bbs code
>however can anyone help me how do you get the code to use ax25 ver2
>the entire soft package is some what usless in a ax25 ver2 network
>infact if i try to use it to connect to the local node all i get
>back in responce to a SABM is DM and busy from the node

I don't know why the local node (Netrom?) gives you a DM.  Even
AX25L2V1 should still work.

MSYS's poor AX25 has become somewhat of a bad joke. :-(
I run it here and it has real problems.  I can connect to 3 BBSes
from which I receive/send mail and they are all 2 digipeater hops away.
The links are somewhat "difficult" :-(

It's a real pity as otherwise the code is excellent. I use it here
to support 2 radio ports on VHF and a serial link to the Xenix machine.
It acts as the local gateway between the two local frequencies;
144.800Mhz 4800 baud and 147.575Mhz 1200 baud.

>bpq v 3.53 its changed some what! is it posible to use bpq-code
>in kiss input to get wa8bxn's msys code to talk ax25 v2 and make it
>work please any help to me

No you can't.  MSYS doesn't support the packet driver you have to use.

You could try putting NET/ROM code into your TNC and using an nrs link
(NET/ROM async protocol).  MSYS does support it however the instructions
on using it are buried deep within the bit in the manual on using the
MSYS Network code. (Around page 60 in the MSYS 1.10 manual)

Carl.
[e-mail]
[e-mail]
3:620/241.7

------------------------------

Date: 16 May 91 15:35:37 GMT
From: [e-mail]
Subject: msys ax25 ver-1 help
To: [e-mail]

In <[e-mail]> [e-mail] (BARRY TITMARSH) writes:
>>infact if i try to use it to connect to the local node all i get
>>back in responce to a SABM is DM and busy from the node

Did you set your callsign?  If your TNC is identifying as 'NOCALL',
net/rom networks will DM you.
    - Brian

------------------------------

Date: 16 May 91 11:17:41 GMT
From: [e-mail]
Subject: Proposed SoCal 220 MHz bandplan revision
To: [e-mail]

A copy of a proposed 220 MHz bandplan for Southern California arrived
here this evening.  I understand that this proposal will be voted upon
at the 220SMA (the SoCal 220 MHz frequency coordinating association)
meeting coming up in a few weeks.  I'm distributing it on the net so
that people in California and the civilized world can see what's up.

[Note: the original I'm working from was a diagram; this is the best I
could do in typing it in from a low-rez fax. -bk]

The proposal:
-----------------------------------------------------------------------
222.000 - 222.025       EME
222.025 - 222.160       CW/SSB/ACSB/AM
222.180 - 223.380       Duplex pair inputs
223.400 - 223.580       FM Voice Simplex
223.600 - 223.760       Digital
223.780 - 224.980       Duplex pair outputs
    "61 20 KHz Duplex pairs"
    "Control Channels at Odd 20 KHz Spacing"

CHANGES:
1. EME/CW/SSB/SCSB/AM Increased from 100 KHz to 160 KHz.
2. Aux, Link, and Control Channels Reduced from 1.680 MHz to NO
dedicated Aux. Link Channels and 120 "possible" Control Frequencies.
Actually lost 37 multi-use Aux. Link Channels.
3. Digital reduced from two 100 KHz Wide-Band Channels and two
Narrow-Band Channels (plus two private coordinated Digital use channels)
(approx. 280 KHz total) to 180 KHz for sub-coordination by the SCDCC.
4. FM Voice Simplex did not change the number of 20 KHz Channels. (Now
all together.)
5. DUPLEX PAIRS (Voice and Digital). Reduced from 69 Channels to 61
Channels (loss of 160 KHz).
-----------------------------------------------------------------------

To me, this looks like a very good plan, as it seems to make a quite
equitable distribution of the remaining portion of the band.  It looks
as though quite a bit of thought went into it, and it will serve the
interests of most of the 220 community reasonably well.

My biggest worry is that the 220 Spectrum Management Association
members might vote it down out of frustration with the FCC, and
then have to replace it with something they dream up in place at
the meeting.

A few of my own notes and comments:

I'm guessing what is meant by 'odd channels' for control is that the
control freqs will be wedged at the 10khz points in between the duplex
pair inputs and outputs.  Given proper selection of those for
geographical separation, and the low usage of real control channels,
that will probably work quite well.  Non-duplex links may be a problem
if they're active and stuck in there.  A lot of rice-rockets may not
be able to do 10 KHz stepping on 220.

Note that the FM simplex chunk retains the national calling frequency of 223.5.

Losing 8 repeater/remote pairs is a pain, but because the new subbands
are pretty close to what the old repeater bands were, a lot of people
won't have to move.  There will perhaps be some problems with radios
that know the bandplan a bit too intimately choosing to select simplex
or duplex operation in the wrong place, but I don't know of any where
the operator can't override that.  There will be some more crowding - in
SoCal, there are at least two systems per channel, often more, already,
and losing 8 pairs will make that worse.

Packet-radio-related comments:

SCDCC is the So Cal Digital Coord Committee; they're the packet people
for much of SoCal.  This proposal suggests delegating coordination of
the digital sub-band to them; let us hope they do it wisely.

My hope is that they'll put a 100 khz "wideband" channel for 56kb usage
in the middle of that sub-band (centered at 223.680, from 223.630 to
223.730), leaving 4 20 KHz channels for conventional narrowband FM
packet, allocate the bottom two channels (223.600, 223.620) for user
access, and the top two (223.740, 223.760) for networking - perhaps one
intercity, one intra- (metro net).  The wideband channel can be used as
a 56kb simplex channel, or the input half of a duplex 56kb channel, with
the output on 433.150 MHz or somewhere.
    - Brian

------------------------------

Date: 17 May 91 00:55:43 GMT
From: swrinde!mips!samsung!munnari.oz.au!uniwa!cc.curtin.edu.au![e-mail]
Subject: Time bug in KA9Q v 910423
To: [e-mail]

   I reported this bug myself a couple of weeks ago. It isn't a DOS bug --
it happens on my system running DOS 4.01. It does appear to be a problem in
NET.EXE, since it doesn't happen with pa0gri's NOS0828.
.....Ron
--

===============================================================================
 Internet: [e-mail]                | "A pipe gives a wise man
 Bitnet: [e-mail]    | time to think, and a
 UUCP  : uunet!munnari.oz!cc.curtin.edu.au!Murray_RJ | fool something to stick
Amateur Packet Radio: VK6ZJM@VK6BBS.#WA.AUS.OC       | in his mouth"
           TCP/IP: 44.136.204.14, 44.136.204.19  |    -- Murphy's Law I
===============================================================================

------------------------------

Date: 16 May 91 05:21:49 GMT
From: cruzio![e-mail]
Subject: west coast ham bbs
To: [e-mail]

Can anyone tell me of a good ham bbs on the west coast that has TCP/IP
(with DOCS!) for packet and a some packet software...other good ham pd
or shareware aimed at VHF/UHF ops...
What software do you recommend?

Brett Breitwieser KC6UPU      ..uunet!cruzio!brettb

------------------------------

Date: 17 May 91 00:37:27 GMT
From: [e-mail]
Subject: Which TNC would you buy?
To: [e-mail]

Paul AA6PZ ask which TNC would you buy? I have purchased two of the
KAM TNC's and like them b=very much. I like the dual port capibility
and the service from Kantronics. Even here in Japan they take care
of me. I also like being able to be on the display freq and not
have to try and add or subtract for Frequency differences. It may
be operator malfunctions but I have tried and have seen others operate with
TNC's that cause the display freq on the transceiver to be placed on
a freq other than the operating freq.
de [e-mail]

------------------------------

End of Packet-Radio Digest
******************************
Date: Sat, 18 May 91 04:30:06 PDT
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V91 #123
To: packet-radio


Packet-Radio Digest         Sat, 18 May 91       Volume 91 : Issue 123

Today's Topics:
           Kyokuto Denshi radio on packet?
              NNTP client in NOS
            Packet radio in France
    ROSE X.25 Source/Executable/Documentation Announcement
          Time bug in KA9Q v 910423 (2 msgs)

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

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: 17 May 91 15:17:12 GMT
From: swrinde!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!emory!wa4mei!ke4zv![e-mail]
Subject: Kyokuto Denshi radio on packet?
To: [e-mail]

In article <[e-mail]> [e-mail] (Jeff Crilly N6ZFX) writes:
>
>P.S. I understand that the IC22 is a crystal controlled radio for
>146-148 MHz.  Is this true?  If so, is there a mod sheet somewhere
>to get it to work below 146MHz?  I hear that this radio is used
>alot on 9600bps packet in socal.

Merely realigning the IC-22A, note the A, will allow it to cover *any*
2 Mhz segment of 2 meters. For packet, just go in and tweak for maximum
smoke on your packet frequency. That will become the new center frequency
of the radio. For the IC-22S, note the S, some modifications are required.
The A is crystal controlled while the S is diode programmed synthesiser
based.

Gary KE4ZV

------------------------------

Date: 15 May 91 11:10:18 GMT
From: uhccux!uhcmtg.phys.hawaii.edu![e-mail]
Subject: NNTP client in NOS
To: [e-mail]

I'm looking for some help in getting the NNTP client in NOS to work properly.

I want to restrict the newsgroups received to only a few so for example I do a
'nntp groups rec.radio.amateur.packet'.  But instead of getting only articles
from that group, I get stuff from several other groups that I've never
specified.  Anyone know how to prevent this from happening?

I also noticed that when our local newsserver starts the transfer, it starts
sending with the oldest articles in a group.  I presume this is because the
nntp client has no current history of the received messages from a newly added
newsgroup and so the history needs to be 'primed'.  Is there any way of
manually adjusting this history mechanism?

Tony
AH6BW
[e-mail]

--
Antonio Querubin
[e-mail] / [e-mail] / [e-mail]

------------------------------

Date: 15 May 91 07:33:28 GMT
From: [e-mail]
Subject: Packet radio in France
To: [e-mail]

I'll shortly be moving from the UK to France (Grenoble, to be precise). Is
there much packet or other activity in the area? I'd appreciate any comments
on the amateur scene over there, email replies would probably be best.

Thanks

Steve McKinty, GI8OYA
email: [e-mail]

------------------------------

Date: 17 May 91 18:39:12 GMT
From: sdd.hp.com!mips!atha!aupair.cs.athabascau.ca![e-mail]
Subject: ROSE X.25 Source/Executable/Documentation Announcement
To: [e-mail]

>       nro.cs.athabascau.ca:~ftp/hams/rose-422.zip

>I will also place a (12 bit) compressed tar archive there in a day
>or so containing everything except the binaries (and with CRLF to LF
>bashing done on the text files) for the Unix crowd.

... which I have now done. I left the binaries in, and the npa.arc file
has been split out into its individual files in the npa/ sub-directory.

To get the files via anonymous FTP:

    nro.cs.athabascau.ca:hams/rose-422.zip
    nro.cs.athabascau.ca:hams/rose-422.tar.Z

If you have a uucp connection to aunro, try:

    uucp aunro!~ftp/hams/rose-422.zip ~uucp
    uucp aunro!~ftp/hams/rose-422.tar.Z ~uucp

For those of you who are still in the dark ages, nro.cs.athabascau.ca lives
at IP address 131.232.1.1.

--
    Lyndon Nerenberg  VE6BBM / Computing Services / Athabasca University
       atha!cs.athabascau.ca!lyndon || [e-mail]
            Packet: [e-mail]
      The only thing open about OSF is their mouth.  --Chuck Musciano

------------------------------

Date: 17 May 91 15:15:50 GMT
From: photon![e-mail]
Subject: Time bug in KA9Q v 910423
To: [e-mail]

In article <[e-mail]>, [e-mail] (Ron Murray) writes:
|>
|>    I reported this bug myself a couple of weeks ago. It isn't a DOS bug --
|> it happens on my system running DOS 4.01. It does appear to be a problem in
|> NET.EXE, since it doesn't happen with pa0gri's NOS0828.
|> .....Ron
|> --

Just as another data point, I ran NET.EXE w/ DOS 3.3 & Desqview 2.31.  Versions 910420 and 910423 both cause the rollover to the next day to
be lost.  If I leave the system up but without NET.EXE running, the system catches the rollover fine -- even i'm running something like a kermit
download at midnite.

I also can't figure out where it's happening. 8-(

------------------------------

Date: 17 May 91 23:03:44 GMT
From: epic![e-mail]
Subject: Time bug in KA9Q v 910423
To: [e-mail]

In article <[e-mail]>, [e-mail] (Willis Marti) writes:
|> Just as another data point, I ran NET.EXE w/ DOS 3.3 & Desqview 2.31.  Versions 910420 and 910423 both cause the rollover to the next day to
|> be lost.  If I leave the system up but without NET.EXE running, the system catches the rollover fine -- even i'm running something like a kermit
|> download at midnite.
|>
|> I also can't figure out where it's happening. 8-(

I redid much of the time-of-day processing in those versions so it's
entirely possible that I introduced a bug. I'll go back and check.

I hate MS-DOS timekeeping. What a crock.

Phil

------------------------------

End of Packet-Radio Digest
******************************
Date: Sun, 19 May 91 04:30:02 PDT
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V91 #124
To: packet-radio


Packet-Radio Digest         Sun, 19 May 91       Volume 91 : Issue 124

Today's Topics:
         Current Mac version of KA9Q - Where?
               PACKET->Internet Gateway
             Packet-Radio Digest V91 #123
               PK-88 birdie fix
                   Security
              TEKK/K9NG/G3RUH repeater?

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

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: 15 May 91 22:59:49 GMT
From: ncr-sd!ncrcae!oiscola![e-mail]
Subject: Current Mac version of KA9Q - Where?
To: [e-mail]

Can anyone tell me where i can find a current version of
ka9q for the Macintosh?

I looked on thumper.bellcore.com and other sites with no
luck.

Thanks,
--
----------
Michael L. Kornegay,
  [e-mail], x7628/x7507/x7956, or
  [e-mail], and [e-mail]

------------------------------

Date: 17 May 91 00:22:24 GMT
From: swrinde!zaphod.mps.ohio-state.edu!menudo.uh.edu!nuchat!farwest![e-mail]
Subject: PACKET->Internet Gateway
To: [e-mail]

Organization: San Diego State University Computing Services

Don't know if the other message/article was posted here, so I'll request again.
Does anyone know if a PACKET (either AX.25 and/or TCP/IP) gatewaye exists
between PACKET radio and Internet?  If so, could someone please state where it
is located?  If not, why has this not been performed?  Additionally, what would
be needed in getting set up?

Robert S. Radvanovsky, KC6ONL


 * Origin: Two Wheelers  bikie hangout (1:106/88.0)

------------------------------

Date: 18 May 91 22:51:36 GMT
From: [e-mail]
Subject: Packet-Radio Digest V91 #123
To: [e-mail]

DELETE

------------------------------

Date: 18 May 91 14:02:42 GMT
From: uhccux![e-mail]
Subject: PK-88 birdie fix
To: [e-mail]

Sorry for the delay of this summary.  Final exams mugged me.  :-)

Thanks for the letters, everyone.  The simplest, quickest way to
get rid of the birdie on 145.01 is to adjust the trimmer capacitance
on the clock oscillator crystal.  The MFJ I just wired up for a friend
has a variable capacitor exlicitly for the purpose of shifting
the harmonics a few kHz.

I noticed that my ZOOM 2400 telephone modem put out a nasty spur on 145.01
too.  A couple of 33 pF disc ceramics shifted the birdie down to 144.98 MHz.
(This circuit used one capacitor on each crystal lead.)

Some people suggested improving the shielding with proper bonding and
grounding.  This is always a Good Thing.  Sandpaper, star washers, and
screwdrivers are effective weapons.  Stiff filtering of ALL leads entering
the TNC is also a good idea.  Toroids are generally sufficient.  Snap-apart
toroids are useful for those serial cables with DB-25 connectors.

One person even went so far as to filter the clock outputs inside the TNC.
That is more than I am willing to do, since the noise floor here in Honolulu
is pretty high anyway, and I can usually receive better than I can "talk"
(subject to pagers and taxicabs.)

Thanks for the help!
    de John KJ9U / KH6   and   Ted  NH6YK

------------------------------

Date: 17 May 91 22:32:02 GMT
From: swrinde!zaphod.mps.ohio-state.edu!think.com!snorkelwacker.mit.edu!bloom-beacon!eru!hagbard!sunic!mcsun!hp4nl!phigate!philica![e-mail]
Subject: Security
To: [e-mail]

In article <[e-mail]> [e-mail] (Andrew Payne) writes:
>       A simple authentication system that works well for packet goes
>something like this (this has been discussed at length already, so I'll keep
>it short):  suppose you and the BBS share a password.  This password is
>arranged off the air and never goes out over the air.  Now, when you connect
>to the BBS, it "challenges" you with a random string or word.  Now, you
>must take this random string, encrypt it with your password, and send it
>back to the BBS.  The BBS compares your answer to what it thinks it
>should have gotten (remember, it has your password too).  If it is correct,
>the BBS assumes you are you, because you are the only one who could have
>properly encrypted the reply.

I improved this scheme a few years back (remember when W0RLI still came
with source?) to make it slightly more secure.
Every time you log in, you make part of your key known. A determined hacker
could monitor all of this and re-build the key from the challenges and
the responses he collected in time.

What I did was sending the user multiple (in my case 3) challenges,
and requiring the user to fix one (but just one) of them, randomly picked.
Now, the guy monitoring receives an answer which is valid for one of these
challanges, but he doesn't know which one. He needs to get much more
challenge-answer combinations to extract the key and needs statistics
to do so.
This way, a key is much longer usable. Also, the techniques to re-build it
are slightly more difficult.

Maybe this gives someone an idea. I used it mostly for remote sysop work
(there was a time when we has some locals who thought it was fun to wipe
a BBS. I don't think they are still doing that now.)

73, Geert Jan PE1HZG

------------------------------

Date: 17 May 91 17:38:19 GMT
From: [e-mail]
Subject: TEKK/K9NG/G3RUH repeater?
To: [e-mail]

Has the topic of a 9600 regenerative repeater come up?  Does anyone know
what would be required?  KC0OX mentioned wanting to do that recently..
Ron, speak up old man.  Do the TEKK radios have split TX and RX strips,
or must one use 2 of them?  Has anyone gotten the whole idea plotted
out?  Perhaps Gracillis would do well to "can" the idea and sell it huh?
I have NOT given up on the goal of a full duplex WA4DSY 56K system, BUT,
we need something the masses can afford to get involved with.

If you have a response on this, please post it to the net and also CC:
[e-mail] 128.104.198.22  ..

Tnx a million!

Pat, KD9UU, Wisconsin/Michigan U.P. AMPR IP ADDRESS COORD.

P.S., I'm not beyond following schematics...  Be nice, offer me one :-).

------------------------------

End of Packet-Radio Digest
******************************
Date: Mon, 20 May 91 04:30:06 PDT
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V91 #125
To: packet-radio


Packet-Radio Digest         Mon, 20 May 91       Volume 91 : Issue 125

Today's Topics:
         Current Mac version of KA9Q - Where?
             KA9Q nntp docs - what I know
      Packet - TCP/IP Station, questions and discussion
                Working UO-14

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

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: 19 May 91 05:44:22 GMT
From: uhccux!uhcmtg.phys.hawaii.edu![e-mail]
Subject: Current Mac version of KA9Q - Where?
To: [e-mail]

In article <[e-mail]> [e-mail] (Michael L. Kornegay) writes:
>Can anyone tell me where i can find a current version of
>ka9q for the Macintosh?

You can usually find it on apple.com in the pub/ham-radio directory.  Apple
is currently re-organizing things on their FTP server.  I think they're moving
everything over to ftp.apple.com so you may want to search through that host
once it becomes available.

That version of KA9Q for the Mac conforms to the old 'NET' version.  I don't
know if anyone is working on a 'NOS' for the Mac.

Tony
AH6BW


--
Antonio Querubin
[e-mail] / [e-mail] / [e-mail]

------------------------------

Date: 20 May 91 01:47:10 GMT
From: munnari.oz.au!manuel!ccadfa!sserve!csadfa![e-mail]
Subject: KA9Q nntp docs - what I know
To: [e-mail]

Here is a quick summary of nntp in the latest ka9q, from what I've been
able to gather from the source, and using the program. Oh BTW, a manual
bug, ping's delay value in the manual is in seconds, in the program it is
milliseconds, this can be embarrasing.

    Warren Toomey


nntp
----

Valid commands are: addserver directory dropserver groups kick
            listservers trace


nntp addserver <hostid> <seconds>
---------------------------------

    Add the server given by the hostid; news will be sought after
from this server. The time in seconds holds the interval that nos waits
until looking for new news.

nntp directory <spooldir> <controldir>
--------------------------------------

    Tell nntp which directories to use for news. The spool dir
will hold the actual news articles. For example, if spooldir is /ka9q/spool
and you are receiving a group alt.foo.bar, articles in that group will be
placed in a file /ka9q/spool/news/alt/foo/bar.txt. The control directory
will hold the files `history' (those news articles that nos has received),
and `nntp.dat', which holds that date the nntp server was last checked.
Note that the bar.txt file is in a format that can be read as mail (e.g
with bm etc.).

nntp dropserver <hostid>
------------------------

    Remove the named server from the list of nntp servers.

nntp groups <groupname> <groupname> ...
---------------------------------------

    This gives the list of groups in which you want to receive news.
You can have more than one of these commands. I think '*' stands for all groups.

nntp kick <hostid>
------------------

    Initiate an nntp session between nos and the server(s).

nntp listservers
----------------

    Lists the servers nos gets news from. The list gives the hostid,
the delay between checking for news, and the number of seconds left until
the next time nos checks for news.


nntp trace <0|1|2|3|4>
----------------------

    Turn tracing of nntp on according to the given number, which has
the following meaning:

    0 - Turn tracing off
    1 - Serious errors are reported
    2 - Transient errors are reported
    3 - The nntp session progress is reported
    4 - As per 3, but the actual articles are displayed

------------------------------

Date: 20 May 91 05:58:54 GMT
From: uvaarpa!murdoch!turing![e-mail]
Subject: Packet - TCP/IP Station, questions and discussion
To: [e-mail]

Howdy! I'm a new Amateur Radio Operator (A Codeless Wonder, CW for short)!

:)

So, what I'd like to do is bend the ears of a few Elmers if I may...

I'd like info and discussion on the feasibility of hooking together my
AT&T 3B1 (a 10Mhz 68010 based UNIX desktop), KA9Q TCP/IP software (Which,
I admit, I don't have yet, can someone give me a FTPable site pointer?,)
a Kantronic KAM (3.x ROMS,) and a 2M/70CM radio.

I understand there is an internet out there. Does this mean it's got routers
and nameservers, etc...? Or must each site maintain a set of hosts and networks
and gateways files?

I'd like to be able to have such a configuration, but I'd like to be able to
switch to a async/tty connection to the KAM in packet mode so that folks W/O
the skills, money, and time to put into a TCP/IP based digital radio communic-
ations system can access the 3B1 to read news, or use email using any available
simple packet station.

Also, I'd like to be able to connect to my UNIX host in my office, by land line
to UUCP mail and news over.

The radio will be either a TH77A or a IC-W2A and in a month or two after
I get the radio, I'll get a AR270 Cushcraft antenna, and a RFC 2/70G AMP.
So, I think I'll be able to put up a reasonable and reachable digital
station (I don't want to call it a BBS)

A month or so after that I'll get a decent 35W or so mobile unit and
free up the HT for regular portable use (including, of course, a pocket
packet station :)

To best meet my needs, I'd like to be able to reconfigure from TCP/IP
to Packet easily, and as often as I like. I'd like to put up a cron job
that switchs modes . That way I can publish a schedule for users.

I'm really looking forward to serving the local Amateur community with
a lot of whiz bang stuff. I operated a multiline (as many as 4) BBS
(had a LAN in my 'shack' W/ 6 machines, and 6 phone lines, etc.. :)
I'm a Network Engineer for a living, so I should be able to do well
enough at this after I can get some info and discussion.

Any and all responses are most appreciated!


--
______
\ OO / Mr. Jeffersons Academical Village
 \++/  Terrestrial Coordinates: 38 04 06N / 79 03 53W
  \/   Sic Semper Tyrannus

------------------------------

Date: 19 May 91 08:07:20 GMT
From: kb2ear!overlf![e-mail]
Subject: Working UO-14
To: [e-mail]

I would be interested in hearing from anyone who is working the UO-14
satellite using nondirectional antennas. I would be interested in data on the
antennas and rf gear used. In addition I would like to know any information
about using the g3ruh modems with this bird.

Dave Marthouse
Internet: [e-mail]
Internet: [e-mail]
Packet: n2aam @ w2emu-4.nj.usa.na
Fidonet: dave marthouse 1:107/323

------------------------------

End of Packet-Radio Digest
******************************
Date: Tue, 21 May 91 04:30:07 PDT
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V91 #126
To: packet-radio


Packet-Radio Digest         Tue, 21 May 91       Volume 91 : Issue 126

Today's Topics:
               300-baud Baycom or PMP?
          PACKET->Internet Gateway (2 msgs)
      Packet - TCP/IP Station, questions and discussion (2 msgs)
            packet radio in France
             Reply RE: MSYS 1.11

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

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: 20 May 91 23:44:02 GMT
From: swrinde!zaphod.mps.ohio-state.edu!think.com!news![e-mail]
Subject: 300-baud Baycom or PMP?
To: [e-mail]

Has anyone made Baycom work at 300 baud?  I built a Bell 103 modem for HF
packet, but I haven't been able to get Baycom to see packets, even though
the signal looks pretty good on the 'scope.

What about PMP?  I just started looking at it, and it requires a few
changes to get the timing stuff right (it's hardcoded to 1200 bps, and I
think there is a potential overflow problem in the 16-bit timer stuff for
the *slow* 300 bps).
--
--Bruce Walker
  Thinking Machines Corporation, Cambridge, MA
  [e-mail]; [phone]; N1IKV/AE

------------------------------

Date: 19 May 91 03:21:54 GMT
From: swrinde!zaphod.mps.ohio-state.edu!menudo.uh.edu!lobster!nuchat!farwest![e-mail]
Subject: PACKET->Internet Gateway
To: [e-mail]

Organization: San Diego State University Computing Services

Don't know if the other message/article was posted here, so I'll request again.
Does anyone know if a PACKET (either AX.25 and/or TCP/IP) gatewaye exists
between PACKET radio and Internet?  If so, could someone please state where it
is located?  If not, why has this not been performed?  Additionally, what would
be needed in getting set up?

Robert S. Radvanovsky, KC6ONL
o


 * Origin: Two Wheelers  bikie hangout (1:106/88.0)

------------------------------

Date: 20 May 91 18:22:48 GMT
From: epic![e-mail]
Subject: PACKET->Internet Gateway
To: [e-mail]

In article <[e-mail]> [e-mail] (Robert S. Radvanovsky KC6ONL) writes:
>Organization: San Diego State University Computing Services
>
>Don't know if the other message/article was posted here, so I'll request again.
>Does anyone know if a PACKET (either AX.25 and/or TCP/IP) gatewaye exists
>between PACKET radio and Internet?  If so, could someone please state where it
>is located?  If not, why has this not been performed?  Additionally, what would
>be needed in getting set up?
>
>Robert S. Radvanovsky, KC6ONL

I'm preparing a list of "frequently asked questions" about amateur radio
TCP/IP, and this is prominent on it.

If you mean "connectivity at the IP level", the answer is "no, at
least not officially". The problems are both technical and legal. The
technical problems have to do with the addressing conventions used in
the Internet, particularly the amateur use of a class-A network number
(44) despite the AMPRNET being a collection of isolated "islands" of
activity. This is fixable, however, through a combination of "hacks"
such as encapsulation and/or source routing.

As for mail-level gateways, there is no technical problem; MX records
pointing to a local gateway are all you need.

The much bigger problem is the FCC's rules on third party traffic and
content screening. I see no solution to this problem short of
reforming the rules to bring them into the latter half of the 20th
century.  In fact, given the FCC's recent crackdown on internal
amateur-amateur packet networking, I'm sadly coming to the conclusion
that a meaningful amateur TCP/IP network will never happen.

The Private Radio Bureau staff at the FCC seems to consider the amateur
service as their own private regulatory fiefdom. If they do not "like"
a particular application or use, they simply issue a decree against
it.  When you try to protest (e.g., at the FCC's so-called "forum" at
Dayton) you encounter a brick wall.

Part 15 probably represents the best route for building a "real"
packet radio Internet. You can encrypt, you can use it for business,
and you don't have to be licensed. You can do a lot with 1 watt on 902
MHz, given good equipment, antennas and sites. Yes, it's a shame if we
have to go this route considering that packet radio has been one of
the few "jewels" in amateur radio's "crown" over the past decade, but
the "amateur spirit" is often stronger and better nurtured in places
other than amateur radio.

Phil

------------------------------

Date: 20 May 91 15:23:27 GMT
From: swrinde!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!emory!wa4mei!ke4zv![e-mail]
Subject: Packet - TCP/IP Station, questions and discussion
To: [e-mail]

In article <[e-mail]> [e-mail] (Jon Gefaell) writes:
>
>I'd like to be able to have such a configuration, but I'd like to be able to
>switch to a async/tty connection to the KAM in packet mode so that folks W/O
>the skills, money, and time to put into a TCP/IP based digital radio communic-
>ations system can access the 3B1 to read news, or use email using any available
>simple packet station.

KA9Q supports simple AX25 connects as well as TCP/IP connections. Given the
source for KA9Q on your machine (no, I don't know where a current version is
available either), you should be able to hack an interface using PTYs (don't
know if your version of Unix supports this). Note that KA9Q runs in user space
rather than kernel space like the commercial TCP/IP packages so you must use
a "backdoor" approach to logins of any nature. On the 386 Unix version, you
can use the PTY trick, or you can let the user log in to the KA9Q package and
allow him to spawn child processes to do his interfacing with your Unix system.
This isn't at all secure. I have old KA9Q sources that say they work on 3B
systems in the Makefile. If all else fails, send me mail and I'll try to
arrange for you to fetch them. The latest should be on thumper.bellcore.com
however, in the pub/ka9q directory.

>Also, I'd like to be able to connect to my UNIX host in my office, by land line
>to UUCP mail and news over.

KA9Q supports SLIP.

>The radio will be either a TH77A or a IC-W2A and in a month or two after
>I get the radio, I'll get a AR270 Cushcraft antenna, and a RFC 2/70G AMP.
>So, I think I'll be able to put up a reasonable and reachable digital
>station (I don't want to call it a BBS)
>
>A month or so after that I'll get a decent 35W or so mobile unit and
>free up the HT for regular portable use (including, of course, a pocket
>packet station :)

I'd urge you not to use a HT for a packet server. There are lots of
possible problems that can baffle even experienced hams. HTs can be,
and are, used by lots of folks, but it isn't optimum. You'll need to
solve RFI, overload, and keyup interfacing problems that can discourage
you quickly.

Good luck

Gary KE4ZV

------------------------------

Date: 21 May 91 02:16:40 GMT
From: swrinde!elroy.jpl.nasa.gov!lll-winken!aunro!aupair.cs.athabascau.ca![e-mail]
Subject: Packet - TCP/IP Station, questions and discussion
To: [e-mail]

[e-mail] (Gary Coffman) writes:

>I'd urge you not to use a HT for a packet server. There are lots of
>possible problems that can baffle even experienced hams. HTs can be,
>and are, used by lots of folks, but it isn't optimum. You'll need to
>solve RFI, overload, and keyup interfacing problems that can discourage
>you quickly.

Horse Pucky!!!

I ran the local BBS on an FT-470 for the better part of four months
with no problem whatsoever (that could be attributed to the HT :-)
The 470 locks on in TX mode very quickly. The slow squelch could be
a problem, but that's endemic to most rigs - whether they are base, mobile,
or HT's. Besides, most TNC support software carrier detect, so you just
run with the squelch wide open anyway.

--
    Lyndon Nerenberg  VE6BBM / Computing Services / Athabasca University
       atha!cs.athabascau.ca!lyndon || [e-mail]
            Packet: [e-mail]
      The only thing open about OSF is their mouth.  --Chuck Musciano

------------------------------

Date: 21 May 91 06:40:17 GMT
From: [e-mail]
Subject: packet radio in France
To: [e-mail]

From:   HUTIN@PSI%EPSX25@MRGATE@SNDRTR
To:     "[e-mail]"@M_INTERNET@MRGATE@SNDRTR


Hello

There is more than 40 BBS in france covering most of the country with
good forwarding between them. The closest from Grenoble is probably
F6BIG-1 in annecy. Most of VHF activity is on 144.675 with some also on
145.275 and 144.650 MHz. Around Grenoble there is also a TCPIP subnet.

The most of the Nodes are using THENET but plan is to move to ROSE.
The move has already be done in the South West and is progressing.

There is a large TCPIP network around Paris (May be due to the
visit of N3EUA Bdale last year) 15 stations are 24h stations on
a total of 40 running TCPIP.

73s Remi FE6CNB

------------------------------

Date: 20 May 91 15:51:39 GMT
From: [e-mail]
Subject: Reply RE: MSYS 1.11
To: [e-mail]

Hello all
I see in the digest lots of replies to me question on msys 1.11 ans ax25
Lev 2 Ver 1. In germany we have FLEXNET not NETROM and this will NOT
accept any type of ax25 Lev2 VER 1 !! in any form or shape !
In Europe and mostly in the UK all i hear is "Msys is really great"
BUT "We cant use it cos its VERSION 1 Proto" and "The author refuses
to do anything about it as HE does NOT like ver 1 proto"
OK if he dont want to use it can he at least put a soft switch in the
code so that those potential users who wish to use MSYS code can use
it with ver 2 proto and those who dont can use ver 1 proto
Is that Fair Deal or not ?
In my case i just cant use it in ver 1 proto the network here will not
accept ANY connects in ver 1 Cos FLEXNET dont support OLD proto's
[e-mail]    or [e-mail] or [e-mail]

------------------------------

End of Packet-Radio Digest
******************************
Date: Wed, 22 May 91 04:30:09 PDT
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V91 #127
To: packet-radio


Packet-Radio Digest         Wed, 22 May 91       Volume 91 : Issue 127

Today's Topics:
           Begining TCPIP troubles...Help!
               PACKET->Internet Gateway
           Proposed SoCal 220 MHz bandplan revision
              Time bug in KA9Q v 910423
              Undeliverable mail

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

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: 21 May 91 15:19:00 GMT
From: [e-mail]
Subject: Begining TCPIP troubles...Help!
To: [e-mail]

I am attempting to start some TCPIP activity in the local area. I DL'd a
copy of the NET dated 4-23-91. The problem I have is that the documentation I
have found does jive with this version of the NET. I have discovered the many
variants of of TCPIP that are around that confuse me even more.
My questions are:
1. Is there documentation for this version and is this version any different
   to the others around.
2. If this version has no documentation, what version is recommended for use;
   especially if on wants to turn the MBOX on and have some BBS activity on AX25
3. How do I turn the MBOX ON in this version of the NET and how do I get it
   to send a banner to a connecting station (on AX25) just like the beginners
   guide says.
4. What about the versions hacked by PA0GRI and G1EMM? Are these the versions
   that include all the bells and whistles and hence the ones to uses. I'd like
   to know the differences.

So many questions...I'd like to have a mentor to guide me.

Thanks, 73
Feroz, WU9N

------------------------------

Date: 21 May 91 17:15:35 GMT
From: usc!samsung!caen!ox.com!b-tech![e-mail]
Subject: PACKET->Internet Gateway
To: [e-mail]

>Part 15 probably represents the best route for building a "real"
>packet radio Internet. You can encrypt, you can use it for business,
>and you don't have to be licensed. You can do a lot with 1 watt on 902
>MHz, given good equipment, antennas and sites. Yes, it's a shame if we

Can anyone give me more info on this?  Are there readily available modems
and radios (9600-56kb)?  What kind of range can I expect?

--
Jon Zeeff (NIC handle JZ)        [e-mail]

------------------------------

Date: 21 May 91 21:05:07 GMT
From: [e-mail]
Subject: Proposed SoCal 220 MHz bandplan revision
To: [e-mail]

>The proposal:
>-----------------------------------------------------------------------
>222.000 - 222.025      EME
>222.025 - 222.160      CW/SSB/ACSB/AM
>222.180 - 223.380      Duplex pair inputs
>223.400 - 223.580      FM Voice Simplex
>223.600 - 223.760      Digital
>223.780 - 224.980      Duplex pair outputs
>       "61 20 KHz Duplex pairs"
>       "Control Channels at Odd 20 KHz Spacing"
>
[some details omitted]
>
>To me, this looks like a very good plan, as it seems to make a quite
>equitable distribution of the remaining portion of the band.  It looks
>as though quite a bit of thought went into it, and it will serve the
>interests of most of the 220 community reasonably well.

It may look very good from a SoCal point of view, but I sure hope this
plan, or something similar, doesn't get foisted on the rest of the
continent.  I just can't muster up any enthusiasm for a VHF/UHF bandplan
that allots a paltry 6% of the band to digital modes.  I know that the
repeater pairs can be used for digital operation, but I think this plan is
really inadequate as far as wideband digital operation is concerned.  This
apparently stems from a rather miserly allotment of only two 100 KHz
channels in the previous SoCal bandplan, despite the fact that the ARRL
Board approved the allotment of five such channels (at 220.5 - 221.0 MHz)
in 1987.  In contrast to the SoCal bandplan, the CRRL bandplan for 220-225
MHz which came out in 1989 recommends a total of 1.6 MHz for digital, all
but 200 KHz of which could be used for wideband links.  A similarly
enlightened plan for 222-225 MHz should allot at least 1 MHz for digital.
This obviously won't happen in densely-populated areas which are already
chock-a-block with analog FM repeaters and links, but I firmly believe
that they should not set the pattern for everywhere else.

Then again, there's talk of us losing the *whole* band in Canada, so this
may all become a moot point.  A look at a recent repeater directory will
show how sparse 220 use is up here... we need to get more wideband digital
going on this band, and soon.

Barry VE3JF

------------------------------

Date: 21 May 91 09:58:17 GMT
From: sci34hub!cheroke![e-mail]
Subject: Time bug in KA9Q v 910423
To: [e-mail]

Consider this:

When MS-DOS wants to calculate the current time of day, it works
its way down to the BIOS to get the number of system ticks that have
elapsed since 00:00 (the system tick count is synchronized with
time of day).  This tick count is obtained via INT 1A, AH = 0.

Well, INT 1A, AH = 0 also returns a flag (in AL) indicating
time has crossed 00:00 and MS-DOS uses this clue to bump the
day etc.  When the BIOS returns the flag set, it clears it so
it'll be zero on subsequent calls.

The problem may be that NET.EXE is making INT 1A calls for timing
and "steals" the rollover flag from MS-DOS.  If that appears to
be the case, then

    (1) replace the INT 1A call in NET with fetching the tick
    count from BIOS data area (with ints off since long fetches
    not indivisible):
    cli(); ticks = *(long far *) 0x40006cL; sti();

or (2)  when you see the flag is set, stuff it back into BIOS data
    area:
    if (r.h.al == 1) *(char far *) 0x400070L = 1;

(I use (1) and just thought of (2)).  No guarantees on the two lines
of code except I double checked the absolute addresses in the bios:
40:6C is dword tick count and 40:70 is byte rollover flag.

73 de n4yos


--
 Tom Thompson      { [uunet!]sci34hub!cheroke!tom }     [phone]

------------------------------

Date: 21 May 91 23:29:00 GMT
From: [e-mail]
Subject: Undeliverable mail
To: [e-mail]

Your message could not be delivered to:

    POLDER@WOLGA

Your message has been enqueued and undeliverable for 3 days.
The mail system will continue to try to deliver your message
for an additional 9 days.

The beginning of your message follows:

Date: Sat, 18 May 91 17:00 MET
From: [e-mail]
Subject: Packet-Radio Digest V91 #123
To: POLDER@WOLGA
Message-id: <[e-mail]>
X-Envelope-to: POLDER@WOLGA
X-VMS-To: Gerrit Polder PA3BYA <[e-mail]>

Packet-Radio Digest         Sat, 18 May 91       Volume 91 : Issue 123

Today's Topics:
           Kyokuto Denshi radio on packet?

------------------------------

Date: 21 May 91 15:14:21 GMT
From: usc!wuarchive!udel!haven.umd.edu!uvaarpa!murdoch!turing![e-mail]
To: [e-mail]

References <[e-mail]>, <[e-mail]>, <[e-mail]>(
Subject : Re: Packet - TCP/IP Station, questions and discussion

In article <[e-mail]> [e-mail] (Lyndon Nerenberg) writes:
>[e-mail] (Gary Coffman) writes:
>
>>I'd urge you not to use a HT for a packet server. There are lots of
>>possible problems that can baffle even experienced hams. HTs can be,
>>and are, used by lots of folks, but it isn't optimum. You'll need to
>>solve RFI, overload, and keyup interfacing problems that can discourage
>>you quickly.
>
>Horse Pucky!!!
>
>I ran the local BBS on an FT-470 for the better part of four months
>with no problem whatsoever (that could be attributed to the HT :-)
>The 470 locks on in TX mode very quickly. The slow squelch could be
>a problem, but that's endemic to most rigs - whether they are base, mobile,
>or HT's. Besides, most TNC support software carrier detect, so you just
>run with the squelch wide open anyway.
>

This is indeed a bummer. Looks like we got a good conversation on this
subject brewing, but this is the first message in this thread I've seen
here. Conclusion: Gary Coffman's posts are not making it to UUnet. We're
directly connected, and have a full feed, but I didn't get his message
here, only the qoute in Lyndons message :(

At any rate, From what I can see here, Gary says that an HT isn't the
key piece of equipment for a packet station. I'd tend to agree that it's
not the optimum piece of equipment, but it should do for a few months till
I get another rig to dedicate to the task. I can only afford to buy one
radio at a time (!) so at first it will be the HT for setup and experimenting
then I'll plunk in an Alinco 110 or something for the long haul. (I think
I mentioned this in my message.)

Lyndon is quite right that my KAM has software carrier detect, so I don't
need to worry 'bout slow squelch (thoough I do believe the better HT's have
a settable squelch response) The interference from the computer and all is
very real problem, and one I suppose might be influenced by HT design
criteria.

Thanks for the response(s?) I look forward to hearing more... Specificaly
on the 3B1, KA9Q, and configuration specifics... Thanks!
--
______
\ OO / Mr. Jeffersons Academical Village
 \++/  Terrestrial Coordinates: 38 04 06N / 79 03 53W
  \/   Sic Semper Tyrannus

------------------------------

Date: 21 May 91 19:46:58 GMT
From: elroy.jpl.nasa.gov!usc!wuarchive!emory!wa4mei!ke4zv![e-mail]
To: [e-mail]

References <[e-mail]>, <[e-mail]>, <[e-mail]>*
Reply-To : [e-mail] (Gary Coffman)
Subject : Re: Packet - TCP/IP Station, questions and discussion

In article <[e-mail]> [e-mail] (Lyndon Nerenberg) writes:
>[e-mail] (Gary Coffman) writes:
>
>>I'd urge you not to use a HT for a packet server. There are lots of
>>possible problems that can baffle even experienced hams. HTs can be,
>>and are, used by lots of folks, but it isn't optimum. You'll need to
>>solve RFI, overload, and keyup interfacing problems that can discourage
>>you quickly.
>
>Horse Pucky!!!
>
>I ran the local BBS on an FT-470 for the better part of four months
>with no problem whatsoever (that could be attributed to the HT :-)
>The 470 locks on in TX mode very quickly. The slow squelch could be
>a problem, but that's endemic to most rigs - whether they are base, mobile,
>or HT's. Besides, most TNC support software carrier detect, so you just
>run with the squelch wide open anyway.

Like I said, lots of people do it. That still doesn't mean it will work
for you. Slow squelch is a problem if you use one of those TNCs with
the single chip modems rather than TAPR's original PLL. You can't run open
squelch on these TNCs without modifying the TNC. TAPR sells a little
daughter board kit for most TNCs. Software DCD is not very reliable and
you will often be held off unnecessarily wasting valuable channel time.
RF getting back into the audio line is often a problem because many HTs
use a plastic case and you can't shield them properly. Hash from your
computer similarly gets in the plastic radio. Many HTs simply can't handle
the duty cycle of an active packet station on high power and low power is
often inadequate to get the job done. And probably the worst failing of
all is that today's wideband receive HTs will overload severely if
connected to an outside antenna in a moderately high RF area like
being within a few miles of a commercial FM or TV station or near a
nest of pagers.

I've made various HTs work on packet, but it usually hasn't been simple
plug'n'play. On the other hand, nearly every base or mobile rig I've
tried *has* been essentially plug'n'play. Even old clunkers like the
IC22A or the KDK144 worked easily. Indeed, the old rigs with the narrow
frontends were often easier to use, weren't bothered by intermod, ran
decent power, and were much *cheaper* than a HT.

Gary KE4ZV

------------------------------

Date: 22 May 91 04:32:48 GMT
From: uvaarpa!murdoch!turing![e-mail]
To: [e-mail]

References <[e-mail]>, <[e-mail]>, <[e-mail]>
Subject : Re: Packet - TCP/IP Station, questions and discussion

In article <[e-mail]> [e-mail] (Gary Coffman) writes:
<Lots of very specific, and convincing information, concluded by:>

>I've made various HTs work on packet, but it usually hasn't been simple
>plug'n'play. On the other hand, nearly every base or mobile rig I've
>tried *has* been essentially plug'n'play. Even old clunkers like the
>IC22A or the KDK144 worked easily. Indeed, the old rigs with the narrow
>frontends were often easier to use, weren't bothered by intermod, ran
>decent power, and were much *cheaper* than a HT.


What I think is that you are quite correct. It _can_ be done with an HT,
as [e-mail] points out. That's why I think it's
worth my time to get things set up, and in place using the HT (which,
of course, will be my introduction to the local HAM community (I know
a few, but not a lot) _and_ a workable vehicle for setting up the station.
Give me a two or three months and I'll have a dedicated 35-45 watt xcvr
set up with a power supply, and a battery system. (in case of emergency,
and for field day, etc...)

Thanks for the info here, I intend to take advantage of it, and much better
understand the myriad of ways an HT is not suited to a high efficiency,
reliable station.

Now, on to the Communications configuration of the host system, ka9q NOS
(TCP/IP) on a 3B1, and packet async connection on the same port, using
cron to time the TCP/IP and Packet Service schedule.

BTW, ThanksInAdvance y'all, appreciate the info and opinions!
--
______
\ OO / Mr. Jeffersons Academical Village
 \++/  Terrestrial Coordinates: 38 04 06N / 79 03 53W
  \/   Sic Semper Tyrannus

------------------------------

End of Packet-Radio Digest
******************************
Date: Thu, 23 May 91 04:30:10 PDT
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V91 #128
To: packet-radio


Packet-Radio Digest         Thu, 23 May 91       Volume 91 : Issue 128

Today's Topics:
     300-baud Baycom or PMP? (I want to get PMP) (2 msgs)
            Looking for W0RLI BBS software
         New version of the radio BBS program PCMBOX
             Packet-Radio Digest V91 #127
              Security (2 msgs)
                 Weather Maps

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

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: 22 May 91 13:23:31 GMT
From: usc!cs.utexas.edu!news-server.csri.toronto.edu!utgpu!utzoo!mnetor!ghp![e-mail]
Subject: 300-baud Baycom or PMP? (I want to get PMP)
To: [e-mail]

Who can send me the PMP stuff?  I tried the gateway as suggested
in a previous article, but it won't let me.

73 & tnx, jim
--
Jim Stewart, VE3SRJ
UUCP:  [e-mail]
BELL:  [phone]

------------------------------

Date: 23 May 91 00:01:36 GMT
From: theory.TC.Cornell.EDU![e-mail]
Subject: 300-baud Baycom or PMP? (I want to get PMP)
To: [e-mail]

In article <[e-mail]> [e-mail] (Jim Stewart) writes:
>Who can send me the PMP stuff?  I tried the gateway as suggested
>in a previous article, but it won't let me.

    Yes, it seems that '[e-mail]' won't serve you
unless you are on BITNET.  However, there is hope.  Try the 'other' FTP
mail server at '[e-mail]' (send a message w/ the subject HELP
and the message body HELP).

--
=  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =
Andrew C. Payne, N8KEI        UUCP:  ...!cornell!batcomputer!payne
              INTERNET:  [e-mail]

------------------------------

Date: 22 May 91 19:24:58 GMT
From: usc!apple![e-mail]
Subject: Looking for W0RLI BBS software
To: [e-mail]

Anyone know where I can ftp the W0RLI BBS software package?  Or something
similar?  It's gotta be source written in C (I'm porting it to UNIX).

Thanks!
--
Ed Carp  N7EKG/6        [e-mail]         ...uunet!khijol!erc
Packet:  N7EKG @ N6IIU.#NOCAL.CA.US
UUWEST Consulting       Alameda, CA             415/814-0550

Computers HAVE caused a revolution in how much information we
can safely ignore!    [e-mail] (Rob Schaeffer)

-- Absolutely unabashed Gates McFadden groupie! --

------------------------------

Date: 22 May 91 21:29:35 GMT
From: swrinde!zaphod.mps.ohio-state.edu!think.com!mintaka!bloom-beacon!eru!hagbard!sunic!dkuug!iesd![e-mail]
Subject: New version of the radio BBS program PCMBOX
To: [e-mail]

There is a new version of of the PCMBOX program at iesd.auc.dk
130.225.48.4
The version is a 5.35, and it can be ftp as anonymous ftp from iesd.

Best Regard

Peter



--
Home adr:               | Peter V.H.Sunesen | Department of Computer Science
  Heimdalsgade 42,7     |                   |  University of Aalborg (AUC)
  9000 Aalborg, Denmark |[e-mail]|           Denmark

------------------------------

Date: 22 May 91 14:25:00 GMT
From: [e-mail]
Subject: Packet-Radio Digest V91 #127
To: [e-mail]

UNSUBSCRIBE

------------------------------

Date: 22 May 91 15:16:00 GMT
From: [e-mail]
Subject: Security
To: [e-mail]

What about the public key cryptographic systems?
I won't try to explain
the details, but the idea is that I pick my own secret
key and derive from it a public key.  The math tells us
that a message encrypted using the public key can only be
decrypted by the private key.  So, I tell everyone
in the world my public key.  In particular, I can tell it
over the air to a sysop without caring about
eavesdroppers.  Now anyone who wants to send me a message
uses the public key to encrypt it, and I'm the only person
in the world who can decrypt it.  In particular, when I log in
to a node it picks a random challenge string, encrypts it
with my public key, and expects me to respond with the
decrypted string.

I defer to those far more knowledgeable than I to fill in details
or tell me why it won't work.

-- Michael
   [e-mail]

------------------------------

Date: 22 May 91 19:42:11 GMT
From: theory.TC.Cornell.EDU![e-mail]
Subject: Security
To: [e-mail]

In article <[e-mail]> [e-mail] (Michael Kosowsky) writes:
>What about the public key cryptographic systems?

    There's currently a pretty active thread in 'sci.crypt' about
public key systems.  Seems that someone has managed to collect enough patents
to make implementation of a public key scheme (not only RSA, but others)
without infringement impossible.  Here, "impossible" is a relative thing
that depends on your money and lawyers.

    Progress,



--
=  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =
Andrew C. Payne, N8KEI        UUCP:  ...!cornell!batcomputer!payne
              INTERNET:  [e-mail]

------------------------------

Date: 22 May 91 23:24:01 GMT
From: hpl-opus!hpnmdla![e-mail]
Subject: Weather Maps
To: [e-mail]

I have what (I hope) is a pretty simple request.  What I basically
want to do is to recieve weather sattelite images onto an IBM-PC type
machine.  Although I have a pretty fair EE background I don't have much
experience with amateur radio.  Basically what I want is the cheapest
hardware solution that will get the job done.  I have access to a
(recieve only) SW radio that I can use as a reciever.  Do I have to buy
a packet controller? (Someone recommended a 'packrat' which runs about
$300 and hooks up the serial port.  Although I think this will get the
job done it seems like overkill as this box appears to be able to both
transmit and recieve a number of digital formats including Weather maps)

I guess my basica problem Is I don't know where to go from here.  I am willing
(actually prefer) to write my own software, I am just not aware what the
minimum hardware requirements are and how to get started.  Can anyone point
me in the right direciton?  Any publications/books which might help?

Thanks

John

------------------------------

Date: 22 May 91 17:01:08 GMT
From: sdd.hp.com!wuarchive!ukma!aunro!aupair.cs.athabascau.ca![e-mail]
To: [e-mail]

References <[e-mail]>, <[e-mail]>, <[e-mail]>
Subject : Re: Packet - TCP/IP Station, questions and discussion

OK, I will revise my statement :-)

An FT-470 connected to a Kantronics KAM, running software carrier
detect in the TNC and open squelch on the radio works flawlessly,
subject to possible intermod problems (which we don't have).

What I was getting at was the tone of your posting, which implies
that an HT is worthless as a packet transceiver. In many many cases
that is simply not true.



--
    Lyndon Nerenberg  VE6BBM / Computing Services / Athabasca University
       atha!cs.athabascau.ca!lyndon || [e-mail]
            Packet: [e-mail]
    As a math athiest, I should be excused from this.   --Calvin

------------------------------

Date: 22 May 91 16:51:54 GMT
From: sdd.hp.com!cs.utexas.edu!asuvax!mcdphx!.UUCP![e-mail]
To: [e-mail]

References <[e-mail]>, <[e-mail]>, <[e-mail]>
Reply-To : dlf@.UUCP (Dave Fritsche)
Subject : Re: Time bug in KA9Q, and nntp docs

>>        Actually, it is a know (at least around here) bug with MS-DOS.
>>If you don't do some form of a date/time request each 24 hours, then
>>MS-DOS loses days.  It is because MS-DOS doesn't count how many times it
>
>The problem in the latest versions of NOS doesnt follow this pattern at all.
>On my PC system running DOS 3.2 the date didnt increment at all for over
>a week until there was a power glitch from a thunderstorm yesterday and
>I rebooted.  During this time there were plenty of disk accesses going on,

MS-DOS v3.2 and earlier will not increment the date at midnight.  It
doesn't matter how many disk accesses you do, it simply doesn't increment
the date.  Change to DOS 3.3 or 4.x and the problem will go away.  I've
been there.

73 . . . Dave Fritsche (wb8zxu)
[e-mail] (Tempe, AZ)

------------------------------

End of Packet-Radio Digest
******************************
Date: Fri, 24 May 91 04:30:02 PDT
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V91 #129
To: packet-radio


Packet-Radio Digest         Fri, 24 May 91       Volume 91 : Issue 129

Today's Topics:
            Authentication system
           KISS - does it reduce overhead? (2 msgs)
            Looking for W0RLI BBS software
          PACKET->Internet Gateway (3 msgs)
           Proposed SoCal 220 MHz bandplan revision
          REMOVE curtis@madnix from mail ist
                   Security
               Which TNC would you buy?
              Wireless LANs mailing list

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

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: 23 May 91 19:48:06 GMT
From: [e-mail]
Subject: Authentication system
To: [e-mail]

I am preparing a spec on BBS-to-BBS authentication using DES.  What I
seem to be missing is how a string of characters is translated into
the 56 bit key.  What is an accepted way of doing this?

I hope to have the spec ready next week and will post it here for you
guys to take a shot at.  It should include LZH compression and binary
message transfer too.

Roy, AA4RE

------------------------------

Date: 23 May 91 16:17:48 GMT
From: pa.dec.com!nntpd.lkg.dec.com!sousa!sndpit.enet.dec.com![e-mail]
Subject: KISS - does it reduce overhead?
To: [e-mail]

After looking over the documentation on my new TNC and reading thru "Your
Gateway to Packet Radio by WA1LOU(?)", I find that 20 bytes of overhead per
packet is going to kill my thruput, especially considering I want to send
one 8-byte packet every 25 milliseconds at 9600 baud (full-duplex).  It
almost sounds like KISS mode might eliminate some of the overhead, but I
don't have a very good handle on how it works, does it:

1)      Send a 'normal' packet, with the usual 14(+) byte adress field,
and all the rest of the stuff that makes up the 20 byte overhead,regardless
of the fact that it's not connected.

or

2)      Just send some kind of special packet, with less overhead.

Any ideas?  Where can I find the protocol spec for talking to a TNC in KISS
mode?  Many thanks in advance!  [BTW:  It's a real-time application, and I
can't just send one 256-byte packet every 800 ms.]
Willie Smith
[e-mail]
[e-mail]
{Usenet!Backbone}!decwrl!sndpit.enet.dec.com!smith

------------------------------

Date: 24 May 91 01:39:44 GMT
From: fs7.ece.cmu.edu!o.gp.cs.cmu.edu!andrew.cmu.edu!<[e-mail]>[e-mail]
Subject: KISS - does it reduce overhead?
To: [e-mail]

> I find that 20 bytes of overhead per packet is going to kill my
> thruput, especially considering I want to send one 8-byte packet
> every 25 milliseconds at 9600 baud (full-duplex).  It almost sounds
> like KISS mode might eliminate some of the overhead

KISS is a protocol for transporting data or commands between a computer
and a TNC. The TNC will take anything that is inside a KISS data packet
and append a 16 bit checksum to it and send it to the transceiver.

If you want to reduce the overhead imposed by AX.25 you could either 1)
use higher bit rates, such as 56 kbps or 2) devise your own link level
protocol. What is transported inside a KISS data packet does not
necessarily need to be an AX.25 frame, it could be anything you have
designed that you feel is better. (Legalities not considered.)

Don't forget that most unmodified transmitters have a fairly long key-up
delay, at least 200 ms. At 9600 bit/s that equals to an overhead of 240
bytes.

Anders W3/SM0RGV

------------------------------

Date: 24 May 91 04:03:46 GMT
From: swrinde!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!pitt!w2xo![e-mail]
Subject: Looking for W0RLI BBS software
To: [e-mail]

In article <[e-mail]>, [e-mail] (Ed Carp) writes:
> Anyone know where I can ftp the W0RLI BBS software package?  Or something
> similar?  It's gotta be source written in C (I'm porting it to UNIX).

First, I believe Hank no longer will release source code. The last
C code for W0RLI might be gotten from VE3GYQ, Dave Toth, who was
the last person to work on it and that was way back at version 6.

Several years ago I ported W0RLI to Sys V Unix. It isn't a wonderful
thing because , being a PC program, it is a big loop and uses CPU
cycles even when not running, but I may be able to scare up the
source. I believe others have done this also.  The version I ported
was 2.something, which is pretty old now, but the I/O is the main
thing and it will probably work with newer code. You are welcome
to it if I can find it.

A better solution is to run KA9Q 'net' using KISS tncs which gives
you AX25, Net/Rom, TcpIp and I have bbs code to run with it for
Unix Sys V and Berkely).

-Jim Durham, W2XO   ([e-mail])
        Just Because I'm Paranoid
        Doesn't Mean
        They're not Picking on Me!

>
>
>
>
>

------------------------------

Date: 21 May 91 16:54:06 GMT
From: casbah.acns.nwu.edu!zaphod.mps.ohio-state.edu!usc!elroy.jpl.nasa.gov!grian!puffin!wd6ehr.ampr.org![e-mail]
Subject: PACKET->Internet Gateway
To: [e-mail]

In message <[e-mail]> you write:
>
> Organization: San Diego State University Computing Services
>
> Don't know if the other message/article was posted here, so I'll request
> again.
>
> Does anyone know if a PACKET (either AX.25 and/or TCP/IP) gateway exists
> between PACKET radio and Internet?  If so, could someone please state
> where it is located?

We have a sort of gateway here in Los Angeles on the duplex packet
repeater on 146.745 -600; k6jrr-3 [44.16.0.74], also n6are [44.16.0.81].
Pete feeds some of rec.radio.amateur.packet, tcpgroup, and hs-modem
stuff, as long as it's proper for ham radio.  Julian excerpts whatever
he finds interesting and passes it along.  Both will pass along mail
to the Internet from .ampr.org.

> If not, why has this not been performed?  Additionally, what would
> be needed in getting set up?

Where were you the last several months?  There was a thread that looked
like one of the suspension cables for the Golden Gate bridge!

Quick summary: If unsupervised, there are legal problems because:
 1. non-amateurs would be permitted unsupervised access to amateur
    spectrum;
 2. stuff that's OK on the internet (cusswords, business, etc) is
    NOT OK on ham; and
 3. a lot of other petty (IMHO) details.

A _supervised_ feed either way is OK.

 Yours,
  _ _ _             __
 ' ) ) )   /       /  )        _/_
  / / / o /_  _   /    . . __  /  o _
 / ' (_<_/ <_(/_ (__/ (_/_/ (_<__<_/_)_

 wd6ehr@n6yn.#soca.ca.usa            [e-mail] [44.16.0.21]
 wd6ehr.ampr.org![e-mail]                Compu$erve 73240,3523
 7921 Wilkinson Avenue; North Hollywood CA USA 91605-2210 [phone]
 -----------------------------------------------------------------------

------------------------------

Date: 22 May 91 00:30:54 GMT
From: tut.cis.ohio-state.edu!cis.ohio-state.edu!zaphod.mps.ohio-state.edu!menudo.uh.edu!nuchat!farwest![e-mail]
Subject: PACKET->Internet Gateway
To: [e-mail]

Organization: San Diego State University Computing Services

Don't know if the other message/article was posted here, so I'll request again.
Does anyone know if a PACKET (either AX.25 and/or TCP/IP) gatewaye exists
between PACKET radio and Internet?  If so, could someone please state where it
is located?  If not, why has this not been performed?  Additionally, what would
be needed in getting set up?

Robert S. Radvanovsky, KC6ONL
,


 * Origin: Two Wheelers  bikie hangout (1:106/88.0)

------------------------------

Date: 23 May 91 19:07:18 GMT
From: photon![e-mail]
Subject: PACKET->Internet Gateway
To: [e-mail]

In article <[e-mail]>, [e-mail] (Robert S. Radvanovsky KC6ONL) writes:
|> Organization: San Diego State University Computing Services
|>
|> Don't know if the other message/article was posted here, so I'll request again.
|> Does anyone know if a PACKET (either AX.25 and/or TCP/IP) gatewaye exists
|> between PACKET radio and Internet?  If so, could someone please state where it
|> is located?  If not, why has this not been performed?  Additionally, what would
|> be needed in getting set up?
|>
|> Robert S. Radvanovsky, KC6ONL
|> ,
|>
|>
|>  * Origin: Two Wheelers  bikie hangout (1:106/88.0)
First, get a lawyer; second, get two copies of Part 97, one for you and one for
him.  The problem with gateways is one of legalities as regards the FCC and
their parochial views.
73s
--
Kurt Freiberger, wb5bbw   [e-mail]   409/847-8706
Dept. of Computer Science, Texas A&M University  DoD #264
*** Not an official document of Texas A&M University ***

------------------------------

Date: 24 May 91 04:30:42 GMT
From: swrinde!zaphod.mps.ohio-state.edu!caen!news.cs.indiana.edu!ux1.cso.uiuc.edu![e-mail]
Subject: Proposed SoCal 220 MHz bandplan revision
To: [e-mail]

[e-mail] (Barry McLarnon) writes:

>>222.000 - 222.025     EME
>>222.025 - 222.160     CW/SSB/ACSB/AM
>>222.180 - 223.380     Duplex pair inputs
>>223.400 - 223.580     FM Voice Simplex
>>223.600 - 223.760     Digital
>>223.780 - 224.980     Duplex pair outputs
>>      "61 20 KHz Duplex pairs"
>>      "Control Channels at Odd 20 KHz Spacing"

>It may look very good from a SoCal point of view, but I sure hope this
>plan, or something similar, doesn't get foisted on the rest of the
>continent.  I just can't muster up any enthusiasm for a VHF/UHF bandplan
>that allots a paltry 6% of the band to digital modes.  I know that the

There was a suggested plan published in QST that looks much better to me
for national purposes.  Local and regional needs, of course, still make
it necessary to make adjustments for their purpose.  I just wish that the
process for a national plan had moved faster so that those making the
decisions on local variations would have some insight into the potential
impact with regard to nearby and mobile operations.

There is still a severe problem in the communication of local and regional
bandplans to those that genuinely want to know what they are.

There is a chance I might be in SoCal next month, and if I cannot get a
copy of the local bandplan by the time I get their, I will be operating
under the ARRL national plan, with the usual avoidance of interference
when that becomes known, until such time as the local plan is made
available.

>repeater pairs can be used for digital operation, but I think this plan is
>really inadequate as far as wideband digital operation is concerned.  This
>apparently stems from a rather miserly allotment of only two 100 KHz
>channels in the previous SoCal bandplan, despite the fact that the ARRL
>Board approved the allotment of five such channels (at 220.5 - 221.0 MHz)
>in 1987.  In contrast to the SoCal bandplan, the CRRL bandplan for 220-225
>MHz which came out in 1989 recommends a total of 1.6 MHz for digital, all
>but 200 KHz of which could be used for wideband links.  A similarly
>enlightened plan for 222-225 MHz should allot at least 1 MHz for digital.
>This obviously won't happen in densely-populated areas which are already
>chock-a-block with analog FM repeaters and links, but I firmly believe
>that they should not set the pattern for everywhere else.

One might say that in SoCal, there is more FM repeater usage than there
is packet usage.  Possibly it is more a case of the status quo not being
able to move along with the needs of the future, such as has giving packet
a share equal to the FM share when the level of packet usage comes up that
high.

However, the most likely explanation might very well be that in SoCal,
there having been so much band crowding already, that those interested
in doing new and innovative things like high speed packet, have already
moved up to higher frequencies (23cm, 13cm, 9cm, 5cm, 3cm, etc.) in the
first place.  Many are involved in even higher speeds that a 100 kHz
channel could not even handle (such as 10 megabaud on 10 GHz as I have
heard about).  Basically, probably quite a number of hams in SoCal have
simply written off the 2 meter band.

>Then again, there's talk of us losing the *whole* band in Canada, so this
>may all become a moot point.  A look at a recent repeater directory will
>show how sparse 220 use is up here... we need to get more wideband digital
>going on this band, and soon.

The problem is you get your 220 radios from the same dried up source as we
get ours, on the other side of the Pacific.  What is the ratio of 2m radios
to 220 radios you find on the USED market, even if you DON'T count the ones
originally marketed new for commercial uses.

I scrounged the flea market at the Dayton Hamvention for Icom 220 MHz HT's
and found ONE which was an IC-03AT.  I would have bought an IC-3AT had I
found one.  There was a Yaesu one as well.  There were dozens and dozens
of used Icom, Kenwood, and Yaesu 2m HT's for sale in the flea market.
It sure seems that people are hanging on to their 220 MHz radios.
--
 /***************************************************************************\
/ Phil Howard -- KA9WGN -- [e-mail]   |  Guns don't aim guns at  \
\ Lietuva laisva -- Brivu Latviju -- Eesti vabaks  |  people; CRIMINALS do!!  /
 \***************************************************************************/

------------------------------

Date: 23 May 91 04:29:20 GMT
From: [e-mail]
Subject: REMOVE curtis@madnix from mail ist
To: [e-mail]

Please remove curtis@madnix from your mail list. He is no longer active
at this site.

                    Thanks
                    Ray Hill
                    root@madnix

------------------------------

Date: 23 May 91 19:21:47 GMT
From: epic![e-mail]
Subject: Security
To: [e-mail]

In article <[e-mail]>, [e-mail] (Michael Kosowsky) writes:
|>
|> What about the public key cryptographic systems?

Michael,

I recently wrote a fairly lengthy "white paper" to W4RI at ARRL in
response to his call for comments on authentication systems. If there
is sufficient interest I could post it here, but in the meantime I
will give a quick summary.

1. Cryptographic authentication schemes exist, and they can use either
single or dual key cryptography. (DES is a single key cipher; RSA is a
dual key cipher).

2. Single key schemes are practical only in small scale applications,
preferably where the authorized entities all trust each other (e.g.,
remote control of a repeater).

3. Dual key schemes that use certificates for public key distribution
are potentially useful for authenticating packet messages, but these
schemes are quite complex and require *every* amateur to possess
fairly significant (by amateur standards) local computing capability
to execute them. (Consider that many packeteers still use dumb
terminals or C-64 class machines with their TNCs.) The dual-key
cryptography field is tightly locked up in patents. And I won't even
*mention* the user-education problem...

4. Even a technically well-designed dual-key scheme can't deal with
the problem of a user claiming that his secret key had been stolen and
used by someone else to sign prohibited traffic. (Recall that WA3QNS
has claimed that someone else posted the anti-war message under his
call.)

5. And even if a perfect authentication scheme were devised, it would
still not actually *prevent* the retransmission of prohibited traffic
in real time.  Only an AI program far beyond the present state of the
art could do that.  Given that there seems to be 500,000 different
interpretations of just what the no-business rules mean (one for each
ham), it is not exactly clear how one would program such an AI
algorithm.

6. In short, although cryptographic authentication is a promising
technology that is already practical for small scale use (e.g.,
repeater control links) it is simply "not ready for prime time" in the
context of BBS message authentication. It is also a sledgehammer
response to the "problem".

The real problem that needs to be addressed is an utterly inflexible
FCC to whom the notions of "cost effectiveness" and "not throwing out
the baby with the bathwater" are utterly alien.

Phil

------------------------------

Date: 22 May 91 20:31:58 GMT
From: hpl-opus!hpspdra![e-mail]
Subject: Which TNC would you buy?
To: [e-mail]

My email had four recommendations for Kantronics and two for the PK-88.
Kantronics also had one day seminar on packet here this weekend.  Mike
is a very impressive fellow.  Anyone interested in packet would want to
take in the show even if you had no interest in purchasing anything.

Anyway, my order for a KAM is in process.  Thanks to all who responded
on email.
73 AA6PZ

------------------------------

Date: 24 May 91 00:21:48 GMT
From: swrinde!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!pacbell.com!tandem![e-mail]
Subject: Wireless LANs mailing list
To: [e-mail]

There is currently much discussion and publicity about Wireless LANs, their
possible applications, choice of frequency, protocols, etc.  The I.E.E.E 802
committee has established a sub-committee (802.11) to propose a standard
for Wireless LANs.

Wireless LANs pose a unique challenge to the engineer since they represent
a combination of technologies:

    - RF design
    - Propagation and wave physics
    - Data communications
    - Computer engineering
    ...

Few engineers or designers have all these skills in their portfolio; progress
towards Wireless LANs therefore requires teamwork and an open mind to allow
experts in different technologies to contribute and work towards a common goal.

We propose to establish a moderated mailing list to provide a technical forum
for the development of Wireless LANs specifically aimed at data communications
rather than voice.  Our goal in moderating the mailing list is to avoid the
degeneration of the list into a forum for answering users questions such as
"Which Wireless LAN should I choose ?" or "I have this problem, please help !".

Our hope is that the mailing list will provide a forum for the engineering
and design issues associated with all aspects of wireless LANs.

Assuming that the traffic on the mailing list got to a reasonable level we
also propose to gateway the mailing list into a moderated USENET News group.


If you are interested in contributing towards the technical development of
Wireless LANs and support this proposal for a forum, please e-mail to

    [e-mail]

To subscribe to the mailing list, send a mail message to the above address
with the following command in the body of the message at the beginning
of the line.

    add [e-mail] wireless

Help may be obtained from the list server by including the word HELP at the
beginning of the line in an e-mail message.


Stuart Phillips
Kevin Rowett

------------------------------

Date: 23 May 91 19:05:14 GMT
From: photon![e-mail]
To: [e-mail]

References <[e-mail]>, <[e-mail]>, <[e-mail]>
Reply-To : [e-mail] (Kurt Freiberger)
Subject : Re: Time bug in KA9Q, and nntp docs


  The problem exists with NOS 0423 and DRDOS 5.0 on an AT.
73, Kurt

--
Kurt Freiberger, wb5bbw   [e-mail]   409/847-8706
Dept. of Computer Science, Texas A&M University  DoD #264
*** Not an official document of Texas A&M University ***

------------------------------

Date: 23 May 91 14:34:48 GMT
From: usc!samsung!spool.mu.edu!cs.umn.edu!uc!nachos.SSESCO.com![e-mail]
To: [e-mail]

References <[e-mail]>, <[e-mail]>, <[e-mail]>
Subject : Re: Time bug in KA9Q, and nntp docs

In article <[e-mail]> dlf@.UUCP (Dave Fritsche) writes:
>>>        Actually, it is a know (at least around here) bug with MS-DOS.
>MS-DOS v3.2 and earlier will not increment the date at midnight.  It
>doesn't matter how many disk accesses you do, it simply doesn't increment
>the date.  Change to DOS 3.3 or 4.x and the problem will go away.  I've
>been there.
>

Well, I'm starting to believe this is more of a BIOS problem than a DOS
problem.  I have the same exact version of DOS 4.01 (from the same
distribution disks) running on two different machines.  One machine is
a Zenith Z-147 (4.77 Mhz XT clone) and the other is Northgate 386-20
slimline.  If PROCOMM is left running in terminal mode, connected to
a TNC on both machines..   the Zenith will slip days and the Northgate
will not.

An additional test case is an NEC luggable running NCSA telnet (in FTP
server mode) on top of MSDOS 4.01 which also slips days.  The same
software setup on a Zenith Z-248 does not slip.

So, perhaps a closer investigation of BIOS types and versions is in
order...

Chris

--
Chris Elmquist, N0JCF
Internet: [e-mail]
   AMPRN: [e-mail]
   Telco: [phone]

------------------------------

End of Packet-Radio Digest
******************************
Date: Sat, 25 May 91 04:30:08 PDT
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V91 #130
To: packet-radio


Packet-Radio Digest         Sat, 25 May 91       Volume 91 : Issue 130

Today's Topics:
            440/880MHz glass mount antenna
            56K modem info please
           Begining TCPIP troubles...Help!
                DieBOX
      MBBIOS (Communications handler) V3.5 is available
           radio shack dx-440 mods (2 msgs)
              Time bug in KA9Q v 910423

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

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: 23 May 91 22:01:17 GMT
From: spectr![e-mail]
Subject: 440/880MHz glass mount antenna
To: [e-mail]

I'm looking for any information on a glass mounted antenna that
would cover 440MHz and the 880MHz (cellular) bands.

I figure that a 1/4 wave 440MHz whip may load on 880MHz with a bit of
help, (i.e. matching network) but one of my friends tells me "no way".
(Or how about a 1/2 wave 440 whip?)

I don't want to stick more than one antenna on the car, drilling a
hole is out of the question (would you on a Porsche?) and mag mounts are
a pain in the neck.

Does anyone know of such an antenna? Or how I could maybe MAKE one
(load) on both bands?
I have some data on making single band antennas from a neat article in
the April/91 issue of QST p.31 by Bill English, N6TIW, but I'm hoping
someone out there will help me out on my quest!!!

If you can, please respond direct to me and I'll summarize and post if
there is interest....Thanks...73s
----------------------------------------------------------------------------
Joe Alonso  VE2UNX     |        Spectrom Consultants Inc.        |  S. C. O.
joe@spectr 76064.2505  | 425 St.Paul E. Mtl. QC,CANADA, H2Y 1H5  | Education
uunet!spectr!joe       |(514) 849-UNIX (8649) fax [phone] |  Centre

------------------------------

Date: 24 May 91 10:31:27 GMT
From: mcsun!ukc!edcastle!hwcs![e-mail]
Subject: 56K modem info please
To: [e-mail]

Hi, thanks for reading this and hope you can help..

I read an article (rather dated tho) in CQ a while back which said
an organistaion called GRAPES had produced a kit for a 56K modem for
use with a tranverter onto 70cms.

Being just about to graduate later in july and having some spare time
I would like to try and build one for experimentation purposes in the
EDINBURGH area over the summer vac.

Can anyone give me address/details/prices or any more info about higher
speed packet systems I`m getting bored with TCPIP on 1200 around here...

Thanks

Robin Alexander GM4YED

internet [e-mail]
ampr     [e-mail]

------------------------------

Date: 24 May 91 15:14:15 GMT
From: epic![e-mail]
Subject: Begining TCPIP troubles...Help!
To: [e-mail]

In article <[e-mail]> [e-mail] (Feroz Ghouse 4S7FG/WU9N) writes:
>I am attempting to start some TCPIP activity in the local area. I DL'd a
>copy of the NET dated 4-23-91. The problem I have is that the documentation I
>have found does jive with this version of the NET. I have discovered the many
>variants of of TCPIP that are around that confuse me even more.
>My questions are:
>1. Is there documentation for this version and is this version any different
>   to the others around.

The "base" documentation is in /pub/ka9q/docs/ka9qnos.* (there are three
versions, nroff, postscript and plain text). Although it needs a little
updating, it is fairly accurate for the 0423 version; the main differences
are a few new features (like the "encap" interface) that I haven't documented
up yet. If you don't use the new features, then you won't have any problem...

>2. If this version has no documentation, what version is recommended for use;
>   especially if on wants to turn the MBOX on and have some BBS activity on AX25

There's a mailbox in my "base" code (the stuff in /pub/ka9q/nos).

>3. How do I turn the MBOX ON in this version of the NET and how do I get it
>   to send a banner to a connecting station (on AX25) just like the beginners
>   guide says.

If you mean "why doesn't it say anything right after I connect", this is
a deliberate feature. AX.25 doesn't specify the upper-layer protocol to
be used during the connect establishment, so there's no way to know if you
really want the mailbox, or if you just want to pass IP or NET/ROM datagrams.
By waiting until the user enters an empty line, you can tell for sure that
he wants the mailbox.

BTW, SM0RGV is the author of the mailbox code. I don't support it directly.

>4. What about the versions hacked by PA0GRI and G1EMM? Are these the versions
>   that include all the bells and whistles and hence the ones to uses. I'd like
>   to know the differences.
>

The PA0GRI and G1EMM versions are also on thumper in /pub/ka9q/pa0gri and
/pub/ka9q/g1emm. Please note that I don't support these; I simply provide
space for their redistribution.

Phil

------------------------------

Date: 24 May 91 13:05:51 GMT
From: mcsun!ukc!pyrltd!root44!praxis!praxis![e-mail]
Subject: DieBOX
To: [e-mail]

Hello All,

I've seen a number of German and Dutch BBSes using the DieBOX program.

Does anyone have any details ?

Thanks & 73,

Mike
****
.............................................................................
|                                                | Michael Chace            |
| e-mail   :  [e-mail]                 | PraXis Systems           |
|                                                | Manvers Street           |
| AMPRNET:  [e-mail]   [44.131.20.3] | Bath,  Avon              |
| AX.25  :  G6DHU @ G6DHU-2 or G6DHU @ GB7IMB    | BA1 1PX           UK     |
| Phone  :  (44) [0]225 444700                   |                          |
.............................................................................

------------------------------

Date: 25 May 91 00:09:32 GMT
From: [e-mail]
Subject: MBBIOS (Communications handler) V3.5 is available
To: [e-mail]

I have uploaded MBBIOS V3.5 to tomcat.gsfc.nasa.gov.  New features
are:
  - 16550A UART support for FIFO buffering
  - DesqView wait
  - Improved break handler

The latter two were done by N2GTE and just fitted in by me.

Source code will follow in a few days.

Roy, AA4RE

------------------------------

Date: 24 May 91 21:08:01 GMT
From: hub.ucsb.edu!ucsbuxa![e-mail]
Subject: radio shack dx-440 mods
To: [e-mail]

I would like to modify the if stage bandwidth filter of the
radio shack dx-440 from the stock 5khz to 500 hz for ssb use.
any suggestions would be appreciated.

------------------------------

Date: 24 May 91 21:13:45 GMT
From: hub.ucsb.edu!ucsbuxa![e-mail]
Subject: radio shack dx-440 mods
To: [e-mail]

I am interested in modifying the if stage bandwidth filter oi/ of
the radio shack dx-440 from the stock 5khz to 500 hz for ssb use.
any suggestions would be appreciated.
:

------------------------------

Date: 24 May 91 16:24:03 GMT
From: epic![e-mail]
Subject: Time bug in KA9Q v 910423
To: [e-mail]

In article <[e-mail]> [e-mail] (Tom Thompson) writes:
>    (1) replace the INT 1A call in NET with fetching the tick
>        count from BIOS data area (with ints off since long fetches
>        not indivisible):
>        cli(); ticks = *(long far *) 0x40006cL; sti();

Tom,

Many thanks for the suggestion. With some minor variations I'm making
this change to the code right now. After initial testing I will upload
the new version to thumper.bellcore.com in /pub/ka9q/nos. Hopefully
this will fix the problem.

I hate making absolute references to data variables like this, but the
brain-damaged BIOS time function leaves me with no choice. The Turbo-C
biostime() function I had been using simply called the BIOS INT 1A
AH=0 function directly, ignoring the midnight rollover flag. I guess
they figured no sane user would be calling it so frequently that he
would be likely to be the first caller after midnight (before DOS gets
a chance to update the date).

Phil

------------------------------

End of Packet-Radio Digest
******************************
Date: Sun, 26 May 91 04:30:05 PDT
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V91 #131
To: packet-radio


Packet-Radio Digest         Sun, 26 May 91       Volume 91 : Issue 131

Today's Topics:
            Looking for W0RLI BBS software
               Mac IIcx system for sale
               PACKET->Internet Gateway
            TurboGrafx-16 system for sale
                 Weather Maps

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

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: 24 May 91 17:51:16 GMT
From: nosc!dog.ee.lbl.gov!hellgate.utah.edu!caen!sdd.hp.com!mips!apple![e-mail]
Subject: Looking for W0RLI BBS software
To: [e-mail]

In article <[e-mail]> [e-mail] (Jim Durham) writes:

>First, I believe Hank no longer will release source code. The last
>C code for W0RLI might be gotten from VE3GYQ, Dave Toth, who was
>the last person to work on it and that was way back at version 6.

:( :( :(

>Several years ago I ported W0RLI to Sys V Unix. It isn't a wonderful
>thing because , being a PC program, it is a big loop and uses CPU
>cycles even when not running, but I may be able to scare up the
>source. I believe others have done this also.  The version I ported
>was 2.something, which is pretty old now, but the I/O is the main
>thing and it will probably work with newer code. You are welcome
>to it if I can find it.

For me, the main thing is the backbone connectivity.  What I want to do is
to make the thing run under XENIX/UNIX, taking advantage of the streams
capability of most TNCs.  That way, I can support 10 different users on
the BBS at one time.

>A better solution is to run KA9Q 'net' using KISS tncs which gives
>you AX25, Net/Rom, TcpIp and I have bbs code to run with it for
>Unix Sys V and Berkely).

Well, maybe, but how many folks out there are running net as opposed to W0RLI?
--
Ed Carp  N7EKG/6        [e-mail]         ...uunet!khijol!erc
Packet:  N7EKG @ N6IIU.#NOCAL.CA.US
UUWEST Consulting       Alameda, CA             415/814-0550

Computers HAVE caused a revolution in how much information we
can safely ignore!    [e-mail] (Rob Schaeffer)

-- Absolutely unabashed Gates McFadden groupie! --

------------------------------

Date: 25 May 91 00:30:42 GMT
From: casbah.acns.nwu.edu!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!dali.cs.montana.edu!milton![e-mail]
Subject: Mac IIcx system for sale
To: [e-mail]

Posted for a friend (do not reply to this account)

Mac IIcx system
5 Mb
40 Mb hard drive
Mac RGB monitor

$3000 obo

call Clint [phone]

------------------------------

Date: 24 May 91 02:10:19 GMT
From: nuchat!farwest![e-mail]
Subject: PACKET->Internet Gateway
To: [e-mail]

Organization: San Diego State University Computing Services

Don't know if the other message/article was posted here, so I'll request again.
Does anyone know if a PACKET (either AX.25 and/or TCP/IP) gatewaye exists
between PACKET radio and Internet?  If so, could someone please state where it
is located?  If not, why has this not been performed?  Additionally, what would
be needed in getting set up?

Robert S. Radvanovsky, KC6ONL
t


 * Origin: Two Wheelers  bikie hangout (1:106/88.0)

------------------------------

Date: 25 May 91 00:29:00 GMT
From: think.com!rpi!dali.cs.montana.edu!milton![e-mail]
Subject: TurboGrafx-16 system for sale
To: [e-mail]

TurboGrafx-16 for sale:

  - TurboGrafx-16 base unit
  - TurboBooster stereo/direct video adaptor
  - TurboTap joystick splitter (allows 5 players)
  - TurboStick joystick
  - 2 TurboPad controllers

  - carts:

    Alien Crush
    Blazing Lazers
    Bonk's Adventure
    China Warrior

    Double Dungeons
    Dungeon Explorer
    Galaga '90
    Keith Courage in Alpha Zones

    Legendary Axe
    Military Maddess
    Ordyne
    Splatterhouse

    TV Sports Football
    Victory Run

Retail price over $720, sell for $450 obo

Steve Skrzyniarz  ([e-mail])

------------------------------

Date: 24 May 91 15:48:40 GMT
From: nosc!dog.ee.lbl.gov!hellgate.utah.edu!caen!zaphod.mps.ohio-state.edu!wuarchive!emory!wa4mei!ke4zv![e-mail]
Subject: Weather Maps
To: [e-mail]

In article <[e-mail]> [e-mail] (John McLaughlin) writes:
>I have what (I hope) is a pretty simple request.  What I basically
>want to do is to recieve weather sattelite images onto an IBM-PC type
>machine.  Although I have a pretty fair EE background I don't have much
>experience with amateur radio.  Basically what I want is the cheapest
>hardware solution that will get the job done.  I have access to a
>(recieve only) SW radio that I can use as a reciever.  Do I have to buy
>a packet controller? (Someone recommended a 'packrat' which runs about
>$300 and hooks up the serial port.  Although I think this will get the
>job done it seems like overkill as this box appears to be able to both
>transmit and recieve a number of digital formats including Weather maps)

Unfortunately for the Packratt PK-232, weather pix aren't transmitted
in digital format. The PK-232 modem is only a binary slicer and will
give you a grey scale consisting of black and white. This is fine for
maps, but is sorely lacking for satellite images. It does have the
advantage of already having firmware on board to put the map in a
format that their software can display on the PC. It's also good for
RTTY and Packet work. It also may have been upgraded since I got mine.
MFJ has a box called the 1278 that does packet, RTTY, and supposedly
greyscale weather fax. I haven't used one.

>I guess my basica problem Is I don't know where to go from here.  I am willing
>(actually prefer) to write my own software, I am just not aware what the
>minimum hardware requirements are and how to get started.  Can anyone point
>me in the right direciton?  Any publications/books which might help?

The Weather Satellite Handbook (ARRL) is your best choice. The grey
scale is encoded using tone encoding with something like 1200 hz to
1800 hz being used to encode from sync to peak white. Using a simple
zero crossing detector kicking a spare LPT interrupt and a little assembly
coding on the PC, you should be able to decode the tone pitches to greyscale
values. More elaborate schemes would probably work better on noisey signals.

Gary KE4ZV

------------------------------

Date: 25 May 91 23:22:56 GMT
From: uvaarpa!murdoch!turing![e-mail]
To: [e-mail]

References <[e-mail]>, <[e-mail]>, <[e-mail]>
Subject : Re: Time bug in KA9Q, and nntp docs

In article <[e-mail]> [e-mail] (Kurt Freiberger) writes:
>
>  The problem exists with NOS 0423 and DRDOS 5.0 on an AT.
>73, Kurt

People, this is a very very well known bug (or feature) and is a BIOS level
thing. Might want to check out the PC newsfroups from time to time, it'll
save ya lots of time re-inventing the wheel.

--
______
\ OO / Mr. Jeffersons Academical Village
 \++/  Terrestrial Coordinates: 38 04 06N / 79 03 53W
  \/   Sic Semper Tyrannus

------------------------------

End of Packet-Radio Digest
******************************
Date: Mon, 27 May 91 04:30:07 PDT
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V91 #132
To: packet-radio


Packet-Radio Digest         Mon, 27 May 91       Volume 91 : Issue 132

Today's Topics:
            need info on "wireless modem"

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

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: 26 May 91 07:03:18 GMT
From: orion.oac.uci.edu!ucivax!jarthur!elroy.jpl.nasa.gov!swrinde!zaphod.mps.ohio-state.edu!ncar!unmvax!bbx!yenta![e-mail]
Subject: need info on "wireless modem"
To: [e-mail]

Halp!  I just bought 4 NIFTY gadgets (at a surplus auction), and I'm trying
to get them working with no documentation whatever.

The unit in question is a "wireless modem" which puts out a solid 1/2 W (VHF)
and has high quality, separately tuned (with dip switches), PLL-synthesized
transmitter and receiver sections.  It has an rs-232 port and an antena jack
in the back, and tx/rx leds in the front.

To be more specific, the unit is an "ESTeem wireless modem, model 84" by
Electronic Systems Technology (no address or phone numbers appear anywhere
on product).  I don't think they made too many of these ... one of the ones
I have is serial number 40!

If anybody has any suggestions regarding:
    how to locate the manufacturer
    how to reverse-engineer this thing enough to figure it out
please email.  If you post a response, please only post where appropriate.
This article is crossposted.

Please, no flames from hams about it probably being illegal to put these
thingies on the air.  I'm only interested in the technical exercise of
getting them working with dummy loads.  I'm a licensed ham operator and I
know the laws.  Flame-retardant off.  :-)

                        little david
--
Unix is not your mother.

------------------------------

End of Packet-Radio Digest
******************************
Date: Tue, 28 May 91 04:30:07 PDT
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V91 #133
To: packet-radio


Packet-Radio Digest         Tue, 28 May 91       Volume 91 : Issue 133

Today's Topics:
               Amateurs on the Network
           Looking for W0RLI BBS software.
          PACKET->Internet Gateway (2 msgs)
             PC CUA Interface for Packet?
              Problems with NOS

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

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: 27 May 91 22:53:11 GMT
From: swrinde!mips!atha!aunro!ve6mgs![e-mail]
Subject: Amateurs on the Network
To: [e-mail]

We are all famous for 15 minutes, so here is your chance I guess :-). I
have been running an (ASCII to TNC, UNIX V7) Packet Radio<--->USENET
gateway (mail and news). Anyways, many of the articles that I receive here in
rec.radio groups are passed on to the local MSYS BBS. To help much of the manual
effort, I ended up maintaining an ever expanding list of Amateurs that
post to Usenet. This list is used to place the call of the poster at the
beginning of the subject line as the articles are posted to the packet board.
This list is by NO MEANS complete. Enjoy (I hope).

Ciao, 73 de VE6MGS/Mark -sk-
-------------------------- Cut Here ------------------------------------
[e-mail]            dc0hk   Barry Titmarsh
[e-mail]              dl6rai  Bernhard Buettner
[e-mail]                                   ei2amb  David B. A. Tocher
[e-mail]                          ei9gl   Paul Healy
[e-mail]                      fe6cnb
[e-mail]                   g0cnr   Hugh Davies
[e-mail]                             g1lyx   Nick Bristow
[e-mail]                           g1nna   Bob D. Lloyd
[e-mail]                             gm4byf  Peter J Bates
[e-mail]                          gm4wzp  James Gentles
[e-mail]                       gm4znx  David Stockton
[e-mail]                g6wbj   Pete J. M. Lucas
lee@tosspot                                     g8lck   Lee Reynolds
[e-mail]          gi8oya  Steve McKinty
[e-mail]                              ik5pvx  Pierfrancesco Caci
[e-mail]                              ik5pvx  Pierfrancesco Caci
[e-mail]                          kb0agd  Steve Schallehn
[e-mail]                             kf0ca   Perry Scott
[e-mail]                 wa0cqg  Carl A. Estey
[e-mail]                                 kb0cy   Bob A. Witte
[e-mail]                           k0gu    Jay A. Kesterson
[e-mail]                         n0kcl   Paul Bame
[e-mail]                          n0laj   William R. Hester
[e-mail]                           n0nkg   Jim Hughes
[e-mail]                         kf0ou
[e-mail]                                 w0pbv   Myron A. Calhoun
[e-mail]                              wb0qna  Ken Gianino
[e-mail]                 w0rij   Jack R. Sargeant
[e-mail]                        wa0vnh  Michael Foerster
[e-mail]                              wb0zrd  Paul Anderson
[e-mail]                            n1al    Alan R. Bloom
[e-mail]                     ka1axy  Peter Z. Simpson
[e-mail]                       n1brm   Bob B. Gettys III
[e-mail]                        n1bwt   Paul Wade
[e-mail]                       ad1c    Jim J. Reisert
[e-mail]           ka1cv   Ed Hare
[e-mail]                      ni1d    Paul Koning
[e-mail]                              n1dje   Mike Weihman
[e-mail]                                 ka1eec  Eric S Johansson
[e-mail]                            w1gsl   Steven L. Finberg
[e-mail]                     n1ikv   Bruce Walker
[e-mail]                        n1ipe   John Keyes
[e-mail]                       nt1l    Don Koch
[e-mail]                          wa1lbp  David Cowhig
W1OJ@KA1SRD                                     w1oj    Dean R. Perkins
[e-mail]                              w1oj    Dean R. Perkins
[e-mail]                                wa1omm  Paul F. MacDonald
[e-mail]                                wq1r    Jack Bonn
[e-mail]                             kb1rt   Dan Halbert
[e-mail]                      nu1s    Bernie
[e-mail]                         ka1sna  Jay Appell
[e-mail]                       kc1td   Teahan Taber
[e-mail]                         ka1utu  John L Luigi Giasi
[e-mail]                         wa1uxa  Eugene W. Balinski
[e-mail]                      wm1w    William J. Szarek
[e-mail]                ka1wnu  Scott Ehrlich
[e-mail]                      w1xo    Ted Zateslo
[e-mail]                            kc1yr   Sharon Machlis Gartenberg
[e-mail]                               n2aam   Dave Marthouse
[e-mail]                         k2anc
[e-mail]                               kd2bd   John A. Magliacane
[e-mail]                          k2bt    Forrest E. Gehrke
[e-mail]                               n2dxn   Bob M. Meyer
[e-mail]                             n2dsy   Gordon Beattie Jr       206 N Vivyen St. Bergenfield NJ 07621
[e-mail]                           n2dsy   J. Gordon Beattie       206 N Vivyen St. Bergenfield NJ 07621
[e-mail]                           kb2gcg  Jerry
[e-mail]                       kb2glo  Thomas Kenny
[e-mail]                                  wb2goh  Edward W. Greenberg
[e-mail]                       wa2ise  Robert F. Casey
[e-mail]                           wb2jbs  Richard Harel
[e-mail]                      n2jpg   Meir Green
[e-mail]                            nd2k    Alfred A. Schwarz
[e-mail]                          n2luh   Andrew "Bud" Beers
[e-mail]                   n2lyc   Rajesh Babani
[e-mail]  kb2lzf  Donald L. Schleede
[e-mail]  kb2lzf  Donald L. Schleede
[e-mail]                            k2ph    Robert A. Schreibmaier
[e-mail]                     ka2rc   Roland
[e-mail]                    ka2rxo  Steve E. Goldsmith
[e-mail]                               wa2srq  Ed Gilbert
perley@galaxy                                   ke2tp   Donald P Perley
[e-mail]                               k2unk   W. H. Sohl
[e-mail]                      wf2v    Leonard J. Popyack
[e-mail]                              wg2w    Chris Peckham
[e-mail]                             k2wk    Walter Kornienko
[e-mail]                           kz2x    Robert A. Wilgus
uunet!w2xo.pgh.pa.us!durham                     w2xo    Jim C. Durham
[e-mail]                           w2xo    Jim C. Durham
[e-mail]                               kc2yu   Joseph R. Skoler
[e-mail]                           ka2zlz  Darrin B. Jewell
[e-mail]                        w3bnr   Ed A. Naratil
[e-mail]                            ka3brz  Brian D. Cuthie
WA3CAQ@WA3CAQ.#SOCA.CA.USA.NA.AMPR.ORG          wa3caq  Joe
[e-mail]                        nu3e    John DeGood
uunet!col.hp.com!bdale                          n3eua   Bdale Garbee
[e-mail]                           ak3f    Michael B. Hayden
[e-mail]                            ny3f    Matthew A. Parker
[e-mail]                        kd3fu   Paul W. Schleck
[e-mail]                                wa3fyz  E. Allen Brown
[e-mail]              w3grg   Steve R. Mosier
[e-mail]           w3grg   Steve R. Mosier
[e-mail]                     n3hbz   Jeff DePolo
[e-mail]                         n3ie    Joseph M. Fedoch
[e-mail]                        n3iru   Paul S Masters
[e-mail]                              wa3jpg  Clark Turner
[e-mail]                        wa3jpy  Mark G. Bitterlich
albers@ka3ovk                                   ka3ovk  Jon P. Alber
[e-mail]       w3ph    Paul R. Heller III
[e-mail]                                    km3t    Dave H. Pascoe
[e-mail]                            wa3tbl  Harry P. Bloomberg
[e-mail]                            wa3tld  Paul J. Dujmich
[e-mail]                                 k3tx    Dave Heller
[e-mail]                               wa3uqv  Chuck F. Harris
[e-mail]                          w3vs    Scott J. Loftesness
[e-mail]          ke3z    Jon Bloom
[e-mail]                       nr3z    M. Squicciarini
[e-mail]                                 km4ba   Alan Barrow
[e-mail]                             kn4bs   Mike Gingell
[e-mail]                             kn4bs   Mike Gingell
[e-mail]                            wa4dut  Steve Pazar
[e-mail]                  wb4ehs  Bob Lombardi
[e-mail]                              n4flz   Harold G. Peach Jr
[e-mail]                                 n4hy    Robert W. McGwier Jr
[e-mail]                      aa4mw   Mike A. Waters
[e-mail]                    wb4npl  James Harvey Hobson Jr
[e-mail]                            n4oju   Ross F. Wilder
[e-mail]                            aa4re   Roy Engehausen
[e-mail]                            w6hir   Roy Engehausen
[e-mail]                            w6hir   Roy Engehausen
Tim=J.=[e-mail]     ki4tg   Jim J. Madden
[e-mail]                      kn4ty   Mike Dante
[e-mail]                       kf4vb   Sonny Johnson
[e-mail]                        kc4vjo  John Mayson
[e-mail]                          wa4vzq  Barry L. Ornitz
[e-mail]                             n4wmt   Butch Young
[e-mail]                           n4xhx   Mark J. Brader
[e-mail]                                n4yos   Tom Thompson
[e-mail]                                 ke4zv   Gary R. Coffman
[e-mail]                wb5agf
[e-mail]                            wb5bbw  Kurt Freiberger
[e-mail]                        ka5bou  Craig S. Young
[e-mail]                                 aa5bt   Derek Wills
[e-mail]                             kk5d    David F. Reed
[e-mail]                          wb5fkh  Bruce Borrows
[e-mail]            n5gna   Bob I. Plested
[e-mail]     wb5itt  Christopher W. Boone
[e-mail]                           wd5ivd  James Greg Jones
[e-mail]                                  n5knx   Dugal James P.
[e-mail]                     n5pee   John Stankus
[e-mail]                        n5qvi   Jordan Kossack
[e-mail]                                  k5qwb   Lyn R. Kennedy
[e-mail]                          k5qwb   Lyn R. Kennedy
[e-mail]                              n5rck   Ed Humphries
[e-mail]                            wa5rpf  Steven L. Farmer
[e-mail]                       k5ryk
[e-mail]                               n5x     James C Mankin
[e-mail]                k5zc    Jay R. Maynard III
[e-mail]                k5zc    Jay R. Maynard III
[e-mail]                           nj6a    Jerry Gardner
[e-mail]                        aa6ad   Bruno Bienenfeld
[e-mail]                             wa6azp  Ralph Alan Larson
[e-mail]                     ah6b    Antonio Querubin
[e-mail]                                n6bis   Patty Winter
[e-mail]                             ki6cq   Paul J. Brewer
[e-mail]                      wa6cre  Everett F. Batey
[e-mail]          kb6csp  Wayne A. Lightsey
brian@ucsd                                      wb6cyt  Brian H. Kantor
[e-mail]                          wd6ehr  Mike Curtis
[e-mail]                            aa6er   Tenney
[e-mail]                           n6gn    Glenn E. Elmore
[e-mail]                        n6gn    Glenn E. Elmore
[e-mail]                              wa6ifi  Dave R. Novotny
[e-mail]                                  kk6jq   Dana H. Myers
[e-mail]                    ka6jrg  Cliff K. Yamamoto
[e-mail]                           kb6jxt  Todd C. Jonz
[e-mail]                       n6kk    Joseph Barger
[e-mail]                                  aa6kx   Bruce B. Sawyer
[e-mail]                             n6ltj   David Ollie Eisman
[e-mail]                              n6lxa   Geoffrey G. Baehr
[e-mail]                           wa6mbv  James R. Duncan Jr
[e-mail]                            n6mwc   Phil J. Keller
[e-mail]                      kb6ooc  Gerald J. Walsh
[e-mail]                             aa6pn   Richard Currier
[e-mail]                       n6pyf   Eric Struble
[e-mail]        kh6r    Norman Funamura
[e-mail]                        n6rk    Rick K. Karlquist
[e-mail]                               wb6rqn  Brian Lloyd
[e-mail]                        wa6sdm  Jim Hollenback
[e-mail]                             n6sjd   Ross Wille
[e-mail]                        aa6sq   Chris Thomas
[e-mail]                    kc6sss  Andrew Scott Beals
[e-mail]                                  n6tfx
[e-mail]                                 n6tqs   Doug Faunt
[e-mail]                           kc6txz  Dan Pritchett
[e-mail]                                 aa6ty   Kok Chen
[e-mail]                                n6tyg   Tony Bamberger
[e-mail]                         n6uok   goh kawai
[e-mail]                  kc6upu  Brett Breitwieser
[e-mail]                            kn6w    Edwin Randy Cole
[e-mail]              w6wtu   Hugh E Wells
[e-mail]                            k6xo    Alan Brubaker
[e-mail]                              kk6yb   Gary Morris
[e-mail]                      nh6yk   Ted
[e-mail]                        ke6ze   David Engle
[e-mail]                                 n6zfx   Jeff Crilly
[e-mail]                           n6zfx   Jeff Crilly
[e-mail]                      nm7b    Collier Chun
[e-mail]    wl7bil  Herb Holeman
[e-mail]                        aa7bq   Fred Lloyd
[e-mail]                                   nj7e    John Moore
[e-mail]                            nj7e    John Moore
[e-mail]                                     wb7eel  John F. Woods
[e-mail]                                   n7ekg   Ed Carp
[e-mail]                              kl7glk  Larry Jack
[e-mail]                            kb7gud  Peter John Skelly
[e-mail]                                    kt7h    Tad Cook
[e-mail]                       k7hdk   Ron Stillinger
[e-mail]                               n7ikq   Rusty Carruth
[e-mail]                              k7itm   Tom Bruhns
[e-mail]                     kl7jdq  Brian P. Crawford
[e-mail]                          kl7jl   John R Stannard
[e-mail]                        n7kcg   Robert Giden
[e-mail]                                   wa7kgx  Chuck Forsberg
[e-mail]                          kx7l    Charlie Panek
[e-mail]                         wa7nwp  Bill Vodall
[e-mail]                                n7pex   Dale Mosby
[e-mail]                             n7qnm   Clay Jackson
[e-mail]                                  n7rcx   Mark Zenier
[e-mail]                             n7rcx   Mark Zenier
[e-mail]                                  ws7s    Tom Kloos
[e-mail]                      wa7skg  Michael A. Barnes
[e-mail]                         wb7tza  Jeff Later
[e-mail]                              kd7uw   John Hays
[e-mail]                      ka7wvv  Andre Molyneux
[e-mail]                        kb8cne  Brad Banko
gws                                             n8emr   Gary Sanders
[e-mail]                                  n8emr   Gary Sanders
[e-mail]                                wb8eoh  Gary Bourgois
[e-mail]                               w8erd   Bob Dixon
[e-mail]                        n8hsc
[e-mail]                              kf8nh   Brandon S. Allbery
[e-mail]                     n8kei   Andrew Payne
[e-mail]                     n8kei   Andrew Payne
[e-mail]                    kc8l    Richard Tyo
[e-mail]                       n8oef   Val Breault
[e-mail]                        wb8vnv  Ted Morris
[e-mail]                            kx8x    Quentin Schultze
[e-mail]                         ad8y    Kazdan
[e-mail]                        ke8yy   Mike Edelman
[e-mail]                  wa8zhn  Jim MacMillan
[e-mail]                        k9ald   Roger Taylor
[e-mail]                           n9cgd   Tom Doligalski
[e-mail]                          kb9ffk  Charley Kline
[e-mail]                       n9fzx   Paul Flaherty
[e-mail]   w9ip    Michael Owen
William=E.=[e-mail]       wb9ivr  Willian E. Newkirk
[e-mail]                         n9iyj   Peter Fales
[e-mail]                  n9kdf   dan dreyer
[e-mail]                           wd8kpz  Mike Pflueger
[e-mail]                               n9kut   Bob Crockett
[e-mail]                              kd9kx
[e-mail]                  w9mkv
[e-mail]                       kd9nl   Tom Mann
[e-mail]                    wb9omc  Duane P Mantick
[e-mail]                          ka9q    Phil R. Karn
karn@epic..bellcore.com                         ka9q    Phil R. Karn
[e-mail]                         aj9s    Bob Parnass
[e-mail]                   wx9t    Peter B. Hayward
[e-mail]                   ke9tv   Kevin B. Kenny
[e-mail]                            wb9vgj  John L Broughton
[e-mail]                           ka9wgn  Phil Howard
[e-mail]                       w9wi    Doug Smith
[e-mail]                         ke9zm   Gary Buchholz
[e-mail]                              oh3bk   Pentti Gr|nlund
[e-mail]                               oh3nwq  Tervo Vesa
[e-mail]                                   oh5lfm  Kauto Huopio
[e-mail]                              oh8nup  Ari Husa
[e-mail]                             oh8nup  Ari Husa
[e-mail]          on6ml   Michel
[e-mail]                   pe1hzg  Geert Jan de Groot
[e-mail]            pt2td   Francisco Rogerio Fontenele Aragao
[e-mail]                               ve3jf   Barry McLarnon
[e-mail]                                   ve3mdl  Marcus Leech
steve@espinc                                    ve3nus  Stephen Woo
johnt@espinc                                    ve3smt  John Turner
[e-mail]                          ve5va   Peter Hardie
[e-mail]                         ve6bbm  Lyndon Nerenberg
[e-mail]                           ve6bsv  Richard Loken
[e-mail]                             ve6lhw  Les Worral
[e-mail]                            ve6mgs  Mark Salyzyn
[e-mail]                            ve6pdq  Ross W. Alexander
[e-mail]                            ve6rwh  Ron
[e-mail]                         ve6sfw  Stephen Wolver
[e-mail]                              ve7aii  Robert Skegg
[e-mail]                         ve7tcp  Dennis S. Breckenridge
[e-mail]                       vk1kcm  Carl Makin
uunet!echo.canberra.edu.au!skcm                 vk1kcm  Carl Makin
[e-mail]                        vk1pc   Phil Clark
[e-mail]                        vk1xwt  Warren Toomey
[e-mail]                        vk1xwt  Warren Toomey
[e-mail]                       vk6zjm  Ron Murray
[e-mail]                             zl1bqj  Charlie Tetenburg
[e-mail]                          zl2boi  Giovanni Moretti
[e-mail]                             zl2tnm  Don Stokes

------------------------------

Date: 27 May 91 19:32:31 GMT
From: sdd.hp.com!mips!atha!aunro!alberta!herald.usask.ca![e-mail]
Subject: Looking for W0RLI BBS software.
To: [e-mail]

The C version of W0RLI (called CBBS) is available from TAPR on either 5.25"
or 3.5" floppy. The disk contains executable AND all sources. I used it to
port the code to the AMIGA. Current version is V6.71.
73 de Pete [e-mail]  VE5VA

------------------------------

Date: 27 May 91 21:24:18 GMT
From: photon![e-mail]
Subject: PACKET->Internet Gateway
To: [e-mail]

In article <[e-mail]>, [e-mail] (Mike Curtis wd6ehr.ampr.org![e-mail] [phone]) writes:
|> In message <[e-mail]> you write:
|> >
[stuff deleted]
|> > Does anyone know if a PACKET (either AX.25 and/or TCP/IP) gateway exists
|> > between PACKET radio and Internet?  If so, could someone please state
|> > where it is located?
|>
[stuff deleted]
|> > If not, why has this not been performed?  Additionally, what would
|> > be needed in getting set up?
|>
|> Where were you the last several months?  There was a thread that looked
|> like one of the suspension cables for the Golden Gate bridge!
|>
|> Quick summary: If unsupervised, there are legal problems because:
|>  1. non-amateurs would be permitted unsupervised access to amateur
|>     spectrum;
|>  2. stuff that's OK on the internet (cusswords, business, etc) is
|>     NOT OK on ham; and
|>  3. a lot of other petty (IMHO) details.
|>
|> A _supervised_ feed either way is OK.

One note from that Golden Gate bridge: please be clear what you mean by a gateway -- I assume from the description you're talking about a *mail* and/or News gateway;  there are more functions possible if one can (selectively) route at the IP layer.

Cheers,
  Willis Marti
  n5szf

------------------------------

Date: 28 May 91 04:08:01 GMT
From: sdcc6![e-mail]
Subject: PACKET->Internet Gateway
To: [e-mail]

I have the same question too.  Can this be done?

Oh, by the way, Bob, have I ever talked to you on the CLARA
repeater(145.22MHz)?

        JC, N6YEI

------------------------------

Date: 27 May 91 07:35:54 GMT
From: munnari.oz.au!manuel!ccadfa![e-mail]
Subject: PC CUA Interface for Packet?
To: [e-mail]

Does anyone know of software for a PC which makes a CUA type
interface for packet radio? That is an interface like IBM's
Common User Access (CUA). This can be a Windows 3 interface or
Presentation Manager or something which looks like them (with
or without graphics and mice).

------------------------------

Date: 27 May 91 11:16:37 GMT
From: sdd.hp.com!swrinde!zaphod.mps.ohio-state.edu!think.com!mintaka!bloom-beacon!eru!kth.se!ugle.unit.no!nuug!ifi!ifi.uio.no!sics.se!fuug!news.funet.fi![e-mail]
Subject: Problems with NOS
To: [e-mail]

First the hardware : PC/XT , 20+40 Mb hard disks 360 floppy,
 OH-TNC ( a tnc clone) with kiss mode on, Kenwood TR 2400
Software : MSDOS 3.30a, NOS version 910423 ( quite new ).

My problem : I've been trying to set up ax25 connection for
out local FBB mailbox, so I could send messages to outside world.
Telnetting to localhost ( telnet oh3lku.ampr) gets me to my mailbox,
giving command "SP oh3mvv@OH3RBR" prints line "To: ", but texts in
SMTP trace printout is correct ( Rcpt: <oh3mvv@oh3rbr> ) : However
the smtp trace says that recipient needed after the first data line.
Has anybody succeeded doing what I want or am I the only one ? Note
that no forwarding is yet going on and no aliasing is made for oh3mvv.

I'd  like to receive help for configuring mail connection for
AX25 mailboxes, any points will be considered, also example files.

BTW : mail for tcpip connections works

73 de OH3LKU

------------------------------

Date: 26 May 91 04:41:12 GMT
From: sdd.hp.com!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!pitt!w2xo![e-mail]
To: [e-mail]

References <[e-mail]>, <[e-mail]>, <[e-mail]>o
Reply-To : [e-mail] (Jim Durham)
Subject : Re: Looking for W0RLI BBS software

In article <[e-mail]> [e-mail] (Ed Carp) writes:
>In article <[e-mail]> [e-mail] (Jim Durham) writes:

>>A better solution is to run KA9Q 'net' using KISS tncs which gives
>>you AX25, Net/Rom, TcpIp and I have bbs code to run with it for
>>Unix Sys V and Berkely).
>
>Well, maybe, but how many folks out there are running net as opposed to W0RLI?
>--
The two are apples and oranges. 'Net' is just the networking
software. W0RLI is a bbs that runs under MS-DOS. What you
do is run an RLI-compatable bbs talking to 'net' through
some IPC channel. This allows you do do some neat stuff like
use the unix file structure and utilities to support the bbs.
For instance, bbs mail can be handled by a separate process
which is akin to 'Sendmail'. This is extremely powerful and
allows you to handle bbs<-->smtp mail, bbs<-->internet mail and
whatever your imagination dreams up. Number of users is
basically unlimited, as you spawn a new bbs with each user, each
talking to 'net' thru an IPC channel. (I use SYS V message queues, but
you could use streams, which is more modern). Each bbs will block
when there is no input or output and use far fewer cycles.

73
Jim, W2XO   ([e-mail])

------------------------------

End of Packet-Radio Digest
******************************
Date: Wed, 29 May 91 04:30:10 PDT
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V91 #134
To: packet-radio


Packet-Radio Digest         Wed, 29 May 91       Volume 91 : Issue 134

Today's Topics:
           AX.25 Packet TNC Timing Parameters HELP!
        Internet-packet gateway mailing list (2 msgs)
               W0RLI BBS WANTED

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

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: 28 May 91 02:08:50 GMT
From: usc!rpi!think.com!spool.mu.edu!munnari.oz.au!yoyo.aarnet.edu.au!frodo.cc.flinders.edu.au!adelaide.edu.au![e-mail]
Subject: AX.25 Packet TNC Timing Parameters HELP!
To: [e-mail]

Over the past few months on our local Packet LANs here in Adelaide
I have noticed an increasing amount of congestion as a result of
very badly set TNC timing parameters. Some people appear do have
things like Dwait set to zero! I would like to put together
a set of suggested parameters to put in the local packet news
letter here and wonder if people could offer some suggestions as
to what the various TNC parameters should be set to.

The LANs here typically consist of 1 BBS with multiconnect/multiuser
capabilities (4 users plus a forwarding BBS conenct), several
digipeaters and about 10-20 people on simultaneously either being
connected to the BBS (often via one of the digipeters) or having
conversations/file transfers via several of the digipeaters or
using the fairly large number of PMS's that are on the channel
(of which there are about 10 on 24 Hours a day).

Any suggestions on what typical TNC parameters should be used would
be most useful.

The users here have typically either the older style TNC-2's with the
dwait parameters and increasingly there are TNC's like the
MFJ and KAMs which have the slottime/persist parameters. What
would be the optimum parameters for the BBS and the Digipeaters
and also for the users to use?

Also I would be interested in a detailed description of how the
slottime/persist parameters work.

Please send replies via E-Mail to my address below. If there are
sufficient replies I will sumarise and post the results in a couple
of weeks.

Thanks in Advance...  Grant VK5ZWI
--
Grant Willis (VK5ZWI) Elec.Eng.| AARNet/Internet1: [e-mail]
Adelaide Uni. South Australia  | ACSnet/Internet2: [e-mail]
Disclaimer: What I write is    | Packet Radio: VK5ZWI@VK5TTY.#SA.AUS.OC
mine, NOT the uni's!           | AmPRnet TCP/IP: [44.136.171.11]

------------------------------

Date: 28 May 91 12:15:15 GMT
From: uhccux!mpg.phys.hawaii.edu![e-mail]
Subject: Internet-packet gateway mailing list
To: [e-mail]

I would like to setup a mailing list of hams who run an Internet-packet
mail gateway.  The purpose of the mailing list would be to share ideas and
concerns about running such gateways.  I figure such discussions might be
inappropriate for tcp-group and would get lost in the noise in
rec.radio.amateur.packet.  The information shared in such a mailing list would
be a little more 'secure' and low-profile than if it were blurted out in
tcp-group or rec.radio.amateur.*.

If you run such a system, please let me know and I will place you on the list
if you're interested.

Tony
AH6BW
--
Antonio Querubin
[e-mail] / [e-mail] / [e-mail]

------------------------------

Date: 28 May 91 21:13:57 GMT
From: photon![e-mail]
Subject: Internet-packet gateway mailing list
To: [e-mail]

Please put me on the list.  My reply to you bounced.  Guess aggieland doesn't
know Hawaii is a state yet!! 8-}

--
Kurt Freiberger, wb5bbw   [e-mail]   409/847-8706
Dept. of Computer Science, Texas A&M University  DoD #264
*** Not an official document of Texas A&M University ***

------------------------------

Date: 28 May 91 12:32:02 GMT
From: fs7.ece.cmu.edu!o.gp.cs.cmu.edu!andrew.cmu.edu![e-mail]
Subject: W0RLI BBS WANTED
To: [e-mail]

Does anyone know if there is any machine on the network where I
can obtain the W0RLI BBS Program (Not the source code, just the
executable), via anonymous FTP?
The local packet bbs sysop is getting his copy via modem and long
distance phone call. I promised him that I would check to see
if it's available on the net via ftp. Again....I don't need the
source...just the binary executables.
Which machine would have the latest releases?

Thanks
\paul
WA3TLD

------------------------------

Date: 29 May 91 01:09:48 GMT
From: swrinde!mips!spool.mu.edu!munnari.oz.au!uniwa!cc.curtin.edu.au![e-mail]
To: [e-mail]

References <[e-mail]>, <[e-mail]>, <[e-mail]>
Subject : Re: Time bug in KA9Q v 910423

In article <[e-mail]>, karn@epic..bellcore.com (Phil R. Karn) writes:
> In article <[e-mail]> [e-mail] (Tom Thompson) writes:
>>    (1) replace the INT 1A call in NET with fetching the tick
>>        count from BIOS data area (with ints off since long fetches
>>        not indivisible):
>>        cli(); ticks = *(long far *) 0x40006cL; sti();
>
> Tom,
>
> Many thanks for the suggestion. With some minor variations I'm making
> this change to the code right now. After initial testing I will upload
> the new version to thumper.bellcore.com in /pub/ka9q/nos. Hopefully
> this will fix the problem.
>
> Phil

   This seems to fix the problem (at least on my machine, anyway!).
Thanks, Phil.

.....Ron
--

===============================================================================
 Internet: [e-mail]                | "The Universe is so
 Bitnet: [e-mail]    | utterly disorganised
 UUCP  : uunet!munnari.oz!cc.curtin.edu.au!Murray_RJ | that it can only have
Amateur Packet Radio: VK6ZJM@VK6BBS.#WA.AUS.OC       | been written in Pascal"
           TCP/IP: 44.136.204.14, 44.136.204.19  |  -- The Phantom Waffler
===============================================================================

------------------------------

End of Packet-Radio Digest
******************************
Date: Thu, 30 May 91 04:30:10 PDT
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V91 #135
To: packet-radio


Packet-Radio Digest         Thu, 30 May 91       Volume 91 : Issue 135

Today's Topics:
             KA9Q under Unix - now what?
               PACKET->Internet Gateway
               Request for information

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

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: 29 May 91 17:52:33 GMT
From: uswnvg![e-mail]
Subject: KA9Q under Unix - now what?
To: [e-mail]

Well - I now have the KA9Q Net software (which, BTW is better than  a
lot of COMMERCIAL software I've seen) running on my SCO Unix Box, and
I can use it in AX.25 mode to talk to my local (SEAW) AX.25 PBBS.

I have two questions:

1)  What do I do next?  I have any IP address, but I have no idea where
there are any other IP hosts and how I might connect to them.  I'd like
to test ftp, and work on getting SMTP (which should be a real trick,
as those of you who have worked with MMDF can appreciate) working.

2)  The version of net I have seems pretty old (a lot of the commands
documented in the stuff I have don't work, like tip).  It
announces itself as version 890421.1a (n3cvl unix test).  Is there a
later version somewhere (I got this one from WB3FFV?  I'd need
either an anonymous uucp site or a packet FTP (assuming I get ftp
working ;-) ) site.

73!
--
Clay Jackson - N7QNM
US WEST NewVector Group, Inc
[e-mail] | ...uunet!uswnvg!cjackso

------------------------------

Date: 29 May 91 17:06:26 GMT
From: pacbell.com!mips!sdd.hp.com!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!cunixf.cc.columbia.edu!cunixb.cc.columbia.edu![e-mail]
Subject: PACKET->Internet Gateway
To: [e-mail]

In article <[e-mail]> [e-mail] (Jung Ching Ho) writes:
>I have the same question too.  Can this be done?
>
>Oh, by the way, Bob, have I ever talked to you on the CLARA
>repeater(145.22MHz)?
>
>               JC, N6YEI

Newsgroups: rec.radio.amateur.misc,rec.radio.amateur.packet
Subject: Internet-Packet Gateway / Was Re: FUCKING ICOM HANDHELDS!
Reply-To: [e-mail] (Meir)
Distribution: rec
Organization: Columbia University

In article <[e-mail]> [e-mail] (Ari Husa OH8NUP) writes:
>FUCKFUCKFUCKFUCKFUCK!
>
>I AM REALLLLLLLLLY PISSED!
>
>I just lost THIRD battery back by Icom because of their EXTREMELY
>STUPID battery back connector that is made in PLASTIC!!!
>
>Please, DO NOT tell me I should not drop my handhelds on the ground,
>for in my opinion they REALLY SHOULD take it! Or, at least, they
>should develop an electrical fault, NOT MECHANICAL! Who the fuck was
>that IDIOT who decided the S-series battery connector is going to be
>made of plastic? I WANT TO STRANGLE HIM PERSONALLY!!!
>
>SUCH IDIOTS SHOULD NOT BE ALLOWED NEAR FUNCTIONAL HAND-HELD RADIOS!
>
>BLOODY HELL! Does anyone know a good way to fix these things?
>
>       Luru
>
>--
>       ///
>       o-o    Ham Radio Operators Do It In Higher Frequency
>        o

This is the reason that direct gateways between Internet and Amateur Radio
are illegal!

Of course, even a relatively simple program would probably catch the blatant
language used here.

 * * * * * * *  ======================= Meir Green
* * * * * * * * ======================= [e-mail]
 * * * * * * *  ======================= N2JPG

------------------------------

Date: 29 May 91 11:11:19 GMT
From: crdgw1!islandgirl![e-mail]
Subject: Request for information
To: [e-mail]

    Could anyone please send me some brief information concerning the
existence of and access to BBS on HF packet (call letters, frequencies,
times, etc).  Interested in 80 through 10 meters.  Thanks.



                    Rick Gaus
                    WA3INC

------------------------------

End of Packet-Radio Digest
******************************
Date: Fri, 31 May 91 04:30:04 PDT
From: Packet-Radio Mailing List and Newsgroup </dev/[e-mail]>
Reply-To: [e-mail]
Subject: Packet-Radio Digest V91 #136
To: packet-radio


Packet-Radio Digest         Fri, 31 May 91       Volume 91 : Issue 136

Today's Topics:
               PACKET->Internet Gateway

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Packet-Radio Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio".

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: 29 May 91 15:02:19 GMT
From: nuchat!farwest![e-mail]
Subject: PACKET->Internet Gateway
To: [e-mail]

Organization: San Diego State University Computing Services

Don't know if the other message/article was posted here, so I'll request again.
Does anyone know if a PACKET (either AX.25 and/or TCP/IP) gatewaye exists
between PACKET radio and Internet?  If so, could someone please state where it
is located?  If not, why has this not been performed?  Additionally, what would
be needed in getting set up?

Robert S. Radvanovsky, KC6ONL
I


 * Origin: Two Wheelers  bikie hangout (1:106/88.0)

------------------------------

Date: 30 May 91 18:02:05 GMT
From: [e-mail]
To: [e-mail]

References [e-mail], (Lisa, Schuster)
Subject : (none)

> pr
> gen
> info

What is this and why did I receive it??

Lisa Schuster.
KMAA@MARISTB

------------------------------

End of Packet-Radio Digest
******************************