++++++ IMPORTANT ++++++
++++++ IMPORTANT ++++++
++++++ IMPORTANT ++++++

This functionality will be available in a future release. It is NOT available currently.

++++++ IMPORTANT ++++++
++++++ IMPORTANT ++++++
++++++ IMPORTANT ++++++

Airdriver-ng is a script that provides status information about the wireless drivers on your system plus the ability to load and unload the drivers. Additionally, airdriver-ng allows you to install and uninstall drivers complete with the patches required for monitor and injection modes. Plus a number of other functions.

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.
• 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.
• Kernel: This command lists any wireless stack or wireless driver which has been compiled directly into the kernel itself.
• 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.
• Loaded: This command 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.
• Unload: This command removes (unloads) the specified driver from memory. The driver number is obtained from the output of the “loaded” command.
• 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.
• Remove: This command removes the specified driver from your system. This removes the module 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.
• 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.

The airdriver-ng script is only available under linux installations.

Usage: airdriver-ng <command> [drivernumber]

Where these are the valid commands:

* supported       - lists all supported drivers
* kernel          - lists all in-kernel drivers
* installed       - lists all installed drivers
* loaded          - lists all loaded drivers

• load <drivernum> - loads a driver
• unload <drivernum> - unloads a driver
• install <drivernum> - installs a driver
• remove <drivernum> - removes a driver

• details <drivernum> - prints driver details
• detect - detects wireless cards

Here are usage examples for each command.

Enter:

 airdriver-ng supported

The system responds:

 Following stacks are supported:
 0. IEEE80211
 1. IEEE80211 Softmac
 2. mac80211
 Following drivers are supported:
 0. ACX100/111 - IEEE80211
 1. Broadcom 4300 - IEEE80211
 2. HostAP - IEEE80211
 3. Intel Pro Wireless 2100 B - IEEE80211
 4. Intel Pro Wireless 2200 B/G - IEEE80211
 5. Intel Pro Wireless 3945 A/B/G - IEEE80211
 6. Madwifi[-ng] - IEEE80211
 7. Prism54 - IEEE80211
 8. Realtek rtl8180 - custom
 9. Realtek rtl8187 - custom
 10. Ralink rt2500 - IEEE80211 Softmac
 11. Ralink rt2570 - IEEE80211 Softmac
 12. Ralink rt61 - IEEE80211 Softmac
 13. Ralink rt73 - IEEE80211 Softmac
 14. WLAN-NG - IEEE80211
 15. ZyDAS 1211 - IEEE80211 Softmac
 16. ZyDAS 1211rw - IEEE80211 Softmac
 17. Intel Pro Wireless 3945 A/B/G - mac80211
 18. Intel Pro Wireless 3945 A/B/G - raw mode - mac80211
 19. NDIS Wrapper - custom

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.

Enter:

 airdriver-ng kernel

The system responds:

 Found following stacks in the Kernel:
 Found following drivers in the Kernel:

In this example, no stacks or drivers are built into the kernel.

Enter:

 airdriver-ng installed

The system responds:

 Found following stacks installed:
 0. IEEE80211
 1. IEEE80211 Softmac
 2. mac80211
 Found following drivers installed:
 1. Broadcom 4300 - IEEE80211
 2. HostAP - IEEE80211
 3. Intel Pro Wireless 2100 B - IEEE80211
 4. Intel Pro Wireless 2200 B/G - IEEE80211
 6. Madwifi[-ng] - IEEE80211
 7. Prism54 - IEEE80211
 9. Realtek rtl8187 - custom
 13. Ralink rt73 - IEEE80211 Softmac
 18. Intel Pro Wireless 3945 A/B/G - raw mode - mac80211

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.

Enter:

 airdriver-ng loaded

The system responds:

 Found following stacks loaded (as module):
 Found following drivers loaded (as module):
 6. Madwifi[-ng] - IEEE80211
 9. 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.

Enter:

 airdriver-ng load 13

Where:

• 13 is the driver number obtained from the “installed” command results.

The system responds:

 Driver "Ralink rt73" specified for loading.
 Loaded driver "Ralink rt73" successfully

Enter:

 airdriver-ng unload 13

Where:

• 13 is the driver number obtained from the “loaded” command results.

The system responds:

 Driver "Ralink rt73" specified for unloading.
 Unloaded driver "Ralink rt73" successfully

Enter:

 airdriver-ng install 9

Where:

• 9 is the driver number obtained from the “supported” command results.

The system responds:

 Driver "Realtek rtl8187" specified for installation.
 1. Getting the source...
 2. Extracting the source...
 3. Getting the patch...
 4. Patching the source...
 5. Compiling the driver...
 6. Installing the driver...
 Running "depmod -ae"...
 Installed driver "Realtek rtl8187" successfully
 Loaded driver "Realtek rtl8187" successfully

Enter:

 airdriver-ng remove 13

Where:

• 13 is the driver number obtained from the “installed” command results.

The system responds:

 Driver "Ralink rt73" specified for removing.
 Starting to remove "Ralink rt73" driver
 rm: remove regular file `/lib/modules/2.6.21-1.3228.fc7/extra/rt73.ko'? y
 Running "depmod -ae"...
 Removed driver "Ralink rt73" successfully

Enter:

 airdriver-ng details 9

Where:

• 9 is the driver number obtained from the “installed” command results.

The system responds:

 Driver details for: "Realtek rtl8187"
 
 Compiled into kernel:   No
 Installed:              YES
 Loaded:                 No
 
 Modules:
 r8187 
 
 Files:
 /lib/modules/2.6.21-1.3228.fc7/kernel/drivers/net/wireless/rtl8187/r8187.ko 2007-07-08 10:19

 version:        V 1.1
 depends:        ieee80211-rtl
 vermagic:       2.6.21-1.3228.fc7 SMP mod_unload 686 4KSTACKS 
 
 For more information see:
 http://www.aircrack-ng.org/doku.php?id=r8187

Enter:

 airdriver-ng detect

The system responds:

 Found "Realtek rtl8187" device: (r8187)
 Bus 001 Device 002: ID 0bda:8187 Realtek Semiconductor Corp.
 
 Found "Madwifi[-ng]" device: (ath_pci)
 01:00.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)
 
 USB devices (generic detection):
 Bus 001 Device 003: ID 148f:2573 Ralink Technology, Corp.
 Bus 001 Device 002: ID 0bda:8187 Realtek Semiconductor Corp.

None at this time.

None at this time.