Date: Fri, 15 Jan 93 04:30:13 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 #15
To: tcp-group-digest


TCP-Group Digest            Fri, 15 Jan 93       Volume 93 : Issue   15

Today's Topics:
                           930104 and echo
                          AmigaNOS (3 msgs)
                   In-Reply-To: Terminal with NOS?
                New Gotha Mail (gmail) release at ucsd
                   NOS in limited RAM environments
                     PK88 hanging xmitter in KISS
                          PNEWS 1.0 uploaded
                   Routing for Australia. (6 msgs)
                     Terminal with NOS? (3 msgs)
                Using Terminal with JNOS 1.07 (2 msgs)

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, 14 Jan 93 19:37 GMT
From: <DEVANS%COLOLASP.BITNET@CORNELLC.cit.cornell.edu>
Subject: 930104 and echo
To: tcp-group@ucsd.edu

I've seen a couple of references here to people who built Phil's 930104
and discovered that characters were not echoed on the command screen. I built
an executable from the distribution yesterday (BC++ 3.1 -3 switch) and
discovered the same problem. If a fix has been posted here, I haven't seen
it. Anyone found a fix yet?
  Doc  NQ0I

SPAN: ORION::DEVANS
Internet: devans@orion.colorado.edu
BITNET: devans@cololasp.bitnet

Snail: Radiophysics, Inc., 5475 Western Ave., Boulder, CO  80301
Analogue switching network: +1 303 447 9524
Digital picture switching network: +1 303 447 8632

Non work related may go to:
TCP/IP: nq0i @ nq0i.ampr.org; nq0i @ [44.20.0.3]
AX.25: NQ0I @ NQ0I.#NECO.CO.USA.NA

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

Date: Thu, 14 Jan 93 08:20:02 -0600
From: sbrown@charon.dseg.ti.com (Steve Brown)
Subject: AmigaNOS
To: tcp-group@ucsd.edu

Hello,

I'm trying to get AmigaNOS up and running and have been having a
rough time finding information/knowledgeable people.  I know there
must be some out there because things keep appearing on ucsd.edu in
the Amiga directory!

Is there anyone who is willing to help a poor, struggling
soul?  In payment, I will promise to update the TCP/IP FAQ (and other
documents?) with some Amiga-specific information so the next person
who wants to do what I'm trying to do won't have such a hard time.

The kind of questions I need answered are:

   1) Where do these posting come from?  Who are the movers and
      shakers in AmigaNOS?

   2) What are the underlying assumptions?  What machine must one
      have?  Is an Amiga 1000 with 1.5M and two floppys usable?

   3) What software must one have other that the AmigaNOS kit?  From
      what I have been able to tell from the kit, there is a shell
      program involved?  Arexx?  SKSH?  I think I recognize that the
      distribution uses the Amiga Resource Project command replacement
      set.  Is that correct?

   4) Is there any Amiga-specific documentation available other than
      the help files in the kit?  I have read all or most of the
      usual KA9Q documentation.

Thanks,

  Steve Brown, WD5HCY         
  sbrown@charon.dseg.ti.com   
  wd5hcy@kf5mg.#dfw.tx.usa.na 
  44.28.0.61 (Real Soon Now)  
  (214) 575-3597 work         
  (903) 564-3323 home         

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

Date: Thu, 14 Jan 93 13:45:40 EST
From: crompton@NADC.NAVY.MIL (D. Crompton)
Subject: AmigaNOS
To: sbrown@charon.dseg.ti.com, tcp-group@ucsd.edu

Steve,

 I have a local user k3oyh.ampr.org - 44.80.8.28 - Jack Kohler who
is an expert in that area. He works for Commodore. He is gateway
accessible via WG2W-8 gateway. I do not think he has internet access.
I could get you his phone number if all else fails. He is is Hatboro, PA
near Phila.

Doug

? Would it screw something
else up?

Mirrorshades seems to be having some more difficulty. It was working
fine yesterday but was not last night.

Doug

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

Date: Thu, 14 Jan 93 18:40:07 PST
From: algedi!kenk (Ken Koster) (Ken Koster)
Subject: AmigaNOS
To: pilchuck!uunet!ucsd!charon.dseg.ti.com!sbrown

Hi Steve (Steve Brown), in <9301141420.AA11915@charon> on Jan 14 you wrote:

> Hello,
>
> I'm trying to get AmigaNOS up and running and have been having a
> rough time finding information/knowledgeable people.  I know there
> must be some out there because things keep appearing on ucsd.edu in
> the Amiga directory!
>
> Is there anyone who is willing to help a poor, struggling
> soul?  In payment, I will promise to update the TCP/IP FAQ (and other

No payment necessary :-)

Since 'algedi' is running AmigaNOS and has been for a number of years
I can probably help you out.  Send me Email at the data-io address below
and we'll carry this on out of the way of the tcp-group list.

My system sits on both the local packet radio network and uucp and acts as
a gateway between the two so I really give AmigaNOS a workout. (130,000+
messages last year)  Configuration of AmigaNOS is very similar to the
MSDOS version but there are enough differences that it can get tricky and
the documention on this version is even worse than that for MSDOS.

Drop me a message and I'll see what can be done.
--
73's,  Ken

W   W EEEEE TTTTT N    N EEEEE TTTTT  : Ken Koster
W   W E       T   NN   N E       T    :
W W W EEEE    T   N N  N EEEE    T    : PBBS: N7IPB@N7IPB.WA.USA.NA
WW WW E       T   N  N N E       T    :
W   W EEEEE   T   N   NN EEEEE   T    : AMPR: kenk@algedi.ampr.org [44.24.0.45]
                                      :
Washington Experimenters TCP NETwork  : UUCP: algedi!kenk@Data-IO.com

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

Date: Thu, 14 Jan 93 22:50:06 PST
From: algedi!aa6ed (aa6ed)
Subject: In-Reply-To: Terminal with NOS?
To: tcp-group@ucsd.edu

In response to James Dean's request:


>  I am curious as to whether NOS could support a simple terminal on one
> comm port with the tnc on the other comm port.

What you might try is setting up a JNOS port at a 'TIPMAIL' port.  This port
recognizes RLSD (DCD) type connects, and all you have to do is configure your
PK-88 to respond to a connect, different from the mailbox.  The user will have
to log on as though it were a TelNet session.  JNOS will have no idea if the
caller is a ham or not.  I had to compile my JNOS software without the
'Converse' software, seems if it was compiled in, I couldn't enter into any
thing but a 'Converse' connect.  By setting up the FTPUSERS file properly,
callers can access the user TNC port.

One problem with 'TIPMAIL' is that it doesn't respond well to hang-ups, i.e.
a user terminating the call without the 'bye' command (loss of RSLD).

I don't have good answers for the rest of your questions.

To give you an idea, I'm running a telephone BBS, complete with file uploads
and downloads (phone number listed below), and a non-ham message system.  It
also links (via a special null modem cable) to another computer running  WG7J
JNOS 1.06, supporting three TNC comm ports (1-AX.25, 2-TCPIP LANS).  The
special NULL modem cable is controlled by my telephone BBS, I use the RTS line
from the BBS (wire crossed over) to control the RLSD (DCD) line input to
JNOS.  The Telephone BBS is a 'True' Windows 3.1 application, JNOS is a DOS
application, both run on the same 386-25 computer.  I have to use the special
NULL modem cable because DOS can't communicate to Windows Applications using
DDE.

If you want more info, send mail to the address listed below, let's not
clutter up this mail group until we get some useful information to share
with the rest of TCP-GROUP!

73's
AA6ED

|-----------------------------------------------------------------------|
| Ham   : aa6ed.ampr.org [44.24.103.157]       William [Bill] Bytheway  |
| LLBBS : (206) 271-4657 (300/1200/2400)       11108 SE 184th Place     |
| Voice Phone : (206) 271-4476 (w/recorder)    Renton, WA  98055        |
|-----------------------------------------------------------------------|
| Return mail from UUCP/Internet should use : algedi!aa6ed@Data-IO.COM  |
|-----------------------------------------------------------------------|

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

Date: Thu, 14 Jan 93 08:36:37 CST
From: anderson@cat.ATK.COM (Dean S. Anderson)
Subject: New Gotha Mail (gmail) release at ucsd
To: tcp-group@ucsd.edu

To all those who have been waiting:
   I have just uploaded gmail.zip into the "incoming" directory at
