On 11/06/2015 04:53 PM, Vadim Kochan 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 <vadi...@gmail.com> wrote:
libnl-route is used in netsniff-ng tool for dump nlmsg flags.
Signed-off-by: Vadim Kochan <vadi...@gmail.com>
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.
I'm fine with that iff we throw a proper error in such cases (i.e. that
it was built w/o libnl support and therefore the setup cannot be supported).
Thanks,
Daniel
--
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 netsniff-ng+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
