You should provide more info. (output maby???)
The procedure looks fine - more info more answers.
RTL8187 / managed mode
Hi,
I have a problem with the managed mode of my alfa card.
I can inject and crack any wep but i can't connect to any network, it doesn't make any link.
i did (as usually under bt3) that under bt4:
ifconfig wlan0 down
iwconfig wlan0 mode managed
ifconfig wlan0 up
iwconfig wlan0 ap bssid
iwconfig wlan0 key hexakey
dhclient wlan0
i tested many networks with the right keys but i can't connect to it
i just found that it works when i precise channel & essid, i don't understand because it works well under bt3 and the signal is 50%+...
root@bt:~# dhclient wlan0
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit
mon2: unknown hardware address type 803
mon1: unknown hardware address type 803
wmaster2: unknown hardware address type 801
wifi0: unknown hardware address type 801
wmaster1: unknown hardware address type 801
wmaster0: unknown hardware address type 801
mon0: unknown hardware address type 803
mon2: unknown hardware address type 803
mon1: unknown hardware address type 803
wmaster2: unknown hardware address type 801
wifi0: unknown hardware address type 801
wmaster1: unknown hardware address type 801
wmaster0: unknown hardware address type 801
mon0: unknown hardware address type 803
Listening on LPF/wlan0/5a:fb:bb:91:85:f6
Sending on LPF/wlan0/5a:fb:bb:91:85:f6
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
root@bt:~# iwconfig wlan0 essid essid_name
root@bt:~# iwconfig wlan0 channel 2
root@bt:~# dhclient wlan0
There is already a pid file /var/run/dhclient.pid with pid 5890
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit
mon2: unknown hardware address type 803
mon1: unknown hardware address type 803
wmaster2: unknown hardware address type 801
wifi0: unknown hardware address type 801
wmaster1: unknown hardware address type 801
wmaster0: unknown hardware address type 801
mon0: unknown hardware address type 803
mon2: unknown hardware address type 803
mon1: unknown hardware address type 803
wmaster2: unknown hardware address type 801
wifi0: unknown hardware address type 801
wmaster1: unknown hardware address type 801
wmaster0: unknown hardware address type 801
mon0: unknown hardware address type 803
Listening on LPF/wlan0/5a:fb:bb:91:85:f6
Sending on LPF/wlan0/5a:fb:bb:91:85:f6
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
DHCPOFFER of *.*.*.* from *.*.*.254
DHCPREQUEST of *.*.*.* on wlan0 to 255.255.255.255 port 67
DHCPREQUEST of *.*.*.* on wlan0 to 255.255.255.255 port 67
DHCPACK of *.*.*.* from *.*.*.254
bound to *.*.*.* -- renewal in 269341 seconds.
root@bt:~#
the connection is less stable that under backtrack 3 and sometimes it refuses to reconnect to the network
Under standard Ubuntu 8.10 and BT4b I have had trouble with the mac80211 drivers for the rtl8187. The signal strength and quality are crap compared to the old ieee80211 drivers. See the pics here for a comparison of the two drivers with airodump-ng. I can replicate these results every time with different computers and different ALFA's. I have just blacklisted the rtl8187 mac80211 driver under BT4b and installed the old ieee80211 driver. Guess what, BT4b and the ALFA work spot on again.
http://forums.remote-exploit.org/sho...t=20133&page=2
this has been a previous topic of discussion on ubuntu forums.
aircrack-ng.org/doku.php?id=r8187#general
Thank you i will try thatOriginally Posted by timstewart
I already tried under debian with the aircrack-ng driver installation tutorial but it didn't worked very well (very bad injection ~2 packets injected every 30s), i will retry that under bt4...
like i said, this driver in this tutorial didn't work well under my debian but i will try under bt4
Here's what I did to change to the old drivers:
blacklist the rtl8187 driver:
add 'blacklist rtl8187' at the bottom and save (without the quotes)Code:# nano /etc/modprobe.d/blacklist
then more or less follow (as root) the instructions on the aircrack-ng website:
(unload and mac80211 and rtl8187 modules that are loaded with rmmod first)
thenCode:# wget http://dl.aircrack-ng.org/drivers/rtl8187_linux_26.1010.zip # unzip rtl8187_linux_26.1010.zip # cd rtl8187_linux_26.1010.0622.2006/ # wget http://patches.aircrack-ng.org/rtl8187_2.6.27.patch # tar xzf drv.tar.gz # tar xzf stack.tar.gz
go down to lines 46 and 47 and change 'asm' to 'linux' on both linesCode:# nano beta-8187/r8187.h
then to finish
Code:# patch -Np1 -i rtl8187_2.6.27.patch # make # make install
thank you for your help, will try that
timstewart
I have done exactly like you said and wlan0 doesn't go up.. nothing in iwconfig and ifconfig (ifconfig wlan0 up (no such device)).
And if i doi receve this:Code:./wlan0up
I have a rtl8187b. Any ideas?Code:insmod: can't read "ieee80211_crypt-rtl.ko" : No such file or directory insmod: can't read "ieee80211_crypt_wep-rtl.ko" : No such file or directory insmod: can't read "ieee80211_crypt_tkip-rtl.ko" : No such file or directory insmod: can't read "ieee80211_crypt_ccmp-rtl.ko" : No such file or directory insmod: can't read "ieee80211-rtl.ko" : No such file or directory insmod: can't read "r8187.ko" : No such file or directory wlan0: ERROR while getting interface flags: No such device
Posting Permissions