User Tools

Site Tools


airdriver-ng

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
airdriver-ng [2008/03/13 23:08]
darkaudax added details about when to use each command
airdriver-ng [2014/11/01 01:08]
mister_x Airdriver is removed in 1.2 rc1
Line 1: Line 1:
-====== Airdriver-ng ====== +====== Airdriver-ng ​- REMOVED in 1.2 rc 1 ======
- +
-++++++ IMPORTANT ++++++\\ +
-++++++ IMPORTANT ++++++\\ +
-++++++ IMPORTANT ++++++\\ +
- +
-This functionality will be available in a future release. It is NOT available currently. +
- +
-++++++ IMPORTANT ++++++\\ +
-++++++ IMPORTANT ++++++\\ +
-++++++ IMPORTANT ++++++\\+
  
 ===== Description ===== ===== Description =====
Line 18: Line 8:
  
   * No Command: Running airdriver-ng without a command displays the kernel number you are running and the valid airdriver-ng commands.   * No Command: Running airdriver-ng without a command displays the kernel number you are running and the valid airdriver-ng commands.
-  * Supported:  ​This command lists the wireless stacks and wireless drivers which the script currently supports. ​ If the stack or driver you want is not listed then airdriver-ng does not currently support it.  These are NOT the stacks or drivers installed on your system. +  * Supported:  ​Lists the wireless stacks and wireless drivers which the script currently supports. ​ If the stack or driver you want is not listed then airdriver-ng does not currently support it.  These are NOT the stacks or drivers installed on your system. 
-  * Kernel: ​This command lists any wireless stack or wireless driver which has been compiled directly into the kernel itself. ​ Use this if you wish to determine if a particular driver is already compiled into the kernel. ​ You cannot install a driver if it  is already part of your kernel. ​ You would first have to recompile your kernel without the specific driver. +  * Kernel: ​Lists any wireless stack or wireless driver which has been compiled directly into the kernel itself. ​ Use this if you wish to determine if a particular driver is already compiled into the kernel. ​ You cannot install a driver if it  is already part of your kernel. ​ You would first have to recompile your kernel without the specific driver. 
-  * Installed: ​This command lists the wireless stacks and drivers actually installed on your system. ​ These are NOT the stacks/​drivers currently loaded (running) on your system. ​ Use this if you to know if the driver is already installed on your system. ​ These are drivers which are NOT part of the kernel. +  * Installed: ​Lists the wireless stacks and drivers actually installed on your system. ​ These are NOT the stacks/​drivers currently loaded (running) on your system. ​ Use this if you to know if the driver is already installed on your system. ​ These are drivers which are NOT part of the kernel. 
-  * Loaded: ​This command lists the wireless stacks and drivers which are currently loaded (running) in memory.+  * Loaded: ​Lists the wireless stacks and drivers which are currently loaded (running) in memory.
   * Load: This command loads the specified driver into memory. ​ The driver number is obtained from the output of the "​installed"​ command. ​ Use this command to load the desired driver into memory if it did not load when you plugged in your wireless device or booted up.   * Load: This command loads the specified driver into memory. ​ The driver number is obtained from the output of the "​installed"​ command. ​ Use this command to load the desired driver into memory if it did not load when you plugged in your wireless device or booted up.
   * Unload: This command removes (unloads) the specified driver from memory. ​ The driver number is obtained from the output of the "​loaded"​ command. ​ This is sometimes required when recompiling or installing a new version of the driver. ​ Normally a reload should be sufficient after installing a new version.   * Unload: This command removes (unloads) the specified driver from memory. ​ The driver number is obtained from the output of the "​loaded"​ command. ​ This is sometimes required when recompiling or installing a new version of the driver. ​ Normally a reload should be sufficient after installing a new version.
