Date: Thu, 27 May 93 04:30:13 PDT
From: Advanced Amateur Radio Networking Group <tcp-group@ucsd.edu>
Errors-To: TCP-Group-Errors@UCSD.Edu
Reply-To: TCP-Group@UCSD.Edu
Precedence: Bulk
Subject: TCP-Group Digest V93 #136
To: tcp-group-digest


TCP-Group Digest            Thu, 27 May 93       Volume 93 : Issue  136

Today's Topics:
                            Kiss question
                             Mac IP bits
                         Node source request
                              subscrive
                     Thenet X1H patchinstructions

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: Wed, 26 May 93 20:22:20 MDT
From: jr@upl.com (J.R. Westmoreland)
Subject: Kiss question
To: tcp-group@ucsd.edu

If I have the TNC in KISS mode how much processing does the TNC do and what does
the KISS packet look like coming from the TNC?
Does the TNC do all of the 0 bit removal and flag byte removal on
the HDLC packet?  I believe it is possible but is it legal to send
raw SLIP or possibly raw IP datagrams
over the radio?  If you can transmit raw IP
datagrams over the radio then wouldn't the circuit (radio)
almost look like a slow ethernet?

I appreciate any help in answering these questions and hope they are not too obvious
that everyone in the world knows but me.

J.R.  (n7mff)

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

Date: Wed, 26 May 93 17:23:50 PDT
From: tking@oes.ca.gov (Tom King)
Subject: Mac IP bits
To: TCP-group@ucsd.edu

Can anybody tell me who is maintaining the MAC IP software now? 

Also where might I find them?

Thanks,
Tom King
KA6SOX

Packet:   KA6SOX@K6TZ.#SOCAL.CA.USA.NA
Internet: tking@oes.ca.gov

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

Date: Wed, 26 May 1993 09:13:36 PDT
From: "Jeffrey D. Angus" <jangus@skyld.tele.com>
Subject: Node source request
To: TCP-group@UCSD.edu

If you have the source code for TheNet (obviously Net/Rom is a
highly guarded secret) please let me know how I can obtain a 
copy of it. Respond via e-mail if you wish to remain anonomous.

73 es GM from Jeff
-- 
J. Angus: jangus@skyld.tele.com -- "Als ik Kan", Gustav Stickley
US Mail:  PO Box  4425  Carson, CA  90749-4425  1 (310) 324-6080

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

Date: Thu, 27 May 1993 12:21:08 +0200
From: ik3ngu@osi.iunet.it (Pizzichetti)
Subject: subscrive
To: tcp-group@ucsd.edu

As I have a dialup line to Internet , I ask you to take into 
consideration again this new request of subscrive to your mailing list .
So send me mail to my pop server on osi.iunet.it.
Thank you.

ik3ngu@osi.iunet.it. Treviso Italy

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

Date: 27 May 93 08:24:26 EET-2EEST
From: "Markus Lamminmaki OH6LSA"  <MARKUS@TECHNIS.vtyh.fi>
Subject: Thenet X1H patchinstructions
To: tcp-group@ucsd.edu

It looks like my first posting of this patch didn't make it to this
group so I'll post it again, my apologies if you receive this twice
from the tcp-group.

Before I found this patch I was quite frustrated because I didn't get
the IP part of the node working properly.

-------clip here--------------------------------------------------

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

Date: (null)
From: (null)
In addition, here are two more patches. One is to cure the ARP
digipeat garbage bug, the other is to lower the minimum transport
retries to 1.

1. The Arp garbage bug.

Took ages to find this - in the event it was trivially silly.
The problem is that when an arp request is sent tothe node it
replies with a garbage filled digi list. The patch cures this.

In the file THENET2.X1H, patch the byte at offset 0x77cf from 0x2a to
0x21.

2. The transport retries.

In some networks, transport retries are not wanted, but the node does
not allow the retry counter to be set below 2. This patch allows it
to be set to 1.

In the file THENET2.X1H, patch the byte at offset 0x7933 from 0x02 to
0x01.

An easy way to patch the files is to use debug - but remember to add
0x100 to the addresses. Hence to perform the arp patch, type :

debug thenet2.x1h
e 78cf
21
w
q

Line 1 invokes debug on the file
Line 2 edits the byte at offset 77cf ( it is at address 78cf )
Line 3 changes it to 0x21 - note that it should read 0x2a !
Line 4 writes out the changed file
Line 5 exits from debug.

These patches only apply to thenet-x1h. If you are using x-1g you need
to upgrade first. In addition, if you are using x-1g you will also
find that ip frames sent out as UI frames will have garbage digi
lists. This was fixed in X-1H together with a couple of other bugs.

73's
Dave
G8KBB @ GB7MXM.#36.GBR.EU

------clip here-------------------------------------------------------


---
Vasa Polytechnic                 Email: markus@ygdrasil.vtyh.fi (NeXT Mail)
PB 6, SF-65201, FINLAND                 markus@technis.vtyh.fi  (PMail)
Fax: +358-61-3230 610                   OH6LSA@OH6RBV.FIN.EU    (Packet)
Home:+358-61-3211 194            Work:  +358-61-3230 661
              Looks great on the outside, but Intel inside.

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

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