Commit | Line | Data |
---|---|---|
af359dea | 1 | .\" Copyright (c) 1990, 1991 The Regents of the University of California. |
1c15e888 C |
2 | .\" All rights reserved. |
3 | .\" | |
4 | .\" This code is derived from software contributed to Berkeley by | |
5 | .\" the Systems Programming Group of the University of Utah Computer | |
6 | .\" Science Department. | |
af359dea C |
7 | .\" Redistribution and use in source and binary forms, with or without |
8 | .\" modification, are permitted provided that the following conditions | |
9 | .\" are met: | |
10 | .\" 1. Redistributions of source code must retain the above copyright | |
11 | .\" notice, this list of conditions and the following disclaimer. | |
12 | .\" 2. Redistributions in binary form must reproduce the above copyright | |
13 | .\" notice, this list of conditions and the following disclaimer in the | |
14 | .\" documentation and/or other materials provided with the distribution. | |
15 | .\" 3. All advertising materials mentioning features or use of this software | |
16 | .\" must display the following acknowledgement: | |
17 | .\" This product includes software developed by the University of | |
18 | .\" California, Berkeley and its contributors. | |
19 | .\" 4. Neither the name of the University nor the names of its contributors | |
20 | .\" may be used to endorse or promote products derived from this software | |
21 | .\" without specific prior written permission. | |
1c15e888 | 22 | .\" |
af359dea C |
23 | .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND |
24 | .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE | |
25 | .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE | |
26 | .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE | |
27 | .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL | |
28 | .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS | |
29 | .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) | |
30 | .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT | |
31 | .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY | |
32 | .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF | |
33 | .\" SUCH DAMAGE. | |
1c15e888 | 34 | .\" |
af359dea | 35 | .\" @(#)rmp.4 5.2 (Berkeley) 3/27/91 |
1c15e888 | 36 | .\" |
af359dea C |
37 | .Dd March 27, 1991 |
38 | .Dt RMP 4 hp300 | |
39 | .Os | |
40 | .Sh NAME | |
41 | .Nm rmp | |
42 | .Nd | |
43 | .Tn HP | |
44 | Remote Maintenance Protocol Family | |
45 | .Sh SYNOPSIS | |
46 | .Cd "options RMP" | |
47 | .Fd #include <sys/types.h> | |
48 | .Fd #include <sys/socket.h> | |
49 | .Fd #include <netrmp/rmp.h> | |
50 | .Fd #include <netrmp/rmp_var.h> | |
51 | .Ft int | |
52 | .Fn socket AF_RMP SOCK_RAW proto | |
53 | .Sh DESCRIPTION | |
1c15e888 C |
54 | Hewlett-Packard's Remote Maintenance Protocol family is a collection |
55 | of protocols layered atop | |
af359dea | 56 | .Tn IEEE 802.3 . |
1c15e888 | 57 | The current implementation of the RMP family provides protocol support only |
af359dea C |
58 | for the |
59 | .Dv SOCK_RAW | |
60 | socket type. | |
61 | As a result, | |
62 | .Xr sendto 2 | |
63 | and | |
64 | .Xr recvfrom 2 | |
65 | must be used to send and | |
66 | receive | |
67 | .Tn RMP | |
68 | packets. | |
69 | .Pp | |
70 | The format of an | |
71 | .Tn RMP | |
72 | packet is defined in the include file | |
73 | .Aq Pa netrmp/rmp_var.h . | |
74 | The | |
75 | .Tn RMP | |
76 | packet arrives encapsulated in an | |
77 | .Pf ( Tn HP | |
78 | extended) | |
79 | .Tn IEEE 802.2 | |
1c15e888 C |
80 | packet. |
81 | The | |
af359dea | 82 | .Tn IEEE 802.2 |
1c15e888 C |
83 | packet |
84 | is preceded by the kernel address of an | |
af359dea | 85 | .Ar ifnet struct |
1c15e888 C |
86 | which is used to `route' a packet out the same interface it |
87 | arrived on. | |
88 | Outgoing packets are encapsulated in a standard | |
af359dea | 89 | .Tn IEEE 802.3 |
1c15e888 | 90 | packet, while incoming packets have this information stripped away. |
af359dea C |
91 | .Sh ADDRESSING |
92 | .Tn RMP | |
93 | .Pf ( Tn IEEE | |
94 | 802.3) addresses are 6 octets in length (48 bytes). | |
1c15e888 C |
95 | Sockets in the Remote Maintenance Protocol family use the following |
96 | addressing structure: | |
af359dea | 97 | .Bd -literal -offset indent |
1c15e888 C |
98 | struct sockaddr_rmp { |
99 | short srmp_family; | |
100 | u_char srmp_dhost[6]; | |
101 | }; | |
af359dea C |
102 | .Ed |
103 | .Sh PROTOCOLS | |
104 | The | |
105 | .Tn RMP | |
106 | protocol family supported by the operating system | |
1c15e888 | 107 | is currently comprised of the Boot Protocol |
af359dea | 108 | .Pq Em proto= Ns Dv RMPPROTO_BOOT . |
1c15e888 C |
109 | Unfortunately, we have no documentation on the Remote Maintenance |
110 | Protocol and only sketchy information about the Boot Protocol. | |
af359dea C |
111 | .Sh SEE ALSO |
112 | .Xr socket 2 , | |
113 | .Xr bind 2 , | |
114 | .Xr sendto 2 , | |
115 | .Xr recvfrom 2 , | |
116 | .Xr intro 4 , | |
117 | .Xr rbootd 8 | |
118 | .Rs | |
119 | .%T "An Advanced 4.3 BSD Interprocess Communication Tutorial" | |
120 | .Re | |
121 | .Sh HISTORY | |
122 | The | |
123 | .Nm | |
124 | protocol interface | |
125 | .Ud | |
126 | .Sh BUGS | |
127 | .Bl -bullet | |
128 | .It | |
129 | The | |
130 | .Tn HP ROM | |
131 | uses | |
132 | .Tn IEEE | |
133 | 802.3 (as opposed to Ethernet) packets. While the | |
1c15e888 C |
134 | kernel heuristically recognizes these packets, a more general mechanism |
135 | for doing so should be provided. | |
af359dea C |
136 | .It |
137 | The | |
138 | .Tn HP ROM | |
139 | uses a multicast address when first trying to locate boot | |
1c15e888 C |
140 | servers. While the Ethernet [sic] board is programmed to recognize |
141 | this particular multicast address (9:0:9:0:0:4), a more general | |
142 | mechanism for doing so should be provided. | |
af359dea C |
143 | .It |
144 | The kernel supports only | |
145 | .Tn RAW | |
146 | sockets for the | |
147 | .Tn RMP | |
148 | protocol. | |
1c15e888 C |
149 | This is either a bug or a feature, since the kernel is smaller at the |
150 | price of greater complexity in the server. | |
af359dea C |
151 | .It |
152 | There is no support for | |
153 | .Xr bind Ns 'ing | |
154 | an address in the | |
155 | .Tn RMP | |
156 | domain. | |
157 | Something like an | |
158 | .Dv RMPADDR_ANY | |
159 | should be provided to prevent more than one | |
160 | .Xr rbootd | |
1c15e888 | 161 | server from running at the same time. |
af359dea | 162 | .El |