From: Jan Kiszka <jan.kiszka@web.de>
To: Kalle Valo <kalle.valo@iki.fi>
Cc: linux-wireless@vger.kernel.org
Subject: Re: ar9170 in AP mode
Date: Sun, 08 Nov 2009 14:47:46 +0100 [thread overview]
Message-ID: <4AF6CC02.8080204@web.de> (raw)
In-Reply-To: <878wehf85v.fsf@purkki.valot.fi>
[-- Attachment #1: Type: text/plain, Size: 1423 bytes --]
Kalle Valo wrote:
> Jan Kiszka <jan.kiszka@web.de> writes:
>
>> the ar9170 is not advertising its AP feature. However, hacking in the
>> bit allows me to run an AP on my D-Link DWA 160A with the sources of
>> yesterday's wireless-testing. Works mostly fine so far, just device
>> startup (firmware loading?) is sometimes a bit fragile, and rate control
>> seems to jump more than needed when the connection gets worse.
>>
>> There was some telling the multicast transmission would not work, but I
>> just tested it and cannot confirm this. Did something change or does a
>> specific multicast scenario still fail? Otherwise I would like to see AP
>> mode enabled in the ar9170 so that it works without modifying kernel
>> sources. Would post a patch then.
>
> Did you test with a client which had power save mode enabled? That's
> the tricky part.
Probably not, ath5k on my notebook doesn't support it. Now looking for
some station that does.
>
> IMHO AP mode should not be enabled until it's confirmed that power
> save mode works properly.
How common is the combination of powersaving and mcast in practice?
Given that quite a few useful scenarios are blocked right now (unless
you know what to patch), I would at least vote for a config option or a
module parameter. That gives a chance to warn the user about this
limitation without locking out people that are no hackers.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2009-11-08 13:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-08 13:29 ar9170 in AP mode Jan Kiszka
2009-11-08 13:38 ` Kalle Valo
2009-11-08 13:47 ` Jan Kiszka [this message]
2009-11-08 14:01 ` Johannes Berg
2009-11-08 14:40 ` Jan Kiszka
2009-11-08 14:56 ` Johannes Berg
2009-11-09 8:16 ` Holger Schurig
2009-11-09 8:37 ` Kalle Valo
2009-11-09 14:14 ` John W. Linville
2009-11-09 21:09 ` Jan Kiszka
2009-11-10 10:39 ` Johannes Berg
2009-11-09 18:52 ` Jeffrey Baker
2009-11-09 19:49 ` Luis R. Rodriguez
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=4AF6CC02.8080204@web.de \
--to=jan.kiszka@web.de \
--cc=kalle.valo@iki.fi \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.