Page 1 of 2 12 LastLast
Results 1 to 10 of 13

Thread: Review of the Alfa AWUS036H on BT3 beta

  1. #1
    Just burned his ISO
    Join Date
    Nov 2007
    Posts
    13

    Cool Review of the Alfa AWUS036H on BT3 beta

    Hello again,

    Time for yet another review of the Alfa AWUS036H USB adapter.

    This time, I'm using the stock drivers provided with BT3 beta. Here goes:

    Upon connection, the following modules were loaded:

    Code:
    r8187
    ieee80211_rtl
    ieee80211_crypt_rtl
    The interface was initialized, but not up, so I executed:

    Code:
    ifconfig wlan0 up
    Using the following command:

    Code:
    watch iwconfig wlan0
    I was able to see the card was now channel-hopping in search of an AP.

    I waited... and waited... and watched...
    The card cycled through all channels several times, and never associated. I decided to give it a little help:

    Code:
    iwconfig wlan0 essid mycoolessid
    upon providing the essid, the Alfa immediately changed to the proper channel, and associated with the AP.

    This tells me that the adapter does not auto-associate with the first good AP it finds. You must specify the AP to associate. If anyone gets different results than this, please let me know.

    I did notice that once associated, the Bit Rate was listed as 11Mb/s. This is reminiscent of the test results I received with the drivers from the aircrack-ng site in my previous Alfa post. (You can find it under the wireless forum, I still can't post links. )

    the following command:

    Code:
    iwlist wlan0 bitrate
    provides the following output:

    Code:
    wlan0     4 available bit-rates :
              1 Mb/s
              2 Mb/s
              5.5 Mb/s
              11 Mb/s
              Current Bit Rate=11 Mb/s
    I don't see 54 Mb/s listed. Time to test the throughput...

    After testing throughput, I averaged 1.5MB/s. That's not bad, and certainly better than my testing of the downloaded drivers in my first review. It's on-par with the in-kernel drivers that I tested in that same review. Looks like this set of drivers is not capped at 11Mb/s.

    Packet injection works just as well as any of my previous tests. I get an average of 500 pps.

    macchanger works like a charm:

    Code:
    macchanger -m 11:22:33:44:55:66
    Code:
    Current MAC: 00:11:22:33:44:55 (Cimsys Inc)
    Faked MAC:   11:22:33:44:55:66 (unknown)
    I noticed that I get about 50 carriage-returns after running the command. That could just be the notebook system I am using, but it happens each time. It's nothing more than a cosmetic annoyance, so no biggie.

    Manual channel specification does not work in these drivers. You will be required to specify the essid you need to connect to in order to change to the channel it is on. If you need to see it, here is the command and resulting output:

    Code:
    iwconfig wlan0 channel 1
    Code:
    Error for wireless request "Set Frequency" (8B04) :
        SET failed on device wlan0 ; Operation not supported.
    Overall, the drivers provided in BT3 work wonderfully. Only a couple of little quirks noted, but nothing that impedes their functionality.

    As usual, I'd greatly appreciate any feedback on this post. In addition, I'd love to hear about other people's experiences with this adapter under BT3.

    Thanks to the dev team for BT3, it's awesome.

  2. #2
    Developer
    Join Date
    Mar 2007
    Posts
    6,124

    Default

    Interesting. I have not had a chance to do any numbers testing but this "dummy" test with which I was discouraged. When i load up wlan0 now at my house I usually "see"5-9 Ap's when I use it in bt3 I see only one, Mine. This is just using the crappy wlassisstant however.

  3. #3
    Member
    Join Date
    Mar 2007
    Posts
    204

    Default

    the power levels of my adapter do not seem to be altered wiht this driver compared to the old one, I'm still seeing the 10 or so AP's i normally see using the v5 patch.

    I also had great success with this driver under BT3 for cracking WEP i'm gonna try connecting to a AP now see how that turns out.

  4. #4
    Just burned his ISO
    Join Date
    Apr 2007
    Posts
    16

    Default

    not being able to change the channel manually except maybe via 'airmon-ng start wlan0 channel#'' pisses me off cause lots of people use the same bssid's on different channels one could have wep and one could be open yet i fail at associating in such instances maybe its time we look at the source to see wtf

  5. #5
    Member
    Join Date
    Nov 2007
    Posts
    65

    Default

    I noticed that I get about 50 carriage-returns after running the command. That could just be the notebook system I am using, but it happens each time. It's nothing more than a cosmetic annoyance, so no biggie.
    I get this too, maybe its some bug in the drivers

    Im having the same issues that i had with BT2, everything good, injection test too, but when i try to auth and inject into my ap i get this:

    Code:
    bt ~ # aireplay-ng -1 0 -a 00:13:10:8A:DB:12 -h 00:11:22:33:44:55  wlan0
    07:02:54  Waiting for beacon frame (BSSID: 00:13:10:8A:DB:12) on channel 11
    
    07:02:54  Sending Authentication Request (Open System) [ACK]
    07:02:54  Authentication successful
    07:02:54  Sending Association Request [ACK]
    07:02:54  Association successful :-)
    And when i got aireplay -3 i have no pps flow, and of course no ARPś.

    I have locked down to the channel also, so its not that, and im close to my ap, i dont know this [ACK] thingys keep showing up, its strange and screws the injection all the time, even with injection test working 95%

    Cheers and great review, as usual from you

  6. #6
    Just burned his ISO
    Join Date
    May 2007
    Location
    West Sussex, England
    Posts
    8

    Default

    To set the channel, use the following command

    airmon-ng start wlan0 [Channel]

    Works for me.


    SRT.

  7. #7
    Junior Member
    Join Date
    Nov 2007
    Posts
    79

    Default

    On wesside I get get the auth about 3 times

    I'll edit this post in a while with an example from the console.

  8. #8
    Junior Member
    Join Date
    Mar 2008
    Posts
    94

    Default

    I found this browsing the forum, I am thinking about buying the Alfa AWUS036H....does this mean its not that good of a card such as I was told?

  9. #9
    Junior Member
    Join Date
    Aug 2007
    Posts
    54

    Default

    I think it's an awesome card. I haven't had any problems with it connecting, interface being up, or anything else. Luck of the draw I guess.
    A+, Network+, Security+, and CCNA Certified

  10. #10
    Good friend of the forums
    Join Date
    Feb 2010
    Posts
    328

    Default

    I currently cant connect to my WPA PSK
    WEP works ok w cracking

    I had to update air-ng and madwifi

    but I still can't get WPA to work I tried wpa_supplicant too and it just crapps out

    Code:
    # all manners of airmon start/stip and ifconfig up / down .. I still get this
    
    killall wpa_supplicant
    sleep 2
    wpa_passphrase rmccurdy_com SECRET > /etc/wpa_supplicant.conf
    
    wpa_supplicant -w -Dwext -iwlan0 -c/etc/wpa_supplicant.conf
    
    bt stuff # wpa_supplicant -w -Dwext -iwlan0 -c/etc/wpa_supplicant.conf
    ioctl[SIOCSIWAUTH]: Operation not supported
    WEXT auth param 7 value 0x1 - ioctl[SIOCSIWENCODEEXT]: Operation not supported
    ioctl[SIOCSIWENCODEEXT]: Operation not supported
    ioctl[SIOCSIWENCODEEXT]: Operation not supported
    ioctl[SIOCSIWENCODEEXT]: Operation not supported
    ioctl[SIOCSIWAUTH]: Operation not supported
    WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
    WEXT auth param 5 value 0x1 -

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •