On 2015-11-06 at 16:53:02 +0100, Vadim Kochan <[email protected]> wrote: > On Fri, Nov 06, 2015 at 04:36:08PM +0100, Tobias Klauser wrote: > > On 2015-11-06 at 15:46:16 +0100, Vadim Kochan <[email protected]> wrote: > > > libnl-route is used in netsniff-ng tool for dump nlmsg flags. > > > > > > Signed-off-by: Vadim Kochan <[email protected]> > > > > Good catch! Applied, thanks. > > I think it would be good to make (if it is possible) to make libnl > dependency optionally. As I remember is is used mostly for creating mon > interfaces, so may be it is better to do just panic if the config for > libnl is not defined by configure script, so it will be needed to wrap > libnl callers with #ifdef's where panic will be invoked.
Besides the nlmsg dissector it's used for rfmon support, i.e. this would mean making making --rfraw in netsniff-ng and trafgen compile time dependent. I would much prefer to avoid this, unless there's a strong reason for it. Do you see a use case for an netsniff-ng without libnl to justify this change? Given also, that all major distributions I know of provide libnl and it has a rather small footprint... -- You received this message because you are subscribed to the Google Groups "netsniff-ng" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
