PCAP_SET_TSTAMP_PRECISION(3PCAP)

💖 NAME 💖

okay bestie, this is PCAP_SET_TSTAMP_PRECISION(3PCAP) — yep, the 3PCAP manual — and the actual name is pcap_set_tstamp_precision: it sets the time stamp precision returned in captures. She’s specific, she’s useful, she slays. 💅

✨ SYNOPSIS ✨

#include <pcap/pcap.h>

int pcap_set_tstamp_precision(pcap_t *p, int tstamp_precision);

🌸 DESCRIPTION 🌸

So pcap_set_tstamp_precision() sets the precision of the time stamp you want for packets captured on the pcap descriptor, using the type you pass in tstamp_precision. Iconic behavior. 🎀

🚨 important vibe check: it must be called on a pcap descriptor created by pcap_create(3PCAP) that has not yet been activated by pcap_activate(3PCAP). No activating it first, bestie — that’s not the move. 😭

There are two time stamp precisions supported, microseconds and nanoseconds. You can use the options:

• PCAP_TSTAMP_PRECISION_MICRO — request microsecond precision.
• PCAP_TSTAMP_PRECISION_NANO — request nanosecond precision.

By default, time stamps are in microseconds. Periodt. ⭐

💅 RETURN VALUE 💅

pcap_set_tstamp_precision() returns:

• 0 on success, if the specified time stamp precision is expected to be supported by the capture device — we love a supportive device 🫶
• PCAP_ERROR_TSTAMP_PRECISION_NOTSUP if the capture device does not support the requested time stamp precision — the device said no 💀
• PCAP_ERROR_ACTIVATED if called on a capture handle that has been activated — you activated it first, bestie, and the function noticed 🙈

🦋 BACKWARD COMPATIBILITY 🦋

This function became available in libpcap release 1.5.1 🌈. In previous releases, time stamps from a capture device or savefile are always given in seconds and microseconds. So if you’re time-traveling in old libpcap, that’s the deal. 🕰️

🔥 SEE ALSO 🔥

• pcap(3PCAP)
• pcap_get_tstamp_precision(3PCAP)
• pcap-tstamp(7)

xoxo, the PCAP_SET_TSTAMP_PRECISION(3PCAP) page from libpcap 💖 — dated 23 August 2018 🎀