Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Placing your wireless device(s) into monitor mode
#1
First things first, do you have to do this?... no, but should you do this?... yes, in my opinion.

Now that we have that out of the way, this will only be helpful to those using a wireless device and / or chipset that is compatible with the TinyPaw-Linux build release that you are currently using. If you are not sure if your device is supported then please consult the project Wiki section for exactly that:

https://sourceforge.net/p/tinypaw-linux/...20drivers/

Once you've established whether one or all of your devices are supported then we can continue. You may be asking "but r1sen, don't many of these tools and scripts place your device into monitor mode for you?" - yes, no and sort of. Though many of these scripts do or can place your device into monitor mode, doing things this way though not necessarily wrong... can lead to or occasionally lead to multiple instances being created for the same interface which can cause functionality and / or compatibility issues. Also, some of the eaves dropping, capture, sniffing tools - upon startup list only active interfaces, meaning that unless your device(s) are already placed in monitor mode or currently active in a connection they may not be listed as available interfaces - meaning that you may only see "ETHx" or "USBx" on your list for available interfaces to choose from. So in a nutshell, in my opinion this is why one of the very first things you ought to do upon booting into TinyPaw-Linux is placing the wireless device(s) you wish to use into monitor mode.

How is this done you ask? Simple:

1.) You will need to initiate Airmon-ng from one of two ways, either the "Airmon" launcher icon located in your WBAR at the bottom of your screen or from the terminal.

2.) Regardless of how you decide to go about initiating Airmon-ng you will be prompted to enter the proper command string to begin.

- First: sudo airmon-ng check kill

*This will terminate any process interacting or trying to interact with any wireless interface*

- Second: sudo airmon-ng

*This should display any and all available interfaces "wlan0, wlan1, wlan2, etc" - if none are listed, check to ensure your device is supported and / or you have USB redirection enabled in your VM*

- Third: sudo airmon-ng start wlan0 "or wlan1 or wlan2 or etc"

*This will now place each and any device you choose into monitor mode - of course if the device you choose supports monitor mode*

*The interface you've selected will now be listed as mon - ie: "wlan0mon , wlan1mon , wlan2mon , etc"

- Forth: sudo airmon-ng stop wlan0mon "or wlan1mon , or wlan2mon , or etc"

*This will place the interface you've selected back into managed mode from monitor*
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)