🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: dnet.ham
Article #72

TCP-Group Digest 280691.1815

#72
From: daily posting
Date: Fri, 28 Jun 1991 16:15
311 lines
12342 bytes
From: Dave Goodwin <GOODWIN%SMCVAX.BITNET@mitvma.mit.edu>
Date: Thu, 27 Jun 91 13:01 EDT
Subject: NOS Telnet/Ttylink Problem

I saw mention of a bug in the Telnet command from the mailbox here some time
ago, but didn't pay much attention.  Wouldn't you know it, though, that some
body tried to chat with me the other night from the mailbox and it didn't
work.  The symptoms are no transmission of packets for anything I type on the
console.  Closing the session appeared to send one combined packet of those
things I had typed, but then ended the session as requested.

Can anyone advise whether this has been fixed in the latest PA0GRI releases?
I don't recall exactly which GRI release I'm running currently, but I think
its 053091.  Thanks for any info...
==========================================================================
Dave Goodwin                                  |
Assistant Director, Academic Computing        | To err is human.
VAX System Manager                            | To really foul things up,
----------------------------------------------| You need a computer.
BitNet/CREN : Goodwin@Smcvax                  |
Ma Bell     : (802)655-2000 X2220             |
Pony Express: Saint Michael's College         |           -Who Knows?
              Department of Computer Services |
              Winooski Park                   |
              Colchester, VT 05439            |
Ham Radio   : N1HRO                           |
==========================================================================


----
From: clark@tomcat.gsfc.nasa.gov (Tom Clark -- W3IWI)
Date: Thu, 27 Jun 91 18:00:06 UTC
Subject: Comments/questions on PA0GRI NOS_0618

Gerard -- I am trying your version of nos_0618 on tomcat and have several
comments/questions:

1. Regarding the fkey command: For one of our VAXes, I need to set some
key like <del> to be the delete key, 0x7f. I have tried a lot of combinations
to map the delete key back into being a delete key and none work! If the
leading character in the field is a "^", then it maps the next character as 
a standard control character, and passes the rest thru as a string. I have
tried to use the "<alt>127" sequence and that doesn't work at all. Any
suggestions?

2. Regarding "mem" -- there are two new options I don't understand, "circular"
and "efficient/slower". Can you explain?

3. Apparently "mail" is equivalent to "smtp kick"?

4. How do you set up rlogin entries?

5. Can you explain "source" and "tail"?

6. Can you explain the "watchdog" on/off for me?

7. Am I correct that "comm" merely sends out a character string to the
designated iface?

8. A suggestion: when you set domain verbose&translate on, the "tcp stat"
line overflows because the local host name name is fully expanded. Maybe
"half-verbose" (not expanding the local host). Also, the socket number
runs into the following field. Perhaps one white space would make it more
readible.

9. A feature in Phil's code which is lacking in yours is "domain query"
which implements an nslookup function.

10. Although rarp says that it allows for ethernet address queries:

>  net> rarp q
>  Usage: rarp query <interface> <ether addr|callsign> [<ether addr|callsign>]

And I have ethernet defined as a device on tomcat, I get the following reply
to a valid ethernet address on our LAN:

>  net> rarp q ethernet 08:00:20:07:83:22
>  Only AX25 interfaces allowed

11. General comments: The "ftype" switch is nice. Also, it looks like mget 
works again. If you are doing things with fkeys, it would be nice to have
the default <f3> replay the last line typed in. I still haven't set up pop --
a good tutorial from someone would be a big help!

73, Tom


----
From: mwester@sunbird.Central.Sun.COM (Mike Westerhof SE Chicago Metro)
Date: Thu, 27 Jun 91 17:38:07 CDT
Subject: AX.25 on IP

The latest version of the ax25ip software is on its way to the "incoming"
directory on UCSD.EDU.

ax25ip runs on UNIX (specifically SunOS; I hope future versions will support
more systems), and transfers AX.25 frames between a serial line (in KISS 
format) and IP packets (using RFC-1226 format).  The README file (which
I will put on UCSD.EDU as readme.ax25ip to save everyone from having to
download the entire package) describes the software more completely.

I just completed testing this with KA9Q's NOS (running on UNIX) with Anders'
rfc1226 implementation; works just fine!

Mike KA9WSB
Mike.Westerhof@Central.Sun.COM


