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 [2007/07/16 21:01]
darkaudax Added known problems with madwifi-ng driver.
airdriver-ng [2014/11/01 01:08] (current)
mister_x Airdriver is removed in 1.2 rc1
Line 1: Line 1:
-====== ​Airserv-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 17: Line 7:
 Here is a complete list of commands supported by the script: Here is a complete list of commands supported by the script:
  
-  * No Command: Running airdriver-ng without a command displays the kernel number you are running and the valid 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 the script ​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. +  * 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. +  * 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. +  * 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. +  * 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
-  * InstallThis 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. +  * ReloadReloads 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. 
-  * Remove: This command ​removes the specified driver from your system. ​ This removes the module ​from memory and the module tree. +  * 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
-  * 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. +  * 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. 
-  * 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.+  * 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:​ Removes the specified stack from your system. ​ This removes the stack from memory and the module tree. 
 +  * 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: ​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 airdriver-ng script is only available under linux installations. The airdriver-ng script is only available under linux installations.
Line 34: Line 29:
 ===== Usage ===== ===== Usage =====
  
-Usage: airdriver-ng <​command>​ [drivernumber]        ​+Usage: airdriver-ng <​command>​ [driver number | driver name]        ​
  
 Where these are the valid commands: Where these are the valid commands:
-  ​+
   * supported ​      - lists all supported drivers   * supported ​      - lists all supported drivers
   * kernel ​         - lists all in-kernel drivers   * kernel ​         - lists all in-kernel drivers
Line 45: Line 40:
   * load <​drivernum> ​       - loads a driver   * load <​drivernum> ​       - loads a driver
   * unload <​drivernum> ​     - unloads a driver   * unload <​drivernum> ​     - unloads a driver
 +  * reload <​drivernum> ​     - reloads a driver
   * install <​drivernum> ​    - installs a driver   * install <​drivernum> ​    - installs a driver
   * remove <​drivernum> ​     - removes a driver   * remove <​drivernum> ​     - removes a driver
 +
 +  * remove_stack <​num> ​     - removes a stack 
 +  * install_stack <​num> ​    - installs a stack
  
   * details <​drivernum> ​    - prints driver details   * details <​drivernum> ​    - prints driver details
Line 55: Line 54:
  
 Here are usage examples for each command. Here are usage examples for each command.
 +
  
 ==== Supported Command ==== ==== Supported Command ====
Line 68: Line 68:
    1. IEEE80211 Softmac    1. IEEE80211 Softmac
    2. mac80211    2. mac80211
 +   
    ​Following drivers are supported:    ​Following drivers are supported:
    0. ACX100/111 - IEEE80211    0. ACX100/111 - IEEE80211
-   1. Broadcom 4300 - IEEE80211 +   1. ADMtek 8211 - IEEE80211 
-   2. HostAP - IEEE80211 +   2. ADMtek 8211 - mac80211 
-   3. Intel Pro Wireless 2100 B - IEEE80211 +   3. Atmel at76c50x - IEEE80211 
-   4. Intel Pro Wireless 2200 B/G - IEEE80211 +   4. Broadcom 4300 - IEEE80211 
-   5. Intel Pro Wireless 3945 A/B/G - IEEE80211 +   5. Broadcom 4300 - mac80211 
-   6. Madwifi[-ng] - IEEE80211 +   6. Cisco/​Aironet 802.11 - IEEE80211 Softmac 
-   7. Prism54 - IEEE80211 +   7. HostAP - IEEE80211 
-   8Realtek rtl8180 ​custom +   8. Intel Pro Wireless 2100 B - IEEE80211 
-   9Realtek rtl8187 ​custom +   9. Intel Pro Wireless 2200 B/G - IEEE80211 
-   10. Ralink rt2500 - IEEE80211 ​Softmac +   10. Intel Pro Wireless 3945 A/B/G - IEEE80211 
-   11. Ralink rt2570 - IEEE80211 ​Softmac +   11. Intel Pro Wireless 3945 A/B/G - raw mode 
-   12. Ralink rt61 - IEEE80211 ​Softmac +   12. Intel Pro Wireless 3945 A/B/G - mac80211 
-   13. Ralink rt73 - IEEE80211 ​Softmac +   13. Intel Pro Wireless 4965 A/B/G/N - mac80211 
-   14. WLAN-NG - IEEE80211 +   14. Lucent Hermes and Prism II - IEEE80211 
-   15. ZyDAS 1211 - IEEE80211 Softmac +   15. Madwifi[-ng] - IEEE80211 
-   16. ZyDAS 1211rw ​- IEEE80211 Softmac +   16. Prism54 - IEEE80211 
-   17Intel Pro Wireless 3945 A/B/G mac80211 +   17Prism54 ​mac80211 
-   18Intel Pro Wireless 3945 A/B/G - raw mode - mac80211 +   18Ralink rt2400 (legacy) 
-   19. NDIS Wrapper ​- custom+   19. Ralink rt2400 (rt2x00) ​IEEE80211 
 +   20. Ralink rt2400 (rt2x00) - mac80211 
 +   21. Ralink rt2500 (legacy) 
 +   22. Ralink rt2500 ​(rt2x00) ​- IEEE80211 
 +   23. Ralink rt2500 (rt2x00) - mac80211 
 +   24. Ralink rt2570 (legacy) 
 +   25. Ralink rt2570 ​(rt2x00) ​- IEEE80211 
 +   26. Ralink rt2570 (rt2x00) - mac80211 
 +   27. Ralink rt61 (legacy) 
 +   28. Ralink rt61 (rt2x00) ​- IEEE80211 
 +   29. Ralink rt61 (rt2x00) - mac80211 
 +   30. Ralink rt73 (legacy) 
 +   31. Ralink rt73 (rt2x00) ​- IEEE80211 
 +   32. Ralink rt73 (rt2x00) - mac80211 
 +   33. Realtek rtl8180 - custom 
 +   34. Realtek rtl8187 - custom 
 +   35. Realtek rtl8187 - mac80211 
 +   36. WLAN-NG - IEEE80211 
 +   37. Xircom Creditcard Netwave - IEEE80211 
 +   38. ZyDAS 1201 - IEEE80211 Softmac 
 +   39. ZyDAS 1211 - IEEE80211 Softmac 
 +   40ZyDAS 1211rw ​IEEE80211 Softmac 
 +   41ZyDAS 1211rw ​- mac80211 
 +   42. NDIS Wrapper 
 + 
  
 Notice the number in front of each driver. ​ These are the numbers you will need for the "​install"​ command to actually install the particular driver. Notice the number in front of each driver. ​ These are the numbers you will need for the "​install"​ command to actually install the particular driver.
