HDTenEightyP/NetNews huggingface dataset:
Newsgroups: vmsnet.networks.tcp-ip.cmu-tek
Subject: RE: IBM3270 emulation
From: "Michael L. Hitch" <osymh@trex.oscs.montana.edu>
Date: Wed, 27 Jan 1993 10:54:16 MST
Reply-To: osymh@trex.oscs.montana.edu
Organization: The Internet
Return-Path: <@andrew.cmu.edu:CMU-OpenVMS-IP-Request@drycas.club.cc.cmu.edu@mccall.com>
Resent-Date: Wed, 27 Jan 1993 10:54:16 MST
X-MX-Warning: Warning -- Invalid "Resent-From" header.
Resent-From: @andrew.cmu.edu:CMU-OpenVMS-IP-Request@drycas.club.cc.cmu.edu
Resent-Message-ID: <9301280047.AA11916@depot.cis.ksu.edu>
Errors-To: CMU-OpenVMS-IP-Request@drycas.club.cc.cmu.edu
Resent-Reply-To: CMU-OpenVMS-IP@drycas.club.cc.cmu.edu

"Henry W. Miller" <henrym@sacto.mp.usbr.gov> writes:
> uucm000@uxa.ecn.bgu.edu (Tingli Pan) writes:
>
> |Is there a way to emulate IBM termina 3270 on cmu-tek? (free package)
> |
> 	Not at present, but it's an idea whose time has come.

   Has anyone looked at trying to port a 3270 emulator for cmu-tek?  We now
have an IBM AS/400 on our network that only accepts 3270 protocol and I have
a couple of VMS users that would like access to the IBM.  We do have some
DECstations that will run tn3270, but it would be easier on some users to not
have to log onto another system just to get on the IBM.
   I have problems using tn3270 to get to the IBM, but I recently got another
3270 emulator from CERN that works much better.  I haven't looked at the code
yet to see how much effort it would take to port it to VMS.  If no one else is
looking at trying this, I may have to give it a try.

> 	CMUTEK is not free.  Cheap maybe, but not free.  And not easy,
> either.  That's a joke.

  I'll certainly agree with that!

Michael
---
Michael L. Hitch                        osymh@msu.oscs.montana.edu
Computer Consultant                     OSYMH@MTSUNIX1.BITNET
Office of Systems and Computing Services
Montana State University
Bozeman, MT     USA
Newsgroups: vmsnet.networks.tcp-ip.cmu-tek
Subject: RE: IPACP hogging CPU
From: "Andy, Systems Manager" <udaa055@oak.cc.kcl.ac.uk>
Date: Fri, 22 Jan 93 17:32 GMT
Reply-To: CMU-OpenVMS-IP@drycas.club.cc.cmu.edu
Organization: The Internet
Return-Path: <@andrew.cmu.edu:CMU-OpenVMS-IP-Request@drycas.club.cc.cmu.edu@mccall.com>
Errors-To: CMU-OpenVMS-IP-Request@drycas.club.cc.cmu.edu
Via: uk.ac.kcl.cc.oak; Fri, 22 Jan 1993 17:40:11 +0000

>Since I posted my message 'IPACP goes wild' a week ago, nobody has come back
>with any ideas as to what the problem might be, or how to start diagnosing
>it - BUT I have had mailings from two other people who are encountering
>the same thing.
>
>So if you have ANY light to shed on why IPACP should suddenly start hogging
>99.999% of the CPU for large periods of time, or ANY ideas about how to start
>diagnosing the problem, there are at least three of us who would be very glad
>to hear from you.

This problem is, I believe, due to a coding error within the IPACP that causes
it to react badly to certain error conditions.  I had this problem with 6.6-5
and a patched version is available (6.6-5A) which works fine.  I got my patch
from Henry Miller and you might care to ask him how to access it. It's one of
several useful updates to 6.6-5 but I'm not sure if Henry's sufficiently happy
with the results to make them generally available, so I won't give details
here.. If he's listening, he'll doubtless update this information to the list.

By the way, I can't speak for versions other than 6.6-5! I don't think the same
problem existed in 6.6-x (x <5) but I'm not positive.


Regards,

