From: Ben Greear <greearb@candelatech.com>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: jpo234 <pommnitz@yahoo.com>,
linux-wireless@vger.kernel.org, ath5k-devel@venema.h4ckr.net
Subject: Re: [PATCH] ath5k: Put hardware in PROMISC mode if there is more than 1 stations.
Date: Fri, 04 Mar 2011 07:52:59 -0800 [thread overview]
Message-ID: <4D710ADB.4060001@candelatech.com> (raw)
In-Reply-To: <20110304142814.GA3899@redhat.com>
On 03/04/2011 06:28 AM, Stanislaw Gruszka wrote:
> On Fri, Mar 04, 2011 at 06:14:37AM -0800, Ben Greear wrote:
>> On 03/04/2011 02:04 AM, jpo234 wrote:
>>> | From: Ben Greear<greearb@...>
>>> |
>>> | It seems ath5k has issues receiving broadcast packets (ARPs) when
>>> | using multiple STA interfaces associated with multiple APs.
>>> | This patch ensures the NIC is always in PROMISC mode if there
>>> | are more than 1 stations associated.
>>>
>>> Is this a band aid or a real fix?
>>
>> I don't know. It definitely makes things work, but it smells
>> like a hack. Considering ath9k works fine, it must be something
>> in the ath5k driver, but I can't see any other problems.
>
> In opposite to ath9k, there is no possibility to set multiple sta
> addresses in the ath5k hw. I'm not sure if multiple station virtual
> interfaces have sense is such case.
There is an ssid-mask, and sending directed (layer-2 ethernet frames
directly to/from the STA's MAC addresses) work fine. It's just ARP
(and probably other broadcast or multicast) that fails to work, as
far as I can tell.
Since my patch only takes affect when there are more than one virtual
station, I think it might be OK, even if it's a bit of a hack. Normal
users won't see their NIC suddenly go promisc, for instance.
Thanks,
Ben
>
> Stanislaw
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2011-03-04 15:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-03 22:39 [PATCH] ath5k: Put hardware in PROMISC mode if there is more than 1 stations greearb
2011-03-04 10:04 ` jpo234
2011-03-04 14:14 ` Ben Greear
2011-03-04 14:28 ` Stanislaw Gruszka
2011-03-04 15:52 ` Ben Greear [this message]
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=4D710ADB.4060001@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath5k-devel@venema.h4ckr.net \
--cc=linux-wireless@vger.kernel.org \
--cc=pommnitz@yahoo.com \
--cc=sgruszka@redhat.com \
/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).