Date: Thu, 18 Nov 93 04:30:02 PST
From: Advanced Amateur Radio Networking Group <tcp-group@ucsd.edu>
Errors-To: TCP-Group-Errors@UCSD.Edu
Reply-To: TCP-Group@UCSD.Edu
Precedence: Bulk
Subject: TCP-Group Digest V93 #300
To: tcp-group-digest


TCP-Group Digest            Thu, 18 Nov 93       Volume 93 : Issue  300

Today's Topics:
                           jnos discussion
                      SLIP, AX.25, KISS, etc...
                              subscribe
                             TEKK Radios

Send Replies or notes for publication to: <TCP-Group@UCSD.Edu>.
Subscription requests to <TCP-Group-REQUEST@UCSD.Edu>.
Problems you can't solve otherwise to brian@ucsd.edu.

Archives of past issues of the TCP-Group Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives".

We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party.  Your mileage may vary.  So there.
----------------------------------------------------------------------

Date: Thu, 18 Nov 93 08:24:22 +0100
From: eratho@eras70.ericsson.se (Thomas W Nilsson AR/RW)
Subject: jnos discussion
To: tcp-group@ucsd.edu

Hi,

where does the jnos discussion take place nowadays? (I remember me seeing
a mail mention a special list on the subject somewhere.)


/Thomas SM0KBD

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

Date: Wed, 17 Nov 93 10:39:53 CST
From: andyw@aspen.cray.com (Andy Warner)
Subject: SLIP, AX.25, KISS, etc...
To: agodwin@acorn.co.uk (Adrian Godwin), tcp-group@ucsd.edu (TCP Group)

Adrian writes :-

> Perhaps quite cheaply .. I've been considering this for a while on the grounds
> that an NE1000 card costs $100 or less (much cheaper second-hand), and has an 
> [...]
> the system (though I don't think the Z80 SIO has the 8530's 3-byte fifo).

I have a designed a V40 based board with a DMA driven ESCC, which I
was planning on putting ethernet on. It's pretty simple - at last count
this was the BOM :-

1 8MHz V40
1 100nS 1Mx8 (or 9) SIMM
2 20 pin GAL/PALs
1 32 MHZ xtal osc
1 ESCC
1 27512 for boot rom
1 MAX232
handful of common (eg available from Maplin/DigiKey) 74HC parts

Myself and Kevin, N0BEL, were planning on porting a cut down NOS
to this board (since the V40 is Intel compatible) to act as a packet
switch (ie no servers/bbs interfaces etc). The plan is for a small,
low power box that would run off 5V and sit quietly on a shelf along
side a radio & a grapes modem. If I could only get the part, I'd
trash the V40 and use a Motorola 68EC360 in a flash, but I haven't
been able to get one of those wonderful chips yet.

This is currently not plug and play. There are no PCBs
available, the only version is wire wrapped and running simple soak
tests in my basement. I need to re-work the I/O device PAL/GAL to
support a PC ethernet card, but any which appear in the IO space &
can use a DMA channel instead of shared memory should work.

The budget for the 4 DMA channels on the V40 is :-

2 support one port of the ESCC full duplex, DMA on TX & RX.
1 supports the other port half duplex.
1 supports the ethernet card.

I was planning on building my own ehternet interface with either
a NICE(Fujitisu)/PCISA(AMD)/91C92(SMD) part, but second hand PC
boards are much cheaper & easier to get.

One widget we wanted was to add the ability for this box to send out
UDP frames every time DCD/RTS changed on a radio port (the ESCCs would
talk directly to modems - no KISS or TNC). That way we could write an
X application to look like the front panel of the "pseudo TNC", so we
started calling the board the X-TNC. 