Andy Harper
Kings College London
Newsgroups: vmsnet.networks.tcp-ip.cmu-tek
Subject: RE: Vms 5.5 and Cmutek 6.6 ??
From: "Michael L. Hitch" <osymh@trex.oscs.montana.edu>
Date: Wed, 27 Jan 1993 10:57:23 MST
Reply-To: osymh@trex.oscs.montana.edu
Organization: The Internet
Return-Path: <@andrew.cmu.edu:CMU-OpenVMS-IP-Request@drycas.club.cc.cmu.edu@mccall.com>
Resent-Date: Wed, 27 Jan 1993 10:57:23 MST
X-MX-Warning: Warning -- Invalid "Resent-From" header.
Resent-From: @andrew.cmu.edu:CMU-OpenVMS-IP-Request@drycas.club.cc.cmu.edu
Resent-Message-ID: <9301280100.AA12437@depot.cis.ksu.edu>
Errors-To: CMU-OpenVMS-IP-Request@drycas.club.cc.cmu.edu
Resent-Reply-To: CMU-OpenVMS-IP@drycas.club.cc.cmu.edu

"Henry W. Miller" <henrym@sacto.mp.usbr.gov> writes:
> tnuug@alyssa.rsinet.tn (TN.U.U.G) writes:
>
> |CMUTEK V6.6 still works with UNIX machines but doesn't work with PC's .
> |I don't know why ? can you explain me the bug please ?
> |Is there any solution ?
> |your help will be very appreciated.
>
> 	Can you be a little more specific?  What portion does not work PC's?

  I have heard reports that the current version of NCSA Telnet doesn't work
with V6.6-5, although I have not verified it yet (I still have an older version
of NCSA Telnet on my PC).  I'll see if I can get more information on what the
problem is.

Michael
---
Michael L. Hitch                        osymh@msu.oscs.montana.edu
Computer Consultant                     OSYMH@MTSUNIX1.BITNET
Office of Systems and Computing Services
Montana State University
Bozeman, MT     USA
Newsgroups: vmsnet.networks.tcp-ip.cmu-tek
Subject: RE: CMU-OpenVMS-IP status
From: Peter Kobe <system@pib1.physik.uni-bonn.de>
Date: Thu, 28 Jan 1993 11:30:56 MEZ
Reply-To: CMU-OpenVMS-IP@drycas.club.cc.cmu.edu
Organization: The Internet
Return-Path: <@andrew.cmu.edu:CMU-OpenVMS-IP-Request@drycas.club.cc.cmu.edu@mccall.com>
Errors-To: CMU-OpenVMS-IP-Request@drycas.club.cc.cmu.edu

Henry Miller writes:

>CMU approached me several months ago about taking over support of
>the product after the end of 1992.  I agreed.  John Clement and Tom
>Allebrandi are working with me.

That is very good news. So we see the product is in good and very busy!
hands and we should wish Henry, John and Tom much success with their work
Good luck to them.

>	I am planning to throw in a HOSTTABLE utility.  My current plans
>are to make it another subfunction of IPNCP.  Any feedback on this?

That is a good idea. though one can live with the current status.
To have NFS running without problems is from my point of view the
more neccessary work to be done.

Peter


=====================================================================
Peter Kobe			Internet: system@pib1.physik.uni-bonn.de
Physikalisches Institut	          HEPNET: 13562::SYSTEM
Universitaet Bonn	             Tel: (49) 228 73 3222
D 53 Bonn		             FAX: (49) 228 73 7869
Nussallee 12
Newsgroups: vmsnet.networks.tcp-ip.cmu-tek
Subject: EGADS.... How embarrassing...
From: "Tim McKee, 803-366-2620" <mckeetr@cvse.cortex.prospect.com>
Date: Mon, 25 Jan 1993 13:30:37 EST
Reply-To: CMU-OpenVMS-IP@drycas.club.cc.cmu.edu
Organization: The Internet
Return-Path: <@andrew.cmu.edu:CMU-OpenVMS-IP-Request@drycas.club.cc.cmu.edu@mccall.com>
Errors-To: CMU-OpenVMS-IP-Request@drycas.club.cc.cmu.edu

Group:

Please accept my humblest and most contrite apologies...  I GOOFED!

