zd1211rw
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
zd1211rw [2007/11/15 00:27] – added more troubleshooting info. darkaudax | zd1211rw [2017/01/09 21:34] – Mark page as deprecated. mister_x | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== | + | ====== |
- | This driver supports the zd1211 and the newer zd1211b chipsets by Zydas. | + | **IMPORTANT NOTE**: |
- | The older zd1211 chipset only partially supports injection. | + | ====== zd1211rw ====== |
+ | authored by sleek | ||
- | The new zd1211b chipset only partially supports injection. | + | **Review |
- | The zd1211rw driver has been incorporated into the latest kernels. | + | The ZyDAS zd1211 and zd1211b (//also known as AR5007UG//) chips are one of the most distributed wireless b/g chips in the market. They are also the cheapest, on eBay, you can get one for about 5-6USD shipping included. In the same time, these chips are very stable, with excellent range and sensitivity, |
- | The following links may be helpful | + | The zd1211rw was included in mainline kernel 2.6.18 as a softmac driver, known to be notoriously unstable and heavily crippled in terms aircrack-ng support. Things turned for the better when the zd1211rw was ported as mac80211 |
- | * [[http:// | + | The only unsupported function is the fragmentation " |
- | * [[http:// | + | |
- | * [[http:// | + | |
+ | Overall, its a great all-purpose chip to have for wireless auditing and general connectivity. | ||
+ | ====== Patching ====== | ||
+ | To enable injection, we'll have to patch the driver first. | ||
+ | ==== Modern kernels ==== | ||
+ | For modern kernels, good results can be obtained even when sticking closely to stock kernels. | ||
- | ===== Patching zd1211rw ===== | ||
- | This section will describe how to patch your driver for injection. There is quite a bit of variation between distributions so this describe the general steps you must take. You will have to tweak the instructions for your specific distribution and kernel version. | + | === Kernel 2.6.39+ === |
+ | See [[http://trac.aircrack-ng.org/ticket/894|ticket 894]] on the bugtracker. | ||
- | You will need to have your kernel | + | **1.** cd into your kernel sources |
- | Copy contents of **/usr/src/linux/net/ieee80211** to a safe place. This is so you can recover if things go bad or if you want to apply a new version of the patch. | + | **2.** Apply the patch: |
+ | wget -O - 'http://trac.aircrack-ng.org/raw-attachment/ticket/894/ | ||
- | Copy contents of **/ | + | **3.** Recompile and reload the driver as usual. Refer to your distro' |
- | Download and expand the latest version of the aircrack-ng suite to obtain the patches or download the from [[http:// | + | === Kernel 2.6.34 - 2.6.38 === |
- | Copy zd1211rw_inject_2.6.22.patch to **/ | + | **1.** cd into your kernel sources |
- | cd /usr/src/linux/ | + | **2.** Apply the patch: |
+ | wget -O - 'http://patches.aircrack-ng.org/zd1211rw-inject+dbi-fix-2.6.26.patch' | ||
- | NOTE: In the following lines, verbose and dry-run have a double dash in front of them. | + | **3.** Recompile and reload |
- | patch -Np1 --verbose --dry-run -i zd1211rw_inject_2.6.22.patch | + | |
- | If it was OK: | + | ==== Legacy kernels ==== |
- | | + | On old kernels, you need to use the compat-wireless approach. |
+ | The most frequent road block you'll stumble upon is compilation errors with compat-wireless. They' | ||
- | Copy ieee80211_inject.patch to / | + | === Kernel 2.26.24+ === |
- | patch -Np1 --verbose --dry-run -i ieee80211_inject.patch | + | |
- | If it was OK: | + | **1.** Go to http:// |
- | patch -Np1 | + | |
- | **NOTE**: In the following lines, change "2.6.20-1.2944.fc6" to match your particular system. | + | **2.** Next up, **cd to your / |
- | cd / | + | **3.** Apply the patches: |
- | make -C / | + | |
- | cd / | + | |
- | make -C / | + | |
- | Now copy the new modules | + | patch -Np0 -i zd1211rw-inject+dbi-fix-2.6.26.patch. |
+ | patch -Np1 -i mac80211.compat08082009.wl_frag+ack_v1.patch. | ||
+ | patch -Np1 -i channel-negative-one-maxim.patch. | ||
+ | __Note:__ //the **xxxxx-xxxx-xxxx.patch** files must be in your compat-wireles-xxxx-xx-xx directory while patching, otherwise you will be asked to provide full path of the file which needs to be patched, example: / | ||
- | cp / | + | **4.** Patching is complete and we are ready to compile our driver, type **make** for the process to begin and wait for few minutes to complete. |
- | cp / | + | |
- | cp / | + | |
- | And finally, rebuild the module dependencies. | + | **5.** Barring any errors, next up is installing, **sudo make install** |
- | | + | **6.** Now that the newly compiled driver is installed, we are ready to use it, but before that we have to unload the old driver by typing **sudo make wlunload** |
- | At this point, the simplest method to bring up the new modules live is to reboot | + | **7.** To load the new driver, just type **sudo modprobe zd1211rw** or simply unplug and plug again your USB adapter. Reboot if you're unsure |
- | If you have problems compiling zd1211rw, you can try: | + | **8.** That's it! This concludes the zd1211 injection tutorial. You should now be able to inject. [[injection_test|Test]] your USB device, by setting it to monitor mode (airmon-ng) |
- | | ||
- | | ||
- | ===== Installing Fedora kernel headers and source ===== | + | # aireplay-ng -9 mon0 |
+ | 14: | ||
+ | 14: | ||
+ | 14: | ||
+ | 14: | ||
+ | 14: | ||
+ | 14: | ||
+ | 14: | ||
+ | Voila ;-) | ||
- | These instructions are specific to Fedora. Change **2.6.20-1.2944.fc6** to the particular kernel version you have installed. **uname -r** can help you | + | Known issues at this point: |
+ | Fragmentation attack | ||
- | You need these packages already installed: | ||
- | kernel-headers-2.6.20-1.2944.fc6 | ||
- | kernel-devel-2.6.20-1.2944.fc6 | ||
- | Running the command **rpm -qa | grep kernel** will show which kernel packages are installed. | + | === Kernels 2.6.23 and lower === |
- | If the headers and development packages | + | As mentioned above, kernels prior to 2.6.25 (2.6.2**4** with compat-wireless) |
- | rpm -ivh kernel-headers-2.6.20-1.2944.fc6.i386.rpm | + | And if you're absolutely bent on installing the softmac driver on an old kernel, you can try [[http:// |
- | rpm -ivh kernel-devel-2.6.20-1.2944.fc6.i686.rpm (obtain i586 or i686 depending on your architecture) | + | |
- | Alternatively, | + | ==== Troubleshooting ==== |
- | Now download and install the full kernel sources if they are not already on your system (This assumes you have downloaded this RPM from your favourite repository). | + | === Couldn' |
- | + | ||
- | rpm -ivh kernel-2.6.20-1.2944.fc6.src.rpm | + | |
- | + | ||
- | Change to the following directory: | + | |
- | + | ||
- | cd / | + | |
- | + | ||
- | Change " | + | |
- | rpmbuild -bp --target=i586 kernel-2.6.spec | + | |
- | + | ||
- | **NOTE**: Change references to versions to your specific version in the next few lines. | + | |
- | + | ||
- | /bin/cp -a / | + | |
- | ln -s / | + | |
- | + | ||
- | + | ||
- | ===== Recompiling Kernel with Loadable Modules ===== | + | |
- | + | ||
- | Some kernels incorporate the functionality built into the kernel. | + | |
- | + | ||
- | These are the settings for menuconfig using 2.6.20-gentoo-r7, | + | |
- | + | ||
- | First, change the appropriate items in menuconfig: | + | |
- | + | ||
- | cd / | + | |
- | + | ||
- | make menuconfig | + | |
- | + | ||
- | | + | |
- | then set | + | |
- | < | + | |
- | < | + | |
- | all other module capable IEEE 80211 items will have automatically set themselves to <M> | + | |
- | + | ||
- | Also check that: | + | |
- | | + | |
- | < | + | |
- | + | ||
- | Exit out and save the config | + | |
- | + | ||
- | Now apply the zd1211 and ieee80211 inject patches and recompile/ | + | |
- | + | ||
- | Apply the zd1211 inject and ieee80211 inject patches as per patch instructions but only do the 4 patch -Np1 commands, in gentoo doing the make commands and copying all the files is unnecessary!! | + | |
- | + | ||
- | After the patches are applied, you can now recompile the kernel and modules with the following commands: | + | |
- | + | ||
- | cd /usr/src | + | |
- | make && make modules modules_install install | + | |
- | + | ||
- | Wait for it to finish and then reboot your system. | + | |
- | + | ||
- | Lastly, test your drivers and the injection patch. | + | |
- | + | ||
- | + | ||
- | ===== Troubleshooting ===== | + | |
- | + | ||
- | ===== General ===== | + | |
- | + | ||
- | Use " | + | |
- | + | ||
- | Bus 003 Device 003: ID 157e: | + | |
- | Bus 003 Device 001: ID 0000: | + | |
- | Bus 001 Device 001: ID 0000: | + | |
- | Bus 002 Device 001: ID 0000:0000 | + | |
- | + | ||
- | If your device is not listed then you first need to determine why and correct it. | + | |
- | + | ||
- | Use " | + | |
- | + | ||
- | | + | |
- | | + | |
- | | + | |
- | usb 3-1: reset high speed USB device using ehci_hcd and address 3 | + | |
- | usb 3-1: firmware version 0x4810 and device bootcode version 0x4802 differ | + | |
- | | + | |
- | | + | |
- | | + | |
- | | + | |
- | + | ||
- | Depending on the error messages in dmesg, take the appropriate action. | + | |
- | + | ||
- | Use " | + | |
- | + | ||
- | | + | |
- | | + | |
- | | + | |
- | | + | |
- | | + | |
- | + | ||
- | A common problem on new kernels is that the new mac80211 version of the driver gets loaded instead of the older legacy driver covered on this page. If that is the case, then you need to blacklist the modules by editing / | + | |
- | + | ||
- | # | + | |
- | | + | |
- | | + | |
- | + | ||
- | Also ensure that the time stamp on zd1211.ko module matches the date and time you compiled it. Otherwise this may mean you are running the wrong version of the module. | + | |
- | + | ||
- | + | ||
- | ===== Couldn' | + | |
If dmesg has an error similar to the following: | If dmesg has an error similar to the following: | ||
Line 200: | Line 106: | ||
- http:// | - http:// | ||
- | - RPM for you distribution. | + | - RPM for you distribution. |
- | ===== Why do I get ioctl(SIOCGIFINDEX) failed ? ===== | + | === Why do I get ioctl(SIOCGIFINDEX) failed ? === |
If you get error messages similar to: | If you get error messages similar to: | ||
Line 209: | Line 115: | ||
* Error message: " | * Error message: " | ||
- | Then [[http:// | + | Then [[faq# |
+ | |||
+ | ===== Feedback ===== | ||
+ | * Instructions and discussion about the zd1211rw in the forum [[http:// | ||
+ |
zd1211rw.txt · Last modified: 2018/03/11 19:04 by mister_x