HP OpenVMS Systems Documentation
Compaq TCP/IP Services for OpenVMS
This section describes the TELNET/AUTHENTICATE command.
/AUTHENTICATEOptional. Default: None.
Specifies that you want the TELNET session to use Kerberos features.
The /AUTHENTICATE qualifier also can be used with the TELNET commands OPEN and CONNECT.
/NOFORWARDOptional. Default: /NOFORWARD.
Forwards a copy of your Kerberos tickets to the remote host. The /NOFORWARD qualifier overrides any forwarding specified in your machine's configuration files. You must request forwardable tickets at the same time that you issue the KINIT command.
You must use the /AUTHENTICATE qualifier when you specify the /FORWARD qualifier.
Requests Kerberos tickets for the remote host in the specified realm, instead of determining the realm itself.
You must use the /AUTHENTICATE qualifier when you specify the /REALM qualifier.
$ TELNET/AUTHENTICATE/REALM=jet.mbs.com terse %TELNET-I-TRYING, Trying ... 15.21.308.11 %TELNET-I-SESSION, Session 01, host terse, port 23 %TELNET-I-ESCAPE, Escape character is ^] terse.ucx.ttg.mbs.com
This example logs in to system terse with Kerberos credentials.
$ TELNET/AUTHENTICATE/FORWARD terse %TELNET-I-TRYING, Trying ... 15.21.308.11 %TELNET-I-SESSION, Session 01, host terse, port 23 %TELNET-I-ESCAPE, Escape character is ^] [Kerberos V5 accepts you as ''firstname.lastname@example.org'' ] [Kerberos V5 accepted forwarded credentials ]
This example forwards credentials to host terse for user j_brown .
1.5.3 Configuring the Kerberos TELNET Server
This version of TCP/IP Services supports a separate Kerberos TELNET
server, in addition to the standard TCP/IP TELNET server.
The Kerberos TELNET server has the same major features as the TCP/IP Services TELNET server. However, there are minor differences between the two servers. For example, although the TELNET server supports IPv6 connections, the Kerberos TELNET server supports only the IPv4 protocol for communication with the Kerberos Key Distribution Center (KDC).
The TELNET server with Kerberos support is enabled by running the TCPIP$CONFIG.COM command procedure, as described in the Compaq TCP/IP Services for OpenVMS Installation and Configuration guide.
If the TELNET server is currently enabled and you want to support Kerberos, you must disable the TELNET service before you install this version of TCP/IP Services to ensure that the required TCPIP$TELNET user account and directory are created.
Because the TELNET server will be stopped, do not use a TELNET connection to perform the following procedure.
To disable the Kerberos TELNET server, perform the following steps:
For instructions on how to enable the Kerberos TELNET server, refer to
the Compaq TCP/IP Services for OpenVMS Installation and Configuration manual.
126.96.36.199 Connecting to the Kerberos TELNET Server
The Kerberos TELNET server uses port 2323. Specify this port on the TELNET command line. For example:
$ TELNET/AUTHENTICATE terse.mbs.com /PORT=2323 %TELNET-I-TRYING, Trying ... 188.8.131.52 %TELNET-I-SESSION, Session 01, host terse.mbs.com, port 2323 -TELNET-I-ESCAPE, Escape character is ^] Welcome to OpenVMS (TM) Alpha Operating System, Version V7.3 Username:
TCP/IP Services supports UNIX subsystems and allows you to modify the attributes of those subsystems to change the way the TCP/IP Services software operates.
Subsystem configuration is provided for compatibility with Compaq Tru64 UNIX. Compaq strongly advises you not to modify the attributes associated with subsystems except when the adjustment of an attribute is indicated (for example, to improve performance). In most cases, corresponding TCP/IP management commands are provided to help limit the side effects of modifying subsystem attributes.
The following sections describe how to display and modify the settings
of the subsystem attributes. Modifying subsystem attributes without
full knowledge of possible effects can cause unpredictable results and
is recommended only as specifically directed by Compaq.
1.6.1 Displaying Subsystem Attributes and Values
You can use the sysconfig -m command to display static and dynamic subsystems, as follows:
$ TCPIP TCPIP> sysconfig -m cm: static inet: static iptunnel: static ipv6: static net: static snmpinfo: static socket: static inetkvci: static proxy: static nfs: static vfs: static
Depending on the configuration of your system, the list of subsystems displayed may differ from this example. There are two types of subsystems:
Subsystems can be loaded but not available for use. To determine which subsystems are loaded, use the sysconfig -s command. This command displays the state of all subsystems. Subsystems can have the following states:
You can modify subsystem attributes at runtime, a change that will persist only as long as the system continues to run, or you can modify them in the system configuration table, preserving the changes through system reboots.
The persistence of a modified attribute value depends on the command or utility option you use, according to the following guidelines:
To modify subsystem attributes so that changes persist across reboots, you must store the attribute's value in the system configuration table (TCPIP$ETC:SYSCONFIGTAB.DAT). This file is an ASCII text file, and is formatted in UNIX stanza file format. When a subsystem is loaded, the attributes that are not listed in the SYSCONFIGTAB.DAT file are set to their default values.
To modify subsystem attributes in the SYSCONFIGTAB.DAT file, follow these steps:
Although you can edit the SYSCONFIGTAB.DAT file with any text editor,
this practice is strongly discouraged. Syntax errors introduced when
you edit the file can result in erroneous or unpredictable situations.
Compaq recommends that you use the
utility to display the system configuration table and the
utility to modify its contents.
184.108.40.206 Creating a Stanza File
To add, update, or remove entries in the database, create a stanza file that contains the names and values for attributes that you want to modify.
The syntax for a stanza file entry is as follows:
entry-name: Attribute1-name = Attribute1-value Attribute2-name = Attribute2-value Attribute3-name = Attribute3-value1, Attribute3-value2 . . .
The entry-name variable specifies the subsystem name.
The attributes for the subsystem are specified with the Attribute1-name, Attribute2-name, and Attribute3-name variables.
The values for the attributes are specified with the Attribute1-value, Attribute2-value, Attribute3-value1, and Attribute3-value2 variables.
The stanza file syntax rules are as follows:
Several special quoting characters allow attribute values to contain special values and data representations. If you specify a quoting character, surround the attribute value with quotation marks. For example, to specify an octal value, use the backslash character:
The TCPIP$ETC:SYSCONFIGTAB.DAT file is formatted as follows:
inet: inet_param1=inet_value1 inet_param2=inet_value2 net: net_param1=net_value1 net_param2=net_value2 proxy: proxy_param1=proxy_value1 socket: socket_param1=socket_value1
To modify a subsystem attribute, create a stanza file in your own directory. In the following example, the stanza file is named SOCKET_ATTRS.TXT.
$ TYPE SOCKET_ATTRS.TXT socket: socket_param1 = socket_value1 $
After you create the stanza file, update the system configuration table using the sysconfigdb utility. To run the sysconfigdb utility, enter the following commands:
$ TCPIP TCPIP> sysconfigdb
For information about using the sysconfigdb utility, refer to the command description in these release notes.
To update the system configuration table, use the sysconfigdb command with the -a option. Specify the stanza file on the command line using the -f option, as follows:
TCPIP> sysconfigdb -a -f stanza-filename subsystem
In this command line, stanza-filename is the file name of the stanza file that you created. The value for subsystem is the subsystem name for which you are changing an attribute.
The sysconfigdb command reads the specified file and updates the database. The modifications are made to the subsystem when it is reloaded.
For example, the following stanza file (TABLE_MGR.STANZA) defines the attributes for two subsystems, TABLE_MGR_1 and TBL_MGR_2.
$ TYPE TABLE_MGR.STANZA table_mgr_1: size = 10 name = Ten-Element-Table tbl_mgr_2: size = 5 name = Five-Element-Table $>sysconfig
Maintains the subsystem configuration.
sysconfig -c | -d | -m | -q | -Q | -r | -s | -u [subsystem-name] [attribute-list]
The sysconfig command queries and modifies the in-memory subsystem configuration. Use this command to add subsystems, reconfigure subsystems that are already in memory, query subsystems, and unconfigure and remove subsystems.
TCPIP> sysconfig -s inet: loaded and configured net: loaded and configured socket: loaded and configured iptunnel: loaded and configured ipv6: loaded and configured snmpinfo: loaded and configured
This example shows how to display the subsystems and their status.
TCPIP> sysconfig -q net net: ifnet_debug = 0 ifqmaxlen = 1024 lo_devs = 1 lo_def_ip_mtu = 4096 nslip = 0
This example shows how to display subsystem attributes and their values.
TCPIP> sysconfig -s net net: loaded and configured
This example shows how to query the state of a particular subsystem.