--- Begin Message ----------- Forwarded Message -------- Subject: Re: [tcpdump] About smiInit() parameter On 30/03/2020 19:54, Guy Harris wrote: > >> On Mar 30, 2020, at 10:24 AM, Francois-Xavier Le Bail >> <devel.fx.leb...@orange.fr> wrote: >> >> Hi Guy, >> >> We have: >> $ git grep -n '"tcpdump"' >> netdissect.c:72: smiInit("tcpdump"); >> >> netdissect.c is a part of libnetdissect. >> >> Should we use >> smiInit("libnetdissect"); >> or something else to separate the lib and the tool ? > > The man page at > > https://www.ibr.cs.tu-bs.de/projects/libsmi/smi_config.html > > [...] > > I don't know if anybody's actually *using* that particular libsmi feature, > but smiInit has been called with "tcpdump" as an argument since at least > tcpdump 0.7. For what it's worth, the configuration file example they give > in the man page *does* have a "tcpdump:" statement in it: > > Example configuration: > [...] > > tcpdump: load DISMAN-SCRIPT-MIB > > so there might be some who have "tcpdump:" statements in libsmi configuration > files.Yes, good point. > So either > > 1) we should consider leaving "tcpdump" there Yes. > 2) we should make the tag an argument to nd_init and pass it "tcpdump" > from tcpdump > > although the latter means that any new program using libnetdissect might > dissect SNMP packets differently from tcpdump, whether that's a bug or a > feature. Because the choice is difficult here. If someone complain in the list or in an issue, we could consider an update.
--- End Message ---
_______________________________________________ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
