Jump to content

awus036neh


Harddrive
 Share

Recommended Posts

  • 2 months later...

Hi.

I just registered to report the same problem with my two identical Ralink units. I thought that reports of this problem around the web were lacking a bit of details, so I thought about buffing up the problem description for troubleshooting sake.

I've tried the units on three different systems -- an AMD desktop, an old EEEPC and a modern Asus UX303L laptop. The first two are running a native Gentoo up-to-date system. The Asus laptop runs two VMs, a Gentoo system (with VBox additions) and a Kali Linux (live CD version, not a full installation). On all systems, airodump-ng is able to scan through all channels, but there is no access point showing up at all (the antenna is fine btw).

These systems are all running a recent kernel version (3.1x.x). Could it be a problem with recent kernels?

I have tried 6 different versions of the firmware, found here and there on the web. Here are their checkums:

$ md5sum rt2870.bin*
ac4f6d8b679945208a978e397c016aa7  rt2870.bin
2bb89af3a7d446deb4695c9a3daa7f9d  rt2870.bin.1
36c944c3138125605d28c0a3a1338be9  rt2870.bin.2
4613706159f1b75b9e6c040c19e09388  rt2870.bin.3
ac4f6d8b679945208a978e397c016aa7  rt2870.bin.4
c8ecd4dad23c594966b3a56a86ecef46  rt2870.bin.5
bd024cacbce269c4b5429583566b7385  rt2870.bin.6
$ ls -l rt2870.bin
lrwxrwxrwx 1 root root 12 Dec 22 17:15 rt2870.bin -> rt2870.bin.4

The lsusb output of my two Alfa AWUS036NEH devices is:

Bus 001 Device 006: ID 148f:3070 Ralink Technology, Corp. RT2870/RT3070 Wireless Adapter

A rather unusual symptom is that starting the monitor mode takes several seconds, which is quite longer than other typical devices. I experience the same delay when setting the interface up/down with ifconfig.

$ time sudo ifconfig wlp0s6u2 down

real    0m2.314s
user    0m0.000s
sys     0m0.030s
$ time sudo ifconfig wlp0s6u2 up

real    0m11.363s
user    0m0.000s
sys     0m0.240s

NetworkManager is not running on any of the Gentoo systems, and I stopped it on Kali before using airmon-ng.

As a final word, I am frankly quite suprised why this device is considered one of the best supported adapter on Linux, given that many other people are not even able to see access points with it. I for one would really like to understand how to fix this particular issue. Please, someone. ;)

Link to comment
Share on other sites

For reference purposes, here is another topic on aircrack-ng.org that describes the exact same problem and also with no solution to it: http://forum.aircrack-ng.org/index.php?topic=308.0 (according to the board page, the topic has over 12k views and is locked, so no one can contribute anymore to it).

NB: Not sure how to edit my previous post. Had to double post.

Link to comment
Share on other sites

Since you're running Gentoo I'm assuming you know your way around compiling a kernel. Did you try "make firmware" as part of the building process?

Does anything show up in the logs when you try to use the adapter, particularly when you run into that massive delay?

Does your kernel have support for this adaptor built-in or as a module? In case of a module, was the module already loaded before you attached the adapter, or did you allow that to happing automagically/do so manually after insertion?

To edit your post, notice the "MultiQuote" and "Quote" buttons to the lower-left corner of your post? To the left of them there's a faint grey text with the remaining options, specifically "report", "edit" and "delete". It's not particularly obvious, but they're there.

Link to comment
Share on other sites

According to this post by m3t4tr0n (which I'm quite confident is the 'metatron' user that used to be active on this forum in a distant past) you might need a small patch.

All I can say is that the 'metatron' on this forum is a very knowledgeable chap with a particular knack for wifi-related things. If he says something works, that something works.

Link to comment
Share on other sites

  • 3 weeks later...

Hi Cooper and a happy new year. Thanks for replying so fast - didn't expect that, so I haven't given much attention to the problem lately.


Since you're running Gentoo I'm assuming you know your way around compiling a kernel. Did you try "make firmware" as part of the building process?

Does anything show up in the logs when you try to use the adapter, particularly when you run into that massive delay?

Does your kernel have support for this adaptor built-in or as a module? In case of a module, was the module already loaded before you attached the adapter, or did you allow that to happing automagically/do so manually after insertion?

To edit your post, notice the "MultiQuote" and "Quote" buttons to the lower-left corner of your post? To the left of them there's a faint grey text with the remaining options, specifically "report", "edit" and "delete". It's not particularly obvious, but they're there.

Yes I've compiled the kernel countless times in the past on various Linux systems, but I usually just use `genkernel` nowadays. I'll give it a try at a manual compilation with `make firmware`, which I've never had the opportunity to try before.

The log is verbose, but nothing out of the ordinary AFAICT. I could post a complete log generated by the insertion of the device plus other related up/down operations.

I've build the module. I've tried pretty much all combination of inserting it before/after loading the module, with different timings, etc. I've literally spent a couple dozens of hours on the issue in the last months. (Although I've never tried building support in the kernel directly, so might try that.)

