| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
When we scold programmers don't to assume that everything is Ethernet,
mention both DLT_LINUX_SLL and DLT_LINUX_SLL2 as possible link types for
the "any" device.
|
|
|
|
|
|
|
|
| |
Use the BSD house style, in which, in
foobar() returns 17 on success and 137 on failure.
"foobar" is boldfaced but "()" isn't.
|
|
|
|
|
|
|
| |
All manpage references such as pcap_create(3PCAP) will now be formatted
with the identifier (e.g. "pcap_create") in **bold** and the section
name (e.g. "(3PCAP)") in roman (default) face. This is how most manpages
seem to be formatted and makes things more consistent.
|
|
|
|
| |
[skip ci]
|
|
|
|
| |
[skip ci]
|
| |
|
|
|
|
|
| |
This change reflects only meaningful (i.e. not purely editorial) changes
in the text.
|
|
|
|
|
|
| |
This change removes CVS keywords that express that the file belongs to
libpcap repository. All such keywords represented the revision and
timestamp by the end of 2008 or even older.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Note for pcap_loop()/pcap_dispatch(), and for
pcap_next()/pcap_next_ex(), that in order to interpret the packets you
have to know the link-layer header type for the pcap_t, as returned by
pcap_datalink().
Note in all the places we discuss the value returned by pcap_datalink()
that the program *MUST NOT ASSUME* that it will return a particular
value, and specifically note that the Linux "any" device has a
pcap_datalink() value of DLT_LINUX_SLL even if all the network
interfaces on the system happen to have some other link-layer header
type.
|
|
|
|
|
|
|
|
|
|
|
| |
Return PCAP_ERROR_NOT_ACTIVATED, not PCAP_ERROR (-1), for calls to
pcap_datalink(), pcap_datalink_ext(), and pcap_list_datalinks() if
called on a non-activated pcap_t. Pre-pcap_create() code will never see
PCAP_ERROR_NOT_ACTIVATED, and code using pcap_create() will either not
see it (if it's correct) or is already getting bogus results (if it's
not correct).
Document that while we're at it.
|
|
|
|
|
|
| |
Use "link-layer header type" as the term for DLT_ values; it doesn't
necessarily correspond to the actual data link type of the device
(802.11 devices, for example, can supply Ethernet headers).
|
|
pcap-linktype man pages; it should be section 7 for UN*Xes using the
V7/BSD conventions (this includes *BSD, Linux, and Mac OS X), and
section 5 for UN*Xes using the System V conventions (this includes
Solaris and HP-UX, and possibly AIX).
|