Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

Sorry Guest, you are banned from posting and sending personal messages on this forum.

This ban is not set to expire.

[aaditya_purani]

Hello,

So Basically i am Using a Dell PC with Chipset Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
I have Dual Booted Kali Linux 2.0 (Sana) and Doing my testing on it. So i have two questions which will come below

So first, i tried to set up my wlan0 to Monitor Mode from the Managed Mode By following command

airmon-ng check

Which showed me 4 services, but i killed them using

airmon-ng check kill

Now, i started up wlan0mon by use of following command

airmon-ng start wlan0

Everything worked fine and when i check iwconfig
It shows
wlan0mon is in Monitor Mode.
Now, at the same time. My wifi connection gets off. So i cannot use airodump-ng or any Further features.

So what i did is
service network-manager restart

Then i got Back the wifi, but at the same time wlan0mon Changed from Monitor Mode -> Managed Mode

So two questions here:
1) Is there any Way to get connected to Internet also and Keep my Interface wlan0mon into Monitor Mode?

2) Now, when i try airmon-ng wlan0mon stop. It comes back to Managed Mode But after typing ifconfig/ iwconfig. I am unable to see My Old interface name
i.e wlan0 . Now i see wlan0mon. 

It would be grateful if someone could help me out. Thank you

[Jano]

Hi aaditya_purani,

So two questions here:
1) Is there any Way to get connected to Internet also and Keep my Interface wlan0mon into Monitor Mode?

- With the same interface already put in monitor mode, no.
(use different card or internal LAN)

2) Now, when i try airmon-ng wlan0mon stop. It comes back to Managed Mode But after typing ifconfig/ iwconfig. I am unable to see My Old interface name

- Work for me, see Airmon-ng message --> (mac80211 station mode vif enabled on [phy0]wlan0) in the last command.

Code: [Select]

jano@ghostlab:~$ sudo airmon-ng check
[sudo] password for jano:

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
  782 avahi-daemon
  786 avahi-daemon
 1088 NetworkManager
 1221 dhclient
 3729 wpa_supplicant

jano@ghostlab:~$ sudo airmon-ng start wlan0

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
  782 avahi-daemon
  786 avahi-daemon
 1088 NetworkManager
 1221 dhclient
 3729 wpa_supplicant

PHY Interface Driver Chipset

phy0 wlan0 rtl8187 Realtek Semiconductor Corp. RTL8187

(mac80211 monitor mode vif enabled for [phy0]wlan0 on [phy0]wlan0mon)
(mac80211 station mode vif disabled for [phy0]wlan0)

jano@ghostlab:~$ sudo airmon-ng stop wlan0mon

PHY Interface Driver Chipset

phy0 wlan0mon rtl8187 Realtek Semiconductor Corp. RTL8187

(mac80211 station mode vif enabled on [phy0]wlan0)

(mac80211 monitor mode vif disabled for [phy0]wlan0mon)

jano@ghostlab:~$ ifconfig && aircrack-ng --help | head -n 5
eth0      Link encap:Ethernet  IndirizzoHW 44:87:XX:XX:XX:XX 
          indirizzo inet:10.10.10.XX  Bcast:10.10.10.255  Maschera:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:60902 errors:0 dropped:0 overruns:0 frame:0
          TX packets:43366 errors:0 dropped:0 overruns:0 carrier:0
          collisioni:0 txqueuelen:1000
          Byte RX:12536692 (12.5 MB)  Byte TX:3482705 (3.4 MB)
          Interrupt:19

lo        Link encap:Loopback locale 
          indirizzo inet:127.0.0.1  Maschera:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:471 errors:0 dropped:0 overruns:0 frame:0
          TX packets:471 errors:0 dropped:0 overruns:0 carrier:0
          collisioni:0 txqueuelen:0
          Byte RX:43861 (43.8 KB)  Byte TX:43861 (43.8 KB)

wlan0     Link encap:Ethernet  IndirizzoHW 00:1f:XX:XX:XX:XX 
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisioni:0 txqueuelen:1000
          Byte RX:0 (0.0 B)  Byte TX:0 (0.0 B)


  Aircrack-ng 1.2 rc3 r2756 - (C) 2006-2015 Thomas d'Otreppe
  http://www.aircrack-ng.org

  usage: aircrack-ng [options] <.cap / .ivs file(s)>
jano@ghostlab:~$ - I suggest you to update yor Aircrack-ng version installed on Kali 2, and use different card if you need Internet connection during your tests.

Bye Jano

[aaditya_purani]

Hello Jano,

Thanks for the Reply. You response to My Question 1 was to get Another Network Card. So what are best supplementary network cards according to you.
For information: I have Internal Chipset: Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
                                 Driver : ath9k
                                 For Internet i use : USB Wi-Fi Dongle (Plug and Play )
                                 
So should i have any External / Internal Network Cards. If yes, could you specify some of compitible to Dell inspiron 15R n5110
Help would be much appreciated
Thank you

[Jano]

@aaditya_purani,
- When using Aircrack-ng is not necessary use the Internet connection active, indeed it's not recommended.

- If you have an internal LAN adapter connected to a router/switch you can use that.
- However, in order not to spend money to buy another WiFi adapter, I suggest you to install the older version of Airmon-Ng and recompile the Suite replacing only this.

1) Download old Airmon-ng:

Code: [Select]

wget -O airmon-ng https://svn.aircrack-ng.org/trunk/scripts/airmon-ng?p=2429-Or download/save from this URL: Old Airmon-Ng.

2) Go to "Aircrack-Ng/scripts" folder on Kali 2 --> substitute your Armon-Ng installed with this one --> uninstall Aircrack-Ng --> recompile Aircrack-Ng Suite.

- Now your virtual interface created by Airmon-Ng is named in old style "mon0", and your wifi card remain in managed mode.

Bye Jano

[kcdtv]

Something that could be a concern : If you use the same card, the monX interface in monitor mode will be locked on the channel used by he wlanX interface to be connected.
By the way , if you use the old airmon-ng that doesn't solve the issues with the latest network manager versions and systemd and you will have to "check kill" anyway...
...unless you modify the netwiork manager configuration file to create an exception for the monX ...
One way or the other you would have to modify your network manager configuration file to have both managed and monitor mode active at the same time
Or shift from network manger to wcid.