Hi, I have managed to get the "kismet" package to build using the latest upstream version (kismet-2010-07-R1) and with a few other modifications. The configuration file format has changed from the Bering-uClibc v3.x version (kismet-2007) and I would like to do some more testing before loading the code into CVS.
The kismet build process complains loudly if it cannot find libnl (netlink), either v1 or ideally v2. It looks for libnl by checking for a .pc (package config) file in $(BT_STAGING_DIR)/usr/lib/pkgconfig and this does not exist even though we have libnl v1.1 installed. (That's easy enough to fix by tweaking the buildtool.mk for libnl to copy the .pc file to the right place. I have not done that yet, but I will.) What I discovered is that libnl v1.1 is rather old - 2008 as far as I can tell - even though that is the newest pre-packaged download available at the libnl site. The libnl v2 code is available by downloading HEAD from their git repository, and the latest changes are from April 2010 so it is reasonably stable. I did get libnl v2 to build before I understood the problem with v1 and the .pc file, though this needed some work with automake / aclocal. I wonder whether the newer libnl might help with some of the other WiFi issues... or we could just switch to the new libnl anyway. Does anyone know if it is just hostapd which uses libnl (apart from kismet)? Anyway, kismet is well on the way to being fixed. I expect I will load the working version into CVS tomorrow. davidMbrooke ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ leaf-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/leaf-devel
