1 .\" Copyright (c) 1996-1999 Whistle Communications, Inc.
2 .\" All rights reserved.
4 .\" Subject to the following obligations and disclaimer of warranty, use and
5 .\" redistribution of this software, in source or object code forms, with or
6 .\" without modifications are expressly permitted by Whistle Communications;
7 .\" provided, however, that:
8 .\" 1. Any and all reproductions of the source or object code must include the
9 .\" copyright notice above and the following disclaimer of warranties; and
10 .\" 2. No rights are granted, in any manner or form, to use Whistle
11 .\" Communications, Inc. trademarks, including the mark "WHISTLE
12 .\" COMMUNICATIONS" on advertising, endorsements, or otherwise except as
13 .\" such appears in the above copyright notice or in the software.
15 .\" THIS SOFTWARE IS BEING PROVIDED BY WHISTLE COMMUNICATIONS "AS IS", AND
16 .\" TO THE MAXIMUM EXTENT PERMITTED BY LAW, WHISTLE COMMUNICATIONS MAKES NO
17 .\" REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, REGARDING THIS SOFTWARE,
18 .\" INCLUDING WITHOUT LIMITATION, ANY AND ALL IMPLIED WARRANTIES OF
19 .\" MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.
20 .\" WHISTLE COMMUNICATIONS DOES NOT WARRANT, GUARANTEE, OR MAKE ANY
21 .\" REPRESENTATIONS REGARDING THE USE OF, OR THE RESULTS OF THE USE OF THIS
22 .\" SOFTWARE IN TERMS OF ITS CORRECTNESS, ACCURACY, RELIABILITY OR OTHERWISE.
23 .\" IN NO EVENT SHALL WHISTLE COMMUNICATIONS BE LIABLE FOR ANY DAMAGES
24 .\" RESULTING FROM OR ARISING OUT OF ANY USE OF THIS SOFTWARE, INCLUDING
25 .\" WITHOUT LIMITATION, ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY,
26 .\" PUNITIVE, OR CONSEQUENTIAL DAMAGES, PROCUREMENT OF SUBSTITUTE GOODS OR
27 .\" SERVICES, LOSS OF USE, DATA OR PROFITS, HOWEVER CAUSED AND UNDER ANY
28 .\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
29 .\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
30 .\" THIS SOFTWARE, EVEN IF WHISTLE COMMUNICATIONS IS ADVISED OF THE POSSIBILITY
33 .\" Author: Archie Cobbs <archie@whistle.com>
36 .\" $Whistle: netgraph.3,v 1.7 1999/01/25 07:14:06 archie Exp $
50 .Nd netgraph user library
52 .Fd #include <netgraph.h>
54 .Fn NgMkSockNode "const char *name" "int *csp" "int *dsp"
56 .Fn NgNameNode "int cs" "const char *path" "const char *fmt" "..."
58 .Fn NgSendMsg "int cs" "const char *path" "int cookie" "int cmd" "const void *arg" "size_t arglen"
60 .Fn NgSendAsciiMsg "int cs" "const char *path" "const char *fmt" "..."
62 .Fn NgSendMsgReply "int cs" "const char *path" "struct ng_mesg *msg" "const void *arg" "size_t arglen"
64 .Fn NgRecvMsg "int cs" "struct ng_mesg *rep" "size_t replen" "char *path"
66 .Fn NgRecvAsciiMsg "int cs" "struct ng_mesg *rep" "size_t replen" "char *path"
68 .Fn NgSendData "int ds" "const char *hook" "const u_char *buf" "size_t len"
70 .Fn NgRecvData "int ds" "u_char *buf" "size_t len" "char *hook"
72 .Fn NgSetDebug "int level"
74 .Fn NgSetErrLog "void (*log)(const char *fmt, ...)" "void (*logx)(const char *fmt, ...)"
76 These functions facilitate user-mode program participation in the kernel
78 graph-based networking system, by utilizing the netgraph
84 should be called first, to create a new
86 type netgraph node with associated control and data sockets. If
88 is non-NULL, the node will have that global name assigned to it.
92 will be set to the newly opened control and data sockets
93 associated with the node; either
97 may be NULL if only one socket is desired.
99 loads the socket node type KLD if it's not already loaded.
102 assigns a global name to the node addressed by
106 sends a binary control message from the socket node associated
109 to the node addressed by
113 indicates how to interpret
115 which indicates a specific command.
116 Extra argument data (if any) is specified by
123 and argument data are defined by the header file corresponding
124 to the type of the node being addressed.
128 to send reply to a previously received control message.
129 The original message header should be pointed to by
133 performs the same function as
137 encoding of control messages.
139 formats its input a la
141 and then sends the resulting
143 string to the node in a
145 control message. The node returns a binary version of the
146 message, which is then sent back to the node just as with
150 conversion may not be supported by all node types.
153 reads the next control message received by the node associated with
156 The message and any extra argument data must fit in
161 is non-NULL, it must point to a buffer of at least
163 bytes, which will be filled in (and NUL terminated) with the path to
164 the node from which the message was received.
169 except that after the message is received, any binary arguments
174 request back to the originating node. The result is the same as
176 with the exception that the reply arguments field will contain
179 version of the arguments (and the reply
180 header argument length field will be adjusted).
183 writes a data packet out on the specified hook of the node corresponding
186 The node must already be connected to some other node via that hook.
189 reads the next data packet (of up to
191 bytes) received by the node corresponding to data socket
195 which must be large enough to hold the entire packet. If
197 is non-NULL, it must point to a buffer of at least
199 bytes, which will be filled in (and NUL terminated) with the name of
200 the hook on which the data was received.
205 are used for debugging.
207 sets the debug level (if non-negative), and returns the old setting.
208 Higher debug levels result in more verbosity. The default is zero.
209 All debug and error messages are logged via the functions
210 specified in the most recent call to
212 The default logging functions are
217 At debug level 3, the library attempts to display control message arguments
220 format; however, this results in additional messages being
221 sent which may interfere with debugging. At even higher levels,
222 even these additional messagages will be displayed, etc.
226 can be used on the data and the control sockets to detect the presence of
227 incoming data and control messages, respectively.
228 Data and control packets are always written and read atomically, i.e.,
231 User mode programs must be linked with the
233 flag to link in this library.
235 To enable Netgraph in your kernel, either your kernel must be
238 in the kernel configuration
243 KLD modules must have been loaded via
250 return -1 if there was an error and set errno accordingly.
256 the following additional errors are possible:
259 The node type does not know how to encode or decode the control message.
261 The encoded or decoded arguments were too long for the supplied buffer.
263 An unknown structure field was seen in an
267 The same structure field was specified twice in an
272 control message parse error or illegal value.
274 ASCII control message array or fixed width string buffer overflow.
286 system was designed and first implemented at Whistle Communications, Inc. in
289 customized for the Whistle InterJet.
291 .An Archie Cobbs Aq archie@whistle.com