pcap

In the field of computer network administration, pcap is an application programming interface (API) for capturing network traffic. While the name is an abbreviation of packet capture, that is not the API's proper name. Unix-like systems implement pcap in the libpcap library; for Windows, there is a port of libpcap named WinPcap that is no longer supported or developed, and a port named Npcap for Windows 7 and later that is still supported.

libpcap
Developer(s)The Tcpdump team
Stable release
1.9.1 / September 30, 2019 (2019-09-30)[1]
Repositorylibpcap on GitHub
Written inC
Operating systemLinux, Solaris, FreeBSD, NetBSD, OpenBSD, macOS, other Unix-like
TypeLibrary for packet capture
LicenseBSD[2]
Websitewww.tcpdump.org
WinPcap
Developer(s)Riverbed Technology
Final release
4.1.3 / March 8, 2013 (2013-03-08)[3]
Operating systemWindows
TypeLibrary for packet capture
LicenseFreeware
Websitewww.winpcap.org
Npcap
Developer(s)the Nmap project
Stable release
0.9996 / August 7, 2020 (2020-08-07)[4]
Operating systemWindows
TypeLibrary for packet capture
Websitenmap.org/npcap

Monitoring software may use libpcap, WinPcap, or Npcap to capture network packets travelling over a computer network and, in newer versions, to transmit packets on a network at the link layer, and to get a list of network interfaces for possible use with libpcap, WinPcap, or Npcap.

The pcap API is written in C, so other languages such as Java, .NET languages, and scripting languages generally use a wrapper; no such wrappers are provided by libpcap or WinPcap itself. C++ programs may link directly to the C API or use an object-oriented wrapper.

Features

libpcap, WinPcap, and Npcap provide the packet-capture and filtering engines of many open-source and commercial network tools, including protocol analyzers (packet sniffers), network monitors, network intrusion detection systems, traffic-generators and network-testers.

libpcap, WinPcap, and Npcap also support saving captured packets to a file, and reading files containing saved packets; applications can be written, using libpcap, WinPcap, or Npcap, to be able to capture network traffic and analyze it, or to read a saved capture and analyze it, using the same analysis code. A capture file saved in the format that libpcap, WinPcap, and Npcap use can be read by applications that understand that format, such as tcpdump, Wireshark, CA NetMaster, or Microsoft Network Monitor 3.x.

The MIME type for the file format created and read by libpcap, WinPcap, and Npcap is application/vnd.tcpdump.pcap. The typical file extension is .pcap, although .cap and .dmp are also in common use.[5]

History

libpcap was originally developed by the tcpdump developers in the Network Research Group at Lawrence Berkeley Laboratory. The low-level packet capture, capture file reading, and capture file writing code of tcpdump was extracted and made into a library, with which tcpdump was linked.[6] It is now developed by the same tcpdump.org group that develops tcpdump.[7]

pcap libraries for Windows

While libpcap was originally developed for Unix-like operating systems, a successful port for Windows was made, called WinPcap. It has been unmaintained since 2013,[8] and several competing forks have been released with new features and support for newer versions of Windows.

WinPcap

WinPcap consists of:[9]

Programmers at the Politecnico di Torino wrote the original code; as of 2008 CACE Technologies, a company set up by some of the WinPcap developers, developed and maintained the product. CACE was acquired by Riverbed Technology on October 21, 2010.[10]

Because WinPcap uses the older NDIS 5.x APIs, it does not work on some builds of Windows 10, which have deprecated or removed those APIs in favor of the newer NDIS 6.x APIs. It also forces some limitations such as being unable to capture 802.1Q VLAN tags in Ethernet headers.

Npcap