ucsd.edu.  This is not the final release but contains a number of
new features that make it quite usefull (IMHO :-).  I would like to
get comments and suggestions on how to improve this program from
those who use it.  Enjoy!

73 de Dean S. Anderson, KA0MCM
anderson@cat.atk.com

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

Date: Thu, 14 Jan 93 09:52 CST
From: Jay Maynard                          <S0JM@ADMIN.HSC.UTH.TMC.EDU>
Subject: NOS in limited RAM environments
To: tcp-group@UCSD.EDU

I ran NOS for a long time on a 512K Data General/One. The DG/1
soaks up 48K for the display buffer, and by the time DOS is
loaded and such, only about 420K or so is available.

Squeezing it into this little RAM (geez. I can remember when I
had a gonzo system at home with 60K...) pretty much requires
that you recompile NOS and remove lots of standard stuff that
you don't need; I removed most optional protocols and stripped
out packet driver and Ethernet support. I generally had 70K or
so available after the system had stabilized. You won't be able
to shell out to DOS, either.

I can't speak to the PCJr, but hopefully this will help.

...Jay, K5ZC

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

Date: Thu, 14 Jan 1993 08:15:06 PST
From: Mike_Beezley.houstoncssc@xerox.com
Subject: PK88 hanging xmitter in KISS
To: tcp-group@ucsd.edu

I just started checking out NET and I discovered something that may have just
been a one time anomaly.  I have used my PK88 in standard AX.25 mode using
Lan-Link and QModem and never had a glitch in 2 years owning the device.  I
undestand that KISS takes away most of the intelligence of the TNC and just
passes packets through for NET/NOS to process.  I was logging off of a BBS and
reading the NET manual when I looked up and saw the 'send' light was on solid.
I checked the xcvr and it was transmitting.  It wasn't a terribly long time,
about 30 secs or so, but it concerned me about leaving the unit operating
unattended.  During the time it is xmitting I don't know if it was just a
carrier or if it was sending out garbage packets on the packet channel.  Any
PK88 users run into this problem out there?  I kinda figured it had to do with
being in KISS mode and the TNC not knowing whats going on and getting itself
hung.  I'd sure hate to have this happen when I was not in the same room with
it to turn off the transmitter when and if it happens again.

__mike (N5PWP)

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

Date: Thu, 14 Jan 1993 20:13:48 +0200
From: Costas Krallis SV1XV <kkrallis@leon.nrcps.ariadne-t.gr>
Subject: PNEWS 1.0 uploaded
To: tcp-group@ucsd.edu

PNEWS.ZIP was uploaded earlier today in hamradio/packet/tcpip/incoming
directory (file pnews.zip). It is a news article posting utility
for WG7J nos. Please try it and send me any feedback so I can
improve it.

Regards Costas SV1XV


------------------------------------------------------------------
|   Dr. K. Krallis  SV1XV *   Epsilon Software S.A.
|  ------
|  Internet:  kkrallis@leon.nrcps.ariadne-t.gr
|  Packet radio: SV1XV @ SV1IW.ATH.GRC.EU
|  AMPRnet:   sv1xv@sv1xv.ampr.org         [44.154.1.11]
|  Snail Mail:  P.O.BOX 3066, GR-10210 Athens, GREECE
------------------------------------------------------------------

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

Date: Thu, 14 Jan 93 9:36:29 EST
From: barry@dgbt.doc.ca (Barry McLarnon)
Subject: Routing for Australia.
To: tcp-group@ucsd.edu

> But it might be possible for a regional network to say all of net 44 that
> it sees goes to this address, and forget what any other administrative 
> domain says.  Then you would get all net 44 traffic that made it to  
> the administrative domain boundary (the reverse problem :-)

We have such an arrangement here in Ottawa.  It only applies to the
university's class B network that our gateway sits on, but at least
it gives us access to DNS and other services from local Internet hosts
without routing through the mirrorshades router.

Barry VE3JF

-- 
Barry McLarnon                  |  Internet: barry@dgbt.doc.ca
Communications Research Center  |  AMPRnet:  barry@bbs.ve3jf.ampr.org
Ottawa, Canada  K2H 8S2         |  PBBSnet:  ve3jf@ve3jf.#eon.on.can

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

Date: Thu, 14 Jan 93 20:05:11 GMT
From: lars@spectrum.CMC.COM (Lars Poulsen)
Subject: Routing for Australia.
>> Is it possible to have a router defined to handle a subnet of network
>> 44?

