[tcpdump-workers] Re: Pcap debug at runtime

On 02/03/2023 09:22, Francois-Xavier Le Bail wrote: > On 01/03/2023 20:28, Denis Ovsienko wrote: >> On Tue, 28 Feb 2023 17:01:51 +0100 >> Francois-Xavier Le Bail wrote: >> >>> In addition to printf()/fprintf(), here is a brand new way to help >>> debugging a program using libpcap, currently only

[tcpdump-workers] Re: Pcap debug at runtime

[Send, second try] On 02/03/2023 09:22, Francois-Xavier Le Bail wrote: > On 01/03/2023 20:28, Denis Ovsienko wrote: >> On Tue, 28 Feb 2023 17:01:51 +0100 >> Francois-Xavier Le Bail wrote: >> >>> In addition to printf()/fprintf(), here is a brand new way to help >>> debugging a program using

[tcpdump-workers] Sharing code between print-icmp.c and print-icmp6.c

Hi, I'm working on RFC8335 (PROBE) support for tcpdump - I've already submitted the pull request for IPv4. I'm working on IPv6 support, and it looks like this is the first case that the packet format is identical between ICMP and ICMPv6 but complex enough that it's worth reusing code. My commit

[tcpdump-workers] Re: Sharing code between print-icmp.c and print-icmp6.c

On Feb 5, 2024, at 9:38 AM, Bill Fenner wrote: > Is this a reasonable way to proceed? Yes. Perhaps have a file icmp-common.c or print-icmp-common.c with code and data structures common to ICMP(v4) and ICMPv6? ___ tcpdump-workers mailing list --

[tcpdump-workers] Re: Test

Guy Harris wrote: > Is the list working? It was not. I finally found the web process hanging onto a database lock, and cleared that. ___ tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org To unsubscribe send an email to

[tcpdump-workers] Test

Is the list working? ___ tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s