(As for the edit button, maybe there's something special with my account, but I can't see it; only the Report link.)


According to this post by m3t4tr0n (which I'm quite confident is the 'metatron' user that used to be active on this forum in a distant past) you might need a small patch.

All I can say is that the 'metatron' on this forum is a very knowledgeable chap with a particular knack for wifi-related things. If he says something works, that something works.

It's interesting, but I'll politely discard any solution that is that old; downgrading the kernel and applying manual patches sound a very good way to call for more problems.

What I find very disappointing is how Hak5 advertises the adapter to be working out of the box, while numerous users find themselves forced to manually patch an incredibly outdated kernel to make it work, sometimes, after days/weeks of troubleshooting. I've mailed them, but have received no clear explanation so far. They've been kind enough to provide me with a second unit to test with though, and that's very appreciated.

Thanks again for the info and I'll try to provide the above info soon enough.

Link to comment
Share on other sites

As for the edit button, maybe there's something special with my account, but I can't see it; only the Report link.

I've since learned from another user here who ran into this problem that the 'edit' option only appears once you reach 6 posts.

It's interesting, but I'll politely discard any solution that is that old; downgrading the kernel and applying manual patches sound a very good way to call for more problems.

Yeah, I looked at the posting and the associated patch. This was from 2010 so any patch floating around back then should've been integrated in an actual release by now.

What I find very disappointing is how Hak5 advertises the adapter to be working out of the box, while numerous users find themselves forced to manually patch an incredibly outdated kernel to make it work, sometimes, after days/weeks of troubleshooting.

That's a bit harsh. You're the first user on this forum that I recall who's having such troubles with the adapter. It was my suggestion for you to look at that thread for a solution, not realizing it was ancient and yes, you shouldn't need to run such an old kernel just so you can make a device work. You're not being 'forced' to use it as I'm sure there are other/better ways than that to get the thing going. Finally, I don't work for nor am I otherwise associated with Hak5. I'm just a bloke on their forum that likes to help people solve their problems. Sometimes that works better than other times but to see my responses on this forum as a formal response from the Hak5 crew is a big misrepresentation.

Link to comment
Share on other sites

@Harddrive

Shows usb is installed but when I try to find an ap. It show none. I'm running kali linux via VM.

I see others are having the same problem as well. The description on the shophak site it shows that it should work out of box. But it's not for me. What am i doing wrong?

- Just for giggles, what are the commands you are using to "bring up" the interface of the USB card in question. Aside from posts by some of the others on what to try, is that specifically the case the op is having issues with, or is there something else we're missing, since the Op who posted the question has yet to reply to this thread at all with any feedback on what they actually tried in getting it to work. Not saying the other posts aren't valid for their specific issues, but is that what @Harddrive is having issues with specifically?

"I'm running kali linux via VM"

Have you passed the USB device to the VM, can it be seen by the VM, is the interface up, etc. I think cooper was trying to establish getting more info from the op on what to see is going on and without knowing what and how their VM is setup, and the op actually replying, what more can we do with a post from September he has yet to reply to?

Edited by digip
Link to comment
Share on other sites

I've also brought an NEH issue to light on the forums. https://forums.hak5.org/index.php?/topic/34338-awus036neh-big-driver-issues/#entry255220

Seb has noted my issue and findings, and may make an attempt to update the driver. As I see that the bin for the driver is outdated a few versions behind aswel, and also I linked to some possible hints on solid fixes.

I havent personaly dug into fixing the problem myself, but this post and mine all seems to be breadcrumbs leading to something solid

Granted completely different issues on different systems, still shows how problem riddled the drivers are and can be.

But for me, on a kali setup the card works fine. But the pineapple mkv has some wonky driver issues for the neh.

Edited by DataHead
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...