Annotated edit history of
protocols(5) version 1, including all changes.
View license author blame.
| Rev |
Author |
# |
Line |
| 1 |
perry |
1 |
PROTOCOLS |
| |
|
2 |
!!!PROTOCOLS |
| |
|
3 |
NAME |
| |
|
4 |
DESCRIPTION |
| |
|
5 |
FILES |
| |
|
6 |
SEE ALSO |
| |
|
7 |
---- |
| |
|
8 |
!!NAME |
| |
|
9 |
|
| |
|
10 |
|
| |
|
11 |
protocols - the protocols definition file |
| |
|
12 |
!!DESCRIPTION |
| |
|
13 |
|
| |
|
14 |
|
| |
|
15 |
This file is a plain ASCII file, describing the various |
| |
|
16 |
DARPA internet protocols that are available from the TCP/IP |
| |
|
17 |
subsystem. It should be consulted instead of using the |
| |
|
18 |
numbers in the ARPA include files, or, even worse, just |
| |
|
19 |
guessing them. These numbers will occur in the protocol |
| |
|
20 |
field of any ip header. |
| |
|
21 |
|
| |
|
22 |
|
| |
|
23 |
Keep this file untouched since changes would result in |
| |
|
24 |
incorrect ip packages. Protocol numbers and names are |
| |
|
25 |
specified by the DDN Network Information |
| |
|
26 |
Center. |
| |
|
27 |
|
| |
|
28 |
|
| |
|
29 |
Each line is of the following format: |
| |
|
30 |
|
| |
|
31 |
|
| |
|
32 |
''protocol number aliases ...'' |
| |
|
33 |
|
| |
|
34 |
|
| |
|
35 |
where the fields are delimited by spaces or tabs. Empty |
| |
|
36 |
lines and lines starting with a hash mark (#) are ignored. |
| |
|
37 |
Remainder of lines are also ignored from the occurrence of a |
| |
|
38 |
hash mark. |
| |
|
39 |
|
| |
|
40 |
|
| |
|
41 |
The field descriptions are: |
| |
|
42 |
|
| |
|
43 |
|
| |
|
44 |
''protocol'' |
| |
|
45 |
|
| |
|
46 |
|
| |
|
47 |
the native name for the protocol. For example ip, tcp or |
| |
|
48 |
udp. |
| |
|
49 |
|
| |
|
50 |
|
| |
|
51 |
''number'' |
| |
|
52 |
|
| |
|
53 |
|
| |
|
54 |
the official number for this protocol as it will appear |
| |
|
55 |
within the ip header. |
| |
|
56 |
|
| |
|
57 |
|
| |
|
58 |
''aliases'' |
| |
|
59 |
|
| |
|
60 |
|
| |
|
61 |
optional aliases for the protocol. |
| |
|
62 |
|
| |
|
63 |
|
| |
|
64 |
This file might be distributed over a network using a |
| |
|
65 |
networkwide naming service like Yellow Pages/NIS or |
| |
|
66 |
BIND/Hesiod. |
| |
|
67 |
!!FILES |
| |
|
68 |
|
| |
|
69 |
|
| |
|
70 |
''/etc/protocols'' |
| |
|
71 |
|
| |
|
72 |
|
| |
|
73 |
The protocols definition file. |
| |
|
74 |
!!SEE ALSO |
| |
|
75 |
|
| |
|
76 |
|
| |
|
77 |
getprotoent(3) |
| |
|
78 |
|
| |
|
79 |
|
| |
|
80 |
Guide to Yellow Pages Service |
| |
|
81 |
|
| |
|
82 |
|
| |
|
83 |
Guide to BIND/Hesiod Service |
| |
|
84 |
---- |
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.