Re: BPF issues that require careful planning

[Denis Ovsienko <denis () ovsienko info>]

On Tue, 7 Jan 2025 16:38:30 +0000
Denis Ovsienko <denis () ovsienko info> wrote:

> 4. The "enable/disable IPv6" build option, when non-standard IPv6
> stacks were commonplace and libpcap depended on these, had a purpose
> and managed the optional dependency.  After quite some development in
>    libpcap and elsewhere --enable-ipv6 has been the default for a
> while and the effect of --disable-ipv6 became very patchy.  For
> example, "ether proto \ip6" stops working, but "ip6" continues to
> work, even though both mean exactly the same (EtherType 0x86dd) and
> do not depend on IPv6-specific code.  Likewise, "ip6 host ::1" and
> "ip6 net ff::/8" consistently stop working, but "icmp6", "ip6 proto
> \tcp", "ip6 and tcp port 80" and "ip6 protochain 17" continue to
> work.  It seems most useful to lose the build option and to make all
> IPv6 syntax always available.  (This would also eliminate a half of
>    libpcap CI build matrix.)

libpcap pull request 1504 implements this, if anyone wishes to tell a
sound reason not to proceed, please do it now.  Otherwise this change is
going to be made in about a week.

-- 
    Denis Ovsienko
_______________________________________________
tcpdump-workers mailing list -- tcpdump-workers () lists tcpdump org
To unsubscribe send an email to tcpdump-workers-leave () lists tcpdump org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s