-  * Reload: ​This command reloads ​the specified driver by removing it from memory then loading it again. ​ The driver number is obtained from the output of the "​loaded"​ command. ​ Use this after installing a new version of the driver or it can sometimes help if your driver is misbehaving. +  * Reload: ​Reloads ​the specified driver by removing it from memory then loading it again. ​ The driver number is obtained from the output of the "​loaded"​ command. ​ Use this after installing a new version of the driver or it can sometimes help if your driver is misbehaving. 
-  * Install: ​This command installs ​the specified driver on your system and loads it into memory. ​ The driver number is obtained from the output of the "​loaded"​ command. ​ All the required steps are taken care of for you including obtaining the driver sources, obtaining injection patches, applying patches, compiling and then loading it into memory. ​ This is one the simplest and easiest methods of ensuring your driver is capable of injection. ​ You may also need to install a related stack for your driver to be fully functional. +  * Install: ​Installs ​the specified driver on your system and loads it into memory. ​ The driver number is obtained from the output of the "​loaded"​ command. ​ All the required steps are taken care of for you including obtaining the driver sources, obtaining injection patches, applying patches, compiling and then loading it into memory. ​ This is one the simplest and easiest methods of ensuring your driver is capable of injection. ​ You may also need to install a related stack for your driver to be fully functional. 
-  * Remove: ​This command removes ​the specified driver from your system. ​ This removes the module from memory and the module tree.  Use this if you wish to remove the driver from your system permanently. +  * Remove: ​Removes ​the specified driver from your system. ​ This removes the module from memory and the module tree.  Use this if you wish to remove the driver from your system permanently. 
-  * Install_Stack: ​This command installs ​the specified stack on your system and loads it into memory. ​ The driver number is obtained from the output of the "​loaded"​ command. ​ All the required steps are taken care of for you including obtaining the stack sources, obtaining injection patches, applying patches, compiling and then loading it into memory. ​ This is one the simplest and easiest methods of ensuring your system is capable of injection. +  * Install_Stack: ​Installs ​the specified stack on your system and loads it into memory. ​ The driver number is obtained from the output of the "​loaded"​ command. ​ All the required steps are taken care of for you including obtaining the stack sources, obtaining injection patches, applying patches, compiling and then loading it into memory. ​ This is one the simplest and easiest methods of ensuring your system is capable of injection. 
-  * Remove_Stack: ​This command removes ​the specified stack from your system. ​ This removes the stack from memory and the module tree. +  * Remove_Stack: ​Removes ​the specified stack from your system. ​ This removes the stack from memory and the module tree. 
-  * Details: ​This command lists detailed information about the module. ​ The driver number is obtained from the output of the "​installed"​ command. ​ This especially valuable to confirm you are using the correct version and when it was installed. ​ The install date is located after the file name.  This can be used to confirm you are in fact using the the recently compiled module. ​ A common problem is that one of the required modules was compiled on a different date.  This normally means you have two different versions of the same modules and the result is that the driver fails. ​ If this happens, delete all the modules and reinstall or recompile. +  * Details: ​Lists detailed information about the module. ​ The driver number is obtained from the output of the "​installed"​ command. ​ This especially valuable to confirm you are using the correct version and when it was installed. ​ The install date is located after the file name.  This can be used to confirm you are in fact using the the recently compiled module. ​ A common problem is that one of the required modules was compiled on a different date.  This normally means you have two different versions of the same modules and the result is that the driver fails. ​ If this happens, delete all the modules and reinstall or recompile. 
-  * Detect: ​This command is used to determine which wireless devices are connect to your system. ​ There is no precise method of doing these types of checks. ​ Consider this more as educated guesses rather then definitive information. ​ Having said that, it will generally provide very useful information.+  * Detect: ​Used to determine which wireless devices are connect to your system. ​ There is no precise method of doing these types of checks. ​ Consider this more as educated guesses rather then definitive information. ​ Having said that, it will generally provide very useful information.
  
 The script also attempts to ensure the success of the operation by first confirming that you have the correct tools and software loaded on your system. ​ You will receive warnings and/or error messages if your system is not capable of the requested operation. ​ Although airdriver-ng attempts to minimize the risk, it will always be there. ​ Please be aware that this is always a certain amount of risk to your system when working with drivers. The script also attempts to ensure the success of the operation by first confirming that you have the correct tools and software loaded on your system. ​ You will receive warnings and/or error messages if your system is not capable of the requested operation. ​ Although airdriver-ng attempts to minimize the risk, it will always be there. ​ Please be aware that this is always a certain amount of risk to your system when working with drivers.
Line 352: Line 342:
    ​vermagic: ​      ​2.6.21-prep SMP mod_unload 686 4KSTACKS ​    ​vermagic: ​      ​2.6.21-prep SMP mod_unload 686 4KSTACKS ​
        
-   For more information see: +   For more information see: [[r8187]]
-   ​http://​www.aircrack-ng.org/​doku.php?​id=r8187+
  
 NOTE:  Notice the date after file name.  This is the compile date and can be used to ensure you are using the module you want. NOTE:  Notice the date after file name.  This is the compile date and can be used to ensure you are using the module you want.
airdriver-ng.txt · Last modified: 2014/11/01 01:08 by mister_x