aireplay-ng error -1 channel

[nix]

i know there are threads on how to fix this, but i followed then and i patched the kernel as per the instructions on
https://forums.kali.org/showthread.p...rt2870-3070usb

and also on

http://www.aircrack-ng.org/doku.php?id=compat-wireless

with the aircrack-ng instruction when i do the make wlunload i get the following error
"make: *** No rule to make target `wlunload'. Stop."

so i just skiped to the next step and it showed that everything was fine

but i still get the following message

19:44:16 Waiting for beacon frame (BSSID: xx:xx:xx:xx:xx:xx) on channel -1
19:44:16 Couldn't determine current channel for mon0, you should either force the operation with --ignore-negative-one or apply a kernel patch


it works with the --ignore-negative-one, but i thought patching will fix that

airmon-ng shows the followng driver

airmon-ng


Interface Chipset Driver

mon0 Atheros AR9462 ath9k - [phy0]
wlan0 Atheros AR9462 ath9k - [phy0]


thanks again

Nix

[nix]

actually even the --ignore-negative-one won't work
it looks like it's working but it's not dauthenticating

[nix]

anyone ?...i can't be the only one that ran into this issue

[tr00n3r]

for me following is working: (no patches applied or using other drivers than in Kali)

airmon-ng check      // will list services that could effect airmon
airmon-ng check kill // will list services and kill it

airmon-ng start wlan0

without doing code above I am also fixed to channel 1

after that channel 1 issue is gone - using Alfa USB NH36... (sorry don't have the exact model at the moment)

written here: http://www.aircrack-ng.org/doku.php?id=airmon-ng
<check|check kill> “check” will show any processes that might interfere with the aircrack-ng suite. It is strongly recommended that these processes be eliminated prior to using the aircrack-ng suite. “check kill” will check and kill off processes that might interfere with the aircrack-ng suite

if check kill fails:
http://www.aircrack-ng.org/doku.php?...eck_kill_fails

[nix]

yes that works, and also if you just bring down wlan0 ifconfig wlan0 down

but it use to work without all those steps, that's why i was surprised when it stoped working and you need to do this now.

my problem with airmon-ng check kill is that once i was done i could not bring back up my interface, i had to reboot, is there another wy to bring them up?

[tr00n3r]

following these steps after you have done your airmoning
this should remove your mon0 interface (without bringing interfaces down)

airmon-ng stop mon0

Interface	Chipset		Driver

mon0		Atheros AR9271	ath9k - [phy0] (removed)
wlan0		Atheros AR9271	ath9k - [phy0]

also check with iwfconfig if it has been removed:

iwconfig
eth0      no wireless extensions.

lo        no wireless extensions.

wlan0     IEEE 802.11bgn  ESSID:off/any  
          Mode:Managed  Access Point: Not-Associated   Tx-Power=20 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off

if you want you network working properly after airmoning:

service network-manager start
dhclient <interface> example: wlan0

hope this helps!