airsnort depends on linux-wlan-ng
Bug #4494 reported by
Johannes Steidl
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| airsnort (Ubuntu) |
Invalid
|
Medium
|
MOTU | ||
Bug Description
when executing airsnort /sbin/wlanctl-ng is called ... available in linux-wlan-ng. should be a dependency of airsnort-0.2.7e-1
Revision history for this message
| Sitsofe Wheeler (sitsofe) wrote Explicit dependency would be inappropriate | #1 |
| Changed in airsnort: | |
| assignee: | nobody → motu |
Revision history for this message
| Barry deFreese (bddebian) wrote | #2 |
| Changed in airsnort: | |
| status: | Unconfirmed → Rejected |
To post a comment you must log in.
It is possible to have airsnort use any wifi driver that supports PF_PACKET (as noted in the README file) even though it defaults to wlan-ng. Whether it tries to execute /sbin/wlanctl-ng depends on whether you've told the interface that you are using a driver type of wlan-ng.
As it happens wlan-ng is even a suggested packages but anything more than that would be overkill for those without prism based cards (or had monitor mode working via hostap or newer orinoco drivers) who wanted to use airsnort.
Related to bug #510 .