| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* amount
* anymore
* authentication
* availability
* bracket
* captured
* casted
* communications
* compliant
* configurable
* cumulate
* deinitialize
* descriptors
* didn't
* disassembler
* disassociate
* distributions
* divvy
* doing
* entries
* everything
* explicitly
* explosion
* expression
* extracting
* failed
* family
* find
* github
* global
* implementations
* incorrectly
* intel
* interlocked
* justifying
* know
* launched
* libraries
* malloced
* mask
* maximum
* network
* nonexistent
* number
* occurred
* optimizer
* overflow
* overwrite lower
* packet
* packetfilter
* packets
* parse hosts
* payload
* phase
* programmers
* promiscuous
* protocol
* receiving
* redefinition
* sampling
* savefile
* schwartz
* should
* snapshot
* something
* specifies
* straightforward
* stream
* subdir
* support
* surrogate
* suse
* system is
* test with
* than
* those
* unmaintained
* valid
* way
* western
* wireshark
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
|
|
|
|
|
|
|
|
|
|
| |
This gives it a name similar to the other README.{operatingsystem}
files.
It also reflects that 1) 16-bit Windows is now so old and tired that
there's no need to use a name that specifically mentions a non-16-bit
version of Windows to indicates that we don't support it and 2) there's
now 64-bit Windows, so "Win32" is an out-of-date name.
|
|
|
|
|
| |
Do not suggest installing the system libpcap_devel package as a build
dependency, add a section for the 32-bit version.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
[skip ci]
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
(npcap.org redirects there.)
[skip ci]
|
|
|
|
|
|
| |
Remove the file from EXTRA_DIST, but keep it for a while longer to point
to the new location (at least chapter 8.1 in Wireshark Developer's Guide
still uses the old URL).
|
|
|
|
| |
This document has been merged into tcpdump-htdocs.
|
|
|
|
|
|
|
|
|
|
|
| |
The following operating systems are either extinct or not supported or
otherwise have been out of contact with libpcap code for many years:
UnixWare, SCO UNIX, SINIX, NeXTSTEP, {DEC OSF/1, Digital UNIX, Tru64
UNIX}, Ultrix, SunOS < 5.3.2, Linux < 2.6.27 and older AIX.
Remove respective prose from the installation documentation, as well as
the passage about counterfeit tcpdump 3.0.3, which is a common wisdom
nowadays. Update the remaining HP-UX section for C99.
|
| |
|
| |
|
| |
|
|
|
|
| |
Document more exemptions for Solaris 11.
|
| |
|
|
|
|
|
|
| |
README.linux is a plain text file, rendering it as Markdown produces
unreadable results. When and if someone converts it to a proper
Markdown, it will be appropriate to rename the file again.
|
| |
|
|
|
|
| |
[skip ci]
|
|
|
|
|
|
|
| |
[skip ci]
We require Linux 2.6.27 or later, and the only configuration option that
applies is CONFIG_PACKET_MMAP, which we require on 2.6.x kernels - 3.x
and later kernels have memory-mapped capture support built in.
|
| |
|
|
|
|
| |
[skip ci]
|
|
|
|
| |
[skip ci]
|
| |
|
|
|
|
| |
[skip ci]
|
|
|
|
| |
[skip ci]
|
|
|
|
|
|
|
| |
It's clearer just to give the commands, as we do for running CMake and
msbuild in a command-line build.
[skip ci]
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Also:
Indicate the name of the components to install to get CMake.
Indicate how to build libpcap from Visual Studio once CMake has finished
successfully.
Clean up some VS 2019 stuff.
[skip ci]
|
|
|
|
|
|
| |
The two spaces separate it from the text if you read the file as plain
text, and it doesn't cause the URL to be displayed as raw non-link
fixed-width text when it's formatte as Markdown.
|
|
|
|
|
| |
Markdown will show them as fixed-width un-clickable text if indented
with tabs, but will show them as indented links if indented with spaces.
|
|
|
|
|
|
| |
This is based on testing with Visual Studio 2019 on Windows 10; more
information should be added for Visual Studio 2017 and Visual Studio
2015.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This is a work in progress, and needs to be completed, but I want
something I can point a section in the Wireshark Developer's Guide to,
and to at least *start* providing help for module writers.
XXX - do this in Markdown?
|
|
|
| |
Fixed a few minor typos while reading through the DAG documentation.
|
| |
|
|
|
| |
Fixed a minor type in the README.linux.md file.
|
| |
|
| |
|
|
|
|
| |
[skip ci]
|
|
|
|
| |
Signed-off-by: Petr Vorel <pvorel@suse.cz>
|
| |
|
| |
|
| |
|