fix aireplay-ng --ignore-negative-one or apply a kernel patch

[mustapha]

I'm not responsible if you use this for illegal things

HI this is my first thread here

if any one have this trouble when you type airplay-ng -1 0 -a XX:XX:XX:XX:XX:XX mon0 or anything like it




root@kali:~# aireplay-ng -1 0 -a XX:XX:XX:XX:XX:XX mon0
No source MAC (-h) specified. Using the device MAC ( XX:XX:XX:XX:XX:XX)
11:41:04 Waiting for beacon frame (BSSID: XX:XX:XX:XX:XX:XX) on channel -1
11:41:04 Couldn't determine current channel for mon0, you should either force the operation with --ignore-negative-one or apply a kernel patch
Please specify an ESSID (-e).



when i was playing in terminal i didn't know the solution but it was very easy and because of that i didnt thought of it the solution is to kill the process NetworkManager when you type in terminal airmon-ng walnX start it will show up like this


Found 3 processes that could cause trouble.
If airodump-ng, aireplay-ng or airtun-ng stops working after
a short period of time, you may want to kill (some of) them!
-e
PID Name
2959 NetworkManager
3728 wpa_supplicant
4096 dhclient

kill it and for the best kill all of them


important after you kill it you can't connetct to any bssid beacuse the NetworkManger will shutdown you most reactivate it by typing in terminal NetworkManager

i want to added something but i don't know if this right i thing when you kill NetworkManager will solve the fixed channel -1 because of third line

Waiting for beacon frame (BSSID: XX:XX:XX:XX:XX:XX) on channel -1
but like i said maybe it will fix it i don't know but you can try it nothing to lose right

that's it
i make this thread to help everybody was in this trouble like me and if any one did this thread before then i'm sorry to repeat it


Goodbye Everyone

[VleNik]

Hello mustapha

I had the same problem.
You could kill the NetworkManager process to 'fix' the channel -1 error, but I just brought my interface down after turning on my monitor-interface.
Commands:
First, launch monitor-interface:
airmon-ng start <INTERFACE>

Example:

root@vlenik:~# airmon-ng start wlan0

Second, bring down the interface:
ifconfig <INTERFACE> down

Example:

root@vlenik:~# ifconfig wlan0 down

[mustapha]

Hello mustapha

I had the same problem.
You could kill the NetworkManager process to 'fix' the channel -1 error, but I just brought my interface down after turning on my monitor-interface.
Commands:
First, launch monitor-interface:
airmon-ng start <INTERFACE>

Example:

root@vlenik:~# airmon-ng start wlan0

Second, bring down the interface:
ifconfig <INTERFACE> down

Example:

root@vlenik:~# ifconfig wlan0 down
thanks this worked to me too