----
From: uunet!samsung!swlvx2.msd.ray.com!anomaly.sbs.com!idsvax!mikebw mikebw@idsvax.ids.com <uunet!samsung!swlvx2.msd.ray.com
Date: Thu, 27 Jun 91 09:08:55 EST
Subject: Fix for PA0GRI ttylink screen

 
The split screen display mode used for the ttylink session in PA0GRI
NOS_0605 (actually dated 910619) shared the same problem as the earlier
releases.  As scolling occurred, characters would become very confused,
parts of received lines would be appended to parts of transmitted lines,
and so on.  This turned out to be a simple failure to call clreol() at
the necessary points, either where a newline is about to occur or where
a newline has just occurred.
 
The changes below result in a clear display such that two users of PA0GRI
NOS in a ttylink session will see identical top windows, except that each
will see their own transmitted text in high intensity and the received
text in normal intensity.  This was the original intent.
 
Added lines are marked with the comment "/* N1BEE */", and the conditional
blocks in PC.C have been clarified typographically.
 
-- Mike Bilow, N1BEE @ KA1RCI.RI.USA.NA  (AX.25)
               mikebw@idsvax.ids.com  (Internet)
 
 
***** (old) TTYDRIV.C lines 91 to 98 *****
[91]					while(rp < cp) {
						putch(*rp++);
					}
					normvideo();
					cputs(Eol);
					sp->tsavex = wherex();
					sp->tsavey = wherey();
[98]					window(1,24,80,25);
 
----- (new) TTYDRIV.C lines 91 to 100 -----
[91]					while(rp < cp) {
						putch(*rp++);
					}
					normvideo();
					clreol();	/* N1BEE */
					cputs(Eol);
					clreol();	/* N1BEE */
					sp->tsavex = wherex();
					sp->tsavey = wherey();
[100]					window(1,24,80,25);
 
***** (old) PC.C lines 810 to 815 *****
[810]		if(sp->split){
			if(c == 0x0a) cputs(Eol);
			else putch(c);
		} else {
			putc(c,Rawterm);
[815]		}
 
 
----- (new) PC.C lines 810 to 818 -----
[810]		if(sp->split){
			if(c == 0x0a) {
				cputs(Eol);
				clreol();	/* N1BEE */
			} else
				putch(c);
		} else {
			putc(c,Rawterm);
[818]		}
 


----
From: "John R. Ackermann" <jra@lawday.daytonoh.ncr.com>
Date: Thu, 27 Jun 91 7:58:39 EDT
Subject: Hardware to multitask NOS

I'm running out of room in the hamshack and am thinking about replacing
the two PC's I'm now using (one AT as the NOS router between Unix and
the radio world, and another AT for general purpose and standard packet
use).

I'm contemplating something like a 20MHz 286 with 2MB of RAM to run
DeskView with NOS in one window and at most one other communications
task in another window.  The NOS window needs to have very high
reliability and uptime, since it's the router that gives radio access
to our Unix system.

I guess I have a couple of questions... first, is NOS under DeskView
reliable?  I assume the 20MHz machine would have enough clock to
handle the ports (one ethernet and one or two Ottawa DMA cards for NOS,
and a serial port for the other comm program); am I guessing wrong?

Finally, does it make sense to buy a 286 for this kind of use, or should
I find a couple of hundred more bucks to buy a 386 or 386SX motherboard
(my "real" system is a 386 with Windows, so I can do fancy GUI stuff on
it; the hamshack system can probably live pretty well without WinWord or
PowerPoint)?

John AG9V


----
From: adam@IGG.TNO.NL
Date: Fri, 28 Jun 91 11:32:56 +0200
Subject: NET/Mac version 51

 
Hello all,


My latest version of NET/Mac has been ftp-ed to ucsd.eu in folder
/pub/hamradio/ka9q/incoming. Filename is NETMac51.sit.hqx


I wonder if the manager of ucsd.eu can create a special folder (directory)
like 'Mac' in the ka9q folder, so that we can upload a newer version every
now and then.


73 de
  __
 /_/  _/  _   ___