Npcap is the Nmap Project's packet sniffing library for Windows.[11] It is based on the Winpcap / Libpcap libraries, but with improved speed, portability, security, and efficiency. Npcap offers:

  • NDIS 6 Support: Npcap makes use of new NDIS 6 Light-Weight Filter (LWF) API in Windows Vista and later (the legacy driver is used on XP). It's faster than the deprecated NDIS 5 API.
  • Latest libpcap API Support: Npcap provides support for the latest libpcap API by accepting libpcap as a Git submodule. The latest libpcap 1.8.0 has integrated more fascinating features and functions than the deprecated libpcap 1.0.0 shipped by WinPcap. Moreover, since Linux already has a good support for latest libpcap API, using Npcap on Windows facilitates software to base on the same API on both Windows and Linux.
  • Extra Security: Npcap can be restricted so that only Administrators can sniff packets. Non-Admin user will have to pass a User Account Control (UAC) dialog to utilize the driver. This is conceptually similar to UNIX, where root access is generally required to capture packets. The driver also has Windows ASLR and DEP security features enabled.
  • WinPcap compatibility: If selected, Npcap will use the WinPcap-style DLL directories (“c:\Windows\System32”) and service name (“npf”), allowing software built with WinPcap in mind to transparently use Npcap instead. If compatibility mode is not selected, Npcap is installed in a different location with a different service name so that both drivers can coexist on the same system.
  • Loopback Packet Capture: Npcap is able to sniff loopback packets (transmissions between services on the same machine) by using the Windows Filtering Platform (WFP). After installation, Npcap will create an adapter named Npcap Loopback Adapter.
  • Loopback Packet Injection: Npcap is also able to send loopback packets using the Winsock Kernel (WSK) technique.
  • Raw 802.11 Packet Capture: Npcap is able to see 802.11 packets instead of fake Ethernet packets on ordinary wireless adapters.

Win10Pcap

Win10Pcap implementation is also based on the NDIS 6 driver model and works stably with Windows 10.[12]

As of 2020, the project has however been inactive since 2016[13].

Programs that use libpcap

  • Apache Drill, an open source SQL engine for interactive analysis of large scale datasets.
  • Bit-Twist, a libpcap-based Ethernet packet generator and editor for BSD, Linux, and Windows.
  • Cain and Abel, a password recovery tool for Microsoft Windows
  • EtherApe, a graphical tool for monitoring network traffic and bandwidth usage in real time.
  • Firesheep, an extension for the Firefox web browser that captures packets and performs session hijacking
  • iftop, a tool for displaying bandwidth usage (like top for network traffic)
  • Kismet, for 802.11 wireless LANs
  • L0phtCrack, a password auditing and recovery application.
  • McAfee ePolicy Orchestrator, Rogue System Detection feature
  • ngrep, aka "network grep", isolate strings in packets, show packet data in human-friendly output.
  • Nmap, a port-scanning and fingerprinting network utility
  • Pirni, a network security tool for jailbroken iOS devices.
  • Scapy, a packet manipulation tool for computer networks, written in Python by Philippe Biondi.
  • Snort, a network-intrusion-detection system.
  • Suricata, a network intrusion prevention and analysis platform.
  • Symantec Data Loss Prevention, Used to monitor and identify sensitive data, track its use, and location. Data loss policies allow sensitive data to be blocked from leaving the network or copied to another device.
  • tcpdump, a tool for capturing and dumping packets for further analysis, and WinDump, the Windows port of tcpdump.
  • the Bro IDS and network monitoring platform.
  • URL Snooper, locate the URLs of audio and video files in order to allow recording them.
  • WhatPulse, a statistical (input, network, uptime) measuring application.
  • Wireshark (formerly Ethereal), a graphical packet-capture and protocol-analysis tool.
  • XLink Kai Software that allows various LAN console games to be played online
  • Xplico, a network forensics analysis tool (NFAT).

Wrapper libraries for libpcap

Non-pcap code that reads pcap files

gollark: In what way?
gollark: I also apparently don't have the disconnect function down yet.
gollark: Probably not worth setting up yet.
gollark: Well, each guild has a "phone" "number" generated from a hash of its ID, which can then be used by other people to "call" it. When you "call" it, the people there are asked to take the call. If they accept, it adds it to the "calls" database, and currently does nothing.
gollark: Anyone with "manage channels".

References

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.