Kismet Wireless

Kismet Forums

 

Posted by:fisted
Subject:kismet_server - segfault in libnl prior to main()
Date:23:31:38 21/11/2012

> > libnl mailing list says this, dragorn:
> >
> > > # ldd ./kismet_server
> > [...]
> > > libnl-genl-3.so.200 => /usr/lib64/libnl-genl-3.so.200
> > > (0x00007fa051ed2000)
> > > libnl-3.so.200 => /usr/lib64/libnl-3.so.200 (0x00007fa051cb6000)
> > [...]
> > > libnl.so.1 => /usr/lib64/libnl.so.1 (0x00007fa050d82000)
> >
> > Linking to two different libnl versions at the same time is not
> > supported. They have partially compatible APIs which obviously
> > conflict so you have libnl1 symbols using libnl3 symbols. Therefore
> > the segfault.
>
> Shouldn't be linking to two. Libbl3 post-dates the 2011 release, so try git.

I rather think it's a bug in kismet's autoconf setup - if libnl1 and libnl3 are available, it seems to link them both.
Contrary, if neither is available, configure notices that and warns about the consequences, anyway, compiling it fails.
With only libnl1 OR libnl3 installed, it's all good.

So perhaps kismet's autohell should disregard libnl1 entirely, if libnl3 is found.

PS: i was using the git version of kismet all the time


Reply to this message