Hi Guy, Guy Harris <g...@alum.mit.edu> writes:
> Using libnl to create a monN interface works better than using Wireless > Extension ioctls to turn on monitor mode, which is what libpcap does if > *not* linked with libnl. Can you provide more information about the problems the libnl mode fixes? How exactly does it work better? I've never received any bug reports about this before so I'm trying to evaluate if tying libpcap to libnl is worth the cost, especially since libnl in Debian looks somewhat messy--we have three different versions maintained by two different people. If the wext mode is good enough for most users, I'd rather not add a binary dependency to libpcap0.8 (especially since so far it had a minimal set, only libc6). > Depending on how the Debian build process works, this might be the > result of libnl not being given in the Build-Depends section of > libpcap's "control" file - if the build process runs the configure > script, and libnl *and* libnl-devel aren't present when the configure > script is run, the configure script won't find libnl and will build > without it. Yes, packages are built in a clean environment with only their listed build dependencies installed. Thanks, -- Romain Francoise <rfranco...@debian.org> http://people.debian.org/~rfrancoise/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