Line 144: Line 170:
    Found following stacks loaded (as module):    Found following stacks loaded (as module):
    Found following drivers loaded (as module):    Found following drivers loaded (as module):
-   6. Madwifi[-ng] - IEEE80211 +   15. Madwifi[-ng] - IEEE80211 
-   9. Realtek rtl8187 - custom +   34. Realtek rtl8187 - custom
-  13. Ralink rt73 - IEEE80211 Softmac+
  
 Notice the number in front of each driver. ​ These are the numbers you will need for the "​load"​ command to actually load the particular driver. Notice the number in front of each driver. ​ These are the numbers you will need for the "​load"​ command to actually load the particular driver.
Line 154: Line 179:
 Enter: Enter:
  
-   ​airdriver-ng load 13+   ​airdriver-ng load 34
  
 Where: Where:
  
-  * 13 is the driver number obtained from the "​installed"​ command results.+  * 34 is the driver number obtained from the "​installed"​ command results.
  
 The system responds: The system responds:
  
-   ​Driver "Ralink rt73" specified for loading. +   ​Driver "Realtek rtl8187" specified for loading. 
-   ​Loaded driver "Ralink rt73" successfully+   ​Loaded driver "Realtek rtl8187" successfully
  
  
Line 170: Line 195:
 Enter: Enter:
  
-   ​airdriver-ng unload ​13+   ​airdriver-ng unload ​34 
 + 
 +Where: 
 + 
 +  * 34 is the driver number obtained from the "​loaded"​ command results. 
 + 
 +The system responds: 
 + 
 +   ​Driver "​Realtek rtl8187"​ specified for unloading. 
 +   ​Unloaded driver "​Realtek rtl8187"​ successfully 
 + 
 + 
 +==== Reload Command ==== 
 + 
 +Enter: 
 + 
 +   ​airdriver-ng reload 34
  
 Where: Where:
  
-  * 13 is the driver number obtained from the "​loaded"​ command results.+  * 34 is the driver number obtained from the "​loaded"​ command results.
  
 The system responds: The system responds:
  
-   ​Driver "Ralink rt73" specified for unloading+   ​Driver "Realtek rtl8187" specified for reloading
-   Unloaded ​driver "Ralink rt73" successfully+   Reloaded ​driver "Realtek rtl8187" successfully
  
  
Line 186: Line 227:
 Enter: Enter:
  
-   ​airdriver-ng install ​9+   ​airdriver-ng install ​34
  
 Where: Where:
  
-  * is the driver number obtained from the "​supported"​ command results.+  * 34 is the driver number obtained from the "​supported"​ command results.
  
 The system responds: The system responds:
Line 199: Line 240:
    3. Getting the patch...    3. Getting the patch...
    4. Patching the source...    4. Patching the source...
-   5. Compiling the driver... +   5. Compiling the source... 
-   6. Installing the driver...+   6. Installing the modules...
    ​Running "​depmod -ae"​...    ​Running "​depmod -ae"​...
    ​Installed driver "​Realtek rtl8187"​ successfully    ​Installed driver "​Realtek rtl8187"​ successfully
Line 206: Line 247:
  
  
 +==== Remove Command ====
  
 +Enter:
  
