Thank you, I’ll do this.
From: Guy Harris
Sent: Monday, February 20, 2023 3:18:24 PM
To: Paschal Chukwuebuk Amusuo
Cc: tcpdump-workers@lists.tcpdump.org
Subject: Re: [tcpdump-workers] Pcap debug at runtime
External Email: Use caution with attachments, links
On Feb 20, 2023, at 12:15 PM, Paschal Chukwuebuk Amusuo
wrote:
> Please, is there a way to print out debug statements at runtime when using
> pcap?
Debug statements in your program? Add printf() or fprintf(stderr, ...) or...
calls to your program.
Debug statements in libpcap? Get the libpc
Hi,
Please, is there a way to print out debug statements at runtime when using pcap?
I am experiencing some weird behavior when using pcap. Packets get stuck in
pcap even when using immediate mode. I would love for a way to view debug logs
and maybe, understand what’s happening.
On Feb 20, 2023, at 2:20 AM, Guy Harris wrote:
> So the code is correct, but could easily be misintrpreted. Perhaps it'd be
> better if we used the values from af.h rather than using AF_INET and
> AF_INET6.
Done in 0dc32a024773968cb1ae00729758e61b7418564a
I'll see whether anything else use
On Feb 20, 2023, at 12:17 AM, Denis Ovsienko wrote:
> AF_INET6 looks a bit more convoluted. There is some code that uses
> AF_INET6 to dissect wire encoding, which is usually a wrong idea. For
> example, pimv2_addr_print() switches on AF_INET and AF_INET6, and the
> PIMv2 header encoding (RFC 4
On Sun, 17 Jul 2022 15:29:39 -0700
Guy Harris via tcpdump-workers
wrote:
> On Jul 17, 2022, at 11:09 AM, Francois-Xavier Le Bail
> wrote:
>
> > Remain some stuff about 'struct in6_addr'. Any need to keep them?
> >
> > $ git grep -l 'struct in6_addr'
> > CMakeLists.txt
> > cmakeconfig.h.in
> >