If there's enough people out there motivated to take what we've done
so far and move it along a little further, I think that would be great.
If we could harness 5% of the creative force on this list, we could
probably all have one of these running on a shelf within 10 months, if you
wait for me to do it (even with N0BEL's help), it may never happen.

I'm using Avocet Locate to relocate the output from Borlands finest,
you'd have to figure out your own way if you didn't have access to Locate
or something similar (check back issues of Dr Dobbs.) Kevin Rowett and
Stuart Phillips from Tandem also wrote an article in Dr Dobbs describing
how to interface Borlands Debugger to a V40 so that would be a useful
addition..

If there's interest, I'll transfer the circuit diagram from the back of
envelopes to OrCad or Schema or something.. I could also set up a mailing
list for co-conspriators to exchange mail on.

> What protocols should such a unit run ? Clearly, an IP router would be the
> [...]
> use a private protocol to talk to a support daemon on the host ?

One idea I like (but apparently no-one else on ham-bsd did) is using
the ax25 protocol stack developed for 386BSD or Linux to talk RFC-1226
(AX25 encapsulated within IP) packets, freeing the *nix box from having
the interrupt load of the serial ports. One problem I forsaw was how
to identify a specific port (eg an X-TNC would have at least two radio
ports) within a RFC-1226 packet. Maybe we should use the UDP version
of AX25 over IP instead, and listen on different udp ports ? Another
advantage (ok, I'm on a roll - don't try and stop me :-)) would be
that you could test out the AX25 kernel stack over ethernet - I'd
like that. Using the AX25 stack on *nix lets the X-TNC become far
simpler, since it's just shuffling packets, no timers or servers etc,
it also allows you to put the servers & BBS interface (puke) on far
more resilient platform.

-- 
andyw. N0REN/G1XRL

andyw@aspen.cray.com Andy Warner, Cray Research, Inc. (612) 683-5835

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

Date: Wed, 17 Nov 93 14:38:15 CST
From: "John Martin" <martin@server.cdpa.state.ms.us>
Subject: subscribe
To: tcp-group@ucsd.edu

quit
------
                                _______
                               /       |
   John W. Martin             /        |   INTERNET:
   Systems Programmer        /         |   martin@server.cdpa.state.ms.us
   Mississippi Central Data  |    C    |   oamartin@vm.cc.olemiss.edu
   Processing Authority      \    D    |   PACKET:
   301 North Lamar Street     |   P    |   kb5ggo @ k5qne.ms.usa.na
   301 Building, Suite 508    /   A    |   
   Jackson, MS 39201-1495    /         |   PHONE: (601) 359-2641
                            |______    |   FAX:   (601) 354-6016
                                  /    |
                                  \____|

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

Date: 17 Nov 93 06:47:25 CST
From: Jack Snodgrass <kf5mg@vnet.IBM.COM>
Subject: TEKK Radios
To: <TCP-Group@UCSD.Edu>

I've got a couple of questions on TEKK talkies.

1). kf0ox posted a message on the ax.25 bbs network about someplace
    in Kansas, Mo. selling 'their' 2 watt data radios for $90. Is
    TEKK located in Kansas, Mo? Anyone have a number for them? If not,
    does anyone know someone in Kansas, Mo. that sells TEKK radios for
    $90?

2). Will TEKK radios work half-duplex on a standard 440, 5mhz repeater
    split?

3). What freq. are the TEKK radios set up with when they're shipped?

4). How hard is it to change the operating freq. on one of these units?

5). Are they're different models of the TEKK talkies? If so, are some
    better than others? Are there any 'gotchas' with these besides the
    low ( 2 watts ) output? If I need to add an amp, will I have to add
    long TXdelay's?

   I'd like to set up a 19.2kb, Full-Duplex repeater with 2 of these
radios and a 440 amp.  (n5snn in austin is using these with minimal
problems at 19.2kb) That is... assuming that you can use a 5mhz split
with these units for the standard users. I think that a lot of local
users can afford $90 for a data radio that will do 19.2kb and 2 of
these will make a nice, full-duplex repeater at a really cheap price.

  Have I missed something really important? Has anyone else tried to
use these radios at 19.2kb? Thanks.

73's de Jack
| (817) 962-4409 | VM Office Systems | 5 West Kirkwood Blvd | MS 06-05-60 |
|  T/L  522-4409 | Performance Group | Westlake, Tx 76299   | Rm. 6569    |
vnet:jgrass@msnvm1   ibmmail:usib34cd@ibmmail   internet:kf5mg@vnet.ibm.com

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

End of TCP-Group Digest V93 #300
******************************
******************************