summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--pcap-filter.manmisc.in8
-rw-r--r--pcap-tstamp.manmisc.in19
-rw-r--r--pcap_activate.3pcap8
-rw-r--r--pcap_breakloop.3pcap8
-rw-r--r--pcap_can_set_rfmon.3pcap6
-rw-r--r--pcap_create.3pcap4
-rw-r--r--pcap_dump.3pcap9
-rw-r--r--pcap_dump_file.3pcap2
-rw-r--r--pcap_dump_flush.3pcap4
-rw-r--r--pcap_dump_ftell.3pcap6
-rw-r--r--pcap_file.3pcap10
-rw-r--r--pcap_fileno.3pcap16
12 files changed, 43 insertions, 57 deletions
diff --git a/pcap-filter.manmisc.in b/pcap-filter.manmisc.in
index 3232f7e9..54378c60 100644
--- a/pcap-filter.manmisc.in
+++ b/pcap-filter.manmisc.in
@@ -29,11 +29,11 @@ pcap-filter \- packet filter syntax
is used to compile a string into a filter program.
The resulting filter program can then be applied to
some stream of packets to determine which packets will be supplied to
-.BR pcap_loop() ,
-.BR pcap_dispatch() ,
-.BR pcap_next() ,
+.BR pcap_loop(3PCAP) ,
+.BR pcap_dispatch(3PCAP) ,
+.BR pcap_next(3PCAP) ,
or
-.BR pcap_next_ex() .
+.BR pcap_next_ex(3PCAP) .
.LP
The \fIfilter expression\fP consists of one or more
.IR primitives .
diff --git a/pcap-tstamp.manmisc.in b/pcap-tstamp.manmisc.in
index 38c56518..12405c83 100644
--- a/pcap-tstamp.manmisc.in
+++ b/pcap-tstamp.manmisc.in
@@ -93,9 +93,9 @@ call and before a
call to specify the type of time stamp to be used on the device.
The time stamp types are listed here; the first value is the #define to
use in code, the second value is the value returned by
-.B pcap_tstamp_type_val_to_name()
+.B pcap_tstamp_type_val_to_name(3PCAP)
and accepted by
-.BR pcap_tstamp_type_name_to_val() .
+.BR pcap_tstamp_type_name_to_val(3PCAP) .
.RS 5
.TP 5
.BR PCAP_TSTAMP_HOST " - " host
@@ -149,9 +149,9 @@ call will fail, and the time stamps supplied after the
call will have microsecond resolution.
.LP
When opening a savefile, the
-.BR pcap_open_offline_with_tstamp_precision (3PCAP)
+.BR \%pcap_open_offline_with_tstamp_precision (3PCAP)
and
-.BR pcap_fopen_offline_with_tstamp_precision (3PCAP)
+.BR \%pcap_fopen_offline_with_tstamp_precision (3PCAP)
routines can be used to specify the resolution of time stamps to be read
from the file; if the time stamps in the file have a lower resolution,
the fraction-of-a-second portion of the time stamps will be scaled to
@@ -164,14 +164,3 @@ when capturing packets, this does not reflect the actual precision of
the time stamp supplied by the hardware or operating system and, when
reading a savefile, this does not indicate the actual precision of time
stamps in the file.
-.SH SEE ALSO
-.na
-pcap_set_tstamp_type(3PCAP),
-pcap_list_tstamp_types(3PCAP),
-pcap_tstamp_type_val_to_name(3PCAP),
-pcap_tstamp_type_name_to_val(3PCAP),
-pcap_set_tstamp_precision(3PCAP),
-pcap_open_offline_with_tstamp_precision(3PCAP),
-\%pcap_fopen_offline_with_tstamp_precision(3PCAP),
-\%pcap_get_tstamp_precision(3PCAP)
-.ad
diff --git a/pcap_activate.3pcap b/pcap_activate.3pcap
index ceb2aa74..162a9293 100644
--- a/pcap_activate.3pcap
+++ b/pcap_activate.3pcap
@@ -50,15 +50,15 @@ promiscuous mode.
.TP
.B PCAP_WARNING_TSTAMP_TYPE_NOTSUP
The time stamp type specified in a previous
-.B pcap_set_tstamp_type()
+.B pcap_set_tstamp_type(3PCAP)
call isn't supported by the capture source (the time stamp type is
left as the default),
.TP
.B PCAP_WARNING
Another warning condition occurred;
-.B pcap_geterr()
+.B pcap_geterr(3PCAP)
or
-.B pcap_perror()
+.B pcap_perror(3PCAP)
may be called with
.I p
as an argument to fetch or display a message describing the warning
@@ -115,7 +115,7 @@ Additional warning and error codes may be added in the future; a program
should check for positive, negative, and zero return codes, and treat
all positive return codes as warnings and all negative return
codes as errors.
-.B pcap_statustostr()
+.B pcap_statustostr(3PCAP)
can be called, with a warning or error code as an argument, to fetch a
message describing the warning or error code.
.SH SEE ALSO
diff --git a/pcap_breakloop.3pcap b/pcap_breakloop.3pcap
index 03b8d8d1..f3cb52e2 100644
--- a/pcap_breakloop.3pcap
+++ b/pcap_breakloop.3pcap
@@ -33,9 +33,9 @@ void pcap_breakloop(pcap_t *);
.SH DESCRIPTION
.B pcap_breakloop()
sets a flag that will force
-.B pcap_dispatch()
+.B pcap_dispatch(3PCAP)
or
-.B pcap_loop()
+.B pcap_loop(3PCAP)
to return rather than looping; they will return the number of packets
that have been processed so far, or \-2 if no packets have been
processed so far.
@@ -60,7 +60,7 @@ packets arrive and the call completes.
.PP
.ft B
Note also that, in a multi-threaded application, if one thread is
-blocked in pcap_dispatch(), pcap_loop(), pcap_next(), or pcap_next_ex(),
+blocked in pcap_dispatch(), pcap_loop(), pcap_next(3PCAP), or pcap_next_ex(3PCAP),
a call to pcap_breakloop() in a different thread will not unblock that
thread.
.ft R
@@ -107,4 +107,4 @@ the flag is cleared, so a subsequent call will resume reading packets.
If a positive number is returned, the flag is not cleared, so a
subsequent call will return \-2 and clear the flag.
.SH SEE ALSO
-pcap(3PCAP), pcap_loop(3PCAP), pcap_next_ex(3PCAP)
+pcap(3PCAP)
diff --git a/pcap_can_set_rfmon.3pcap b/pcap_can_set_rfmon.3pcap
index eee004dd..0baac7a6 100644
--- a/pcap_can_set_rfmon.3pcap
+++ b/pcap_can_set_rfmon.3pcap
@@ -54,9 +54,9 @@ The capture handle has already been activated.
.TP
.B PCAP_ERROR
Another error occurred.
-.B pcap_geterr()
+.B pcap_geterr(3PCAP)
or
-.B pcap_perror()
+.B \%pcap_perror(3PCAP)
may be called with
.I p
as an argument to fetch or display a message describing the error.
@@ -64,7 +64,7 @@ as an argument to fetch or display a message describing the error.
Additional error codes may be added in the future; a program should
check for 0, 1, and negative, return codes, and treat all negative
return codes as errors.
-.B pcap_statustostr()
+.B pcap_statustostr(3PCAP)
can be called, with a warning or error code as an argument, to fetch a
message describing the warning or error code.
.SH SEE ALSO
diff --git a/pcap_create.3pcap b/pcap_create.3pcap
index 3040b3b2..5a15007b 100644
--- a/pcap_create.3pcap
+++ b/pcap_create.3pcap
@@ -48,7 +48,7 @@ argument of "any" or
can be used to capture packets from all interfaces.
.PP
The returned handle must be activated with
-.B pcap_activate()
+.B pcap_activate(3PCAP)
before packets can be captured
with it; options for the capture, such as promiscuous mode, can be set
on the handle before activating it.
@@ -69,4 +69,4 @@ is assumed to be able to hold at least
.B PCAP_ERRBUF_SIZE
chars.
.SH SEE ALSO
-pcap(3PCAP), pcap_activate(3PCAP)
+pcap(3PCAP)
diff --git a/pcap_dump.3pcap b/pcap_dump.3pcap
index 6402b4b4..7f201b7c 100644
--- a/pcap_dump.3pcap
+++ b/pcap_dump.3pcap
@@ -35,11 +35,11 @@ u_char *sp);
.SH DESCRIPTION
.B pcap_dump()
outputs a packet to the ``savefile'' opened with
-.BR pcap_dump_open() .
+.BR pcap_dump_open(3PCAP) .
Note that its calling arguments are suitable for use with
-.B pcap_dispatch()
+.B pcap_dispatch(3PCAP)
or
-.BR pcap_loop() .
+.BR pcap_loop(3PCAP) .
If called directly, the
.I user
parameter is of type
@@ -47,5 +47,4 @@ parameter is of type
as returned by
.BR pcap_dump_open() .
.SH SEE ALSO
-pcap(3PCAP), pcap_dump_open(3PCAP), pcap_dispatch(3PCAP),
-pcap_loop(3PCAP)
+pcap(3PCAP)
diff --git a/pcap_dump_file.3pcap b/pcap_dump_file.3pcap
index 8fea610a..d2074312 100644
--- a/pcap_dump_file.3pcap
+++ b/pcap_dump_file.3pcap
@@ -33,6 +33,6 @@ FILE *pcap_dump_file(pcap_dumper_t *p);
.SH DESCRIPTION
.B pcap_dump_file()
returns the standard I/O stream of the ``savefile'' opened by
-.BR pcap_dump_open() .
+.BR pcap_dump_open(3PCAP) .
.SH SEE ALSO
pcap(3PCAP)
diff --git a/pcap_dump_flush.3pcap b/pcap_dump_flush.3pcap
index c8f110bb..a2bd1418 100644
--- a/pcap_dump_flush.3pcap
+++ b/pcap_dump_flush.3pcap
@@ -34,10 +34,10 @@ int pcap_dump_flush(pcap_dumper_t *p);
.B pcap_dump_flush()
flushes the output buffer to the ``savefile,'' so that any packets
written with
-.B pcap_dump()
+.B pcap_dump(3PCAP)
but not yet written to the ``savefile'' will be written.
.SH RETURN VALUE
.B pcap_dump_flush()
returns 0 on success and \-1 on failure.
.SH SEE ALSO
-pcap(3PCAP), pcap_dump_open(3PCAP), pcap_dump(3PCAP)
+pcap(3PCAP), pcap_dump_open(3PCAP)
diff --git a/pcap_dump_ftell.3pcap b/pcap_dump_ftell.3pcap
index ec621fb3..a5af338f 100644
--- a/pcap_dump_ftell.3pcap
+++ b/pcap_dump_ftell.3pcap
@@ -36,9 +36,9 @@ int64_t pcap_dump_ftell64(pcap_dumper_t *p);
.B pcap_dump_ftell()
returns the current file position for the ``savefile'', representing the
number of bytes written by
-.B pcap_dump_open()
+.B pcap_dump_open(3PCAP)
and
-.BR pcap_dump() .
+.BR pcap_dump(3PCAP) .
\-1 is returned on error.
If the current file position does not fit in a
.BR long ,
@@ -54,4 +54,4 @@ but that fit in a
are supported, this will return the file offset without truncation.
\-1 is returned on error.
.SH SEE ALSO
-pcap(3PCAP), pcap_dump_open(3PCAP), pcap_dump(3PCAP)
+pcap(3PCAP)
diff --git a/pcap_file.3pcap b/pcap_file.3pcap
index cd6b06bb..5a983466 100644
--- a/pcap_file.3pcap
+++ b/pcap_file.3pcap
@@ -34,13 +34,13 @@ FILE *pcap_file(pcap_t *p);
.B pcap_file()
returns the standard I/O stream of the ``savefile,'' if a ``savefile''
was opened with
-.BR pcap_open_offline() ,
+.BR pcap_open_offline(3PCAP) ,
or NULL, if a network device was opened with
-.B pcap_create()
+.B pcap_create(3PCAP)
and
-.BR pcap_activate() ,
+.BR \%pcap_activate(3PCAP) ,
or with
-.BR pcap_open_live() .
+.BR pcap_open_live(3PCAP) .
.PP
Note that the Packet Capture library is usually built with large file
support, so the standard I/O stream of the ``savefile'' might refer to
@@ -54,4 +54,4 @@ or the value returned by
when passed the return value of
.BR pcap_file() .
.SH SEE ALSO
-pcap(3PCAP), pcap_open_offline(3PCAP)
+pcap(3PCAP)
diff --git a/pcap_fileno.3pcap b/pcap_fileno.3pcap
index e8c9ac4d..03465188 100644
--- a/pcap_fileno.3pcap
+++ b/pcap_fileno.3pcap
@@ -35,24 +35,24 @@ If
.I p
refers to a network device that was opened for a live capture using
a combination of
-.B pcap_create()
+.B pcap_create(3PCAP)
and
-.BR pcap_activate() ,
+.BR pcap_activate(3PCAP) ,
or using
-.BR pcap_open_live() ,
+.BR pcap_open_live(3PCAP) ,
.B pcap_fileno()
returns the file descriptor from which captured packets are read.
.LP
If
.I p
refers to a ``savefile'' that was opened using functions such as
-.BR pcap_open_offline()
+.BR pcap_open_offline(3PCAP)
or
-.BR pcap_fopen_offline() ,
+.BR pcap_fopen_offline(3PCAP) ,
a ``dead''
.B pcap_t
opened using
-.BR pcap_open_dead() ,
+.BR pcap_open_dead(3PCAP) ,
or a
.B pcap_t
that was created with
@@ -61,6 +61,4 @@ but that has not yet been activated with
.BR pcap_activate() ,
it returns \-1.
.SH SEE ALSO
-pcap(3PCAP), pcap_create(3PCAP), pcap_activate(3PCAP),
-pcap_open_live(3PCAP), pcap_open_offline(3PCAP),
-\%pcap_fopen_offline(3PCAP), pcap_open_dead(3PCAP)
+pcap(3PCAP)