/ / (_/ (_/ / / /

(Adam van Gaalen)


+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+  
| Please send your reply to:               |Goes to |Mac  |Software  |  
+ - - - - - - - - - - - - - - - - - - - - -+- - - - + - - + - - - - -+  
|   internet:adam@igg.tno.nl               | office |LC   |NCSATelnet|  
|         or:pa2aga@igg.tno.nl             |  same  |same |   same   |  
|earn/bitnet:gaalen@hdetno51.bitnet        |  same  |same |   same   |  
|  Ham-radio:pa2aga@pa2aga   (44.137.32.9) |my place|IIx  | NET/Mac  |  
|         or:pa2aga@pa2aga-1 (44.137.32.61)|  same  |Plus |   same   |  
|         or:pa2aga@pa2aga-2 (44.137.32.19)|  same  |512Ke|   same   |  
|         or:pa2aga@pi8mac   (44.137.32.22)|  same  |SE/30|   same   |  
|    Ham BBS:pa2aga@pa3eae.nld.eu          |  same  |any/4|   same   |  
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+  


----
From: gvdg@cdc.com (Gerard Van Der Grinten)
Date: Fri, 28 Jun 91 6:46:57 CDT
Subject: Re: New NOS (0618)

> Hello Gerard,
Hello Tony,
> 
> I run a NOS-packet gateway in Hawaii and would like to test out the new axip 
> code.  I did the following on my end:
> attach axip ai0 256 129.179.122.10 ah6bw-2
That looks perfect to me. ah6bw-2 is now your local digi entry into
the wormhole to me.
I added  attach axip ai1 256 128.171.41.250 pa0gri-13
Note that every wormhole needs a new SSID so time is there to get multiple xyl's...
Currently there is room for 10 entries.
> 
> When I did an ifconfig I got the following:
> ai0        IP addr 44.14.1.2 MTU 256 Link encap AX25
>            Link addr AH6BW-2
>            flags 0 trace 0x0 netmask 0x00000000 broadcast 0.0.0.0
>            sent: ip 0 tot 0 idle 0:12:56:35
>            recv: ip 0 tot 0 idle 0:12:56:35
> ec0        IP addr 128.171.41.250 MTU 1500 Link encap Ethernet
>            Link addr 00:00:01:02:67:94
>            flags 0 trace 0x0 netmask 0xffffff00 broadcast 128.171.41.255
>            sent: ip 2704 tot 2787 idle 0:00:00:04
>            recv: ip 17576 tot 18777 idle 0:00:00:01
> netrom     IP addr 44.14.1.2 MTU 236 Link encap NETROM
>            Link addr AH6BW-1
>            flags 0 trace 0x0 netmask 0x00000000 broadcast 0.0.0.0
>            sent: ip 0 tot 0 idle 0:12:56:35
>            recv: ip 0 tot 0 idle 0:12:56:35
> ax0        IP addr 44.14.1.2 MTU 256 Link encap AX25
>            Link addr AH6BW-1
>            flags 0 trace 0x0 netmask 0xffffff00 broadcast 44.14.1.255
>            sent: ip 104 tot 629 idle 0:00:00:16
>            recv: ip 0 tot 683 idle 0:00:17:17
> loopback   IP addr 127.0.0.1 MTU 65535 Link encap None
>            flags 0 trace 0x0 netmask 0xffffffff broadcast 255.255.255.255
>            sent: ip 110 tot 110 idle 0:00:31:39
>            recv: ip 110 tot 110 idle 0:00:31:39
> encap      IP addr 0.0.0.0 MTU 65535 Link encap None
>            flags 0 trace 0x0 netmask 0xffffffff broadcast 255.255.255.255
>            sent: ip 0 tot 0 idle 0:12:56:36
>            recv: ip 0 tot 0 idle 0:12:56:36
> 
> Is this correct?  Shouldn't ifconfig show the IP address for ai0 to be 
> 129.179.122.10?
> 
Yes, all is perfect. The ip address in ai0 is of no value but for your
own documentary you can type ifconfig ai0 ip 129.179.122.10 
> Thanks!
> 
Thank you and hope to work soon via 2 meters.....(hi ;-) )

> Tony
> AH6BW
> 
Regards, Gerard.


----
Technical Details
Message-ID: <9106281615.AA03113@infoac.rmi.de>
Path: arc1-ca.pugleaf.net!gmdzi!unido!infoac!news-mail-gateway

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 12f11c,c917303c41300557,start
X-Google-Attributes: gid12f11c,public
X-Google-ArrivalTime: 1991-06-28 10:03:01 PST
Path: arc1-ca.pugleaf.net!gmdzi!unido!infoac!news-mail-gateway
From: DIGEST@infoac.rmi.DE (daily posting)
Newsgroups: dnet.ham
Subject: TCP-Group Digest 280691.1815
Message-ID: <9106281615.AA03113@infoac.rmi.de>
Date: 28 Jun 91 16:15:20 GMT
Sender: daemon@infoac.rmi.de
Reply-To: dl3no@infoac.rmi.de
Organization: RMI Net INFO.box Systems * Aachen * Hamburg * Flensburg
Lines: 311