Author Topic: problem with monitor mode  (Read 805 times)

0 Members and 1 Guest are viewing this topic.

Offline morbid

  • NULL
  • Posts: 4
  • Cookies: 0
    • View Profile
problem with monitor mode
« on: November 28, 2014, 09:58:45 pm »
Hey guys,
I'm having some trouble getting my Alfa external wireless card (wlan1) into monitor mode.  im connected to my wifi through wlan0. have killed the processes, run sudo airmon-ng start -i wlan1 and it shows the wireless cards but no monitor mode. had this problem recently with Kali also but worked great in the past doing the same. any suggestions?

orbid@Morbid ~ $ sudo airmon-ng


Interface    Chipset        Driver

wlan0        Unknown     iwlwifi - [phy0]
wlan1        Atheros     ath9k - [phy1]

morbid@Morbid ~ $ sudo airmon-ng start -i wlan1


Found 5 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!

PID    Name
737    avahi-daemon
740    avahi-daemon
1159    NetworkManager
1225    wpa_supplicant
1902    dhclient
Process with PID 1902 (dhclient) is running on interface wlan0


Interface    Chipset        Driver

wlan0        Unknown     iwlwifi - [phy0]
wlan1        Atheros     ath9k - [phy1]

Offline proxx

  • Avatarception
  • Global Moderator
  • Titan
  • *
  • Posts: 2803
  • Cookies: 256
  • ФФФ
    • View Profile
Re: problem with monitor mode
« Reply #1 on: November 28, 2014, 10:14:02 pm »
And you don't see the problem here?
Did you even read the output..

Quote
Found 5 processes that could cause trouble.
These kids..:S , kill the processes.....?
Damn,
Wtf where you thinking with that signature? - Phage.
This was another little experiment *evillaughter - Proxx.
Evilception... - Phage

Offline morbid

  • NULL
  • Posts: 4
  • Cookies: 0
    • View Profile
Re: problem with monitor mode
« Reply #2 on: November 28, 2014, 11:59:44 pm »
have killed the processes
yeah i did read my output, did you read my first post completely?
perhaps i should of killed the processes then airmon and post the output so you could understand easier.
i can airmon, get processes causing conflicts, kill them and airmon again and it's like my adapter won't go into monitor mode.
« Last Edit: November 29, 2014, 12:02:28 am by morbid »

Offline gray-fox

  • Knight
  • **
  • Posts: 208
  • Cookies: 52
    • View Profile
Re: problem with monitor mode
« Reply #3 on: November 29, 2014, 01:37:18 am »
How  do you kill  the processes? Hint:
http://www.aircrack-ng.org/doku.php?id=airmon-ng

Quote
usage: airmon-ng <start|stop> <interface> [channel] or airmon-ng <check|check kill>

<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

check kill fails

Distros from now on are going to adopt 'upstart' which is going to replace the /sbin/init daemon which manages services and tasks during boot.

Basically do:

service network-manager stop
service avahi-daemon stop
service upstart-udev-bridge stop

and then proceed with greping and killing the pids of dhclient and wpa_supplicant.

This is the only way to kill ALL of the potentially problematic pids for aireplay-ng permanently. The trick is the kill the daemons first and then terminate the 'tasks'.

If this helps, next time; RTFM.
« Last Edit: November 29, 2014, 01:40:06 am by gray-fox »

Offline proxx

  • Avatarception
  • Global Moderator
  • Titan
  • *
  • Posts: 2803
  • Cookies: 256
  • ФФФ
    • View Profile
Re: problem with monitor mode
« Reply #4 on: November 29, 2014, 09:21:23 am »
yeah i did read my output, did you read my first post completely?
perhaps i should of killed the processes then airmon and post the output so you could understand easier.
i can airmon, get processes causing conflicts, kill them and airmon again and it's like my adapter won't go into monitor mode.
If those are killed this wont show up.
If these are not there when you run the command you are supplying garbage information , eitherway I am right.
« Last Edit: November 29, 2014, 09:22:12 am by proxx »
Wtf where you thinking with that signature? - Phage.
This was another little experiment *evillaughter - Proxx.
Evilception... - Phage