Hello!
Many thanks to those who responded namely:
J. Dubois (Analog S.I.)" <j_dubois_at_digital.ca>
Scott Ruch - DTN 462-6082 <swr_at_unx.dec.com>
RONNY_at_CSMC.EDU
system_at_pslaxp.nmsu.edu
Stephen Beck <beck_at_CS.Princeton.EDU>
Selden E Ball Jr <SEB_at_LNS62.LNS.CORNELL.EDU>
"E. Niederacher" <niederacher_at_morrow.tvlbg.ac.at>
>Am currently trying to configure a particular port (say port 1) for SLIP
>connectivity. Don't have the corresponding manuals on hand --
>so I just logged in to the terminal server, set priv-ed and was brought
>in to the Local> prompt.
>Tried help command and tutorial (on how to configure it as SLIP) and am
>somewhat faced by this error message below:
>Local> CHANGE PORT 1 SLIP HOST (ip.address)
>Local> CHANGE PORT 1 FLOW CONTROL DISABLED
>Local> CONNECT SLIP
>Local -550- SLIP not enabled on that port
>Local> connect port 1 slip
>Local -702- Keyword "SLIP" not known or ambiguous
>Local> CONNECT SLIP
>Local -550- SLIP not enabled on that port
>Local> CONNECT PORT 1 SLIP
>Local -702- Keyword "SLIP" not known or ambiguous
Seems that I indeed missed much..
Selden Ball's Comments:
======================
The server needs to have its own internet address.
Each port has its own address as well.
The subnet mask applies to all.
A port's address must be in the same subnet as the server's address.
(When you configure SLIP on the system using a port, that system has to
be told to use the server as its gateway.)
You need to define one or more gateways in the terminal server
so it can connect to other systems.
(i.e. You need to tell the terminal server how to access other subnets.)
Since the DECserver700 does not support individual user authentication,
you must NOT allow it to access addresses outside your local domain.
This is because access to other networks must be auditable in case
of problems
Here's the configuration of one of our SLIP-capable ports:
lOCAL> sho port 16 char
Port 16: Server: DS7WLF
Character Size: 8 Input Speed: 9600
Flow Control: CTS Output Speed: 9600
Parity: None Signal Control: Enabled
Stop Bits: Dynamic Signal Select: CTS-DSR-RTS-DTR
Access: Local Local Switch: None
Backwards Switch: None Name: PORT_16
Break: Local Session Limit: 4
Forwards Switch: None Type: Ansi
Default Protocol: LAT
Preferred Service: None
Authorized Groups: 0
(Current) Groups: 0
Enabled Characteristics:
Autobaud, Autoprompt, Broadcast, Dialup, Failover, Inactivity Logout,
Input Flow Control, Lock, Loss Notification, Message Codes, SLIP,
Output Flow Control, Verification
===================
Notes:
1. hardware flow control is required, otherwise you'll get lots
of errors due to lost bytes. DEC sells special 'high speed' modem
cables which are unique to the 700. You need them.
2. if you need to switch from normal terminal use (LAT or TELNET)
to SLIP (i.e. dialin, then C SLIP), then the port's SLIP address must
be just DEFINEd, not SET or CHANGEd.
In the example below, the SLIP port (16) is inactive.
(I've put in dummy letters for the actual addresses. sorry.)
Local> sho port 16 slip
Port 16: Server: DS7WLF
Host Address: 0.0.0.0 MTU: 1006
Local> list port 16 slip
Port 16: Server: DS7WLF
Host Address: 128.84.xxx.sss MTU: 1006
============
( 128.84.xxx.sss above is the port's address)
( 128.84.xxx.xxy below is the server's address)
( 255.255.255.0 is our subnet mask)
If TCP/IP is enabled, you can look at the various server characteristics
related to its use. For example:
Local> Show internet
Internet Address: 128.84.xxx.xxy
Subnet Mask: 255.255.255.0
Local> sho inter gate
Gateway: 128.84.xxx.hhh Host: 128.84.xxx.hhh
Gateway: 128.84.xxx.ggg Network: 128.84.xxx.0 Mask: 255.255.255.0
Gateway: 128.84.xxx.ggg Network: 128.84.yyy.0 Mask: 255.255.255.0
Local> sho inter host
Internet Address Name
128.84.yyy.hhh LNShhh
128.84.yyy.iii LNSiii
Local> sho inter arp ent
Internet Address Ethernet Address Status
128.84.xxx.ggg aa-bb-cc-dd-ee-ff
=================
Local> sho inter cou
TCP Segments:
Transmitted: 16143 Bytes Transmitted:
10865
Data: 6921 Bytes Data:
10857
Data Retransmitted: 3 Bytes Data
Retransmitted: 8
Other: 9219 Bytes Received:
1246961
Received: 12090
Segments Discarded: 0
Internet Connections:
IP Packets Transmitted: 419458 Requested: 21
IP Packets Received: 415422 Accepted:
IP Fragments Received: 0 Established: 21
IP Fragments Dropped: 0 Closed: 21
IP Error in Header: 0 Dropped: 0
ICMP Messages: UDP Datagrams:
Transmitted: 13 Transmitted: 0
Received: 18 Received: 0
Dropped: 0 Dropped: 0
Destination Unreachable: 0
>From system_at_pslaxp.nmsu.edu
===========================
If I recall correctly, once you configure the server for SLIP/CSLIP/PPP you
have to reboot the server to have it take effect.
>Do I still have to configure something on the Alpha? Am currently on a
>v2.0b.
No special configuration needs to be done on on any of the systems
that the terminal server is to be used with.
Followup question:
>Is it possible on a DEC700 to configure in such a way that a particular
>port can be assigned to a particular tty (or the other way around using
LAT).
>From Scott Ruch <swr_at_unx.dec.com>:
=================================
Using LAT, there are 2 ways to do this:
1) define a service for each tty, bind each tty to a particular service, and
set the port to auto-connect to the service which corresponds to the tty
you want.
2) define an application port which points to a particular server/port. Then
when you run a getty on that tty, it will connect to the port and wait for
a login. This method is less reliable as you may experience problems with
certain modem set-ups and terminal server types.
The first method is "recommended". Since you don't have a lot of modems, it
shouldn't be a problem.
Received on Fri Jun 16 1995 - 10:29:15 NZST