In article <9301131607.AA00260@ucsd.edu>
   S0JM@ADMIN.HSC.UTH.TMC.EDU (Jay Maynard) writes:
>Not as the Internet routing model is currently defined.

Jay is being slightly overconservative. The feature being asked for
is known to router people as "disjoint subnets". It is technically
illegal, but there are various ways to do it.

In general, routing within the internet is mostly automatic; routers
exchange routing intformation with each other, and each router only has
to be manually configured for a subset of local topology data. The
protocols used to exchange routing information can only deal with "whole
network numbers", not with subnets. Newer routing protocols are slowly
being deployed to alleviate this, but it will be a long time before all
routers know how to do this.

On the other hand, the key routers could very well be configured to "do
the right thing" with a bit of manual configuration. Several ways come
to mind. One possibility is to make the 44.x.y.z network internally
connected by establishing a tunnel between the Australian subnet and
- say UCSD.EDU.

-- 
/ Lars Poulsen, SMTS Software Engineer Internet E-mail: lars@CMC.COM
  CMC Network Products / Rockwell Int'l Telephone: +1-805-968-4262 
  Santa Barbara, CA 93117-3083  TeleFAX:   +1-805-968-8256

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

Date: Fri, 15 Jan 93 10:37:02 +1100
From: "Carl Makin" <makinc@hhcs.gov.au>
Subject: Routing for Australia.
To: tcp-group@ucsd.edu

>> But it might be possible for a regional network to say all of net 44 that
>> it sees goes to this address, and forget what any other administrative 

> We have such an arrangement here in Ottawa.  It only applies to the
> university's class B network that our gateway sits on, but at least

