Lines Matching +full:smp +full:- +full:offset
3 <!--
4 A { text-decoration:none }
5 -->
32 <TH VALIGN=TOP>SMP</TH>
34 runs in conjunction with a libpcap front-end.</TD>
39 with a custom device driver/libpcap back-end.</TD>
44 Each IOP will be capable of supporting multiple connections from an SMP
62 …<TD VALIGN=TOP>Since a CTRL-C was used to terminate the application, pcap_breakloop() is never cal…
74 capturing following a pcap_breakloop() without any re-initialization.
86 The following list of functions is the sub-set of Pcap functions that have been
88 functions continue to perform their duties un-altered. Libpcap only supports this
106 "SMP/IOP Inter-Process Communication Protocol" section.
114 <TR><TH VALIGN=TOP NOWRAP>SMP -> IOP</TH>
116 The SMP will open a connection to the selected IOP on its 'sniffer' port
121 <TR><TH VALIGN=TOP NOWRAP>IOP -> SMP</TH>
141 <TR><TH VALIGN=TOP NOWRAP>SMP</TH>
146 <TR><TH VALIGN=TOP NOWRAP>SMP -> IOP</TH>
148 The SMP will sequentially open a connection to each IOP on its 'sniffer' port to ensure
153 <TR><TH VALIGN=TOP NOWRAP>IOP -> SMP</TH>
157 <TR><TH VALIGN=TOP NOWRAP>SMP -> IOP</TH>
159 The SMP closes the TCP connection with each IOP.
162 <TR><TH VALIGN=TOP NOWRAP>SMP</TH>
164 The SMP adds the received information to its internal structure.
174 <TR><TH VALIGN=TOP NOWRAP>SMP</TH>
176 The SMP frees the structure it built as a result of the previous
187 <TR><TH VALIGN=TOP NOWRAP>SMP -> IOP</TH>
190 the SMP will pass down the monitor start command and various parameters the IOP should use.
193 <TR><TH VALIGN=TOP NOWRAP>IOP -> SMP</TH>
198 <TR><TH VALIGN=TOP NOWRAP>SMP</TH>
200 The SMP will read the reverse channel of the connection between the SMP and the
201 IOP that provides the captured data (via 'p->read_op' which is 'pcap_read_linux()'
209 …OP continues to listen for additional commands as well as capturing and forwarding data to the SMP.
222 <TR><TH VALIGN=TOP NOWRAP>SMP -> IOP</TH>
225 the SMP will pass down the monitor start command and various parameters the IOP should use.
228 <TR><TH VALIGN=TOP NOWRAP>IOP -> SMP</TH>
233 <TR><TH VALIGN=TOP NOWRAP>SMP</TH>
235 The SMP continuously reads the next packet from the reverse channel of the connection
236 between the SMP and the IOP that provides the captured data (via 'p->read_op'
243 …OP continues to listen for additional commands as well as capturing and forwarding data to the SMP.
256 <TR><TH VALIGN=TOP NOWRAP>SMP -> IOP</TH>
259 the SMP will pass down the monitor start command and various parameters the IOP should use.
262 <TR><TH VALIGN=TOP NOWRAP>IOP -> SMP</TH>
267 <TR><TH VALIGN=TOP NOWRAP>SMP</TH>
269 The SMP reads only the next packet from the reverse channel of the connection
270 between the SMP and the IOP that provides the captured data (via calling pcap_dispatch()
276 …OP continues to listen for additional commands as well as capturing and forwarding data to the SMP.
286 <TR><TH VALIGN=TOP NOWRAP>SMP -> IOP</TH>
289 the SMP will pass down the monitor start command and various parameters the IOP should use.
292 <TR><TH VALIGN=TOP NOWRAP>IOP -> SMP</TH>
297 <TR><TH VALIGN=TOP NOWRAP>SMP</TH>
299 The SMP reads only the next packet from the reverse channel of the connection
300 between the SMP and the IOP that provides the captured data (via calling pcap_dispatch()
307 …OP continues to listen for additional commands as well as capturing and forwarding data to the SMP.
317 <TR><TH VALIGN=TOP NOWRAP>SMP -> IOP</TH>
319 The SMP sends a 'set filter' command followed by the BPF commands.
322 <TR><TH VALIGN=TOP NOWRAP>IOP -> SMP</TH>
340 <TR><TH VALIGN=TOP NOWRAP>SMP -> IOP</TH>
342 The SMP sends a message to the IOP requesting its statistics.
345 <TR><TH VALIGN=TOP NOWRAP>IOP -> SMP</TH>
350 <TR><TH VALIGN=TOP NOWRAP>SMP</TH>
352 The SMP fills in the structure provided with the information retrieved from the IOP.
362 <TR><TH VALIGN=TOP NOWRAP>SMP -> IOP</TH>
364 The SMP closes the file descriptor, and if the descriptor is that of
370 If the IOP detects that its communication session with an SMP
381 <H3>SMP/IOP Inter-Process Communication Protocol</H3>
384 <LI><P>Communications between an SMP and an IOP consists of a TCP session
385 between an ephemeral port on the SMP and the well known port of 49152
392 <LI><P>A session is closed when the SMP closes the TCP session with the IOP.
395 <B>Note: </B>All multi-octet entities are sent in network neutral order.
402 <TD VALIGN=TOP ALIGN=CENTER NOWRAP>SMP -> IOP</TD>
420 <TD VALIGN=TOP ALIGN=CENTER NOWRAP>IOP -> SMP</TD>
424 <TD VALIGN=TOP ALIGN=CENTER NOWRAP>SMP -> IOP</TD>
442 <TD VALIGN=TOP ALIGN=CENTER NOWRAP>IOP -> SMP</TD>
461 <TD VALIGN=TOP ALIGN=CENTER>1-255</TD>
479 <TD VALIGN=TOP ALIGN=CENTER>0-255</TD>
503 <TD VALIGN=TOP ALIGN=CENTER>1-255</TD>
511 <TD VALIGN=TOP ALIGN=CENTER>0-255</TD>
519 <TD VALIGN=TOP ALIGN=CENTER>0-255</TD>
527 <TD VALIGN=TOP ALIGN=CENTER>0-255</TD>
533 <TD VALIGN=TOP ALIGN=CENTER NOWRAP>SMP -> IOP</TD>
537 <TD VALIGN=TOP ALIGN=CENTER NOWRAP>IOP -> SMP</TD>
543 <TD VALIGN=TOP ALIGN=CENTER NOWRAP>SMP -> IOP</TD>
561 <TD VALIGN=TOP ALIGN=CENTER NOWRAP>IOP -> SMP</TD>
567 <TD VALIGN=TOP ALIGN=CENTER NOWRAP>SMP -> IOP</TD>
606 <TD VALIGN=TOP ALIGN=CENTER NOWRAP>IOP -> SMP</TD>
612 <TD VALIGN=TOP ALIGN=CENTER NOWRAP>SMP -> IOP</TD>
613 <TD VALIGN=TOP>At any time, the SMP can issue a set filter command which contains
616 of C-style structures.
638 Each command consists of that C-style structure which contains:
654 <TD VALIGN=TOP>The 'jump if true' program counter offset.</TD>
659 <TD VALIGN=TOP>The 'jump if false' program counter offset.</TD>
675 <TD VALIGN=TOP ALIGN=CENTER NOWRAP>IOP -> SMP</TD>
681 <TD VALIGN=TOP ALIGN=CENTER NOWRAP>SMP -> IOP</TD>
682 <TD VALIGN=TOP>At any time, the SMP can issue a 'retrieve statistics' command which contains:<BR>
699 <TD VALIGN=TOP ALIGN=CENTER NOWRAP>IOP -> SMP</TD>
731 <TD VALIGN=TOP ALIGN=CENTER NOWRAP>SMP -> IOP</TD>
732 <TD VALIGN=TOP>At any time, the SMP can close the TCP session with the IOP.</TD>
762 The format of the trace data that is sent to the SMP follows a portion of the libpcap file format
769 …more records for each captured packet, trace data sent to the SMP does NOT begin with a global hea…
774 <TD STYLE="background-color: #c0FFc0"> [Packet Header] </TD>
775 <TD STYLE="background-color: #c0FFc0"> [Packet Data] </TD>
776 <TD STYLE="background-color: #c0c0FF"> [Packet Header] </TD>
777 <TD STYLE="background-color: #c0c0FF"> [Packet Data] </TD>
778 <TD STYLE="background-color: #e0c0c0"> [Packet Header] </TD>
779 <TD STYLE="background-color: #e0c0c0"> [Packet Data] </TD>
789 <FONT SIZE=-1>
809 <TD>The microseconds when this packet was captured, as an offset to <em>ts_sec</em>.
891 …<TR> <TD VALIGN=TOP ALIGN=CENTER><FONT FACE="COURIER">xxxx1xxx</FONT></TD> <TD>Re-Tx Limit Reached…
901 …=CENTER><FONT FACE="COURIER">xxxxxxx1</FONT></TD> <TD>Undefined</TD> <TD>Non-Octet Aligned</TD> <…
916 …<TR VALIGN=BOTTOM><TD ALIGN=CENTER>0x01</TD> <TD>-</TD> <TD>LAPB (BOP) <SUP> </SUP> </TD> …
917 … <TR VALIGN=BOTTOM><TD ALIGN=CENTER>0x02</TD> <TD>-</TD> <TD>Ethernet <SUP>1</SUP> </TD> </TR>
918 …<TR VALIGN=BOTTOM><TD ALIGN=CENTER>0x03</TD> <TD>-</TD> <TD>Async (Interrupt IO) <SUP> </SUP>…
919 …<TR VALIGN=BOTTOM><TD ALIGN=CENTER>0x04</TD> <TD>-</TD> <TD>Async (Block IO) <SUP> </SUP> </…
920 …<TR VALIGN=BOTTOM><TD ALIGN=CENTER>0x05</TD> <TD>-</TD> <TD>IPARS <SUP> </SUP> </TD> </TR>
921 … <TR VALIGN=BOTTOM><TD ALIGN=CENTER>0x06</TD> <TD>-</TD> <TD>UTS <SUP> </SUP> </TD> </TR>
922 …<TR VALIGN=BOTTOM><TD ALIGN=CENTER>0x07</TD> <TD>-</TD> <TD>PPP (HDLC) <SUP> </SUP> </TD> …
923 … <TR VALIGN=BOTTOM><TD ALIGN=CENTER>0x08</TD> <TD>-</TD> <TD>SDLC <SUP> </SUP> </TD> </TR>
924 …<TR VALIGN=BOTTOM><TD ALIGN=CENTER>0x09</TD> <TD>-</TD> <TD>Token Ring <SUP>1</SUP> </TD> </TR>
925 … <TR VALIGN=BOTTOM><TD ALIGN=CENTER>0x10</TD> <TD>-</TD> <TD>I2C <SUP> </SUP> </TD> </TR>
926 …<TR VALIGN=BOTTOM><TD ALIGN=CENTER>0x11</TD> <TD>-</TD> <TD>DPM Link <SUP> </SUP> </TD> </…
927 …<TR VALIGN=BOTTOM><TD ALIGN=CENTER>0x12</TD> <TD>-</TD> <TD>Frame Relay (BOP) <SUP> </SUP> <…