Send users mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        
http://rt2x00.serialmonkey.com/mailman/listinfo/users_rt2x00.serialmonkey.com

or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of users digest..."


Today's Topics:

   1. Response to packet checksum errors with rt2800usb drivers
      (Erick Couts II)


----------------------------------------------------------------------

Message: 1
Date: Sat, 11 Aug 2012 05:50:22 -0500
From: Erick Couts II <[email protected]>
To: [email protected]
Subject: [rt2x00-users] Response to packet checksum errors with
        rt2800usb       drivers
Message-ID:
        <cad3sqsmt4vhgtez5j0nc6xr9mbqzb82njmzsm-kb1uuiowl...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

In response to:

You've gotta be more specific about what is failing and how you are
detecting these
failures, otherwise it is very difficult for us to analyze the problem.

Also, the rt2x00 drivers doesn't really have a version, and version
0.29 is certainly
not associated with the rt2x00 driver. Do you by chance mean the
firmware version?

---
Gertjan

-------------------------------------------------------------------------------------------------

Okay, injection fails via anything.  The 0.29 was the version reported by
airmon-zc.  It has been verified not working on two systems and that other
cards worked with injection perfectly.  It does actively receive data
though, but I'm concerned about how it seems to improperly handle packet
checksums as indicated by wash via the reaver-wps suite.
I will also be testing this with the newest 3.5.1 kernel later to verify
that even the normal kernel fails injection and checksums with it.
The device that the rt2800usb drivers are being used for is a Rokland N3.
 It will receive, but it just won't inject; even when the AP is only a few
feet away.

My ath5k works flawlessly with all of the software I'm using and the device
works inside of WIndows, so it leaves only the driver/firmware to be the
issue.  In normal operation, I've also found that the device fails to
connect to APs.  It's as though it can see everything coming in, but it
just won't send anything out.

Thanks,
Erick
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://rt2x00.serialmonkey.com/pipermail/users_rt2x00.serialmonkey.com/attachments/20120811/572b8e06/attachment-0001.html>

------------------------------

_______________________________________________
users mailing list
[email protected]
http://rt2x00.serialmonkey.com/mailman/listinfo/users_rt2x00.serialmonkey.com


End of users Digest, Vol 42, Issue 10
*************************************

Reply via email to