|
2011-07-30
, 07:38
|
|
Posts: 298 |
Thanked: 341 times |
Joined on Aug 2010
@ This world :)
|
#122
|
Happy to help.
BTW, did "dpkg -l | grep aircrack-ng" return one or two results? It's quiet likely you had both "aircrack-ng" and "aircrack-ng-1.1" or something like the latter installed. If so it would explain where the extra binaries came from. (That's where all the aircrack-ng packages would put the binaries into until I took over maintenance and figured out how to change install paths.)
At any rate, if that's the case I suggest removing all the 'extra' aircrack-ng binaries from /usr/local/bin and /usr/local/sbin - they're most likely going to be much older versions.
Good luck with your work on fAircrack
|
2011-12-02
, 19:41
|
Posts: 1,680 |
Thanked: 3,685 times |
Joined on Jan 2011
|
#123
|
The Following 3 Users Say Thank You to vi_ For This Useful Post: | ||
|
2012-08-04
, 23:22
|
Posts: 2,225 |
Thanked: 3,822 times |
Joined on Jun 2010
@ Florida
|
#124
|
Greetz traceur.
It would seem that airmon-ng is totally brorken. This is because airmon-ng relies upon some switches for 'ps' that are not available for busybox or BB power.
There are only two ways (that I can think of) to fix this problem.
1. Package full-fat ps from debian lenny armel and make aircrack-ng depend on it.
2. Rip airmon-ng apart and make it specific for the n900. Airmon-ng is a generic tool designed to put any card into monitor mode. Thus it has a lot of hardware 'detection' and failsafe routines. The n900 has 1 card. There is only 2 ways to put it into monitor (iw or iwconfig (probably more)). Thus airmon-ng can be modified to be n900 specific.
If you have any interest in updating aircrack-ng I will start on the latter if you cannot be assed with the former (which would be the better solution (less chance of future breakage)).
|
2013-05-13
, 08:22
|
|
Posts: 1,974 |
Thanked: 1,834 times |
Joined on Mar 2013
@ india
|
#125
|
|
2013-09-19
, 05:53
|
Posts: 2,225 |
Thanked: 3,822 times |
Joined on Jun 2010
@ Florida
|
#126
|
The Following 4 Users Say Thank You to Mentalist Traceur For This Useful Post: | ||
|
2014-04-17
, 10:23
|
Posts: 1,163 |
Thanked: 1,873 times |
Joined on Feb 2011
@ The Netherlands
|
#127
|
The Following User Says Thank You to mr_pingu For This Useful Post: | ||
|
2015-01-25
, 20:02
|
Posts: 2,225 |
Thanked: 3,822 times |
Joined on Jun 2010
@ Florida
|
#128
|
|
2015-01-25
, 23:16
|
Posts: 2,225 |
Thanked: 3,822 times |
Joined on Jun 2010
@ Florida
|
#129
|
|
2015-01-28
, 05:49
|
Posts: 2,225 |
Thanked: 3,822 times |
Joined on Jun 2010
@ Florida
|
#130
|
The Following 4 Users Say Thank You to Mentalist Traceur For This Useful Post: | ||
BTW, did "dpkg -l | grep aircrack-ng" return one or two results? It's quiet likely you had both "aircrack-ng" and "aircrack-ng-1.1" or something like the latter installed. If so it would explain where the extra binaries came from. (That's where all the aircrack-ng packages would put the binaries into until I took over maintenance and figured out how to change install paths.)
At any rate, if that's the case I suggest removing all the 'extra' aircrack-ng binaries from /usr/local/bin and /usr/local/sbin - they're most likely going to be much older versions.
Good luck with your work on fAircrack