From: Roberto Riggio <roberto.riggio@create-net.org>
To: "Björn Smedman" <bjorn.smedman@venatech.se>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Strange ACK Behaviour with ath9k
Date: Sat, 15 May 2010 11:24:31 +0200 [thread overview]
Message-ID: <4BEE684F.2070707@create-net.org> (raw)
In-Reply-To: <AANLkTimnzAJd9Y02m8OBVLHphL5pbFw56M2LfB1L5oKz@mail.gmail.com>
Hi,
at both ends of the communications I get the hwaddr from the iwconfig
command and I pass the output to my software. In fact the other host
acks the frame carrying the echo request message and generates the
corresponding echo reply whose frame is actually acked by the recipient
the point is that they keep resending the frames until the max data retries
is reached.
On 05/14/2010 01:15 AM, Björn Smedman wrote:
> Hi Roberto,
>
> When I've seen this it has been caused by a mismatch between the
> addresses in the injected frame and that configured in the hardware.
> The transmitting radio doesn't understand it is the intended recipient
> of the ack and continues retrying.
>
> /Björn
>
> On Thu, May 13, 2010 at 6:04 PM, Roberto Riggio
> <roberto.riggio@create-net.org> wrote:
>
>> Hi,
>>
>> I'm having a very strange behaviour between two sr71a (ath9k) cards
>> operating in monitor mode. I'm using the following patch to specify
>> the transmission rate frame by frame:
>>
>> http://thread.gmane.org/gmane.linux.kernel.wireless.general/47441
>>
>>
>> However if I try to send some traffic between the two nodes with both
>> interfaces operating in monitor mode I can see from a third machine
>> using wireshark that albeit the frame is sent and the corresponding
>> ack generated, the originator seems to ignore the ACK and keepts
>> retransmitting the frame. This is happening on both ends of the
>> communication (i'm ping one node from the other).
>>
>> As a matter of fact i thought that ACK are handled directly by the
>> firmware. Any hints?
>>
>> R.
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>>
>
>
>
next prev parent reply other threads:[~2010-05-15 9:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 16:04 Strange ACK Behaviour with ath9k Roberto Riggio
2010-05-13 23:15 ` Björn Smedman
2010-05-15 9:24 ` Roberto Riggio [this message]
2010-06-04 13:59 ` Roberto Riggio
2010-06-04 15:00 ` Felix Fietkau
2010-06-04 15:02 ` Roberto Riggio
2010-06-04 15:52 ` Felix Fietkau
2010-06-04 17:36 ` Roberto Riggio
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BEE684F.2070707@create-net.org \
--to=roberto.riggio@create-net.org \
--cc=bjorn.smedman@venatech.se \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).