iX 6.0)

24 Chapter 1

Introduction to Internet Services

Protocols File

The protocols ﬁle contains a list of protocols known to the system, plus

the identiﬁcation number and one or more aliases for each. It is

unlikely that you will need to edit the protocols ﬁle, but you may need

to install and link it.

Creating and Linking Protocols File

You may already have a protocols ﬁle installed on your system. If you

know that you have such a ﬁle, and it is accessible by the POSIX ﬁle

name /etc/protocols you may skip these steps.

If not, follow the steps below to create and link the protocols ﬁle,

PROTOCOL.NET.SYS. If you have such a ﬁle, but are unsure whether or

not it is linked, perform step 2 only.

1. Use the COPY command to create the protocols ﬁle. Enter:

:COPY PROTSAMP.NET.SYS, PROTOCOL.NET.SYS

Make sure that you enter the singular form of protocol in the new

MPE ﬁle name. That is, “PROTOCOL” and not “PROTOCOLS”

should appear on the right side of the COPY command.

2. Create a symbolic link from /etc/protocols in the POSIX name

space to PROTOCOL.NET.SYS. Enter:

:NEWLINK /etc/protocols, PROTOCOL.NET.SYS

Again, make sure that you enter the singular form of protocol in the

new MPE ﬁle name PROTOCOL.NET.SYS.

Viewing Protocols File

Use an MPE text editor to open the ﬁle. It is unlikely that you will need

to edit the ﬁle, but you can look at it now to familiarize yourself with its

contents.

# This file associates protocol numbers with official protocol names and

# aliases. This allows the user to refer to a protocol by a symbolic

# name instead of a number. For each protocol a single line should be

# present with the following information:

# The form for each entry is:

# <official protocol name> <protocol number> <aliases>

# See the Configuring and Managing MPE/iX Internet Services Manual

# for more information (HP Part No. 32650-90835).

# Note: The entries cannot be preceded by a blank space.

11 tcp 6 TCP # transmission control protocol

12 udp 17 UDP # user datagram protocol