 |
» |
|
|
|
To activate special network features, you may also want to
configure /etc/services, /etc/networks, and /etc/protocols. Each of these steps is optional. | | | |  | NOTE: If you are using NIS, modifications to the /etc/services, /etc/networks and /etc/protocols files should only be made on the NIS Master Server.
Refer to the NFS Services Administrator’s Guide for
more information | | | | |
Modifying
the /etc/services File | |
The /etc/services file associates port numbers with mnemonic service
names and alias names. The /etc/services file contains the names, protocol names, and port
numbers of all services known to your local host. The netstat diagnostic uses the /etc/services file. If you install HP-UX Internet Services or HP-UX NFS, these
products will also use the /etc/services file. | | | | | NOTE: You can modify this file if you have special requirements,
but it is properly configured when you receive HP-UX LAN. | | | | |
Each service has a one line entry in the /etc/services file. Each entry in /etc/services file takes the following form: service_name port_num/protocol [alias]... |
- service_name
Name of the service. Service names can contain any
printable character except spaces, newline, or the comment character
(#). - port_num / protocol
port_num is the protocol port number assigned to this service.
All requests for this service must use this port number. protocol is the protocol name, as listed in /etc/protocols, that the service uses. - alias
Common name or names for the service. An alias is
a substitute for service_name. Alias names are optional.
Lines cannot start with a blank or
tab character. Fields can have any number of blanks or tab characters
separating them. Comments are allowed and designated by a pound sign
(#) character preceding the comment text. Trailing blank and tab characters are allowed. Blank line entries are allowed. Only one entry per line is allowed.
/etc/services
PermissionsThe /etc/services file should be owned by user bin, group bin, and it should have 0x444 (-r--r--r--) access permission. Refer to the /etc/services file for examples of actual format and contents.
For more information on /etc/services, refer to the services(4) man page in the HP-UX Reference Pages. The following /etc/services entry contains the service name, port number,
protocol name, and alias name for the shell service. shell 514/tcp cmd #remote command, no passwd used |
Creating
the /etc/networks File | |
The /etc/networks file associates network addresses with mnemonic
names and alias names. The /etc/networks file contains the name and address of known internet
networks with which your host can communicate. The HP-UX LAN diagnostic netstat and the route command use the /etc/networks file. You must configure this file for your host
if you want route or netstat to use symbolic network names instead of addresses. You can create an /etc/networks file two ways: From scratch, entering the known nodes
in the format shown below. By copying the file from another node.
If you copy an /etc/networks file from another host, you may need to update
the file by adding unofficial aliases or unknown networks, including
your own network. Each network has a one line entry in the /etc/networks file. Each entry in /etc/networks file takes the following form: network_name network_address [alias]... |
- network_name
Name of the internet network. Network names can
contain any printable character except spaces, newline, or the comment
character (#). - network_address
Network address that uniquely identifies the network.
This address can be a subnet or supernet address. It may also contain
the netmask translation. network_address must be in dot notation. See Chapter 6 for details
on network addresses. - alias
Common name or names for the network. An alias is
a substitute for network_name. Alias names are optional.
Lines cannot start with a blank or
tab character. Fields can have any number of blanks or tab characters
separating them. Comments are allowed and designated by a pound sign
(#) character preceding the comment text. Trailing blank and tab characters are allowed. Blank line entries are allowed. Only one entry per line is allowed.
/etc/networks
PermissionsThe /etc/networks file should be owned by user bin, group bin, and it should have 0x444 (-r--r--r--)access permission. For more information on /etc/networks, refer to the networks(4) man page in the HP-UX Reference Pages. The following /etc/networks entry contains a network name, network address,
and an alias name for the network neta. Modifying
the /etc/protocols File | |
The /etc/protocols file associates port numbers with mnemonic names
and alias names. The /etc/protocols file contains the names and protocol numbers of
all protocols known to your local host. The netstat diagnostic uses the /etc/protocols file. If you install HP-UX Internet Services or
HP-UX NFS, those products will also use the /etc/protocols file. | | | | | NOTE: You can modify this file if you have special requirements,
but it is properly configured when you receive the HP-UX LAN software. | | | | |
Each protocol has a one line entry in the /etc/protocols file. Each entry in /etc/protocols file takes the following form: protocol_name protocol_num [alias]... |
- protocol_name
Name of the protocol. Protocol names can contain
any printable character except spaces, newline, or the comment character
(#). - protocol_num
Protocol number that identifies this protocol. - alias
Common name or names for the protocol. An alias
is a substitute for protocol_name. Alias names are optional.
Lines cannot start with a blank or
tab character. Fields can have any number of blanks or tab characters
separating them. Comments are allowed and designated by a pound sign
(#) character preceding the comment text. Trailing blank and tab characters are allowed. Blank line entries are allowed. Only one entry per line is allowed.
/etc/protocols
PermissionsThe /etc/protocols file should be owned by user bin, group bin, and it should have 0x444 (-r--r--r--) access permission. Refer to the /etc/protocols file for examples of actual format and contents.
For more information on /etc/protocols, refer to the protocols(4) man page in the HP-UX Reference Pages. The following /etc/protocols entry contains a protocol name, protocol number
and an alias name. |
Printable version
