aireplay-ng
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
aireplay-ng [2018/03/11 19:06] mister_x updated link to bug tracker |
aireplay-ng [2019/08/20 22:50] (current) mister_x [interfaceX is on channel Y, but the AP uses channel Z] Fixed link |
||
|---|---|---|---|
| Line 244: | Line 244: | ||
| This means something is causing your card to channel hop. Possible reasons is that failed to start airodump-ng locked to a single channel. airodump-ng needs to be started with "-c <channel-number>. | This means something is causing your card to channel hop. Possible reasons is that failed to start airodump-ng locked to a single channel. airodump-ng needs to be started with "-c <channel-number>. | ||
| - | Another reason is that you have processes such as a network manager or wpa_supplicant channel hopping. You must kill off all these processes. See[airmon-ng] for details on checking what is running and how to kill the processes off. | + | Another reason is that you have processes such as a network manager or wpa_supplicant channel hopping. You must kill off all these processes. See [[airmon-ng]] for details on checking what is running and how to kill the processes off. |
| ==== General ==== | ==== General ==== | ||
aireplay-ng.txt · Last modified: 2019/08/20 22:50 by mister_x
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