The previous posting was intended to be a response to an individual,
not to most of the civilized world.

[I will supply the wet noodles for all of you to lash me with...]

tim mckee
================================================================================
Timothy R. McKee                        |  Senior Consultant - VAX/VMS Internals
Cortex Corp. - SouthEast Field Office   |       mckeetr@cvse.cortex.prospect.com
Phone: (803) 366-2620                   |                    FAX: (803) 366-6517
================================================================================
From: newsmgr@logica.co.uk
Newsgroups: vmsnet.networks.tcp-ip.cmu-tek
Subject: Re: CMU-OpenVMS-IP status
Date: 26 Jan 93 12:03:51 GMT

In article <9301251734.AA16409@phcoms.seri.philips.nl>, <roes@phcoms.seri.philips.nl> writes:
> 
> Volunteers? Any other thoughts how to stimulate this product? Or am I just
> plain wrong and is everything ok? Reactions please!
> 
>      Aloys Roes

We originally obtained CMU because we wanted to be able to ping vaxes from our 
network management system, and we were delighted when we found how much more 
we could do with it.  I think we have just outgrown it now, at least on one 
or two machines.

I think it would be a great pity if the remaining bugs did not get fixed.  I'm
sure that they aren't that difficult to fix (for someone that knows the code):
I mean I don't get the feeling that the code is riddled wioth problems, it just
seems to need a little attention in one or two specific areas.  Frankly I think
that it would have been good if the release of CMU into the public domain could
have been handled a bit more smoothly: it seems at least to an outsider that
once the decision was taken, the code was bundled out of the door as fast as
the name could be changed, and I feel a bit let down by that - in the sense
that it does not match up to the level of support that I had come to
expect from CMU, which I fully accept I had no right to insist on.  Anyway, 
no doubt there were factors at work at CMU that prevented a smoother release,
but the people who have put effort into supporting the code over the years must
be feeling a bit sorry about the way it has happened...

Had I a Bliss compiler, I'd be looking at at least some of the problems.  But
few people seem to have Bliss compilers, and this must be one of the issues
facing the future of the package.  Let's face it, not many people are buying
Vaxes these days, and the performance is also pretty slow compared to the
commercial offerings.  So, if you'll permit me to overstate the case for
dramatic effect, we have a slow package written for an ageing platform in an
obsolete langauge.  I think that the best thing would therefore be if we could
find some way of getting the outstanding bugs fixed so that there is a rock
solid documented release, rather than looking at extended functionality. 

IF we can agree upon a list of things to fix and someone who can do the work, I
would be prepared to make a modest financial contribution to get the bugs
fixed.  Perhaps others feel the same way.  If so maybe we could get enough
money together to get the problems sorted and put a really stable version into
the public domain.

William Lees
newsmgr@logica.co.uk
Newsgroups: vmsnet.networks.tcp-ip.cmu-tek
Subject: CMU QUESTIONS
From: David Staschover <73240.536@compuserve.com>
Date: 25 Jan 93 14:01:18 EST
Reply-To: CMU-OpenVMS-IP@drycas.club.cc.cmu.edu
Organization: The Internet
Return-Path: <@andrew.cmu.edu:CMU-OpenVMS-IP-Request@drycas.club.cc.cmu.edu@mccall.com>
Errors-To: CMU-OpenVMS-IP-Request@drycas.club.cc.cmu.edu

Hi,

I have a few questions about CMU IP 6.6 for VMS. I'm not sure if this is the
right address to ask questions, but I'll give it a shot.

1) FTP seems awfully slow. I tried transferring a 1 mbyte file between an
RS6000 and our MicroVax 3600, and it was sending (it seemed) slower than
2400 baud. Any tuning ability?

2) TELNET seems to delay once in a while.

3) I started printing the .ps doc file, and it started to cut off on the
right side of the page.  I was using the dos copy command to a postscript
printer.  Is there a way to fix this, or are the docs available in straight
ascii format?

Thanks!

David Staschover
From: newsmgr@logica.co.uk
Newsgroups: vmsnet.networks.tcp-ip.cmu-tek
Subject: 6.6-5A has problems too
Date: 26 Jan 93 04:10:48 GMT

