home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
GRIPS 2: Government Rast…rocessing Software & Data
/
GRIPS_2.cdr
/
dos
/
ncsa_tel
/
digests
/
v1.06
< prev
next >
Wrap
Text File
|
1990-12-29
|
5KB
|
151 lines
NCSA Telnet Digest Friday, 30 Oct 1987 Volume 1 : Issue 6
Today's Topics:
System 4.1 and Keyboard Mapping
Blinking with the Bell
PC IO Addresses
NCSA Telnet, KIP, and Subnets
Subject: Re: NCSA Telnet, KIP, and subnets
Subject: Re: NCSA Telnet, KIP, and subnets
----------------------------------------------------------------------------
From: hpoppe@scdpyr.UCAR.EDU (Herb Poppe)
Subject: Re: NCSA Telnet 2.0 for the Macintosh comments
Gaige:
1) I switched to System 4.1 on the Plus and the problem with Telnet
not recognizing "option" as "control" disappeared. Perhaps you could
mention that System 4.1 is required in the Preface under "System
Requirements".
Thanks for the info.
2) However, the old, separate numeric keypad still does not work correctly.
You did not indicate whether I should expect it to. Will you be able
to support this device?
There must be a mechanism to specify the "arrow keys" versus "+", "*"
"/" ",". VersaTerm uses "command-arrowkey" to do this.
Thanks, Herb.
----------------------------------------
From: :marisa@cpa (MARISA@OAK.CADIF.CORNELL.EDU)
Date: Wed, 21 Oct 87 16:57:29 edt
Subject: blinking screen on bell
I vote to remove the blinking screen when bell characters are received,
(or make it an option, as suggested.)
Rich Marisa
Cornell Manufacturing Engineering and Productivity Program
----------------------------------------
From: "Michael A. Shiels" <mshiels%orchid.waterloo.edu@RELAY.CS.NET>
Date: Wed, 28 Oct 87 10:05:35 EST
Subject: PCTEL20.ARC
I have a copy of this now and it looks great but I can't get
it to run since I don't have a way to configure the IO port??
Any ideas?? Any undocumented configuration parameters??
Can someone tel me the locations to patch??
------------------------------------------------------
[Ed Note -
[ The following messages taken from info-appletalk because of their
[ interest to the group.
[ Gaige ]
From: saturn!saturn.ucsc.edu!brad@jade.Berkeley.EDU
Subj: NCSA Telnet, KIP, and subnets.
Date: 27 Oct 87 03:06:44 GMT
Does anyone know how to get NCSA Telnet to access a subnet of
a class B net (i.e. subnet mask 255.255.255.0)? I have tried
all kinds of values in the "Use Subnetting Mask" box of NCSA
Telnet version 2.0 (a great piece of software at the perfect
price!), including "ffffff00", "ff.ff.ff.0", "0xff.0xff.0xff.0",
all of the previous with "F"s, and 255.255.255.0. All cases
seem to have no effect; from what I can see (with tcpdump on
a Sun) it looks like the Kbox catches the packet, makes its own
decision as to whether it is going to a different network (which
doesn't detect subnets) and arps for the host on the attached
Ethernet (which the host isn't attached to).
The Kbox is running release # 5 of the KIP code (I assume...
the srec file I load to it is "at-gw.srec.5").
Any help will be greatly appreciated,
Brad Smith
System Administrator
CIS Board, UC Santa Cruz
brad@saturn.ucsc.edu
----------------------------------------------------------------
From: gaige@ncsa.uiuc.edu
Subj: RE: NCSA Telnet, KIP, and subnets.
Date: Wed, 28 Oct 87 09:13:39 CST
Brad,
NCSA Telnet attempts to route packets to the best of its ability, but as
far as the K-Box is concerned it has no say in the matter (although this
feature does work with the EtherSC, EtherPortSE, and EtherTalk cards).
Since I have a very similar networking problem, I know what you are going
though, I was unable to find an "off the shelf" gateway that would handle
class B with 8 bit subnets and no promiscuous gateways. To the rescue comes
the KIP code. Although it doesn't handle the subnetting correctly by default,
source code is available, so a small tweaking of the code makes routing
more effective.
Good luck!
Gaige B. Paulsen
National Center for Supercomputing Applications
University of Illinois
gaige@ncsa.uiuc.edu
--------------------------------------------------------
Date: Fri, 30 Oct 87 10:22:08 CST
Message-Id: <8710301622.AA05292@lurch.ncsa.uiuc.edu>
Subject: Re: NCSA Telnet, KIP, and subnets
The current format for NCSA Telnet subnet masks is eight hexidecimal digits
indicating an actual bit mask for the IP number. The most common example,
for a class B net with eight bits of subnetting is "ffffff00", which happens
to be the same as class A, sixteen bits of subnet. Similarly, class A with
eight bits is "ffff0000."
It is important to note that if the kinetics box stradles subnets (has one
IP net number on the ethernet side and a different one on the AppleTalk side),
the AppleTalk side of the Kinetics box must be specified as a gateway in the
config.tel file. An example of this is a KBox running the combined gateway from
kinetics with 128.174.20.1 Ethernet and 128.174.22.1 AppleTalk. Assuming a
class B, eight bit subnet, the subnet mask would be "ffffff00" and the following
entry should be in the config.tel:
name=Kbox hostip=128.174.22.1 gateway=1
I hope this helps,
Gaige B. Paulsen
National Center for Supercomputing Applications
University of Illinois
gaige@ncsa.uiuc.edu