Quote Originally Posted by Jano. View Post
- You have solved the problem about exchange MAC address ?
well, I am not somewhere that has internet access via wireless right now, but I can tell you that I can connect fine and ping with a faked mac address, like so (using the rt2800usb driver) ::

Code:
root@bt:~# ifconfig wlan0 down
root@bt:~# macchanger -r wlan0
Current MAC: XX:XX:XX:XX:XX:XX (unknown)
Faked MAC:   2a:43:da:19:3a:9e (unknown)

root@bt:~# ifconfig wlan0 up
root@bt:~# iwconfig wlan0 mode managed essid "APname" key off ap xx:xx:xx:xx:xx:xx

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 http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/2a:43:da:19:3a:9e
Sending on   LPF/wlan0/2a:43:da:19:3a:9e
Sending on   Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
DHCPOFFER of 10.1.2.22 from 10.1.2.1
DHCPREQUEST of 10.1.2.22 on wlan0 to 255.255.255.255 port 67
DHCPACK of 10.1.2.22 from 10.1.2.1
bound to 10.1.2.22 -- renewal in 397215188 seconds.

root@bt:~# ping 10.1.2.1
PING 10.1.2.1 (10.1.2.1) 56(84) bytes of data.
64 bytes from 10.1.2.1: icmp_seq=1 ttl=64 time=20.2 ms
64 bytes from 10.1.2.1: icmp_seq=2 ttl=64 time=8.50 ms
64 bytes from 10.1.2.1: icmp_seq=3 ttl=64 time=4.92 ms
64 bytes from 10.1.2.1: icmp_seq=4 ttl=64 time=4.69 ms
64 bytes from 10.1.2.1: icmp_seq=5 ttl=64 time=19.2 ms
64 bytes from 10.1.2.1: icmp_seq=5 ttl=64 time=25.6 ms (DUP!)
64 bytes from 10.1.2.1: icmp_seq=6 ttl=64 time=5.97 ms
^C
--- 10.1.2.1 ping statistics ---
6 packets transmitted, 6 received, +1 duplicates, 0% packet loss, time 5014ms
rtt min/avg/max/mdev = 4.692/12.756/25.631/8.065 ms
I will check that out, once I get home ... and let ya know what I find out.

Quote Originally Posted by Jano. View Post
- My personal script in "/etc/udev" with "macchanger" or "hw ether" command,are no longer accepted, because the card always reset the default MAC.
hmmmm, as u see above I used macchanger, and it accepted it (using rt2800usb linux driver), and looking right now, I still have the same faked MAC (what I am getting at here = so far I still have the same faked MAC about 4-5mins after I "faked" it using macchanger)

Code:
root@bt:~# macchanger -s wlan0
Current MAC: 2a:43:da:19:3a:9e (unknown)
Quote Originally Posted by Jano. View Post
- This is not good for some situations with wep encryption and for use wpa attack with tool "Tkiptun-ng".
u talking about this driver = rt2x00 (specifically rt2800usb)? I have been successful with WEP cracking so far, and have been able to capture WPA handshake. I not so sure that I've tested with tkiptun-ng yet... I am interested in what you mean, mind elaborating?

thanks for commenting, glad to see others are interested in this adapter!

-peace-
fnord0