Printable View
Hi. If i do
and it scans worse (only 1 or 2 APs appear) than doing directlyCode:airmon-ng start wlan0 && airodump-ng mon0
(appear all APs around )Code:airodump-ng wlan0
What may cause trouble to scanning on mon0? The card is ALFA, rtl8187 is the driver.
@Mods: Correct me if I'm wrong.
mon0 is an 'alias' of wlan0 in promiscious mode to sniff/intercept traffic, so scanning the area twice with physicly the same interface might cause collisions on the interface.
You can't have the same interface scanning different channels at the same time.
Either capture with mon0 or wlan0, not both.
Actually yes it's the same interface.Quote:
Originally Posted by voidnecron
oops. i was connected to my AP on wlan0 and trying to scan on mon0. That caused trouble )) I was damn sure it became possible in BT4. There was not any mon0 alias in BT3 and dumbs like me could not do it.
I don't get what's the difference between wlan0 and mon0. From some reason I can't get me assiciated with the AP while I'm using wlan0(got open system something error). With mon0 it works just fine.
Do I get mon0 only for wlan0 or there is mon0 wirh rausb0 as well?
hi try to do this
#airmon-ng start wlan0
"must appear that the interfaz mon0 its in mode monitor enabled"
#airmon-ng mon0
"must work correctly and you can see the networks availables
Using wlanconfigQuote:
Originally Posted by NoaHjk
Isnt that only used for VAPs ?Quote:
Originally Posted by Barry
It was more for an explanation of what a VAP is.Quote:
Originally Posted by TAPE