First of all, many thanks to those of you who replied to my plea for help with
IPACP consuming excessive CPU.  The advice I received fell into two categories:
install IPACP 6-5A, or go for a commercial package.

I installed 5A on my systemyesterday, but I got out of bed just now and took it
off.  It gave MX serious problems: outgoing messages were aborting because no
apparent response was received from the other end after a line or two of the
header, and incoming messages were aborting after a line or two of the header
with 'status code 2C'.  These aborts were happening about one time in two. 
With the previous IPACP (6-5) back in place, the problem has gone away.

When I get to work tomorrow I think I've got to get myself a commercial
package...


William Lees
newsmgr@logica.co.uk
Newsgroups: vmsnet.networks.tcp-ip.cmu-tek
Subject: Re: IPACP quotas
From: FRASER_H@eismv3.dofasco.ca (Hugh Fraser)
Date: Mon, 25 Jan 1993 08:54:42
Organization: Dofasco Inc.

In article <289@moretonp.demon.co.uk> Peter S Moreton <peter@moretonp.demon.co.uk> writes:
>Hey, you say that the IPACP starts from the SYSTEM account and it
>has EXQUOTA. Bear in mind that EXQUOTA allows an account to exceed
>diskquota limits and has nothing to do with normal process quotas
>such as pgflquo etc. If your problem is a virtual memory thing, I
>would double PGFLQUO, double VIRTUALPAGECNT in Modparams.dat and
>AUTOGEN the system. (maybe extend pagefile.sys also, but autogen should
>do this).

Thank's for reminding me of that. I'll try adjusting the sysgen parameters.  
We already have VIRTUALPAGECNT quite high (120000) for other reasons, so I'll 
play with PGFLQUO.
From: judson@phakt.usc.edu (Tom Judson)
Newsgroups: vmsnet.networks.tcp-ip.cmu-tek
Subject: where can I get CMU-OpenVMS-IP?
Date: 25 Jan 1993 12:05:52 -0800
Organization: University of Southern California, Los Angeles, CA
Distribution: world
NNTP-Posting-Host: phakt.usc.edu


I guess the subject says it all, where can I get CMU-OpenVMS-IP?
I currently do not have any TCP/IP software and our machine is
running VMS 5.5.

Thanks for any info,
-TJ Judson
judson@usc.edu
judson@hac2arpa.hac.com
Newsgroups: vmsnet.networks.tcp-ip.cmu-tek
Subject: RE: Telnet problem
From: "Tim McKee, 803-366-2620" <mckeetr@cvse.cortex.prospect.com>
Date: Mon, 25 Jan 1993 12:33:02 EST
Reply-To: CMU-OpenVMS-IP@drycas.club.cc.cmu.edu
Organization: The Internet
Return-Path: <@andrew.cmu.edu:CMU-OpenVMS-IP-Request@drycas.club.cc.cmu.edu@mccall.com>
Errors-To: CMU-OpenVMS-IP-Request@drycas.club.cc.cmu.edu

I just got a request for the saveset from <COURRIER@IRCM.UMontreal.CA>
and told her that I would ftp it to her if she could give me an ftp
login.  The offer is open, I can send it to you also...

Just give me an ftp login and instructions and I will take care of it
this afternoon!

(I am not allowed to provide external access to the company machine...)

tim
================================================================================
Timothy R. McKee                        |  Senior Consultant - VAX/VMS Internals
Cortex Corp. - SouthEast Field Office   |       mckeetr@cvse.cortex.prospect.com
Phone: (803) 366-2620                   |                    FAX: (803) 366-6517
================================================================================
Newsgroups: vmsnet.networks.tcp-ip.cmu-tek
Subject: RE: Wollongong emulation
From: "Henry W. Miller" <henrym@sacto.mp.usbr.gov>
Date: Tue, 26 Jan 1993 01:50:43 EST
Reply-To: CMU-OpenVMS-IP@drycas.club.cc.cmu.edu
Organization: The Internet
Return-Path: <@andrew.cmu.edu:CMU-OpenVMS-IP-Request@drycas.club.cc.cmu.edu@mccall.com>
CC: henrym@sacto.mp.usbr.gov
Errors-To: CMU-OpenVMS-IP-Request@drycas.club.cc.cmu.edu