Ok.  so it is possible. :-)  That was the easy part.  Now we have to work
how to get it installed. :-(


Thanks!

Carl.

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

Date: Thu, 14 Jan 93 20:05:11 GMT
From: lars@spectrum.CMC.COM (Lars Poulsen)
Subject: Routing for Australia.
To: tcp-group@ucsd.edu

|> Is it possible to have a router defined to handle a subnet of network
|> 44?

In article <9301131607.AA00260@ucsd.edu>
   S0JM@ADMIN.HSC.UTH.TMC.EDU (Jay Maynard) writes:
|Not as the Internet routing model is currently defined.

Jay is being slightly overconservative. The feature being asked for
is known to router people as "disjoint subnets". It is technically
illegal, but there are various ways to do it.

In general, routing within the internet is mostly automatic; routers
exchange routing intformation with each other, and each router only has
to be manually configured for a subset of local topology data. The
protocols used to exchange routing information can only deal with "whole
network numbers", not with subnets. Newer routing protocols are slowly
being deployed to alleviate this, but it will be a long time before all
routers know how to do this.

On the other hand, the key routers could very well be configured to "do
the right thing" with a bit of manual configuration. Several ways come
to mind. One possibility is to make the 44.x.y.z network internally
connected by establishing a tunnel between the Australian subnet and
- say UCSD.EDU.

-- 
/ Lars Poulsen, SMTS Software Engineer Internet E-mail: lars@CMC.COM
  CMC Network Products / Rockwell Int'l Telephone: +1-805-968-4262 
  Santa Barbara, CA 93117-3083  TeleFAX:   +1-805-968-8256

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

Date: Thu, 14 Jan 1993 23:12:10 -0600 (CST)
From: lcz@dptspd.sat.datapoint.com (Lee Ziegenhals)
Subject: Routing for Australia.
To: tcp-group@ucsd.edu (tcp/ip networking group)

>This is exactly what I had in mind for our NNJ gateway. Have the 
>LOCAL internet machine route the local AMPR directly. Of course it
>would not advertise this. This would eliminate the mirrorshades
>hop and allow DNS at the internet site directly to AMPR.
>
>Is there something wrong with this concept? Would it screw something
>else up?

I do that for our internal network at Datapoint and it works fine.  I just
configured a static route for net 44 in the Cisco router that connects to
the internet.  It is, of course, set up so that the route is not advertised
to the regional network.  This at least eliminates the route through
mirrorshades for hosts within the company.

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

Date: Fri, 15 Jan 1993 09:51:31 +0200 (EET)
From: mea@Mea.cc.utu.fi ("Matti E. Aarnio [OH1MQK]")
Subject: Routing for Australia.
To: tcp-group@ucsd.edu

> >This is exactly what I had in mind for our NNJ gateway. Have the 
> >LOCAL internet machine route the local AMPR directly. Of course it
> >would not advertise this. This would eliminate the mirrorshades
> >hop and allow DNS at the internet site directly to AMPR.
> >
> >Is there something wrong with this concept? Would it screw something
> >else up?
> 
> I do that for our internal network at Datapoint and it works fine.  I just
> configured a static route for net 44 in the Cisco router that connects to
> the internet.  It is, of course, set up so that the route is not advertised
> to the regional network.  This at least eliminates the route through
> mirrorshades for hosts within the company.

  For most uses, mail delivery via regional MXed gateways and static IP
routing with a particular gateway is all you really wish, but FTP won't
work -- of course...  (MX-gateway is not to be on an AMPR-net address,
but it can reach local AMPR-net subnet(s) more or less directly.)

  One the new Internet routing structure is in place (maybe a bit before)
it may be possible to define masked subnets to be routed instead of just
routing everything to nearest gateway to network X.

 /Matti Aarnio <mea@utu.fi> OH1MQK

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

Date: Thu, 14 Jan 93 13:57:28 CST
From: jks@giskard.uthscsa.edu
Subject: Terminal with NOS?
To: tcp-group@ucsd.edu

Hi James... (jdean@drao.nrc.ca)

You ask:
>  I am curious as to whether NOS could support a simple terminal on one
> comm port with the tnc on the other comm port.

Yes.... but you must have a version with TIPBBS or something like that compiled
in. Few of the distributed versions of executables have this feature. Basically
you configure TIPBBS to answer one specific comm port.

> What variant of NOS should I use? I might have to use a PC Jr for the
> first little while to prove the concept. Will NOS run reliably on
> the Jr? Can NOS be stripped down to fit into the limited disk and
> memory space the Jr provides?

Any KA9Q, or if you can find it the 1989 vintage PE1CHL NET. Although there are
some objections to doing the latter these are simpler/smaller versions of JNOS,
TNOS, GRINOS, etc.....

A PCjr will run any of the SMALLER net.exe versions very well so long as you 
have done the following:

1. Done the 640K memory mod.
2. Done the second diskette drive mod or hard drive mod.
3. Use the PCjr memory configuration software (IBM or Tecmar versions are 
   best).
4. Have the 1200 or 300 baud modem installed.
5. Limit your asynch port speed to 2400 baud.

I ran NOS/NET for 3 years using a 1989 version of PE1CHL NET, and a PK232 in 
kiss mode at 2400 bps (link speed), 1200bps (over-the-air) on a machine that 
answered the above description. I ran the machine on its side with the top off 
and the fan disabled for maximum quiet. You do need to have Well Isolated 
antennae and good coax on your tranceivers to prevent in-shack RFI.

73.

********************************************************************* 
* Dr. John Spitznagel                  *   Sancho Panza Institute   * 
* Internet: jks@giskard.uthscsa.edu    *    for Advanced Studies    * 
* AMPRNet:  kd4iz@kd4iz.ampr.org       *  Department of Bogometrics * 
* CIS:      76044,476                  *                            * 
* Tel:      (210) 567-6616             *  (C) JKS, 1992             * 
********************************************************************* 

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

Date: Thu, 14 Jan 1993 09:19:32 -0600
From: miltonm@inetnode.austin.ibm.com (Milton Miller)
Subject: Terminal with NOS?
To: tcp-group@ucsd.edu

Yes, NOS does support a dumb terminal login to the mailbox.  Phil Karn
wrote the orginal code, although it has severe performance penaltys (each
output character was sent to the terminal individually).   I rewrote the
code, which has made it into WG7J 1.07 (affected file is TIPMAIL.C).

There is one other bug that we just found and fixed ... it is not in the
tip code, but rather can be triggered by it rather easily.  For now, just
make sure you don't issue ^R to redraw the input line if you haven't typed
anything on the line yet.

milton

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

Date: Thu, 14 Jan 1993 09:44:38 CST
From: ben@val.val.com (Ben Thornton)
Subject: Terminal with NOS?
To: tcpgroup@ucsd.edu (TCP/IP Packet Radio Working Group)

> I am curious as to whether NOS could support a simple terminal on one
>comm port with the tnc on the other comm port. Then club members can
>use the shack's terminal to 'log in' to the mailbox just as they would
>over the air, with no chance of changing the system setup.

Yes, the most recent release of WG7J NOS v1.07 can support what is 
referred to as the TIP mailbox, which supports the use of an async 
port to access the NOS mailbox.  It can support a modem as well as 
a directly-connected terminal.  

I'm not sure if the compiled version distributed from from UCSD has 
this feature enabled, but you can obtain a copy from The Antenna Farm
BBS at (512) 444-1052.

>What variant of NOS should I use? I might have to use a PC Jr for the
>first little while to prove the concept. Will NOS run reliably on
>the Jr? Can NOS be stripped down to fit into the limited disk and
>memory space the Jr provides?
>
>Is this idea even feasable? I'd like to use NOS to introduce the local 
>packet group to it, but I'm open to suggestions if somthing else is
>more appropriate.
>

Hmmm...  NOS on a PCJr would probably NOT work, since it really needs
a 640K address space to run in.  In addition, I believe the async port
hardware on the Jr is not compatible with the standard PC-style design,
and NOS will not support this.

  Regards,

      Ben

--
Ben Thornton             packet:  wd5hls@wd5hls.ampr.org
Video Associates Labs  Internet:  ben@val.com
Austin, TX                 uucp:  ...!cs.utexas.edu!val!ben
"Push to Test --->@    ...Release to Detonate"

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

Date: Thu, 14 Jan 93 12:53:01 PST
From: pjb@hss.caltech.edu (Paul Brewer)
Subject: Using Terminal with JNOS 1.07
To: tcp-group@ucsd.edu

When I compiled the TIP server in, I got the following unusual operation:

When a caller called the phone port, he would get a login: prompt.
Upon answering the login prompt, he was immediately thrown into the 
conference bridge. If he exited the conference, he was loggde out.

It seemed to me that this was supposed to allow phoe access to the mailbox.
There are some if's in teh mailbox.c source that determine if an incoming
session goes to the conference or to the mailbox, and I suspect this must
be the problem. 

I would appreciate knowing which versions of JNOS (or perhaps KA9Q's new
net) the tip mailbox works correctly on. We actually plan to use this 
use this ona a dumb terminal for access to an internet/packet gateway 
system at our local radio club. I want people to use it from there without
becoming curious about the other control related commands.

73 de Paul KI6CQ
pjb@hss.caltech.edu (internet)
ki6cq@wb6ymh.#soca.ca.usa (packet)

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

Date: 15 Jan 93 05:36:37 CST
From: Jack Snodgrass <kf5mg@vnet.ibm.com>
Subject: Using Terminal with JNOS 1.07
To: <TCP-Group@UCSD.Edu>

pjb@hss.caltech.edu (Paul Brewer) writes:
>When I compiled the TIP server in, I got the following operation:
>When a caller called the phone port, he would get a login: prompt.
>Upon answering the login prompt, he was immediately thrown into the
>conference bridge. If he exited the conference, he was logged out.

That's a bug. I had the same problem. Thought that it was something
I might have done. Glad it was someone else. :) Lets see... mailbox.c
has mbx_incoming(). mbx_incoming() has a section of code that has
if((int) t & CONF_LINK) {
.
.
.
}

(int) t = m->type = the connection type identifier. Session.H has TIP
set to 10. LABP.H has CONF_LINK set to 8. So the command:
if((int) t & CONF_LINK)
answers for both TIP and CONF_LINK. That's why it starts. I fixed this by
changing it to:

if((int) t != TIP) {
   if((int) t & CONF_LINK) {
   .
   .
   .
   }
}

That seemed to fix it. I don't see the 'bye' message when I logout when
using TIPMAIL, but all the exit processing seems to get done, so I'm
not worrying about it. It may be another (t & CONF_LINK) problem or it
may have been something that I did.

73's  de  Jack - kf5mg
AMPRnet         -  kf5mg@kf5mg.ampr.org       - 44.28.0.14
AX25net         -  kf5mg@kf5mg.#dfw.tx.usa.na - work (817) 962-4409
Internet        -  kf5mg@vnet.ibm.com         - home (817) 488-4386

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

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