ipw2200
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| ipw2200 [2007/06/19 12:25] – screwt-k | ipw2200 [2017/01/09 21:28] (current) – Mark page as deprecated. mister_x | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== DEPRECATED ====== | ||
| + | |||
| + | **IMPORTANT NOTE**: This page is deprecated, updated documentation can be found [[install_drivers|here]] | ||
| + | |||
| ====== ipw2200 ====== | ====== ipw2200 ====== | ||
| - | At this point in time, this page is far from complete. | + | At this point in time, this page is far from complete. |
| - | ======= ipw2200-1.2.1 how to ======= | + | ====== ipw2200-1.2.1 how to ====== |
| - | ----Get the patch and the driver---- | + | The previous version of ipw2200 can't be compiled with the ** linux headers 2.6.20-16-generic ** (used by Ubuntu 7.04) so here is the way to get the rtap0 interface working. |
| + | |||
| + | * **ieee80211-1.2.17.** | ||
| + | Make sure that you have this library else ipw2200-1.2.1 drivers won't compile | ||
| + | <code bach> | ||
| + | wget http:// | ||
| + | tar zxvf ieee80211-1.2.17.tar.gz | ||
| + | cd ieee80211-1.2.17 | ||
| + | sudo make | ||
| + | sudo make install | ||
| + | </ | ||
| + | |||
| + | * **Get the patch and the driver.** | ||
| + | [[http:// | ||
| <code bach> | <code bach> | ||
| wget http:// | wget http:// | ||
| - | wget http:// | ||
| </ | </ | ||
| - | ----Patch the driver---- | + | |
| + | * **Patch the driver.** | ||
| <code bach> | <code bach> | ||
| tar zxvf ipw2200-1.2.1.tgz | tar zxvf ipw2200-1.2.1.tgz | ||
| Line 23: | Line 40: | ||
| </ | </ | ||
| + | * **Turn on the module.** | ||
| + | <code bach> | ||
| + | sudo rmmod ipw2200 | ||
| + | sudo modprobe ipw2200 rtap_iface=1 | ||
| + | </ | ||
| + | At this stage if you see that your module can be loaded, you can load it at boot with the option " | ||
| + | |||
| + | * **Now you should be able to bring up the rtap0 interface and listen with airodump-ng.** | ||
| + | <code bach> | ||
| + | sudo ifconfig eth1 up | ||
| + | sudo ifconfig rtap0 up | ||
| + | sudo airodump-ng rtap0 -c 11 --bssid 00: | ||
| + | </ | ||
| + | |||
| + | ====== 2.6.24 kernel support ====== | ||
| + | |||
| + | See this [[http:// | ||
| + | |||
| + | For the code see: | ||
| + | |||
| + | * http:// | ||
| + | |||
| + | ====== Troubleshooting Tips ====== | ||
| + | ===== Airodump-ng will not channel hop ===== | ||
| + | |||
| + | If you want to channel hop, use the ethX interface where X is the interface that got created while loading the driver. | ||
| + | |||
| + | ===== How do I get the rtapX interface ===== | ||
| + | |||
| + | You get it by specifying rtap_iface=1 while loading the driver or by setting the appropriate value in /sys. | ||
| + | |||
| + | The rtapX interface allows packet capture while you are in managed mode. | ||
| + | |||
| + | ===== "rtap0 is on channel 0, but the AP uses channel X" message ===== | ||
| + | |||
| + | Try adding the channel settings to the modprobe: | ||
| + | |||
| + | | ||
| + | |||
| + | Where X is the AP channel. | ||
| + | |||
| + | ===== Deauthentication does not work ===== | ||
| + | |||
| + | The ipw2200 driver does not support the transmission of management frames such as deauthentication. | ||
| ====== Useful links ====== | ====== Useful links ====== | ||
| + | * [[http:// | ||
| + | * [[ipw2200_generic|Tutorial: | ||
| * [[http:// | * [[http:// | ||
| - | * [[http://tinyshell.be/ | + | * [[http://forum.aircrack-ng.org/ |
| - | * [[http://tinyshell.be/ | + | * [[http://forum.aircrack-ng.org/ |
| - | * [[http://tinyshell.be/ | + | * [[http://forum.aircrack-ng.org/ |
| + | * [[http:// | ||
ipw2200.1182248744.txt.gz · Last modified: by screwt-k