david@ittpub.nl (David P. Morgan) writes:

|Can CMU be made to emulate Wollongong ?
|
|I ask because we need to run Ingres over TCP/IP and it only supports
|UCX and Wollongong. I'm told that Multinet has a W. emulation mode for
|situations like these.
|
	It is still not clear to me exactly what the "ingres" mode is.  I know
that Ingres uses a specific WKS port for something or other, but it's never
been any clearer to me than mud as to exactly what it does.  After talking to
a number of people, I get the distinct impression of, politely, a smoke and
mirror job.

	I don't know if Brian's package can be layered over CMUTEK to provide
an interface to the Ingres port.  I really doubt that Ingres would even attempt
to look at certifying it.  It took a hell of a lot of public pressure and about
two years to get Ingres to certify Multinet, and TGV is without question the
leading TCP/IP product for VMS.

	If anyone can give us some of the internals of the Ingres interface,
I'm certain we can look at it, but again the chances of Ingres certifying it,
unless there is a MASSIVE amount of pressure put upon by the CMUTEK community,
are between slim and none.

	Best,

-HWM
----------
Henry W. Miller
Assistant Systems and Network Manager
U.S. Bureau of Reclamation
Mid Pacific Region
2800 Cottage Way MP1100
Sacramento, CA 95825
(916) 978-5108 / FTS - Same as commercial
Inet:	"henrym@sacto.mp.usbr.gov"

"I've fallen, and I can't get up!"
Newsgroups: vmsnet.networks.tcp-ip.cmu-tek
Subject: RE: EGADS.... How embarrassing...
From: Helen Theresa Lucy Smit Kirchen <kirchen@vax1.elon.edu>
Date: Wed, 27 Jan 1993 14:09:39 EST
Reply-To: CMU-OpenVMS-IP@drycas.club.cc.cmu.edu
Organization: The Internet
Return-Path: <@andrew.cmu.edu:CMU-OpenVMS-IP-Request@drycas.club.cc.cmu.edu@mccall.com>
Errors-To: CMU-OpenVMS-IP-Request@drycas.club.cc.cmu.edu

i, being very nosy, like the mail to go to everyone, so that i may learn
and see what is happening.  CMU-OpenVMS is our lifeline to everywhere.

thank you all that work to keep it going!

terri

Terri Kirchen, Academic Computing, 2306 Campus Box, Elon College NC 27244-2020
U.S.A.          (919) 584-2295                           kirchen@vax1.elon.edu
Newsgroups: vmsnet.networks.tcp-ip.cmu-tek
Subject: RE: EGADS.... How embarrassing...
From: "John F. Sandhoff" <syssand@ccvax.ccs.csus.edu>
Date: Wed, 27 Jan 1993 11:39:50 PST
Reply-To: sandhoff@csus.edu
Organization: The Internet
Return-Path: <@andrew.cmu.edu:CMU-OpenVMS-IP-Request@drycas.club.cc.cmu.edu@mccall.com>
Resent-Date: Wed, 27 Jan 1993 11:39:50 PST
X-MX-Warning: Warning -- Invalid "Resent-From" header.
Resent-From: @andrew.cmu.edu:CMU-OpenVMS-IP-Request@drycas.club.cc.cmu.edu
Resent-Message-ID: <9301280327.AA16981@depot.cis.ksu.edu>
CC: syssand@ccvax.ccs.csus.edu
Errors-To: CMU-OpenVMS-IP-Request@drycas.club.cc.cmu.edu
Resent-Reply-To: CMU-OpenVMS-IP@drycas.club.cc.cmu.edu


> Yes I know the "old" mailing list replied only to the sender, while the
> new replies to the world.

> Perhaps the old way should be resurrected???  Or do people prefer this way???

My vote is for the new way, for a couple of reasons:

