home *** CD-ROM | disk | FTP | other *** search
- TCP-Group Digest Mon, 20 Aug 90 Volume 90 : Issue 114
-
- Today's Topics:
- ARPing through digipeaters
- NOS NET/ROM code broken
- Old bug still present
- Request for RIP Info/Thanks
-
- Send Replies or notes for publication to: <TCP-Group@UCSD.Edu>
- Send requests of an administrative nature (addition to, deletion from the
- distribution list, et al) to: <ListServ@UCSD.Edu>
-
- Archives of past issues of the TCP-Group Digest are available
- (by FTP only) from UCSD.Edu in directory "mailarchives".
- ----------------------------------------------------------------------
-
- Date: Sun, 19 Aug 90 23:54:09 CDT
- From: Jay Maynard <jmaynard@thesis1.hsch.utexas.edu>
- Subject: ARPing through digipeaters
- To: tcp-group@ucsd.edu
-
- We discovered that ARP requests aren't replied to unless the packet has been
- through all the digipeaters in the AX25 path for QST. This is probably a
- feature, but it limits the usefulness of ARP to the area served by one local
- digipeater. Since we can't afford to dedicate a stack of PCs, or Kantronics
- Data Engines, or whatever, to do it right, we're stuck with using digipeaters
- to get from point A to point B. Can anyone suggest a way to cover a large
- metropolitan area using basic equipment? Purist flames to /dev/null, please.
-
- ------------------------------
-
- Date: Sun, 19 Aug 90 15:03 GMT
- From: <DEVANS%COLOLASP.BITNET@CORNELLC.cit.cornell.edu>
- Subject: NOS NET/ROM code broken
- To: tcp-group@ucsd.edu
-
- That error message is exactly the one that I am getting (except that
- I get a LOT more than just one) when I compile 900730 with TC++. I
- think you will find that it has no effect on the operation of NOS
- itself. Neither is it restricted to the NETROM code. Depending on
- what you put ion your autoexec file, you can get the error message
- (which comes from 'free') to point to any one of a number of
- routines.
-
- 73 -- Doc
-
- ------------------------------
-
- Date: Sun, 19 Aug 90 14:52 GMT
- From: <DEVANS%COLOLASP.BITNET@CORNELLC.cit.cornell.edu>
- Subject: Old bug still present
- To: tcp-group@ucsd.edu
-
- Several months ago, I posted details of a NOS bug which caused system
- crashes. Since NOS became much more stable around June time, I didn't
- think to test for the bug, assuming that it had gone away. Six crashes
- in the space of half an hour yesterday convinced me otherwise!
-
- I was running plain vanilla NOS 900730 with executable downloaded
- from thumper.
-
- The problem appears to arise when a station connects to NOS using
- pure NETROM at the same time that there is already a TCP/IP
- connection between the two stations. The symptoms are that the
- entire system halts: screen output stops and the keyboard is
- locked. A reset appears to be all that can be done.
-
- To self-inflict the crash, perform the following:
- (you mat want to do this with tracing on)
- 1. telnet to yourself;
- 2. Issue the N command;
- 3. Connect to a nearby NETROM node;
- 4. When that completes, Connect back to yourself
- Shortly after that connection completes, and after the mailbox
- login message has left your system, the system should completely
- lock up.
-
- Just to be clear, this is the sequence that I go through:
- telnet nq0i
- (login sequence)
- N
- (Connected to 1400004:NQ0I msg and msg about the escape character)
- C FNL [FNL is Ft. Collins NETROM node]
- (Connect msg)
- C NQ0I
- (Connect message)
- Shortly afterwards, the system stops.
-
- The problem arose yesterday when a local station also running 900730
- made a pure NETROM connection to me at the same time that I was
- sending him TCP/IP traffic; it proved to be impossible to keep
- the system up under these circumstances.
-
- Doc nq0i
-
- SPAN: ORION::DEVANS
- BITNET: devans@cololasp
- Internet: devans@orion.colorado.edu
- Snail: Radiophysics, Inc., 5475 Western Ave., Boulder, Colorado 80301 USA
- Analogue switching network: (303)-447-9524
-
- Non-work-related may also go to:
- Packet (AX.25): NQ0I @ KE0XA
- Packet (TCP/IP): nq0i@nq0i.ampr.org [44.20.0.3]
-
-
- ..._._
-
- ------------------------------
-
- Date: Sun, 19 Aug 90 22:12:55 EDT
- From: "Jim Campbell" <jimc@ralvm11.iinus1.ibm.com>
- Subject: Request for RIP Info/Thanks
- To: tcp-group@ucsd.edu
-
- I have been able to figure out how to use Telnet, FTP, etc., based on the
- available documentation. However, I can't figure out what RIP is all
- about. Can some kind soul provide a brief tutorial on what it does, and
- how to use such commands as RIP MERGE, RIP ADD, RIP REQUEST, etc?
-
- Also, my thanks to Bill@ke8kb and Paul@ei9gl for their kind help in getting
- my DRSI board working with NOS. Since I have only SMTP access to the
- internet, David Singer retrieved the latest NOS source for me (thanks David),
- and I compiled it. After some learning experiences, all is working OK.
- I'm now looking forward to trying out some of the more exotic features.
-
- Jim Campbell
- Research Triangle Park, N.C. (Internet: jimc@ralvm11.iinus1.ibm.com)
- (AMPRNET: w4bqp.ampr.org)
-
- ------------------------------
-
- End of TCP-Group Digest
- ******************************