rtl8187
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
rtl8187 [2008/07/14 16:00] – created darkaudax | rtl8187 [2009/07/26 20:59] – Added link to forum regarding installing compat-wireless darkaudax | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== | + | ====== |
- | The r8187 driver | + | The rtl8187 driver is a FOSS mac80211 |
- | This page only deals with the ieee80211 version of the r8187 driver. For the mac80211 rtl8187 version see the [[mac80211|mac80211 page]]. To understand the differences, | + | To use the driver |
+ | * 2.6.28: | ||
+ | * 2.6.29 and up: [[http:// | ||
+ | * wireless-testing/ | ||
- | **IMPORTANT**\\ | + | In addition, apply the latest |
- | If you have a new kernel that support mac80211 and includes | + | |
- | ====== RTL8187 ====== | + | If you have r8187/ |
- | rmmod the rtl8187 module before proceeding: | + | Just a reminder |
- | + | ||
- | ifconfig wlan0 down | + | |
- | rmmod rtl8187 | + | |
- | wget http:// | + | |
- | unzip rtl8187_linux_26.1010.zip | + | |
- | cd rtl8187_linux_26.1010.0622.2006/ | + | |
- | wget http:// | + | |
- | tar xzf drv.tar.gz | + | |
- | tar xzf stack.tar.gz | + | |
- | patch -Np1 -i rtl8187_2.6.24v3.patch | + | |
- | make | + | |
- | make install | + | |
- | + | ||
- | Now reboot your system. | + | |
- | + | ||
- | Please note that a copy of the patch is also included with the aircrack-ng tar file in the " | + | |
- | + | ||
- | + | ||
- | ====== Usage Tips ====== | + | |
- | + | ||
- | + | ||
- | ===== Power Settings ===== | + | |
- | + | ||
- | The transmit power can be adjusted using: | + | |
- | + | ||
- | | + | |
- | + | ||
- | With 0 being the lowest and 35 being the highest transmit power. | + | |
- | + | ||
- | It is important to understand that the values | + | |
- | + | ||
- | To view the current setting enter: | + | |
- | + | ||
- | | + | |
- | + | ||
- | The system responds with the current setting: | + | |
- | + | ||
- | | + | |
- | + | ||
- | Current Tx-Power=5 dBm (3 mW) | + | |
- | + | ||
- | You MUST ignore the dBm and mW labels. | + | |
- | + | ||
- | See this [[http://tinyshell.be/ | + | |
- | + | ||
- | ===== " | + | |
- | + | ||
- | +++++++++ WARNING +++++++++\\ | + | |
- | +++++++++ WARNING +++++++++\\ | + | |
- | WARNING: Enabling high power can damage or destroy your wireless device. | + | |
- | +++++++++ WARNING +++++++++\\ | + | |
- | +++++++++ WARNING +++++++++\\ | + | |
- | + | ||
- | Starting with the rtl8187_2.6.24v3.patch, | + | |
- | + | ||
- | To enable high power: | + | |
- | + | ||
- | | + | |
- | + | ||
- | To disable high power: | + | |
- | + | ||
- | | + | |
- | + | ||
- | + | ||
- | ===== Using Unpatched Driver ===== | + | |
- | + | ||
- | Although it is highly recommended that you patch the driver, it is possible to use the unpatched driver for injection. | + | |
- | + | ||
- | + | ||
- | ====== Troubleshooting Tips ====== | + | |
- | + | ||
- | + | ||
- | ===== Blacklisting mac80211 driver version ===== | + | |
- | + | ||
- | If you have the file rtl8187.ko in the / | + | |
- | + | ||
- | * Move the file to another area on your system as follows then do " | + | |
- | * Edit / | + | |
- | + | ||
- | In both cases, reboot your system afterwards. | + | |
- | + | ||
- | + | ||
- | ===== "sh wlan0up" | + | |
- | Running "sh wlan0up" | + | |
- | + | ||
- | Solution: | + | |
- | Make sure your ieee80211 stack is built as a module and remove all those modules. If it is integrated in the kernel, rebuild your kernel with a modular ieee80211 stack. | + | |
- | + | ||
- | + | ||
- | ===== wlan0 device does not exist message ===== | + | |
- | Trying to run "sh wlan0up" | + | |
- | + | ||
- | Solution: | + | |
- | You sometimes get this message when another driver, which also creates an wlanX interface is loaded before the r8187 driver. Examples: acx111, hostap and all mac80211 drivers. In such a case the rtl8187 device will be wlan1 or wlan2. Look at iwconfig to see if there is such an interface and use that one instead. | + | |
- | + | ||
- | ===== Module loading errors ===== | + | |
- | + | ||
- | The following errors were on Ubuntu: | + | |
- | insmod: error inserting ' | + | |
- | insmod: error inserting ' | + | |
- | insmod: error inserting ' | + | |
- | insmod: error inserting ' | + | |
- | insmod: error inserting ' | + | |
- | insmod: error inserting ' | + | |
- | + | ||
- | Solution: | + | |
- | cd beta-8187 | + | |
- | rm -f Modules.symvers | + | |
- | ln -s ../ | + | |
- | ### NOTE versions of GCC may require this instead: ln -s ../ | + | |
- | cd .. | + | |
- | sh makedrvbk | + | |
- | + | ||
- | ===== Eliminating Warnings ===== | + | |
- | Messages below when compiling the RTL8187 driver on Ubuntu 6.10 with 2.6.17-11 generic (patched for Nvidia) kernel. | + | |
- | + | ||
- | WARNING: " | + | |
- | WARNING: " | + | |
- | WARNING: " | + | |
- | WARNING: " | + | |
- | #many messages suppressed... | + | |
- | WARNING: " | + | |
- | WARNING: " | + | |
- | + | ||
- | Generally, warnings can be ignored. | + | |
- | + | ||
- | ===== Missing files or directory ===== | + | |
- | + | ||
- | Compiling results in an error similar to: | + | |
- | + | ||
- | make: *** / | + | |
- | #Plus other references to "No such file or directory." | + | |
- | + | ||
- | Solution: | + | |
- | See [[install_aircrack# | + | |
- | + | ||
- | ===== " | + | |
- | + | ||
- | While loading the modules you get an " | + | |
- | + | ||
- | insmod: error inserting ' | + | |
- | insmod: error inserting ' | + | |
- | insmod: error inserting ' | + | |
- | insmod: error inserting ' | + | |
- | insmod: error inserting ' | + | |
- | insmod: error inserting ' | + | |
- | wlan0: ERROR while getting interface flags: No such device | + | |
- | + | ||
- | Solution: You must be root to load the modules. You " | + | |
- | + | ||
- | ===== " | + | |
- | + | ||
- | You receive a compile error messages similar to one or more of: | + | |
- | + | ||
- | * / | + | |
- | * / | + | |
- | * " | + | |
- | * In French: " | + | |
- | + | ||
- | Solution: | + | |
- | + | ||
- | "touch / | + | |
- | + | ||
- | Change "/ | + | |
- | + | ||
- | + | ||
- | ===== " | + | |
- | + | ||
- | You get compile errors similar to: | + | |
- | + | ||
- | / | + | |
- | / | + | |
- | / | + | |
- | + | ||
- | and so on... | + | |
- | + | ||
- | / | + | |
- | / | + | |
- | / | + | |
- | + | ||
- | and so on... | + | |
- | + | ||
- | Solution: This typically occurs after you have upgraded your kernel version. Delete the all the patch files and install | + | |
- | + | ||
- | + | ||
- | + | ||
- | ===== Low injection rates ===== | + | |
- | Many people complain that they only get injection rates of about 50 packets per second. Here are few items which are known to cause this: | + | |
- | + | ||
- | * Using VMware Workstation 5.x or earlier. Be sure to use VMware Workstation 6 or above. The root cause is that older versions (< 6.0) use the old USB standard. | + | |
- | * Using VMware Players earlier then version 2. Be sure to use VMware Player 2 or above. The root cause is that older versions (< 2.0) use the old USB standard. | + | |
- | * Using pre-2.0 USB standard hardware. Make sure you are using hardware with support for USB 2.0. | + | |
- | * Having legacy USB support enabled in your BIOS. Try disabling this option. | + | |
- | + | ||
- | **Note:** VMWare Workstation < 6.0 and VMWare Player < 2.0 use USB 1.1 and when injecting at high speed, injection uses all USB bandwith (so, nearly no packets are received) and you can notice a lot of packets lost in airodump-ng. | + | |
- | + | ||
- | + | ||
- | ===== Ubuntu 7.10 Info ===== | + | |
- | + | ||
- | == Pre requirements == | + | |
- | + | ||
- | sudo -s | + | |
- | | + | |
- | | + | |
- | + | ||
- | == Delete old driverfiles == | + | |
- | You have to check the path first, maybe you must replace this " | + | |
- | + | ||
- | sudo -s | + | |
- | uname -r | + | |
- | + | ||
- | + | ||
- | And then delete the files. | + | |
- | + | ||
- | rm -rf / | + | |
- | rm -rf / | + | |
- | rm -rf / | + | |
- | rm -rf / | + | |
- | rm -rf / | + | |
- | rm -rf / | + | |
- | rm -rf / | + | |
- | + | ||
- | After this proceed with the guide at the top of this page. | + | |
- | + | ||
- | ===== Optimizing injection rates ===== | + | |
- | Some people have reported that including "-x 250" on the aireplay-ng command optimizes their injection rates. | + | |
- | + | ||
- | + | ||
- | ===== "SKB BUG" Error Messages ===== | + | |
- | + | ||
- | You receive messages similar to this to the console and system log files: | + | |
- | + | ||
- | SKB BUG: Invalid truesize (304) len=226, sizeof(sk_buff)=176 | + | |
- | + | ||
- | The root cause of these messages is not known at this point in time. They can be hidden by the following means: | + | |
- | + | ||
- | * To remove them from the console: "dmesg -2" | + | |
- | * To remove them from system log files, edit / | + | |
- | + | ||
- | + | ||
- | ====== Limitations ====== | + | |
- | + | ||
- | ===== Injected Packets are not Captured ===== | + | |
- | + | ||
- | While in monitor mode, airodump-ng will not capture or record any packets injected by the aircrack-ng suite. | + | |
- | + | ||
- | + | ||
- | ===== Shared Key Authentication fails in managed mode ===== | + | |
- | + | ||
- | You receive one or more errors similar to: | + | |
- | + | ||
- | * Attempting to setup SKA mode: " | + | |
- | + | ||
- | Error for wireless request "Set Encode" | + | |
- | SET failed on device wlan0 ; Operation not supported. | + | |
- | + | ||
- | * ieee80211_auth_challenge_rt17+0x2fe/ | + | |
- | + | ||
- | SKA is not currently supported with the RTL8187 driver. There is no known workaround. | + | |
rtl8187.txt · Last modified: 2017/01/09 21:35 by mister_x