When a question is answered, unless it's *very specific*, it's nice to
see followups. That's a major reason for this list, IMHO - so we can try
to help each other (especially since there's nobody else any more :-) )

Also, my mail headers make it clear, by the 'From' address, that the
message is CMU/Open related. This allows 'smart' mailers to auto-sort
incoming mail, etc.


    John F. Sandhoff, University Network Support
      California State University, Sacramento - USA
        sandhoff@csus.edu
Newsgroups: vmsnet.networks.tcp-ip.cmu-tek
Subject: RE: GATEWAY configuration
From: "Henry W. Miller" <henrym@sacto.mp.usbr.gov>
Date: Tue, 26 Jan 1993 05:12:52 EST
Reply-To: CMU-OpenVMS-IP@drycas.club.cc.cmu.edu
Organization: The Internet
Return-Path: <@andrew.cmu.edu:CMU-OpenVMS-IP-Request@drycas.club.cc.cmu.edu@mccall.com>
CC: henrym@sacto.mp.usbr.gov
Errors-To: CMU-OpenVMS-IP-Request@drycas.club.cc.cmu.edu

"Andy (Harper), Systems Manager" <UDAA055@elm.cc.kcl.ac.uk> writes:

|Does anyone know what algorithm CMU uses to choose a gateway (router) for
|routing if more than one is configured in?  We have two configured (one as a
|backup) and CMU doesn't appear to use them as I might expect. For instance, if
|both are up and working, CMU routes all traffic through the one that appears
|first in the configuration file. Disconnecting this router should result in
|packets going automatically through the other one (the second one configured),
|without the need for reconfiguration. What seems to happen though, is that CMU
|is unable to recognize the alternate one - it just hangs waiting for the first
|to come back.
|

Andy,
	Yes!  What happens is that the route is hashed into a table based
upon the destination address.  Therefore, the second router would have
hash index n+1, or probably entry 1 in the table.  I can very well believe
that it won't step to the next route in the tbale.  The routing code does
need some work.  There is also a problem in that if you have a primary router,
and it goes down and receives an ICMP redirect from another router, it will
not revert to the primary route once the primary router comes back online.
Clearly, without eschewing routing philosophy, as I am close to falling on
my face tired and I do not want to pump my system up with another Pepsi (the
choice of hackers everywhere) the case of ICMP based routes needs a "drop dead"
timer to cache them out after a period of time.  And, of course mutiple routes
to the same (sub)/(super) network need to be handled.

|Now I don't know what the rules say about multiple routers, and I can't find
|any info about what ought to happen in the CMU documentation. I'ld be very
|grateful if someone could succintly summarize the algorithm and, if it differs
|from how mine appears to work, suggest what might be wrong.
|
	Nothing wrong with your philospohy, Andy, it just don't work in the
current version.  Heck, while I'm in there, I'll see about finishing the
ICMP destination unreachable, so TRACEROUTE to a CMU host will work.

|Version Info:   VMS 5.5-2, CMUtek (pre-open version) 6.6-5A,
|
|Extract from INET$CONFIG:
|
|; Define the gateways known to the system.
|; Gateway:gwyname:gwyaddr:gwynet:gwynetmask
|Gateway:cis-1.kcl.ac.uk:137.73.2.30:0.0.0.0:0.0.0.0
|Gateway:ecb.kcl.ac.uk:137.73.2.23:0.0.0.0:0.0.0.0
|

-HWM
----------
Henry W. Miller
Assistant Systems and Network Manager
U.S. Bureau of Reclamation
Mid Pacific Region
2800 Cottage Way MP1100
Sacramento, CA 95825
(916) 978-5108 / FTS - Same as commercial
Inet:	"henrym@sacto.mp.usbr.gov"

"I've fallen, and I can't get up!"
Newsgroups: vmsnet.networks.tcp-ip.cmu-tek
Subject: <None>
From: courrier@ircm.umontreal.ca
Date: Mon, 25 Jan 93 08:36 EDT
Reply-To: CMU-OpenVMS-IP@drycas.club.cc.cmu.edu
Organization: The Internet
Return-Path: <@andrew.cmu.edu:CMU-OpenVMS-IP-Request@drycas.club.cc.cmu.edu@mccall.com>
Errors-To: CMU-OpenVMS-IP-Request@drycas.club.cc.cmu.edu
X-Vms-To: IN%"CMU-OpenVMS-IP@DRYCAS.CLUB.CC.CMU.EDU"


I would like to know, who sale the package you were talking,
it is very interesting.

Thanks

Louise Labonte
System manager