-==== Remove ​Command ====+   ​airdriver-ng remove 34 
 + 
 +Where: 
 + 
 +  * 34 is the driver number obtained from the "​installed"​ command results. 
 + 
 +The system responds: 
 + 
 +   ​Driver "​Realtek rtl8187"​ specified for removing. 
 +   ​Starting to remove "​Realtek rtl8187"​ driver 
 +   rm: remove regular file `/​lib/​modules/​2.6.21-1.3228.fc7/​kernel/​drivers/​net/​wireless/​rtl8187/​r8187.ko'?​ y 
 +   ​Running "​depmod -ae"​... 
 +   ​Removed driver "​Realtek rtl8187"​ successfully 
 + 
 + 
 + 
 +==== Install_Stack ​Command ====
  
 Enter: Enter:
  
-   ​airdriver-ng ​remove 13+   ​airdriver-ng ​install_stack 0
  
 Where: Where:
  
-  * 13 is the driver ​number obtained from the "installed" command results.+  * is the stack number obtained from the "supported" command results.
  
 The system responds: The system responds:
  
-   Driver ​"Ralink rt73" specified for removing. +   Stack "IEEE80211"​ specified for installation. 
-   ​Starting to remove "Ralink rt73" driver +   1. Getting the source... 
-   rm: remove regular file `/​lib/​modules/​2.6.21-1.3228.fc7/extra/rt73.ko'? y+   2. No extraction needed. 
 +   3. Getting the patch... 
 +   4. Patching the source... 
 +   5. Compiling the source... 
 +   6. Installing the modules... 
 +   ​Running "​depmod -ae"​... 
 +   ​Installed stack "​IEEE80211"​ successfully 
 +   You need to reload the complete stack, or just reboot. 
 + 
 + 
 +==== Remove_Stack Command ==== 
 + 
 +Enter: 
 + 
 +   ​airdriver-ng remove_stack 0 
 + 
 +Where: 
 + 
 +  * 0 is the stack number obtained from the "​installed"​ command results. 
 + 
 +The system responds: 
 + 
 +   Stack "​IEEE80211" specified for removing. 
 +   ​Starting to remove "IEEE80211" driver 
 +   rm: remove regular file `/​lib/​modules/​2.6.20-1.2962.fc6/​kernel/​net/​ieee80211/​ieee80211.ko'?​ y 
 +   rm: remove regular file `/​lib/​modules/​2.6.20-1.2962.fc6/​kernel/​net/​ieee80211/​ieee80211_crypt.ko'?​ y 
 +   rm: remove regular file `/​lib/​modules/​2.6.20-1.2962.fc6/​kernel/​net/​ieee80211/​ieee80211_crypt_wep.ko'?​ y 
 +   rm: remove regular file `/​lib/​modules/​2.6.20-1.2962.fc6/​kernel/​net/​ieee80211/​ieee80211_crypt_tkip.ko'?​ y 
 +   rm: remove regular file `/​lib/​modules/​2.6.20-1.2962.fc6/​kernel/​net/ieee80211/ieee80211_crypt_ccmp.ko'? y
    ​Running "​depmod -ae"​...    ​Running "​depmod -ae"​...
-   ​Removed ​driver ​"Ralink rt73" successfully+   ​Removed ​stack "IEEE80211" successfully
  
  
Line 231: Line 318:
 Enter: Enter:
  
-   ​airdriver-ng details ​9+   ​airdriver-ng details ​34
  
 Where: Where:
  
-  * is the driver number obtained from the "​installed"​ command results.+  * 34 is the driver number obtained from the "​installed"​ command results.
  
 The system responds: The system responds:
Line 243: Line 330:
    ​Compiled into kernel: ​  No    ​Compiled into kernel: ​  No
    ​Installed: ​             YES    ​Installed: ​             YES
-   ​Loaded: ​                No+   ​Loaded: ​                YES
        
    ​Modules:​    ​Modules:​
Line 249: Line 336:
        
    ​Files:​    ​Files:​
-   /​lib/​modules/​2.6.21-1.3228.fc7/​kernel/​drivers/​net/​wireless/​rtl8187/​r8187.ko 2007-07-08 10:19 +   /​lib/​modules/​2.6.21-1.3228.fc7/​kernel/​drivers/​net/​wireless/​rtl8187/​r8187.ko 2007-07-22 12:53 
-  +   ​
    ​version: ​       V 1.1    ​version: ​       V 1.1
    ​depends: ​       ieee80211-rtl    ​depends: ​       ieee80211-rtl
-   ​vermagic: ​      ​2.6.21-1.3228.fc7 ​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.
  
  
Line 282: Line 370:
  
 None at this time. None at this time.
- 
  
  
 ===== Usage Troubleshooting ===== ===== Usage Troubleshooting =====
  
-At the present ​time, there are known issues with the madwifi-ng drivers for atheros-based cards ​Channel hopping and setting the channel does not always work correctly. ​ Very often the card is not set to the requested channel and/or the hopping does not take place. +None at this time.
  
  
airdriver-ng.1184612496.txt.gz · Last modified: 2007/07/16 21:01 by darkaudax